Had a client just last month that were doing SOAP wrong somehow...
Required a SOAP message, that contained no XML after the message tag, but instead the entire message body was to be a JSON, and responded with a JSON if something was wrong, and a fully formed SOAP message if things were Ok.
That and the guys that handle your money use the Http status code as their personal error messages. Except when the error is on their end, in which case they return 200 and a JSON with an error message.
There are plenty of ways to do REST wrong, so let's not lump that into the people that make blog posts complaining about X because X is broken, and working just fine...
As someone working with this setup right now, coming from what is fondly referred to around here as the God-Monolith of our 1.0 version, I couldn't disagree more....
But as always, this is an artform, writing and designing, not laying down pavement.
There's no "right" way, and any blanket statement about anything is false.
Don't use microservices where they don't make sense, make educated decisions, and choose the best option for your situation.
It made sense in our situation, because all our services have very very very specific rules and boundaries and there's no overlap anywhere.
Not everyone should learn to code, just as not everyone should become a chef.
Not everyone will need to program,
not everyone will be inclined to learn it and not everyone will enjoy it.
This bothers me a lot.
I see it quite frequently that "Not everyone should learn to code". Especially with comparisons to other professions...
As if "Knowing how to code" is the same as "Being a chef"...
"Not everyone will need to program", in the same sense the not everyone will need to know how to cook?
It's true, you don't have to in this day and age. But for it's bloody helpful if you do...
Don't get me wrong, not everyone should be a software developer.
But the considering that you use things that run on code every single day,
for the majority of your waking time,
it'd probably be a decent idea to know the basics.
In the same sense that if you are a car driver,
having some basic knowledge of the rules of the road and a basic understanding of physics,
while not necessary to drive, is still bloody helpful.
Now, to comment, as a developer, on the article, it's still good and the part about tutorials is so very true it hits almost a bit too close to home.
Find a tutorial that assumes you're 5. Learn conditionals, understand them. Learn loops, understand them. One. Step. At. A. Time.
Also, the first point just isn't true. I've spent quite some time teaching kids code and Everyone can learn how to code. Even that dyslexic kid with ADD that's chasing the squirrel during class.
Not everyone can get GOOD at writing code. And being a developer isn't for everyone. But LEARNING HOW TO CODE, is something Everyone can do.
Problem is that companies of that size are selling "Your dream and life!" and not a job.
With 200k on the table and a plethora of perks, nobody thinks "Yeah no, I'll need to pass this up because I might quit in 5-10 years and go to another somewhat similar company".
We built a shitty FB app with some fancy features and sold the shit out of it as the next big thing in that space.
It was average at best, they bought it, we made bank, worked for half a year and left to start a company doing what we want to do, without needing any funding.
Required a SOAP message, that contained no XML after the message tag, but instead the entire message body was to be a JSON, and responded with a JSON if something was wrong, and a fully formed SOAP message if things were Ok.
That and the guys that handle your money use the Http status code as their personal error messages. Except when the error is on their end, in which case they return 200 and a JSON with an error message.
There are plenty of ways to do REST wrong, so let's not lump that into the people that make blog posts complaining about X because X is broken, and working just fine...