4 ms·
The disease has a name: over engineering. https://www.smart-jokes.org/programmer-evolution.html https://www.smart-jokes.org/programmer-evolution.html Most wor
by api 4y ago
The disease has a name: over engineering.
https://www.smart-jokes.org/programmer-evolution.html https://www.smart-jokes.org/programmer-evolution.html
Most working programmers are in the middle near “seasoned professional.” They spend all their time thinking about how to manage complexity when they should be thinking about how to avoid it.
- AndrewKemendo 4y agoOh my I hadn't seen this before and it is divine!
- pas 4y agoThe app epidemic is mostly thanks to one single dead dude. Of course it made (and continues to make) billions to Apple. Then naturally half the industry wanted in on the app store game. Eventually it might stop being such a cash cow - maybe thanks to endless numbers of teenagers hyping Fortnite.
- layer8 4y agoTo be fair, the tech stacks they have to work with often have staggering amounts of accidental complexity.
- api 4y agoIt’s seasoned professionals all the way down.
- omnibrain 4y agoOnly yesterday I encountered a fantastic example. I have to implement an API, there is a swagger/openAPI doc for it, but still, the real interaction and meaning of the calls can be a bit hard to grasp. But the developers provide an example application (in C#). I expected something basic that implements the login flow and some of the more important calls. Instead I found something that could be described as an C# architecture example application. If I wanted to learn C#, I think I could learn a lot about application patterns from it. MVVM, how to separate the concerns into separate "packages" for reusability and the likes. What I can't really learn from it (without already being a C# pro, I work in other environments) is how to use the API.