DevOps is broken • Hacker News Board

Re: DevOps is broken

#361

Post by kazen44 » Sat, Oct 22, 2022, 11:33 PM UTC

znpy wrote: post #233

> The problem is most engineers don’t want to do operations work. Nah, the problem is that most (software) engineers don't have the skills to do operations work. Let's not fool ourselves: software development is 95% development (writing code/docs/test etc) and 5% system administration (getting your local mysql or whatever up and running etc) whereas operations is usually 95% screaming at the machines (various linux t…

i wouldn't say the operations view is pessimistic perse.

Its a different frame of mind, mainly because its the place where the rubber meets the road so to speak. Once things are production, you cannot revoke or redesign your product/system because people are directly reliant on it.

Re: DevOps is broken

#362

Post by abledon » Mon, Oct 24, 2022, 11:54 PM UTC

rglover wrote: post #249

travisgriggs wrote: post #34

I have bewilderingly tried to discern why software development continues to grow more and more complex. It wasn’t always like this. There was a time when we talked about languages and OSes and libraries as if they made a difference on how much you could get done with as little people and cognitive load as possible (the claims were very much overrated, but the point was we acted like it mattered). And then it started…

I like the Uncle Bob explanation: the number of developers has a doubling rate of ~5 years due to the constant entry of new developers [1]. Over time, the number of inexperienced developers far outweighs the experienced ones. Inexperienced developers naturally gravitate toward complexity because they don't know any better. Couple that with a social drift toward hyper-specialization. That sort of hierarchy naturally c…

"The lollipop guild" , amazing lol

Re: DevOps is broken

#363

Post by HenriTEL » Tue, Oct 25, 2022, 1:20 PM UTC

davidpfarrell wrote: post #322

HenriTEL wrote: post #269

Earlier quoted context omitted.

As projects grow the Makefile becomes pretty much a big bash script, but with a specific syntax that I always struggle with.

Unrelated to this topic, I invite you take a look at my project which a tool purpose-built to be a better version of what your makefile became: Run: Task runner that helps you easily manage and invoke small scripts and wrappers https://github.com/TekWizely/run Defining commands feels like make, but comes with a bunch of extras targeted at the needs of a task-runner. I hope you'll check it out!

The way to define options is interesting. It's hard to see the benefits from the docs in the README tho, given that it's yet another syntax to learn.

I suggest to add a complete example of common use cases like running the unit tests, building targets while setting the correct options depending on the host (linux vs windows vs macos).