|
The rise of DevOps is more an evolution than a revolution, and developer jobs aren’t going anywhere Uh, the 'dev' part?
Someone actually thought devs were going away just because some of them also deploy to the servers?
|
|
|
|
|
Quote: Instead, argued Knupp, the tyranny of DevOps was forcing coders to become generalists rather than specialists.
The history of labour is largely one of increasing specialization. Trying to reverse this trend is usually imbecilic.
|
|
|
|
|
Ops is maintenance. You can't dev while doing ops.
So, one is paying dev to do ops, wasting money where development takes a backseat to maintenance. I spent years as a dev cleaning up mistakes of rockstar programmer (Hi Ralph!), got fired for the effort and had to sign a contract that the rockstar wasn't to blame. Haven't touched ops since that day. If the software complete, then maintenance shouldn't require a dev in the first place. If it does, you're wasting money.
If you can't afford ops, you can't afford dev. Go buy a lottery ticket. If you want dev, you pay for it, without them doing ops (or support, we had that discussion already)
How about DevOpSales? If you want to combine jobs you do not understand, why stop at two? DevOpsManagement will never be a thing, but what about DevOpsCleanToilets? 
How about just blaming us for all that happens and taking all the credits for the good stuff? Aw, wait.. Hi Ralph! 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: DevOpsManagement will never be a thing, but what about DevOpsCleanToilets?
That's what was going through my mind reading this, and then you wrote it. 
|
|
|
|
|
|
Guilty as charged.
|
|
|
|
|
I have never understood DevOps.
Wikipedia:
Quote: DevOps is a set of practices that combines software development and IT operations. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from Agile methodology.
So it's a practice, that nobody seems to know how to actually implement, to achieve a bunch of buzzwords. And the fact that it's associated with Agile is, for me, a "time to read Dilbert comics instead" moment.
AWS:
Quote: DevOps is the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
I guess this is the kind of stuff that upper management likes to read.
I wonder who the people are that actually sit around all day thinking of names for things, and then obscure the definition into meaningless words, simply so that they sell consulting services to the incompetent.
|
|
|
|
|
Marc Clifton wrote: I have never understood DevOps.
It's simple. It's an attempt to make a thin veneer of build automation serve as justification for being too cheap to employ sysadmins sound cool.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
They're calling them "campfires" — and our star appears to be covered with them. It's actually just a bunch of flashlights strapped together
|
|
|
|
|
I expect that closer investigation will find that the Sun's surface exhibits fractal self-similarity:
Big flares have little flares
Upon them to ignite 'em
And little flares have smaller flares,
And so ad infunitum
EDIT: fixed scansion.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
modified 19-Jul-20 16:57pm.
|
|
|
|
|
A deep dive into why the world depends on simple, reliable, well-understood technologies As a bonus, you get $200 every time you pass it
|
|
|
|
|
So, it's most brilliant feature is that it doesn't come with new features to prove it is new and improved?
Still on .NET 2.0; one doesn't need to be "the latest". One needs be "reliable". What works today, should work tomorrow.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Quote: A deep dive into why the world depends on simple, reliable, well-understood technologies
Like the horse? 
|
|
|
|
|
Every software QA team keeps records about the bugs it finds. But which data points are really worthwhile to track? These four guidelines might help. Collect the whole set!
|
|
|
|
|
Affected users complain that the icon indicate that there is no internet connection available, and Microsoft is at a loss to explain what is going on. It's the icon's fault
|
|
|
|
|
Maybe it was the old Lionel Hutz play: 'No-logging VPN? I meant, No! Logging VPN!' I'm sure there is a log some people would like to give them (repeatedly over the head and shoulders)
|
|
|
|
|
Much as in 2015, US surveillance practices and EU privacy law don't mesh well. Did the US fail a GDPR check?
|
|
|
|
|
GitHub announced that the code was successfully deposited in the Arctic Code Vault on July 8, 2020. "Do you know the Klingon proverb that tells us revenge is a dish that is best served cold?"
Dang, and I had one more pull request to complete and it would have been good-to-go.
|
|
|
|
|
Each line of code is more of a liability than an asset. Unless you succeed through scrolling
|
|
|
|
|
I've heard that if you remove all the features from your program your loc goes to 0, too. (Unless it is linked to Crystal Reports.) I bet that would make the author happy!
|
|
|
|
|
Lots of platitudes, which is about what one could expect from a writer who's been VP of This, That, and the Other Thing. Not that this makes the article useless, but it depends on who's reading.
He mentions pride of ownership as a problem, both in an unwillingness to refactor (ironically, usually caused by resistance from managers who don't care about technical debt) and NIH (a valid point). But he doesn't mention that pride of ownership, in the form of having "owners" who manage the evolution of software components, is known to be an important success factor.
|
|
|
|
|
On the contrary.
Th fwr th lns f cd, th bttr!
|
|
|
|
|
It never has been; it was a measurement of relative productivity. If your LOC hits 0 for a few days, something wrong. Might not even be the person your measuring, but the environment or the code base. Like looking at the temperature and drawing conclusions.
Still, LOC gives an indication of what is happening. But agreed, it doesn't measure success. Think the industry knows that already.
As for each line being a liability; if you build a car, then each part is a liability (proven by Tesla). You don't build a car without parts though. So it is a matter of building good parts, control their quality, and have someone looking at the end-result (which Tesla doesn't).
If you too afraid too build, it's because you lack experience and shouldn't be allowed near anything client-related.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Researchers in Germany uncover some unanticipated vulnerabilities Let's just rename it "Flash 2.0"
|
|
|
|
|
unanticipated must mean something else in Germany.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
