zlacker

[flagged]

>>Arthur+(OP)
Oh, just like every other business then! That's a nice strategic differentiator.

Look, I'm sure focusing on inputs instead of outcomes (not even outputs) will work out great for you. Good luck!

>>nnnnna+55
Weve done this since 1995 and it works perfectly well.

>>Arthur+(OP)
IMO this is completely "based". Delivering customer values and making money off of it is own thing, and software companies collectively being a social club and an place for R&D is another - technically a complete tangent to it. It doesn't always matter how sausages came to be on the served plate. It might be the Costco special that CEO got last week and dumped into the pot. It's none of your business to make sure that doesn't happen. The customer knows. It's consensual. Well maybe not. But none of your business. Literally.

The field of software engineering might be doomed if everyone worked like this user and replaced programmers with machines, or not, but those are sort of above his paygrade. AI destroying the symbiotic relationship between IT companies and its internal social clubs is a societal issue, more macro-scale issues than internal regulation mechanisms of free market economies are expected to solve.

I guess my point is, I don't know this guy or his company is real or not, but it passes my BS detector and I know for the fact that a real medium sized company CEOs are like this. This is technically what everyone should aspire to be. If you think that's morally wrong and completely utterly wrong, congratulations for your first job.

>>numpad+m01
Turning this into a moral discussion is besides the point, a point that both of you missed in your efforts to be based, although the moral discussion is also interesting—but I'll leave that be for now. It appears as if I stepped on ArthurStack's toes, but I'll give you the benefit of the doubt and reply.

My point actually has everything to do with making money. Making money is not a viable differentiator in and of itself. You need to put in work on your desired outcomes (or get lucky, or both) and the money might follow. My problem is that directives such as "software developers need to use tool x" is an _input_ with, at best, a questionable causal relationship to outcome y.

It's not about "social clubs for software developers", but about clueless execs. Now, it's quite possible that he's put in that work and that the outcomes are attributable to that specific input, but judging by his replies here I wouldn't wager on it. Also, as others have said, if that's the case, replicating their business model just got a whole lot easier.

> This is technically what everyone should aspire to be

No, there are other values besides maximizing utility.

>>Arthur+(OP)
What if I told you that a dev group with a sensibly-limited social-club flavor is where I arguably did my best and also had my happiest memories from? In the midst of SOME of the "socializing" (which, by the way, almost always STILL sticks to technical topics, even if they are merely adjacent to the task at hand) are brilliant ideas often born which sometimes end up contributing directly to bottom lines. Would you like evidence of social work cohesion leading to more productivity and happier employees? Because I can produce that. (I'd argue that remote work has negatively impacted this.)

But yes, I also once worked at a company (Factset) where the CTO had to put a stop to something that got out of hand- A very popular game at the time basically took over the mindshare of most of the devs for a time, and he caught them whiteboarding game strategies during work hours. (It was Starcraft 1 or 2, I forget. But both date me at this point.) So he put out a stern memo. Which did halt it. And yeah, he was right to do that.

Just do me this favor- If a dev comes to you with a wild idea that you think is too risky to spend a normal workday on, tell them they can use their weekend time to try it out. And if it ends up working, give them the equivalent days off (and maybe an extra, because it sucks to burn a weekend on work stuff, even if you care about the product or service). That way, the bet is hedged on both sides. And then maybe clap them on the back. And consider a little raise next review round. (If it doesn't work out, no extra days off, no harm no foul.)

I think your attitude is in line with your position (and likely your success). I get it. Slightly more warmth wouldn't hurt, though.

>>nnnnna+oo1
> My problem is that directives such as "software developers need to use tool x" is an _input_ with, at best, a questionable causal relationship to outcome y.

Total drivel. It is beyond question that the use of the tools increases the capabilities and output of every single developer in the company in whatever task they are working on, once they understand how to use them. That is why there is the directive.

>>nnnnna+oo1
No, I think you're mistaking the host for the parasite - he's running a software and solutions company, which means, in a reductive sense, he is making money/scamming cash out of customers through means of software. The software is ultimately smoke and mirrors that can be anything so long it justify customer payments. Oh boy those software be additive to the world.

Everything between landing a contract and transferring deliverables, for someone like him, is already questionably related to revenues. There's everything in software engineering to tie developer paychecks to values created, and it's still as reliable as medical advice from LLM at best. Adding LLMs into it probably won't look so risky to him.

> No, there are other values besides maximizing utility.

True, but again, above his paygrade as a player in a free market capitalist economy which is mere part of a modern society, albeit not a tiny part.

----

OT and might be weird to say: I think a lot of businesses would appreciate vibe-coding going forward, relative to a team of competent engineers, solely because LLMs are more consistent(ly bad). Code quality doesn't matter but consistency do; McDonald's basically dominates Hamburger market with the worst burger ever that is also by far the most consistent. Nobody loves it, but it's what sells.

>>pmarre+oA1
> What if I told you that a dev group with a sensibly-limited social-club flavor is where I arguably did my best and also had my happiest memories from?

Maybe you did, and as a developer I am sure it is more fun, easier, and enjoyable to work in those places. That isnt what we offer though. We offer something very simple. The opportunity for a developer to come in, work hard, probably not enjoy themselves, produce what we ask, to the standard we ask, and in return they get paid.

>>Arthur+aT1
This sounds like an awful place to work lol

>>Arthur+(OP)
This subthread turned into a flamewar and you helped to set it off here. We need commenters to read and follow the guidelines in order to avoid this. These guidelines are especially relevant:

Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.

Please don't fulminate. Please don't sneer, including at the rest of the community.

Eschew flamebait

https://news.ycombinator.com/newsguidelines.html