Is water wet? News at 11.
-
Complexity is killing software developers
The growing complexity of modern software systems is slowly killing software developers. How can you regain control, without losing out on the best these technologies have to offer?
Having a billion microservices and needing to keep on top of orchestration fads makes deployment more complicated?
-
Yeah my orchestration is still mostly represented in batch files, sometimes PowerShell if I feel fancy...
-
Complexity is killing software developers
Well, saves me from doing it then.
There has never been more complexity and choice available to software developers than there is today, but there have also have never been more options to abstract it away.
It's funny how the article gets the right idea and then misses the point right before the finish line.
essential and accidental complexity
The first is usually direct result of accidental complexity in the problem domain itself.
-
@Tsaukpaetra said in Is water wet? News at 11.:
Yeah my orchestration is still mostly represented in batch files, sometimes PowerShell if I feel fancy...
My orchestration is mostly in MuseScore, although I also have a bunch of MIDI and a few .wav and PDF files. I also still have a bunch of old and now-useless Cakewalk Express files hanging around.
-
'Sfunny, but in my day-to-day existence as a software developer, I have exactly none of the problems described in the article.
-
@Steve_The_Cynic said in Is water wet? News at 11.:
'Sfunny, but in my day-to-day existence as a software developer, I have exactly none of the problems described in the article.
Sounds like you need to re-architect your software and redevelop it from the ground up with a microservice based approach.
-
I recognise every problem in this article. I may have quit a job over this.
-
@izzion said in Is water wet? News at 11.:
@Steve_The_Cynic said in Is water wet? News at 11.:
'Sfunny, but in my day-to-day existence as a software developer, I have exactly none of the problems described in the article.
Sounds like you need to re-architect your software and redevelop it from the ground up with a microservice based approach.
Given that my job involves software for a deep-packet-inspection IPS/UTM firewall, a microservice based approach would be approximately 137% wrong for what I do.
-
@Arantor said in Is water wet? News at 11.:
I recognise every problem in this article. I may have quit a job over this.
I've heard of all those problems, and on that basis, quitting my job would seem to pose a strong risk of encountering some or all of them.
-
@Steve_The_Cynic said in Is water wet? News at 11.:
a microservice based approach would be approximately 137% wrong for what I do.
Sounds like nothing is stopping you then!
-
@Steve_The_Cynic this is completely fair. I am not in your fortunate position, however.
-
@Steve_The_Cynic said in Is water wet? News at 11.:
@izzion said in Is water wet? News at 11.:
@Steve_The_Cynic said in Is water wet? News at 11.:
'Sfunny, but in my day-to-day existence as a software developer, I have exactly none of the problems described in the article.
Sounds like you need to re-architect your software and redevelop it from the ground up with a microservice based approach.
Given that my job involves software for a deep-packet-inspection IPS/UTM firewall, a microservice based approach would be approximately 137% wrong for what I do.
All the more reason to pursue it!
-
When the fundamental problem is Too Much Magic, adding more magic is not the solution.
-
@dkf what you need is AbstractMagicFactoryProvider.
-
@Gąska said in Is water wet? News at 11.:
@dkf what you need is AbstractMagicFactoryProvider.
Which will of course lead to the AbstractMagicFactoryProviderLess Service.
-
@CodeJunkie is that a microservice? If it isn't maybe it should be refactored and spun out into a microservice.
-
@Arantor said in Is water wet? News at 11.:
@CodeJunkie is that a microservice? If it isn't maybe it should be refactored and spun out into a microservice.
It could be.
-
