Recently I’ve noticed a pattern that’s evolving around rapid development. The development process has shifted it’s time consumption from writing the actual code to system setup and configuration.
I was just wondering, where the hell are all the developers disappearing. For one, everybody loves to abstract things as much away from the original language/system as possible, thus turning a simple process of product publishing into a factory of armchair leather covers with extended spikes and delegated maid. At first I was like – guys learn to f-ing code, you don’t need to use every possible framework or abstraction just to print out an image and a price. But delving deeper I saw a much larger pattern.
Let’s look at the WPF (Windows Presentation Foundation) and Visual Studio – you can write an app without ever touching any line of code – everything can be bound together with data which in turn will update every UI element on it’s own. The same goes for events and other stuff. Of course you need to write a line or two to make some system specific tasks, but by every iteration it’s getting closer to writing almost no code at all.
Next. I had a talk with one of my ex-colleagues who’s working in this huge cubicle and tie oriented software development company. They are building large enterprise systems, but everything he has done in the past couple of months was configuring modules (by checking check-boxes!) in one of the most popular open-source systems. Not a line of code from him.
So I had a thought. Maybe we should start treating this as a separate profession – the Configurator, if you will. Because I’m afraid. I’m afraid of writing a job offer for a real developer who’s willing to write the code, and every single candidate would only know how to install a module and drag a few objects together WITH A MOUSE! It seems to me that the real developers are either fading away into some underground lair or just dying out.
Seno laikos celtnieki paši raka mālus un dedzināja ķieģeļus…
Nu lūk, tagad ir celtnieki un cepļa strādnieki 😉
This is pretty much what the devops team does at my job. Why not just call it “devops”? Technically, I’m doing similar things except I’m writing Chef code in order to configure my servers.
This already exists. It’s called the Configuration Manager, and it typically stands away from the software development team to differentiate. This isn’t new by any means; Visual Basic 3.0 had the same kind of drag-and-drop end-to-end data application tools through the use of DAO-binding from RDBMS to UI controls.
Had an assignment at college to write a simple address book application, and used that instead. The project would lose points for poorly tested / debugged code, so every line had to be documented and explained. Managed to make a perfect score quite easy.
Что написал этот алкаш-чучмек? О том что он будет конфигурировать кубики мышкой?
Етот “алкаш” написал что того которй конфигурировает кубики мишкоы нелйзя называть программистом а кому то другом. Потаму что сегодня все программисти, но некоторие даже код невидели в жизне.
Leave a comment