...But since you're not the consumer of the result, who cares?
False assumption on your part. Being responsible for maintaining the end result DOES make me the consumer, which means I do have a vested interest in a tool that creates a readable and maintainable product.
Yep, and the solution is to re-generate the results from the inputs. Just like with any other toolchain.
Which only ever works properly if the problem you are working on is one of the few things the toolchain author was able to predict in advance (so again, possibly usable for CRUD coding). The minute you need to write code that the author was not able to predict you would need to write in advance, the whole damn thing falls apart.
Better to just write the code yourself the first time around than risk getting "locked in" to a toolchain that is going to cost you more in the long run than you get from the short-term benefits.
...much of my work for the last 10 years has been a process of cut/paste from my earlier work, or just Goolge a question, follow a link to Stackoverflow, read a few posts for 10 minutes, and only then copy/paste.
Huh, I hate to say it, but it sounds like you really should not have been employed for the past 10 years.
If I wrote code that way I would have for sure been fired LONG ago...
People have been touting variations of this concept for decades, and it NEVER pans out.
You know what happens when you let "AI" do the "heavy lifting" of writing code?
You wind up with crap like Dreamweaver's garbage HTML code...
This MAY work for trivial, formulaic crap like CRUD coding, but for the 50% (minimum) of programming that requires coming up with something novel to address a unique situation? It's going to produce nothing but non-performant, fragile, unmaintainable garbage.
Why would WANT credit for pointlessly being a dick?
You obviously understood what was meant, as you were able to fill in the correction yourself and extract the proper meaning.
Unless you are *actually confused* about what someone said/typed, pointing out their grammar/spelling mistakes is just an attempt to make yourself feel superior to a random stranger.
And I did the math: if I covered my roof in solar panels, I'd lower my electric bill by at most 50-60% on sunny days, and only 30% averaged year round. If I covered my whole property in solar panels and battery energy storage, I might reduce my electric bill to zero...
But what if you covered your whole roof and property in nuclear power plants? How much would you save then?
Does vinyl sound better? I won't touch that one with a 10 foot poll. I'll let the audiophiles and philosophers grind on that one for the next infinity.
Devops the concept is great, "devops" the buzzword is just adding more complexity with little or no benefit.
No, the whole thing is a dumb concept invented by people who don't know how to run a software shop properly.
The idea of devops is the devs design their projects such that they maintain the operations....
Without devops, devs tend to product projects that are brittle and need to be micromanaged. Why would devs care if ops gets called at 1am on a Saturday? If the devs are getting called in the middle of the night, they'll start to care.
Again, what the hell? I deny your above premise scenario as complete BS (or incompetence). This is NOT the way ANY software dev shop should be run!!! I've been doing professional software dev for 20+ years and have worked in half-a-dozen places over that time - and in every single shop I have worked in, the devs have ALWAYS been "third line support".
First line of support: customer service reps handling non-technical issues for users.
Second line of support: ops personnel handling things like connectivity issues (routers, switches), server up time, backups, password resets, OS issues, permission, power issues etc...
Third line of support: any issue with the software/application itself
So in a competently run software shop, the devs ARE the ones getting called at 1am on a Saturday when the software breaks; it's happened to me a couple of times - but I strive to make software robust enough that I don't get those midnight calls.
If your shop is calling the ops people to handle a development software issue in the middle of the night, well: "you're doing it fucking wrong". These same people would probably call a chauffeur instead of a mechanic when their car breaks down FFS.
Ops should be limited to maintaining infrastructure services like VMs and creating tools to allows devs to deploy to prod on their own in a controlled way.
Where the hell have you been working?!? This is *exactly* how it has been done in every software dev shop I have ever worked in, it was simply considered "standard operating procedure" (no one ever called it "Devops" though, they just thought it would be stupid to NOT do it that way)
Lastly, most of the reading I've done on the "DevOps" concept seems to be more overly concerned with teaching sys admins how to code rather than getting coders to handle application maintenance (which is, again, *standard practice* in competent software shops). This is precisely what my boss did at one of my last jobs when he got excited about the "Devops" hype - he sent all the sysadmins and QA engineers and testers on "learn how to code" courses.
Google: "frustum" and enlighten yourself. The graphics engine needs to know the players perspective to decide what to render; that means the rendering engine and graphics card need to know about all entities the player could *possibly* see, in order to decide which ones to render on screen.
This is how "wall hacks" for online games work, by hacking the graphics card to display "non-visible" entities that it has data for.
Get over your fear-of-missing-out and give-me-all-the-things-now addictions.
Oh please, it has nothing to do with "missing out" or an addiction to immediacy, and everything to do with the fact that just about *EVERY* story I see on Slashdot is a repeat of something I saw somewhere else the day before.
I don't expect Slashdot to post "zero-hour" journalism, but I do expect Slashdot articles to at least be current to the *day*. If it was posted elsewhere the day before, it doesn't belong on Slashdot.
...hate their job and their customers; which is why most of them are terrible.
Finding a good IT consultant is like finding a good software dev: look for the people that do it in their spare time, for fun, and who can't stop themselves from doing it - then offer them an over-market salary: Voila! Good IT consultant
Slashdot Mirror
... that Nietzsche is an idiot by the time they finish high school.
I guess the valley is just catching up?
Claude Raines from Casablanca
uh... pretty sure "Claude Raines" was the invisible man from Heroes...
Sounds like a secretary to me, or maybe a glorified secretary. Been doing this shit for 40 years and have never run across a tech admin.
How in the hell have you worked in tech for 40 years and NOT know what a SysAdmin is?
I thought "DevOps" was the new buzzword everyone was embracing these days, is it stupid after all? LOL
I happen to know that the US military uses VB.NET
Well, that certainly explains how they spend more money on military than the entire world put together, but are still effectively useless.
That's because C++ only has two left to pick from. Stroustrup discarded "simpler" way back in 1997 with the introduction of template metaprogramming.
THIS^
Lord I wish I had mod points for you... :(
...But since you're not the consumer of the result, who cares?
False assumption on your part. Being responsible for maintaining the end result DOES make me the consumer, which means I do have a vested interest in a tool that creates a readable and maintainable product.
Yep, and the solution is to re-generate the results from the inputs. Just like with any other toolchain.
Which only ever works properly if the problem you are working on is one of the few things the toolchain author was able to predict in advance (so again, possibly usable for CRUD coding). The minute you need to write code that the author was not able to predict you would need to write in advance, the whole damn thing falls apart.
Better to just write the code yourself the first time around than risk getting "locked in" to a toolchain that is going to cost you more in the long run than you get from the short-term benefits.
... demands crap re-hashes of the really awful EU books, I guess they should be disappointed by that billion dollars.
God the EU novels were fucking terrible! I never understood why people liked them...
Do you understand now, or would you like me to draw you a picture?
I don't care one way or the other, but now I do want you to draw me a picture, please.
...much of my work for the last 10 years has been a process of cut/paste from my earlier work, or just Goolge a question, follow a link to Stackoverflow, read a few posts for 10 minutes, and only then copy/paste.
Huh, I hate to say it, but it sounds like you really should not have been employed for the past 10 years.
If I wrote code that way I would have for sure been fired LONG ago...
People have been touting variations of this concept for decades, and it NEVER pans out.
You know what happens when you let "AI" do the "heavy lifting" of writing code?
You wind up with crap like Dreamweaver's garbage HTML code...
This MAY work for trivial, formulaic crap like CRUD coding, but for the 50% (minimum) of programming that requires coming up with something novel to address a unique situation? It's going to produce nothing but non-performant, fragile, unmaintainable garbage.
Ask SubscribeStar and Gab.ai how well trying to NOT inject politics worked out for them.
LOL What?!?
Gab was *specifically* created to cater to far-right politics; like that was the ENTIRE POINT of the site!
Why would WANT credit for pointlessly being a dick?
You obviously understood what was meant, as you were able to fill in the correction yourself and extract the proper meaning.
Unless you are *actually confused* about what someone said/typed, pointing out their grammar/spelling mistakes is just an attempt to make yourself feel superior to a random stranger.
In short, it makes YOU a dick!
Wow. You're 0 for 3!
Is that you, Mr. President?
And I did the math: if I covered my roof in solar panels, I'd lower my electric bill by at most 50-60% on sunny days, and only 30% averaged year round. If I covered my whole property in solar panels and battery energy storage, I might reduce my electric bill to zero...
But what if you covered your whole roof and property in nuclear power plants? How much would you save then?
I don't work for ANY media company...
Well, that *totally* explains you posting corporate ads as AC! ... my bad.
Whatever, ya wingnut.
Whatever you say, you AC corporate shill, you.
Does vinyl sound better? I won't touch that one with a 10 foot poll. I'll let the audiophiles and philosophers grind on that one for the next infinity.
Why though? This is a settled question: it can't.
Thank you Sony, Philips and the Digital Audio Disc Committee; for your sponsored post about the "Red Book" audio CD format.
It would be nice in the future though, if you posted a disclaimer outlining that this is a sponsored post, otherwise you're just astroturfing.
Cassette tapes? They are the worse medium for music devised by man.
Really?
Worse than wax cylinders?!?
Devops the concept is great, "devops" the buzzword is just adding more complexity with little or no benefit.
No, the whole thing is a dumb concept invented by people who don't know how to run a software shop properly.
The idea of devops is the devs design their projects such that they maintain the operations. ...
Without devops, devs tend to product projects that are brittle and need to be micromanaged. Why would devs care if ops gets called at 1am on a Saturday? If the devs are getting called in the middle of the night, they'll start to care.
Again, what the hell? I deny your above premise scenario as complete BS (or incompetence). This is NOT the way ANY software dev shop should be run!!! I've been doing professional software dev for 20+ years and have worked in half-a-dozen places over that time - and in every single shop I have worked in, the devs have ALWAYS been "third line support".
First line of support: customer service reps handling non-technical issues for users.
Second line of support: ops personnel handling things like connectivity issues (routers, switches), server up time, backups, password resets, OS issues, permission, power issues etc...
Third line of support: any issue with the software/application itself
So in a competently run software shop, the devs ARE the ones getting called at 1am on a Saturday when the software breaks; it's happened to me a couple of times - but I strive to make software robust enough that I don't get those midnight calls.
If your shop is calling the ops people to handle a development software issue in the middle of the night, well: "you're doing it fucking wrong". These same people would probably call a chauffeur instead of a mechanic when their car breaks down FFS.
Ops should be limited to maintaining infrastructure services like VMs and creating tools to allows devs to deploy to prod on their own in a controlled way.
Where the hell have you been working?!? This is *exactly* how it has been done in every software dev shop I have ever worked in, it was simply considered "standard operating procedure" (no one ever called it "Devops" though, they just thought it would be stupid to NOT do it that way)
Lastly, most of the reading I've done on the "DevOps" concept seems to be more overly concerned with teaching sys admins how to code rather than getting coders to handle application maintenance (which is, again, *standard practice* in competent software shops). This is precisely what my boss did at one of my last jobs when he got excited about the "Devops" hype - he sent all the sysadmins and QA engineers and testers on "learn how to code" courses.
Google: "frustum" and enlighten yourself. The graphics engine needs to know the players perspective to decide what to render; that means the rendering engine and graphics card need to know about all entities the player could *possibly* see, in order to decide which ones to render on screen.
This is how "wall hacks" for online games work, by hacking the graphics card to display "non-visible" entities that it has data for.
...as announcing a new "mission statement"
Get over your fear-of-missing-out and give-me-all-the-things-now addictions.
Oh please, it has nothing to do with "missing out" or an addiction to immediacy, and everything to do with the fact that just about *EVERY* story I see on Slashdot is a repeat of something I saw somewhere else the day before.
I don't expect Slashdot to post "zero-hour" journalism, but I do expect Slashdot articles to at least be current to the *day*. If it was posted elsewhere the day before, it doesn't belong on Slashdot.
...hate their job and their customers; which is why most of them are terrible.
Finding a good IT consultant is like finding a good software dev: look for the people that do it in their spare time, for fun, and who can't stop themselves from doing it - then offer them an over-market salary: Voila! Good IT consultant