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

Navigating a Broken Dev Culture

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 49 posts

Re: Navigating a Broken Dev Culture

#31

Post by worik »

sepositus wrote: post #28
flowerbreeze wrote: post #27

Earlier quoted context omitted.

Adding an additional layer also means that layer needs to be managed at all times, and additional setup is required to use it. This starts at installing docker related tooling, having to do extra work to access logs inside containers, additional infrastructure management/maintenance (eg private repository), Docker compatibility between versions (it's not very good at maintaining that) etc. The build/deployment time d…

Sure, in the grand scheme of things, though, I wouldn't argue that seconds is a legitimate slow down. I just really struggle to buy into the argument that "non-Docker" is superior and that introducing Docker is a problem. It's _another_ way to do deployments, and it's not strictly worse. There are tradeoffs on both sides, although I would argue Docker has far fewer than just using systemctl and SSH. > Adding an addit…

I think the point is that not using Docker is easier, simpler, cheaper and better than using Docker.

Unless it is not, then you should use Docker.

But many (all?) of us have had the experience of a manager insisting on some "new thing" (LLMs are the current fad of the day) and if we are not using it we are falling behind. That is not true, as we all know.

It is very hard for the money people to manage the tech stack, but they need to, it is literally their job (at the highest level). We desperately need more engineers, who are suited (I am not!) to go into management

Re: Navigating a Broken Dev Culture

#32

Post by worik »

dpc_01234 wrote: post #17

I think you confuse "good" with "trendy", as the list of things you want is a bit of a mixed bag. Testing is almost unquestionably a benefit (at least to a point) and is something that can be introduced with minimum initial investments and right away gives big benefits. I'd start with that for low effort, big impact. Then CI (but not CD) is like that too. Just have the test executed on every commit/PR to gain some co…

Testing is very important. But....

> something that can be introduced with minimum initial investments

Testing is very expensive. Setting up an automated testing environment is tricky, prone to failure, and requires constant expensive management.

It also adds nothing to the bottom line, on the face of it.

It is very very important. It is possible to limp along with inadequate testing, become a major global infrastructure provider, then have it all go horribly, predictably, wrong.

But the money person that commits large quantities of cash to something that does nothing to improve the bottom line tomorrow (fingers crossed) is taking risks with their personal welfare.

It sucks. Testing is very important. Automated testing is gold. It is very hard for us to implement because....

Re: Navigating a Broken Dev Culture

#33

Post by wink »

dpc_01234 wrote: post #17

I think you confuse "good" with "trendy", as the list of things you want is a bit of a mixed bag. Testing is almost unquestionably a benefit (at least to a point) and is something that can be introduced with minimum initial investments and right away gives big benefits. I'd start with that for low effort, big impact. Then CI (but not CD) is like that too. Just have the test executed on every commit/PR to gain some co…

> Manual SSH into the server, copy the build, and pray

Doesn't sound like a script. Also doesn't sound like there's even a build server or CI.

Re: Navigating a Broken Dev Culture

#35

Post by paulcole »

JTyQZSnP3cQGa8B wrote: post #3

> This is a one-day task; it shouldn’t take more than that Your CTO is an idiot but you can't change that. My first idea would be to write a good resume and start finding another job. The whole description confirms that. I have worked for a lot of companies from the smallest to the biggest and it's always the same scenario. If everything is THAT bad, your only chance is to leave. It would take years to change that co…

> Your CTO is an idiot

How can you say this without knowing what the task is?

Re: Navigating a Broken Dev Culture

#38

Post by matttii »

scinse wrote: post #18

> I know going full-time into FOSS isn’t easy What matters is whether it’s important. I spent a lot of time over the years doing FOSS and learned all that code just like all other code atrophies and dies. Maybe it helps you get a job (mine did), and maybe it drives part of the world. But, eventually, it’s probably not important. Don’t worry about FOSS as criteria for a job doing something that is transient. If you’re…

hi

Re: Navigating a Broken Dev Culture

#39

Post by lightserver »

JTyQZSnP3cQGa8B wrote: post #3

> This is a one-day task; it shouldn’t take more than that Your CTO is an idiot but you can't change that. My first idea would be to write a good resume and start finding another job. The whole description confirms that. I have worked for a lot of companies from the smallest to the biggest and it's always the same scenario. If everything is THAT bad, your only chance is to leave. It would take years to change that co…

thanks for your suggestions, I am well versed with uv / ruff , just didn't mentioned in my post , absoultely loved uv after trying it out. I have started looking out for jobs aggressively.

Re: Navigating a Broken Dev Culture

#40

Post by lightserver »

webdevver wrote: post #16

> Deployments? Manual SSH into the server, copy the build, and pray I know people who would kill to be in your shoes. grass is greener and all that.

to add to that usually there is a proxy server in between to connect to the server you're deploying, which is means you have to scp twice and it's like the most dreadful thing , I'm not sure why did you said "I know people who would kill to be in your shoes." am I missing something ?
Post reply on HN