A micro service is like a "Hello World" program, but thousands of them

It is better than Angular. ;-)

So we are at the extinguish level now:

Embrace, extend, and extinguish

People really need to stop abstracting programming. KISS, SOLID, OOP, Functional, Design patterns, COM, DDD, TDD... THEY ALL FAIL!

They all fail because by abstracting it in patterns, behaviors, principles,.... you give it a death sentence to your project from day one. Your project must represent the real world if it wants to be successful, but the real world is a mixture of different technologies. differnt ideas, different mentalities.

There is no such thing as once size fits all in software development. It never was and it never will be.

The software projects that succeed, they have all one thing in common: A developer that has enough creativity to stamp out new technology from scratch that fits the problem that he wants to solve. He is not a slave of the libraries, he invents the libraries.

For you as a developer it is a death sentence for your career if you blindly follow what others do and never even question if what others are doing is correct?

If you plan to do this for a living...

I want to add, "If you plan to do this for a living, you have to learn 50/365/7/24 so no more social contacts, no more free time, no more relaxed moments". It is basically a life sentence.

"Vlad", does not sound like an Indian name.

Too many different languages that lose support a few years from now why should you even start to learn this?

"This CPU spike was caused by a bad software deploy that was rolled back," adds Graham-Cumming. "Once rolled back the service returned to normal operation and all domains using Cloudflare returned to normal traffic levels."

How is this even remotely possible? How can one line of code cripple a CPU? Yes back when Windows 3.0 existed you could freeze Windows by just going into an endless loop. But we are in 2019 now this should not be an issue!

Imagine how a hacker can, shut down your server with a simple command!

Funny I found my Kylix 1.0 Cd's recently and I was throw them in the garbage can or not. I did choose not to because it is something historical.

Software development is usually carried out by a team of specialists and each does a specific task.

Sadly enough what they sell as specialists, are fired journalists that learned to code.

Also managers believe the hype that outsourcing will be cheaper but we get to clean up the radioactive toxic waste that was produced by an outsourced company.

But in the end they will need us when a spider is crawling their keyboard.

I don't need mentoring, I will do it myself and better.

I don't have the imposter syndrome because I am fully aware what I am capable adapting anyone throws at me. The big challenge is getting past this HR that have no clue what they need or think it is just a bingo game.

What indeed is true that nowadays it is impossible as a developer to keep track of everything companies need. We are in a race to the bottom where developers are use-once-and-throw-away when they burn out.

The learrntocode is only designed to attract fresh meat for a throwaway project and then discard the developers.

However not everything is all doom. It forces you as a developer to adapt fast. You get challenged to become better than the other, you become challenged to have higher quality than the others. This challenge to do the impossible is what drew me to software development in the first place.

Oh their brains are not gone, they just lay low profile because they are top of the food-chain and know when to fight and when to have a low profile.

If you are that old and still be a developer, then it means that you are a survivalist.

But the older generation are still there, just low profile waiting until all projects fail and then they will save it. But it is still a few years from now,.

Didn't you notice the crappy web sites, the failing OS updates, coffee vending machines that sucks,.... Air planes that drop from the skies ?

But they outnumber us at this moment. However survival of the fittest, we will survive.

Probably an journalist that #learnedtocode

The only sad thing in all of this is that developers still can't develop in OOP. One would expect decades later hat by now it would be second nature to developers but yet when I look at the code I have to clean up all I see is classes used as glorified namespaces.

The sad thing in all of this is once your brain is wired to to none-OOP you will never unlearn it and be able to develop in OOP.

If Google etc fire good coders because they don't want to be software engineers, they are fucking morons. Some people just like coding, and are good at it.

Exactly that is why I would never want to work at Google. You only have below average developers.

It is about software and responsibilities.

This is why SCRUM sucks!

IoC is the new hype but they become disaster when your project grows. I don't know who are these people that come up with stupid design patterns like this?

