The Grug Brained Developer

Post by necovek » Sun, Jun 26, 2022, 3:25 AM UTC

karategeek6 wrote: post #387

necovek wrote: post #313

Earlier quoted context omitted.

As mostly an engineer (though I've spent time as a tech/team lead and engineering manager in the past), I think you've missed the point. Most of the things will not need to be "scaled" at all. Ever. As an engineer, I mostly struggle to come up with a simple solution while accommodating all the crappy, leaky abstractions in the rest of the code: that's the hard part of the job. And 20 years in, I still wonder why peop…

> I still wonder why people think it's smarter to introduce seventeen layers of abstractions for things that have one or at most two implementations Tell me you are a Java dev without telling me you are a Java dev. :) (While I know it's not just Java with this problem, my personal experience is that Java is the worst.)

Post by NateEag » Tue, Jun 28, 2022, 3:52 AM UTC

mecha_ghidorah wrote: post #392

NateEag wrote: post #379

Earlier quoted context omitted.

Not even just "look like a prototype" - a prototype must be _incomplete_. If it's not? You have a solution, so of course it's going to be deployed. The fact that your solution is gonna fall over due to being brittle code is really unfortunate, but it was avoidable if you'd just built a prototype instead of a product.

I mean that's easier said than done in some cases. If your manager wants you to build a complete version of the functionality, just one that is very "quick and dirty" there isn't a whole lot you can do to make it not fully functional short of flat out refusing