Neither Developer, nor Operator..his superpower is being mediocre is all fields!
Whacking DevOps on your business card doesn’t make you instantly more valuable. It could also make you a certified guardian of the planet too. Or at least, certified software supplier to the guardians of the planet. At least that’s what we think the US’s Environmental Protection Agency is getting at with its latest efforts to …
Web development alone is more than any one person can fathom, these days... and yeah, I do a little ops too. Being a generalist has its advantages. I just wish I could find some specialists to help... but everyone's a damn generalist...
18F will probably do US.gov some good, mainly by bringing development in-house. Latching onto last decade's hype trains, not so much.
"DevOps" isn't really devs who do some ops, though - it's the guys who specialize in scaling up and out to thousands of servers, right? As in "to hell with efficient code, just throw more CPUs [and megawatts] at your problem!" Not sure how that squares with "green" :)
I have the sinking feeling that since they're somehow equating modern rapid dev practices with environmentalism (new = green, I guess?) we'll see a lot of nodejs and the like running these offerings. I'm wondering how the philosophy of 'who cares about compute, use stuff that's faster to dev and throw more servers at it' is green, when you're basically torpedoing your perf/watt on purpose to save on payroll?
I'm not suggesting we write everything as a custom web server in asm to make it green or anything (that would be ridiculous and hopefully isn't the outcome here either) but let's not claim that these philosophies line up with environmental goals when they don't.
On the other hand it might be a nice inciting incident to force people legislating tech to actually understand tech.
I'm not suggesting we write everything as a custom web server in asm to make it green or anything
It's surprisingly easy to write dynamic Apache modules with apxs; that's not quite asm, but C is close enough.
You do need to think through whether or not that is the right thing to do, of course...
> they're somehow equating modern rapid dev practices with environmentalism
This is the EPA talking, not bonafide tree huggers. Not that either group is known for having a clue about technology.
> we'll see a lot of nodejs and the like
As 'web langs' go, nodejs IS more efficient than php, python, ruby... and genuinely useful in limited circumstances... but even more tedious and error-prone. And it's a wholly different skillset from browser JS. I'm sure we will see more of it, though, until it burns these people.
Waste is mostly an attitude problem, however. Look at all the sites slowing to a crawl under the strain of browser JS bells+whistles, even with fast JS engines. Lazy f---s will find a way to make it even worse, even if they all switch back to asm.
As someone who has worked with the Govt extensively this is a joke Devops and Agile are about making changes and doing things quickly to react to market or other forces....nothing in the government happens quickly or reacts without 40 layers of bureaucracy slowing down even the simplest of changes.
*All* development methodologies are about protecting employers from the combined efforts of large numbers of semi-competent coders.
The problem is that a good programmer can be easily 10 times better -- whether that means more productive, writing more robust and/or efficient code, or probably some combination thereof -- than a mediocre one, but that mediocrity outnumbers excellence by a lot more than 10 to 1.
When I retired at the end of 2011, my agency had just started to deploy Windows 7 to a few developers for evaluation. I expect they, like the Navy and Marine Corps, still have a significant number of Windows XP workstations, along with a POA&M to replace them real soon.
Biting the hand that feeds IT © 1998–2019