"It creates a lot of work and no results. We actually call that 'modern software engineering.'" π
That is the best description for UML Diagrams ever. Our teachers believed that,it is how softwares are developed. I have never used it in my 6 years of work experience.
As a guy with a masters in software engineering I have to say that I have never felt more attacked
CS Major here and we learned that stuff in Databases and Software Engineering Can't imagine 3 years of that
That's the sweetest person you are talking to "oooh :)"
and then we got bad reactions from our lecturer when these squares didn't have round edges and the arrow heads aren't filled properly
you forgot to say "I worked at Netflix btw"
Been there, draw that stuff. But this conversation is just pure gold. βWhat would that create?β - JUST POINT ON π
"It creates lots of work and little solutions, we call it modern software engineering", that is truly brilliant! It should be written in golden letters!
The fact that he just mentioned undergrad level stuff is the cherry on top
Software engineering rizz π£οΈπ£οΈπ£οΈ
Bro looks like he was built by the Tyrell corporation.
I did more programming during my master than my bachelor. I did those diagram things during my bachelor. Stil a waste of time compared to having worked those two years. Especially since I don't work with what I specialized in.
good diagrams can enormously help understanding the bigger picture, if they are seen as sketches. They are good to identify boundaries and unwanted dependencies, but they are not a religion. It just depends, sometimes the problem is simple so that one can immediately start coding, the other time better draw a high-level sketch first.
Computer science master's student here, and he's not exaggerating. Like, at all. If you want to learn anything useful while you're in school, you really need to have personal projects!
I can't believe how powerful that moustache is
I did UMLs, data relationship diagrams etc etc... One thing I found out within a month of developing software... I never used them after their initial completion... They never got updated, they often missed 10 different things that were actually required whilst developing the software. They are useless... They are good if you know exactly how to build a system, perfectly from the get go, otherwise they often get forgotten about... And 99% of the time you'd just get a screenshot of the current active database from it's control panel anyway if you needed a quick look...
When he said β1 β> manyβ I cried π’πππ
I think this mindset in the engineering/programming side of things is why things work at all in the first place. The extremely self critical mindset I see across the board and constant need to create optimizations and improvements is the fuel of technological improvement. Being a novice who is just into this topic as a hobby its incredible to see this mindset coming from the guys building basically everything digital considering how much we rely on it now days.
@ThePrimeagen