It's OK if you disagree, but having spent most of the last 20 years maintaining or improving upon existing code-bases I find that "shit-shoveling" is a pretty apt description for programming in a...
The weird elitism in software development where unless you’re building your programs in the quantum particles that comprise the atoms that make up the silicon your apps are running on you’re just some shit-shoveler always confuses me.
It's OK if you disagree, but having spent most of the last 20 years maintaining or improving upon existing code-bases I find that "shit-shoveling" is a pretty apt description for programming in a business environment or on public-sector projects. Sometimes the shit is code I wrote six months ago. Sometimes the shit is somebody else's code. Either way, there isn't much difference between me and a janitor because I'm still dealing with other people's shit.
Maybe that's the case for you. You know what my job has been for the last 20 years? Wrapping GUIs around stored procedures in a database. I used to do it with Windows forms. Now I do it with HTML,...
If you work as a programmer, your job is usually changing in small or large ways week to week. You are solving new problems and engineering new solutions. Learning new technologies and creating new things.
Maybe that's the case for you. You know what my job has been for the last 20 years? Wrapping GUIs around stored procedures in a database. I used to do it with Windows forms. Now I do it with HTML, CSS, and JavaScript.
You don't need a CS degree to understand n-tier architecture or the model-view-controller pattern.
These sorts of coders won’t have the deep knowledge to craft wild new algorithms for flash trading or neural networks. Why would they need to? That level of expertise is rarely necessary at a job. But any blue-collar coder will be plenty qualified to sling JavaScript for their local bank.
Coding is not hard. Coding well is extremely difficult. And this idea that anyone just starting can do it (for a production environment (for a bank no less)) is dangerous.
Coding is not hard. Coding well is extremely difficult. And this idea that anyone just starting can do it (for a production environment (for a bank no less)) is dangerous.
Well the problem, I think, is that their trying to apply an outdated business model to a modern business practice. It wouldn't be too difficult to have top-level engineers create "blueprints" of...
Well the problem, I think, is that their trying to apply an outdated business model to a modern business practice. It wouldn't be too difficult to have top-level engineers create "blueprints" of code and send them down an assembly-line of coders who are only authorized to mass-produce simple lines of code. We can already see this assembly-line thinking failing in other business as the marketplace changes. This is a good example of someone trying so hard to think outside the box that they hop right back in.
It's OK if you disagree, but having spent most of the last 20 years maintaining or improving upon existing code-bases I find that "shit-shoveling" is a pretty apt description for programming in a business environment or on public-sector projects. Sometimes the shit is code I wrote six months ago. Sometimes the shit is somebody else's code. Either way, there isn't much difference between me and a janitor because I'm still dealing with other people's shit.
Maybe that's the case for you. You know what my job has been for the last 20 years? Wrapping GUIs around stored procedures in a database. I used to do it with Windows forms. Now I do it with HTML, CSS, and JavaScript.
You don't need a CS degree to understand n-tier architecture or the model-view-controller pattern.
lol yeah this might be true if they consider HTML and CSS coding.
I think I just a heart attack.
Coding is not hard. Coding well is extremely difficult. And this idea that anyone just starting can do it (for a production environment (for a bank no less)) is dangerous.
Well the problem, I think, is that their trying to apply an outdated business model to a modern business practice. It wouldn't be too difficult to have top-level engineers create "blueprints" of code and send them down an assembly-line of coders who are only authorized to mass-produce simple lines of code. We can already see this assembly-line thinking failing in other business as the marketplace changes. This is a good example of someone trying so hard to think outside the box that they hop right back in.