The whole purpose of programming is that it helps you in creating better products, but this IoC thing is plastering your code to as many fragmented files you can get away with making finding bust incredibly hard.

That is what the books say not what is in the real world where they are a pain in the ass.

Our source described a culture of suspicion and hostility that emerged under the new leadership. There was recently an all-hands meeting at which employees were encouraged to ask frank questions about the company's new direction.** Those who spoke up were summarily fired last week, the individual said, at the recommendation of an HR consultant.**

They are systematically converting Windows into Linux. Or basically they are merging Linux into Windows and take over Linux.

Slow compilations,

Me and some people in my team can be hired when our current mission completes. We fix broken projects we inherit that have been broken for many years. No restart of our services are required for years.

You need to get better developers.

A re-tracing of how Paul Allen loaded BASIC on the MITS Altair 8800 from paper tape

https://www.youtube.com/watch?v=2wEyqJnhec8

MITS Altair 8800 Computer - December 1974

https://www.youtube.com/watch?v=i8znuGj_yUY

Altair 8800 - Video #2 - Front Panel Programming

https://www.youtube.com/watch?v=EV1ki6LiEmg

The writer is not wrong however I have an issue with the fact that you try to shoehorn it in some design pattern.

Every time someone creates a design pattern, you end up being taken over by complete idiots that thinks it is the holy grail and all other developer should bow bow down and accept it as the only truth.

The issue with software is that you need a creative skill to solve things, not logical skills. Logical skills will actually make your code worse. Logical skills will prevent you from searching solutions that works better than what you have now. Logical skills will prevent you form asking the most important questions "Is there no other way to make this code more readable?"

Most developers I encounter have a 2D way of thinking. because they are constraint to 2D thinking they don't realize that there is a 3D dimension the can also program into. A 2D solution sometimes gets simpler in 3D developing. And sometimes very creative developers can think in 4D or higher.

If you motivate developers to think in higher levels than pure logical design patterns they may find better solutions that fits as a glove. Not only is the code ascetic pleasing, but faster, better more robust and reusable.

For me software is like having clay. I take, it reshape itt, reshape reorder it, add, subtract, until I get a form that is mental pleasing. The structure of the software should guide you to what it does and why it does it. without effort. I do it by morphing it into 1000 different stages until I get the perfect fit for that job!

These devices are used to control IoT devices, sensors,without WiFi.

Spot on!

Liking Angular is a clear indication that you will fail your next project and the one after that and even after that.

The title should be "Getters/Setters in C++ is an awful programming practice.

Any other language Getters and setters should be used. I had this discussion with a colleague that wanted to improve performance by converting it to fields in C# but I told him it has no impact with modern C# compilers.

Now back to C++. he is an idiot even in C++.

He is right that in C++ you get faster execution and less typing if you use struct and fields. It tells the compiler to optimize even further than the normal optimizing. But as a general rule it sucks!

I did outperform in OOP even hardened C++ developers that developed in pure C. Not only did I outperform the C developer I developed my code at a faster pace.

The OOP development in C++ gives me a very good way to scale my application without losing development time. Using struct or using a class is at assembly level exactly the same thing. in both cases you use the first parameter to pass on the struct/class.

He is an idiot because he thinks he has the answer to all solutions and anyone that thinks differently must be fired. But different techniques are needed for different projects:

• Is this code intended for an UI?
• Is this code intended for high speed calculations.
• Is this code to be developed for a faster response cycle?
• Is this code developed with very small memory footprint?
• Is this code developed for multi-threading?

The advantage of having a struct over a class is that you can very fast memcopy it when you need to clone. In multi threaded operations that needs a massive number of threads you can put this struct inside your class and have minimal locks time when you memcopy the struct instead of field by field. Bang! The advantages of OOP design that scales very well and fast speeds by this internal struct.

People should really stop thinking that software is a set of design rules, patterns and logic. It is a living entity that should never be restricted to design rules and patterns.