Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Software engineering is doomed.
The next generation of developers is going to suck as fuck
I've come across a lot of situation that made me think this way.
The most notable examples are right here on devrant.
I've seen a shit ton of rants blaming languages for "bugs" when in fact those "bugs" wouldn't have happened if those fuckers would have read the specifications of said languages.
This new generation doesn't read, when they've got a problem they just fucking go to Google for answers, they don't bother reading specifications, language books, rfc, etc, they don't bother reading where the true source of information are. The documentation ? What's that ? Let's go to stackoverflow first, let's think second.
Same back in school I've seen people in the highest grades that couldn't fucking decompress a tar archive.
In the coming decades we will loose the high skilled people, the people that made the software world as it is today we will be left with fuckers only able to blame things for stuff they don't understand.
This is my first true rant. This is me being pissed off.27 -
I see software engineering mostly devolving to be simpler syntax, more widespread and reach more range of people, including non-tech ones.
That’s now obviously leading to more crappy javascript code, more abandoned frameworks, libraries, more shitty software and more dev rants.5 -
Well, it all started off with hardware-level programming involving jumpers and stuff like that... Then came Assembly, which was good.. B, C compilers. Finally came the interpreted languages, and that's where in my opinion the abstraction should've ended. But no, we needed more frameworks, more libraries, even more abstraction! Where does it end? As it seems to be going, I guess that users will have kid toys - no iToys! - for electronics and we'll be programming on with bloated Scratch GUI's. Nothing against Scratch, but that shit ain't proper programming anymore. God I can't wait for the future.
ABSTRACT ALL THE THINGS!!!
Oh and not to mention that all software will be governed in political correctness by some Alex SJW AI shit that became sentient. Not a single programming term will be non-offensive anymore, no matter how hard you try to not offend anyone, or God forbid - don't care about it because you just want to make something that's readable, usable and working!! Terms, UI names for buttons, heck even icons! REMOVE IT BECAUSE IT OFFENDS SOMEONE THAT I DON'T EVEN KNOW JACK SHIT ABOUT!!!18 -
I see a farmer who wants to work less, he automates his work by using new tools - shovels, tractors, to the point that he has to invest similar amount of time to maintain these tools4
-
To me it seems that Software eng has become a „I wanna get rich“ thing..
Too many idiots do it and think they’ll get tons of money..
Not that many new geeks because of that..
Also, I feel like the mentality has switched from quality oriented to shiny oriented..
3/4 of new Software i use contains serious bugs that don’t get fixed because it takes time..9 -
Arch Linux is officially dead due to fanboys who always says “I use Arch Linux” everytime when they open mouth. It is considered as mental illness so they have to shut down.10
-
I think we're going two sides:
For one, more and more technology is being developed/engineered which is even more and more and more intrusive as for personal privacy, I'm genuinely worried how this'll go as privacy isn't just a about not exposing certain things like passwords/bank account details and so on, it's also about being an individual who has their own thoughts, opinions and so on. If we keep taking that away more and more often, society will change and go towards the Orwell scenario (we're on our way there right now). We can change this as software/design/server engineers but that's up to us and I sadly don't see that happening quickly, also due to the 'nothing to hide' bullshit.
Second one is that were going more and more towards open source.
This is a good thing as this:
- gives freedom to devs around the world to improve software and/or modify it to suit their needs.
- gives people the opportunity to look through the source code of softwares in order to verify it as for backdoors and find security vulnerabilities which otherwise can remain hidden for the general public while spying agencies have way more resources to go vulnerability hunting.
For the people who think this isn't a good idea (even more open source), without it we'd be completely fucked as for moving forward/security/privacy. (I can give examples if wanted).3 -
A lot of engineering fads go in circle.
Architecture in the 80s: Mainframe and clients.
Architecture in the 90s: Software systems connected by an ESB.
Architecture in the 2000s: Big central service and everyone connects to it for everything
Architecture in the 2010s: Decentralized microservices that communicate with queues.
Current: RabbitMQ and Kafka.
... Can't we just go back to the 90s?
I hate fads.
I hate when I have to get some data, and it's scattered on 20 different servers, and to load a fucking account page, a convoluted network of 40 apps have to be activated, some in PHP, others in JS, others on Java, that are developed by different teams, connected to different tiny ass DBs, all on huge clusters of tiny ass virtual machines that get 30% load at peak hours, 90% of which comes from serializing and parsing messages. 40 people maintaining this nightmare, that could've been just 7 people making a small monolithic system that easily handles this workload on a 4-core server with 32GB of RAM.
Tripple it, put it behind a load balancer, proper DB replication (use fucking CockroachDB if you really want survivability), and you've got zero downtime at a fraction of the cost.
Just because something's cool now, doesn't mean that everybody has to blindly follow it for fucks sake!
Same rant goes for functional vs OOP and all that crap. Going blindly with any of these is just a stupid fad, and the main reason why companies need refactoring of legacy code.12 -
Software engineering gets more diverse every year with problems ranging from faking 3d shadows on 2d browsers to accurately mimicking chemical bonds on the electron level.
I guess we primarily will get advanced tools, to make more complex problems easier to tackle. Just compare manual punch card piercing pliers to the JetBrains tool chain.
Also I believe that the roles that developers embody will get even more diverse, people will have way more specific functions in their ecosystem.5 -
Software engineering is becoming main stream.
It will become the average job in the future. Anyone who cant dev is going to be poor and do the dirtiest jobs.
Dev average income is going to drop， mainly because a shit loads of frameworks and dumbification of software and code creation will be set in place to accomodate large population as devs.
The will create a seperation between the normal idiot dev who will be paid minimum wage and the smart ones that create the frameworks and dumbed down code creating tools.
Its oversimplified obviously because im not taking into account sys admin and so on but in general it will follow that trend. Its like this today but because there isnt enough devs， idiots are still revered and payed big bucks.
Give it 50 to 75 years imo.4 -
I feel like there are more and more people who only THINK they can program, but in reality they barely can make the “Hello, world” program. Many of them come from all of these “online courses”, I’m not saying that from there come only the bad ones, but many of them are bad programmers, who just think that one or two courses is good enough.
You have to gain experience by doing actual work, not by doing pre-baked exercises. In real life most of things you have to solve with your imagination - Stackoverflow will only provide you some raw draw!4 -
+ Death of Wix and WordPress (hopefully)
+ Abandonment of Java
- Bajillion JavaScript frameworks
- Software engineers trying to automate everything
+ Cloud blockchain AI containers that mine bitcoin with machine learning technology in high demand2 -
I see AI autocorrecting code in ide before it gets compiled and complex ui getting exported from psd to code in few seconds4
-
I just want a coffee machine that is smart enough to know when I need coffee and then serves it on my desk.
(Also this coffee machine should automatically kill all annoying client's)3 -
Perhaps more of a wishlist than what I think will actually happen, but:
- Everyone realises that blockchain is nothing more than a tiny niche, and therefore everyone but a tiny niche shuts up about it.
- Starting a new JS framework every 2 seconds becomes a crime. Existing JS frameworks have a big war, until only one is left standing.
- Developing for "FaaS" (serverless, if I must use that name) type computing becomes a big thing.
- Relational database engines get to the point where special handling of "big data" isn't required anymore. Joins across billions of rows doesn't present an issue.
- Everyone wakes up one day and realises that Wordpress is a steaming pile of insecure cow dung. It's never used again, and burns in a fire.9 -
Software Engineering in future is just "Framework of frameworks" or one could say.. "Library of Libraries"...2
-
I feel like we've had a similar group rant earlier.. is it just me?
Anyway, more frameworks. During the time it took me to write this, I bet that at least a dozen of them popped up already :')5 -
These days programming has boiled down to how optimally can you find solution to your problem using search tools!2
-
It some point in the future we will have smart enough AIs that they can create the tools an applications for us by just telling them what features we want.
We'll still be the only ones who know _how_ to tell them.3 -
Software engineering is slowly being lowered to a basic skill to please corporations that literally want you to automate your job away. The only fruitful areas of software engineering that I can see being relevant in the next 10 years are those mixed with other hard sciences such as bioinformatics, robotics, bleeding edge statistics and mathematics (AI research), physics, etc. The trend I see right now is that software engineering is being integrated with business-oriented degrees or arts degrees, targeted programs towards beginners offered for free or low prices. There's going to be a higher barrier of entry for the jobs that are actually worth the stress and I'm praying I'll be able to catch the train before it leaves the station.9
-
Software engineering doesn't evolving the way you think of it.
There are no new big patterns. There are no new big concepts and ideas to bring that evolution to us. Rob Pike thinks that the concepts he used twenty years ago are the best possible way of implementing everything and he creates Golang.
The evolution of software engineering, and maybe the whole evolution as a concept is a tick-tock. Software engineering had its latest tick at nineties, when the concepts we call modern were developed. And the latest tock was the rise of the internet, and it given the single-computer-centered Von Neumann architecture really hard challenges. I mean ticks are theoretical inventions and patterns and ideas and etc, while tock is more of some practical, business-oriented implementations.
PHP is still in use. We have troubles with scaling and deployment. Banking systems still run old Java, Windows XP and even COBOL. We had persistence really, really long time ago, and now frontenders reinvent it and call it 'immutability'!
We had our tick many, many years ago. It's time for tock. With not only scientific but commercial use of things such as Clojure, CRDTs and maybe Rust lang, we are heading straight to our new big tock, which'll bring us new great problems to solve.
That's how any evolution goes. -
I hope that in the future we will have a different way to learn new languages than creating a 'hello world!" object 😂7
-
I see it evolving the same way it always has done. The technology will keep changing for the better and the best stuff will emerge on top.
You have a choice to fight the current of new technology that is always flowing by learning and adapting to what comes. If you don't, and you stay stagnant with your chosen tech and skill level, the current will eventually carry away your relevance.
It's natural selection. You have to fight or die. -
The number of scripters and 'data scientists' that call themselves developers will increase, the true art of development will become sidelined and the world's code will become progressively more bloated and inefficient as the rift between hardware and software widens to an echoey chasm.
Then quantum processors will come along, requiring new logic, languages and practices, and once again the true developers will rise up and pave the way for a bunch of entitled, know-it-all and self-promoting QuarkaScripters to come along decades later and pretend like they invented programming. -
Much like traditional engineering I can see software engineering suddenly becoming very very regulated around the world. Different systems safety bodies will open up for things like embedded systems development where their is a risk of harm, mandatory security standards will be put in place etc.
Enjoy the cowboy days ladies/gents/others regulatory bodies are on their way!4 -
More high-level stuff, sweet libs, awesome frameworks and the next generation of devs complaining about bad performance and too much abstraction.
-
A bunch of people who know a bunch of frameworks but lack intrinsic understanding CS, therefore bringing the degeneration of overall quality.
This ultimately leads to:
1- shitty dev jobs (the future blue-collar job, always in risk to be automated)
OR
2- super high-end dev jobs (most likely AI engineering, devops, data science)
As generations pass, this shapes out a whole new world economy.2 -
The near future is in IOT and device programming...
In ten years most of us will have some kind of central control and more and more stuff connected to IOT, security will be even a bigger problem with all the Firmware bugs and 0-day exploits, and In 10 years IOT programmers will be like today's plumbers... You need one to make a custom build and you must pay an excessive hour salary.
My country is already getting Ready, I'm starting next month a 1-year course on automation and electronics programming paid by the government.
On the other hand, most users will use fewer computers and more tablets and phones, meaning jobs in the backend and device apps programming and less in general computer programs for the general public.
Programmers jobs will increase as general jobs decrease, as many jobs will be replaced by machines, but such machines still need to be programmed, meaning trading 10 low-level jobs for 1 or 2 programming jobs.
Unlike most job areas, self-tough and Bootcamp programmers will have a chance for a job, as experience and knowledge will be more important than a "canudo" (Portuguese expression for the paper you get at the end of a university course). And we will see an increase of Programmer jobs class, with lower paid jobs for less experienced and more well-paid jobs for engineers.
In 10 years the market will be flooded with programmers and computer engineers, as many countries are investing in computer classes in the first years of the kids, So most kids will know at least one programming language at the end of their school and more about computers than most people these days. -
Hopefully we will leave the path of shipping tons of crappy software in increasingly shorter periods of time and come back to thought out, well engineered software that actually matters. I would love that.1
-
Right now everything is a CMS. And I hate it. It lets people who don't know what they're doing, think they know what they're doing and make a mess for the real developers.
All I can hope for us some huge educational effort so that if you want to use WordPress you can, but know that there are much better options.
Every change has to be approved ahead of time anyway and its literally my job to keep this website running. I don't need you poking around breaking stuff.3 -
The evolving of software engineering is highly dependent on hardware engineering.
If only software engineering would evolve then there would eventually be a point where theres nothing more to do due to the lack of hardware to develop software for.
So its more a question of how you see hardware engineering evolving.
I expect that there will be a point in the future where we have techology which in big scale does dangerous or time consuming tasks. Like for example at nuclear reactors or at other high level security and high risk locations. This of course requires highly sofisticated ai software. -
Sadly I just can imagine more development directed to increase consumer behavior (ads, social) and less to actually improve people's lives.
Shouldn't software development have an identity other than the enterprise? We are probably the better communicated professional community there is. Shouldn't we rise? ✊2 -
Currently there is a lot of work done in native application development, like android/iOS apps, desktop applications and such.
I feel like those will be replaced over time by websites and electron based apps.
I just don‘t see native apps in ten or twenty years from now1 -
At some arbitrary future point, when things progress further into the realm of unreasonable demands from software engineers as a "regular day at the office", a huge inquiry into the working conditions and hours of devs will take place, and a major rethink into how software projects are handled as a whole, because the current methodologies, mixed with unshifting deadlines, clients and other worldly bullshit is unsustainable given the current industry climate.1
-
Third (or fourth) AI winter coming in despite global warming. Cold war level shit cyber warfare.
C/C++ not dead, Java zombie still in the businesses.
Still no usable IDE (on Linux)5 -
I see a major shift coming up im regards of how we continue to evolve the way our applications work in regards to web based solutions. Http was not meant to do the shit that we are doing today, yeah it works, but it continues to feel like a hack. The advent of A.I and WebAssembly will probably make developers more mindful about compilers and truly optimized code. Languages such as Rust are pointing in the right direction in terms of speed and safety and as our computers become more powerful so will our way to communicate with them. Eventually damn near every web based solution will include A.I even when it is not needed at all.
Regardless of what happens. Yo ass is not going to stop hearing about C++, SQL, and Javascript(top kek)1 -
1. Languages will evolve to make as short as possible in terms of lines of code. Shorter syntaxes all the way.
2. Each platform/part of architecture will have only 1-2 languages to code in. There will be convergence of languages. This is more to do with industry usage. Underground new languages will still continue to flourish.
3. Focus will be more on natural language. Both as research item for understanding humann languages better and possible movement of coding languages in the direction of natural languages. Natural syntax as much as possible.
4. Softwares will be self learning. Every interaction will result in the software to evolve as per your usage. That would mean the same software will behave differently for every user. This will be basis user's interaction.
5. Less physical interaction. More to do with what the user thinks. Intuitive.1 -
I can't really predict anything except AI/ML being used extensively. Let's hope networks become decentralised again. And I really hope that node (although it's not too bad) is replaced by deno
-
We decide the quality of a software only by looking at the programming language that being used to make it.1
-
I’m a bit scared that we as developers will replace ourselves with AI - sure there must be developers for AI and special stuff AI can’t handle at that time, but... I think that not so many developers are needed in the future?5
-
Hopefully, simpler sintax.
And better documentation for every language/framework. Especially for the devs who are just starting, don't write documentation assuming everyone has been working with your framework for years!
That last one was more a rant than answering the actual question, but I needed to say it. It's been on my mind for a while 😑2 -
Engineering never really evolves. The techniques we are using now to build the largest dams in the world are the same ones which were used to build ancient aquaducts.3
-
Evolving so fast that we would make frameworks to keep track of frameworks that make their own frameworks out of frameworks.
Real AI shall be birthed in this manner. -
Things will keep going like they are now, only faster, until some Malthusian Event (natural or cyber) drops everything to a few compiled languages, a web stack, a handful of frameworks, and a couple of kernel types.
-
The software eng. pendulum will swing away from scrum/agile nonsense after years of those things contributing mostly inferior half baked beta software to customers. Unfortunately, it will swing too far the other way but will somehow also manage to claim roots in the musings of Demming and Japanese auto manufacturing when Leave it to Beaver was still a hot TV hit. In other words, the org charts will have different titles, and different buzz words will be used, but developers will still have archetypal pointy haired bosses.
Top Tags
Weekly Rant
View