|
Once upon a time, there were Full Stack Developers, but as time progressed, they disappeared. Now, all we have are impostors. People trying to be full stack, but failing. The Full Stack Developer is now as obsolete as a unicorn So all you people doing front-end, back-end, and middle-tier code: you don't exist!
|
|
|
|
|
Many of us will have been forced up the "full-stack" route at some time or other and most of us will have found that we're much more productive at some parts of it than others. Personally, I'm not great at front-end stuff (particularly web) - I do data an awful lot better than I do UI, that's the way my brain works. Similarly, I know some great UI developers who don't really get databases or back-end code. There may well be people who are equally good across the whole spectrum but they're few and far between.
If you were managing the building of a house, you wouldn't get your brickie to do the electrics while your plumber had a go at the roof. Why should it be any different with software?
The only place full-stack makes sense to me is in tiny teams where there isn't enough resource to use people optimally. The more developers you have, the more sense it makes to use them to their strengths.
98.4% of statistics are made up on the spot.
|
|
|
|
|
It's amazing how long it took the software industry to learn "jack of all trades, master of none".
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
PeejayAdams wrote: The only place full-stack makes sense to me is in tiny teams where there isn't enough resource to use people optimally. The more developers you have, the more sense it makes to use them to their strengths.
Yeah team size is definitely a big part of it; if your team isn't large enough hard specialization doesn't really work.
But even with larger teams while it can make sense for people to split into largely front end/back end/etc roles being able to do at least basic level work at all levels is still beneficial. Handing off in the middle of a task is a source of friction and a potential for errors eg when the backend API doesn't work quite the way the front end dev expects/needs it to do. It also helps with smoothing out timing/backlog issues if the front and backend tasks end up not taking the same amount of time and you end up with a bunch of features only half done because the other person's behind.
Even in those cases allocating the tasks so that the main part of the effort goes to the person with the strongest skills is important; but a lot of work doesn't need an expert on either side. eg CRUD tends to be fairly boilerplate on both the front and back ends; and as long as there's a good reference example a frontend person can copy/paste/rename the relevant backend code even if they don't know why it was done using X instead of Y or Z; and vice versa for the backend person displaying data on basic CRUD forms even if he'd struggle to create the overall styling from scratch.
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
|
|
|
|
|
When I get asked to build a web page or fix a computer because I'm "a computer guy", I use references the average person can understand. Is an auto mechanic the same as a diesel mechanic or small engine repair person or jet mechanic? No, they all have their realm of influence, and, although there may be similarities between them, they aren't necessarily cross-functional.
|
|
|
|
|
A freedom of information request revealed that the FBI used the Best Buy division's repair staff to flag illegal content. "No one stands behind you like Geek Squad"
|
|
|
|
|
Kent Sharkey wrote: stands behind
More like "looks over your shoulder!"
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
There have been some concerns that Windows 10 has a built-in “keylogger,” because the operating system uses typing data to improve autocompletion, next word prediction, and spelling correction. Now they ask politely before watching everything you type
"Microsoft is also testing the idea of Windows 10 users receiving seven individual screens for all the privacy controls in the operating system"
Because more settings screens is better?
|
|
|
|
|
Updates on performance, unit testing, C++ 17 Standards Conformance and probably much more Incrementally better than before!
|
|
|
|
|
Java 10 will be released this month with a focus on cloud and serverless computing, Oracle has announced. Somehow I missed everything between 2 and 10
Guess I can keep ignoring it?
|
|
|
|
|
Previously built using the Microsoft C++ compiler, Google is now using the same compiler for Windows, macOS, Linux, and Android, and the switch makes Chrome arguably the first major software project to use Clang on Windows. Clang, clang, clang went the browser
And they got help from Microsoft to do so?
|
|
|
|
|
Two independent Israeli researchers found a way for an attacker to bypass the lock protection on Windows machines and install malware by using voice commands directed at Cortana. Hey, Cortana, you got some 'splaining to do
|
|
|
|
|
Cortana : I thought it was Chief. And you know I got a soft spot for him !!!  Singularity achieved !
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
A video game company, Ubisoft, is leveraging a new AI tool called Commit Assistant, which flags mistakes in a game's code before programmers even make them. I make msitakes faster than an AI can find them
|
|
|
|
|
A cursory glance at the first paragraph (or even the name of the tool) indicates that it doesn't. It evidently catches errors at commit-time.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Google announced a 72-qubit universal quantum computer that promises the same low error rates the company saw in its first 9-qubit quantum computer. Google believes that this quantum computer, called Bristlecone, will be able to bring us to an age of quantum supremacy. "Low error rates"? Time for the great quantum leap!
|
|
|
|
|
The vulnerabilities affect the attach, detach, and paging procedures that are part of Long-Term Evolution (LTE), a standard for high-speed wireless communication for mobile devices. Three cheers for no security anywhere!
|
|
|
|
|
We're wasting so much time collaborating and toggling between apps it's a miracle any work actually gets done. Someone IMed me an email about a Slack chat on this very topic the other day
|
|
|
|
|
From makeup artists in Venezuela to women in conservative parts of India, people around the world are doing the digital equivalent of needlework —drawing boxes around cars in street photos, tagging images, and transcribing snatches of speech that computers can't quite make out. "It's made of people! PEOPLE!!"
|
|
|
|
|
Blockchain-powered computer programs promise to revolutionize the digital economy, but new research suggests they’re far from secure. "The way it looks I'll probably hang cause there ain't no hope on a chain gang "
|
|
|
|
|
Self Documenting code is not a good goal to aim for. Quite the opposite in my opinion. if(controversy()) { push(traffic); } else {break;}
|
|
|
|
|
Graham Cox wrote: Self Documenting code is not a good goal to aim for. Quite the opposite in my opinion. Self Documenting code is a good goal to aim for.
Fixed. Better click-bait, twice as lengthy.
|
|
|
|
|
It’s going to happen: At some point in your professional career, you’re going to feel stupid, and it’s going to be because you forgot some simple term. FWIW (which isn't in there at the moment)
|
|
|
|
|
Newer Intel microprocessors are provided with Software Guard Extensions (SGX) which allow software programs to run in their own little safe corner of the processor. These safe areas are created on demand and have their own memory, isolated from other system software like hypervisors and the operating system itself. Just when you thought it was safe in the processor
|
|
|
|
|
The technology industry has been overloading the term ‘senior engineer’. A senior engineer is not a senior engineer is not a senior engineer. Does this mean I won't get the discount at the movies?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
