5 ms·
Sounds like most of us you like developing but dont like working in other people's code and design. Corporate work has a bad reputation but lots of upsides. I
by rr888 4y ago
Sounds like most of us you like developing but dont like working in other people's code and design.
Corporate work has a bad reputation but lots of upsides. I work in a small team of 5 people on a system that has about 40 users. Its amazingly better when you can talk to everyone, know what all the users want, dont have to worry about constant uptime or scalability. Flexibility and budget to pay for good platforms. Just dont talk about the refactoring - rewrite from scratch!
Reply: Yes it is expensive, the users are all paid more than us though which means we're helping them be productive. I have to add we also own a second application that has about 100 users that we spend some time on maintenance and support.
- osigurdson 4y ago>> 5 people on a system that has about 40 users Gosh, that is expensive software!
- onion2k 4y agoYou can't tell that from the data provided.
- worldsayshi 4y agoI mean you're right but also; what does a manager do if not producing "software" to a small group of individuals. Or a designer for that matter. Anyone who produces direct output to a small group of people is expensive in a similar way.
- btown 4y agoOr a really really value-add internal tool!
- ghettoCoder 4y agoThat's weird way to look at it. It's about value, not cost. For all we know that 40 user system manages the entire logistics of a national shipping company and saves them 50x the ops cost. Still think its expensive? Or maybe it's a corporate risk register with significant potential regulatory and reputational harm attached to each risk. Still costly?
- osigurdson 4y agoI didn’t intend to suggest that the software does not have a positive ROI. Some applications (control systems, etc.) have no users the traditional sense.
- rco8786 4y agoSeriously. It’s hard to imagine a group of 40 people that would need a sufficient velocity of changes/new features to warrant 5 full time engineers.
- xmaayy 4y agoMassive corporate HR Dept with custom rolled software. Bank team with software for compliance. Endless possibilities...
- shmatt 4y agoFrom my experience, this is pretty common in AI Internal tools used by a dozen or a couple dozen AI engineers/Data Scientists, the models they output used by millions. It's totally worth keeping 5-10 person engineering team to create better and stronger tools that make upgrading and deploying new models easier and faster
- time_to_smile 4y ago> totally worth keeping 5-10 person engineering team I've worked in AI/ML for a long time, and I can tell you that in all but the rarest of exceptions nobody has sat down and done the math to really determine if that value is there. In my experience, most cases it's not. I've seen teams like you describe and then asked them "what's the difference in value between what our model does today and the theoretical optimum"? The answer, which nobody liked, was fractions of a penny per user. That means if the team achieved perfection it wouldn't really matter in practice. We're going to see a lot of the AI/ML teams disappear as companies are forced to focus on determining the real value add being provided.
- cloverich 4y agoImagine each of those people is an employee at the same company, and they each command a salary of say 100k. How much more productive do you need to make them for it to become worth it? If you 3x their productivity, they are now doing the job of 3 people, you just saved 200k _per year_. To tie that back to your comment -- imagine its for a team of 40 users but the company would ideally like them to be a team of 400 users. Yet because of the software being created, those 40 people are doing the work of 400. You can extend that line of thinking pretty far -- and going down that line of thought is when I realized how valuable programming is. When you build the right things you are literally creating value with everything you ship, and it adds up over time.
- TillE 4y agoEvery company needs internal software of some description, and sometimes you're doing unique stuff that can't simply be purchased off the shelf. I mean the extreme case is a developer writing scripts they only use themselves, which would be a 1:1 ratio.
- jsty 4y agoSurely the extreme case is whole teams working on software only one person uses
- francisofascii 4y agoYou are probably right, but not nearly as expensive as the 40 users (assuming employees). So if you can double their productivity it is worth it.
- varjag 4y agoIt could well be this software is what makes it 40 users and not 4000.
- cratermoon 4y agoOh that's nothing. I worked on a project at a fortune 500 footwear company with dozens of developers, FTEs and contract, that worked over a year on just an update to a software package that was used by maybe 5 people at the company. Granted, these 5 people were the folks actually designing and figuring out how to manufacture their shoes, but still. At least 20% of the contractors were just warming their chairs, and more than one were what I call net negative producers: anything they wrote had to be corrected by someone else before it could be called done.
- zabzonk 4y agonot so much. at the last investment bank i worked at we had about 10 developers writing code to support about 10 traders, perhaps a few more. i don't think this is unusual. this is complex stuff that is changing all the time due to regulatory and business issues.
- tome 4y agoThere's a really interesting phenomenon at play here whereby osigurdson said that something was expensive (and it's probably about $1M/year/users) and everyone has replied as though he/she said that it was too expensive.