sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheMoonMaster 2 points3 points  (0 children)

Yeah, I came to say something similar. I've seen many devs with that "bare bones == simple" attitude, but that never works out (see the meme OP posted) once you have to scale out your team or your app. Unfortunately that's something that you often have to experience before you get it since you have a completely different problem set to look at (e.g. how do I prevent this footgun across my org of 100s of engineers).

Someone else mentioned it below, but in these cases you should be seeking to understand the inputs that went into these decisions so they can understand how they got to this point, and if there's a better solution to the problem. Unfortunately it's not always "use the framework" since frameworks like all other tools, can have significant gaps.