News for hackers. Stuff that matters.

A comment on Ask HN: Should we bring software dev in-house?. Parent comment

Re:Ask HN: Should we bring software dev in-house? by cellularmitosis on Thursday August 08, 2024 @05:50PM (#41196711)
Mixed in with this may also be architectural decisions based from a "let's just spin something up quickly" mentality. Those foundational architectural decisions have a way of becoming set in stone, long after the freelancers have left, dooming the project to scalability and latency problems which seem to linger forever.
[ Parent | on HN ]
Re:Ask HN: Should we bring software dev in-house? by carlmr on Friday August 09, 2024 @02:46AM (#41199350)
I've seen equally many projects never achieve lift-off because they were stuck in analysis paralysis trying to architect MVP for scalability, extensibility etc.

And even if that succeeded you often end up with fear of change because the complicated architecture can't be touched.

It's really important to have the right balance here, but KISS and YAGNI are often easier to scale when you need it, than the reverse. If you don't have the mentality that the MVP must never be rewritten.

[ Parent | on HN ]
Re:Ask HN: Should we bring software dev in-house? by switch007 on Friday August 09, 2024 @06:42AM (#41200541)
> Mixed in with this may also be architectural decisions based from a "let's just spin something up quickly" mentality

That, plus "they're probably going to fire us in a year anyway, who cares" thinking

And "we don't need to understand the business domain, let's just MVP", which they get away with because they would get accused of not being agile if they did boring stuff like trying to understand the business

I refer more to bigger off shore consultancy shops than individual freelancers

[ Parent | on HN ]