Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Should we bring software dev in-house?

news.ycombinator.com

Post reply on HN
Print view View original

201–210 of 607 posts

Re: Ask HN: Should we bring software dev in-house?

#201

Post by MrDresden »

cvladan wrote: post #191
j45 wrote: post #130

Earlier quoted context omitted.

As a developer who became this kind of a CTO a decade, maybe two before it became fashionable, I would have agreed with this in the past until I learned why otherwise with companies this size. All the devs in this comments can do what I share below. 1000%. It’s a different way to make an impact and help make healthier spaces for technical teams to do what they want. I’ll share one example. Clever architecture and lev…

OMG. GPT? Claude?

Not even sure they can come up with a word soup that thick.

Re: Ask HN: Should we bring software dev in-house?

#202

Post by cxmcc »

I'm working on digital transformation for a traditional company. Challenges are from both culture (80%) and technology (20%, EDIFACT/COBOL is ok, not the worst part for us). Traditional companies can retain talent -- they definitely can compete with big tech if they want to. Especially in current tech talent market, you still have a good window to hire enough talents. A few key questions that you need to answer: - Can you get support from the top (board/CEO) to modernize HR to create competitive comp structure? - Can you identify real engineering leaders that can commit to the job? -- You can't just hire non-hands-on random middle managers. Good engineers don't want to work for politicians. - Do you have political stability to invest in the transformation long-term (3yr+ or more if you are more massive)?

Re: Ask HN: Should we bring software dev in-house?

#203

Post by imoverclocked »

I’m just an engineer so I’ll leave the “shoulding” to others.

Can you attract experienced developers? Yes.

Do all of your developers need to be highly experienced? No.

EDIFACT is an old standard with lots of code floating around to parse it. I don’t know the ins/outs of its usage but an in-house team should be able to tackle this kind of data exchange without too much difficulty. You will likely want to ask candidates about experience with this data format explicitly. You can also ask about related data formats or information exchange in general but you’ll probably want at least one developer with solid experience with the format.

Re: Ask HN: Should we bring software dev in-house?

#204

Post by [deleted] »

j45 wrote: post #130
davedx wrote: post #62

IME what works best getting new projects kick started is hiring a very small team of senior freelancers, making one of them lead, and letting them loose. I worked on such a team once and it was really excellent. The advantage of this strategy is if the experiment doesn't work out, terminating freelancers is much easier than permanent (I noted you're based in Europe). Contrary to what other people said, I wouldn't try…

As a developer who became this kind of a CTO a decade, maybe two before it became fashionable, I would have agreed with this in the past until I learned why otherwise with companies this size. All the devs in this comments can do what I share below. 1000%. It’s a different way to make an impact and help make healthier spaces for technical teams to do what they want. I’ll share one example. Clever architecture and lev…

[deleted]

Re: Ask HN: Should we bring software dev in-house?

#205

Post by j45 »

cvladan wrote: post #191
j45 wrote: post #130

Earlier quoted context omitted.

As a developer who became this kind of a CTO a decade, maybe two before it became fashionable, I would have agreed with this in the past until I learned why otherwise with companies this size. All the devs in this comments can do what I share below. 1000%. It’s a different way to make an impact and help make healthier spaces for technical teams to do what they want. I’ll share one example. Clever architecture and lev…

OMG. GPT? Claude?

Nope, just me, I promise.

It could have been shorter as it's not my target audience, not really able to edit it now.

Re: Ask HN: Should we bring software dev in-house?

#206

Post by ozim »

kelnos wrote: post #175
poeticsilence wrote: post #128

Earlier quoted context omitted.

Strongly agree here. It's hard to find a CTO if you don't have access to any engineering talent that you trust and have vetted. A small, focused project with a team of very senior freelancers both gives you a chance to dip your toes into the idea of running your own in-house software development, and an opportunity to vet individuals who can help you make good hiring decisions down the road. If you're interested in f…

> I've found that the best programmers (and the ones you'd want) are more interested in the technical aspects of the problem and business and customer impact, rather than the sexiness of the business domain. Just want to heartily agree with this point here. Certainly many of us do get excited about particular business domains from time to time, but in my own experience, I get more excited about technical challenges,…

For me red flag is that for OP as a developer I will end up being a cost.

Even with all the good words he wrote how company can improve by doing own dev - reality is that company makes money in logistics and as a software dev I would be second class citizen and cost center.

That is why I much rather work in company that makes money on software, because here I am money making.

Re: Ask HN: Should we bring software dev in-house?

#207

Post by [deleted] »

uticus wrote: post #6

> We're using a third-party product that functions, but barely. > Our business operates in a specific niche and there are no other providers who cater specifically to our industry. If you decide to do in-house, I’d recommend thinking about competing against existing as a new revenue stream, and spinning it off as a separate business unit as much as possible. I imagine this is implied in your question but it wasn’t sp…

[deleted]

Re: Ask HN: Should we bring software dev in-house?

#208

Post by trollbridge »

Can you simply buy the provider? This may be simpler than it sounds.

Once you own it, it’s your asset and you can then attempt to fix management to focus on producing a better product.

I’ve been involved in a few attempts to do exactly what you’re talking about with varying degrees of success. Feel free to reach out to the email in my bio.

Re: Ask HN: Should we bring software dev in-house?

#209

Post by lowbloodsugar »

No.

As a software engineer, I will never again work at a company where the product is not software. Software at non-software companies is a cost center, not a profit center, and cost centers get fucked. It's thankless, depressing, soul destroying work.

Maybe start a new company whose goal is to write software for companies like yours. I have worked at a startup launched by execs from established industry with inside knowledge of what is required, and it was truly fun, even though the great recession brought it to an end (acquired for pennies).

If you do it yourself, in house, there are plenty of thirsty contractors and consultants who will be very happy to bleed you dry.

Basically, if you have to ask, then the answer is no, you can't afford it.

Post reply on HN