You have probably heard the slogan "Premature Optimization is the Root of All Evil ! " - but over many years of working with performance optimization I have come to believe this is misleading! #shorts #short
In my experience, most softwares are first designed with a "get it to work mentality". When the software is being used well, there's a realization to optimize them.
Hello Jacob, what do you think about Spring Framework? Why its so popular? I'd like to hear your opinion about it... especially in terms of optimization and performance haha..
It makes prototyping and development fast. There are tons of information and examples around. While it may not be the most slim framework, most dev companies will prefer to pay more for the equipment but less for the development time.
It better be a shot of something healthy ;-) Even when I was making the video - it was a lot of "lock the lock - unlock the lock - if the lock is locked - unlock it ... " for me too :-D
If you know upfront your non-functional requirements it makes sense to do the architectural decision that will build a base for performance. On the other hand, if your project has not even taken shape - it might be too early.
Of course you need to know _what_ your system should do before you can analyze how you could optimize it. But once you do - you can make many important performance decisions early on in the process.
