Much of complexity in software is a result of people trying to solve a hypothetical problem they think they'll have. My experience is that it's always best to write the simplest code that adequately solves the problem you actually have.
Conversation
Notices
-
☆ Dmitri ☭ (yogthos@mastodon.social)'s status on Wednesday, 04-May-2022 19:39:33 UTC ☆ Dmitri ☭ -
☆ Dmitri ☭ (yogthos@mastodon.social)'s status on Wednesday, 04-May-2022 19:39:31 UTC ☆ Dmitri ☭ @groovestomp haha yeah I find a lot of senior engineers like to build Rube Goldberg machines. My pet theory is that it's just a way for people to keep things interesting when solving boring problems. :)
Santa Claes 🇸🇪🇭🇰🎅 likes this. -
GrooveStomp (groovestomp@social.linux.pizza)'s status on Wednesday, 04-May-2022 19:39:32 UTC GrooveStomp @yogthos
Them: This system is too complicated!(ie., They didn't write it and don't want to be bothered to learn it.)
Them: Introduce 3 external services as hard dependencies with runtime dependency injection. Nothing is documented and it is not obvious where to make changes.
Them: There! Simpler!
-
GrooveStomp (groovestomp@social.linux.pizza)'s status on Wednesday, 04-May-2022 19:39:33 UTC GrooveStomp @yogthos Do you have like 1000 years of experience or something? 😆
I know developers with >10 years experience more than me who still write software for theoretical problems and make everybody's lives worse as a result.
-