AwkwardLookMonkeyPuppet

deleted by creator

Yes I agree. It would indeed be better if I possessed superhuman abilities.

A development philosophy that nobody understands, or actually follows, but every company insists on using, even when it’s a poor fit for their projects.

They all do things in their own way and argue over what is best, and often fail to see the bigger picture.

It sounds like your programming team is missing a senior engineer/director of engineering. You need an engineer who has the experience to see the big picture, architect solutions, and tell the team what’s what.

PM: “Hey, I know you said it’ll be done in a week, and you need me to stay out of your way so you can focus, but it’s been 7 hours and I was wondering if you have an update for me. Can you create a report that outlines what you’ve done, what is remaining, and precisely when each step will be finished so that I can pester you about each step throughout the development process, interrupting your productivity? It makes me feel like I’m contributing.”

I was self-employed for around 7 years and finally came to the conclusion that I’m just not a very good businessman. When you’re self employed, you’re running the business more than coding, or doing the things that you’re actually passionate about, and I didn’t enjoy it. Not to mention that sometimes I’d work 15-17 hours per day, 7 days per week, for weeks on end, just to be pretty poor. Plus health insurance is a fucking nightmare without some massive corporation subsidizing it. Maybe that part is better now with the ACA and insurance market website, but idk, because I finally gave up and got a job right around the time that the ACA kicked in. Idk, part of me thinks that I could hire a business manager to do the business parts, and I could just architect solutions, but the more realistic part of me thinks they’d probably steal all of my profits while I was trying to solve coding problems.

I’m sure some day someone will build a complete system with a change request log and all that, but it’s not there yet, and I hope it doesn’t get here before I’m retired, or me and my family might be in big trouble.

Thanks.

Oof! Where are the Black Hats when you need them?

What does it say? Clicking that link just takes me to a login screen.

Mmm, cake…

Damn, sounds like a a good time to start a consulting firm. I wish I was a decent businessman, I’d love to own my own consulting company.

His disdain for actual human beings is disgusting. “Time to pack their bags”. Fuck you, buddy!

Edit: I just looked at the second screenshot. Of course he’s a real estate developer.

Ideas are a dime a dozen.

Then a handful of years later they forget it all and repeat…

They don’t forget, they never learned in the first place. In their minds the original engineers messed up, and that’s why there was a vulnerability, or a missing feature. “We need a quick and cheap vendor to fix the mistakes of our awful engineering team that we laid off a year ago”.

“Does anyone want to come clean up my mess? As a gig fee of course though, I don’t need employees. I keep all the money. It’s mine! All mine!”

Plus there’s the problem of a limited context window. Real software projects are spread across dozens, hundreds, or even thousands of files. Then they are deployed, sometimes compiled, run on a variety of devices and clients, and need to meet a couple dozen criteria to be acceptable, even more to be great. The AI can’t track all of that and your request too, its context window is far too small. It can barely track a single file and your request, plus request changes. Tracking all of this from day-to-day, over months and years is just one part of an engineer’s job, and it’s going to be a long time before an AI can do that one small part of the job. Ask an AI why some part of the project was changed 12 months ago. Just try it. It’ll evaluate the code, try to reason, and make something up. Ask a person and they’ll remember the exact reason why, both in the context of the requested change and the coding project limitations.

That’s cool that you take input from new-hires and consider the viewpoints they bring to the team. It’s always annoying to be excited about a new job, and then be told “this is the way we do it, and that’s final”.

That’s some holy and righteous work you accomplished. All future developers on that effort owe you a debt!

Ha! Thanks! They were using it because that’s what Adobe recommends, and I made a very strong and opinionated case as to why Adobe needs to pull their heads out of their asses. Haha. Unexpectedly, everyone agreed with me.

You actually wrote

I’ve been doing it for 2 decades, still don’t get it. So maybe you can enlighten me what IT has to do with naming stuff in code?

You capitalized “it”, so I thought you meant IT, as in Information Technology, as in device management and shit.

Anyways, idk if I can offer any insight that you haven’t read already. But naming conventions are a small detail that people get really passionate about. Additionally, when people don’t follow the agreed upon naming convention for the project, then the pull request ends up turning into a big argument about renaming shit, rather than an actual code review. This will sometimes spark an even bigger conversation in slack, which can turn into a meeting, and waste a lot of time.

Its usually junior engineers that don’t follow it, because they’re using all of their mental faculties to solve the problems, and then senior engineers see the deviation from convention and call it out. If you don’t have a team style guide, then that call-out can turn into a big ol argument between the senior engineers about different philosophies. It’s annoying, but it’s less annoying than working in a project with no agreed-upon naming convention.

Well that makes more sense, but it is still a lot of churn. I guess it’s fine in a project where you can change it all in a couple days. We have tens of thousands of files in the project I’m in charge of, so we’d never consider such an extensive refactor. We discuss naming conventions whenever we start a new project, and then it’s locked in. Thankfully we’re all pretty much of like-mind. Nothing changes from project to project in the naming realm. I did do away with BEM when I started, because I despise that clusterfuck of a convention for more reasons than I care to explain here, but I waited until a new project to do it, and everyone agreed with me.