NKOTB

Posted April 11, 2025 by rizal | Leave a comment

So you’re a Java coder. You were hot stuff in the early 2000s. Guess what? You’re old school now. Oh, so you’re a C# coder. You were hot stuff in the mid-to-late 2000s. You too – you’re old school now. Ok, what’s new school then, you ask. JavaScript? TypeScript? No – these are the same as Java and C#, except with truthiness, falsiness and nullishness thrown in, just to mess with our minds a bit.

I present to you Python, the new kid on the block.

Schoolkids now learn Python as part of their curriculum. Data scientists worldwide use Python as their go-to, because of Jupyter, NumPy, and especially pandas—libraries that they can’t live without. Python is super easy to install, and it’s available on Windows, macOS and Linux. Thanks to Visual Studio Code, Python also gets a nice IDE. As machine learning is becoming more important, so does Python.

What does this mean? There’ll still be plenty of jobs for Java/C# full stack developers – Java and C# still have the best server-side frameworks. But as the new cohort enters the job market, with a strong preference for Python (and perhaps with an equally strong disdain for JavaScript), I don’t see why Python frameworks such as FastAPI wouldn’t gain in popularity, edging out Node.js frameworks such as Express and NestJS.

Software engineering 2025

Posted November 30, 2024 by rizal | 2 Comments

I wanted to specify the title as “Software engineering state of play 2025” but that would be a bit too lengthy. Also, why 2025, since it’s still 2024? Well, 2025 just sounds better—halfway between 2020 and 2030, and it’s almost 2025, anyway.

Compared to a decade ago, when all a software engineer needed on their CV to snag a decent job was either Java or C#, plus a bit of JavaScript, the two most necessary keywords nowadays are “microservices” and “cloud”, and not necessarily in that order. Add “React” or “Angular” for extra points.

To expand on the “cloud” aspect, it’s impossible to work on a new software project without involving either AWS or Azure. Interestingly, the AWS/Azure (admittedly false) dichotomy is pretty much like the Java/C# dichotomy: the path one takes depends on which one you happen to start in. So, if by pure happenstance your first cloud experience involves AWS, then you’re stuck looking for jobs involving AWS forever.

Another interesting thing is that there are now two spinoffs from the vocation of software engineer, namely data engineer and cloud engineer. To be a bit more precise, a cloud engineer is what a DevOps engineer used to be.

There’s also TypeScript, which personally I like a lot, but only because I’m older now, and I forget what “type” the parameter of a function is supposed to be as soon as I finish writing it.

In summary: unlike 2015, Java or C# ain’t enough for 2025. You also need either AWS or Azure, plus either React or Angular.

situs gacor situs slot gacor situs gacor monperatoto toto slot rtp slot kampungbet situs toto situs slot toto slot toto slot toto slot toto slot rtp slot kampungbet slot gacor toto slot toto slot toto slot situs toto pragmatic casino rtp slot situs slot gacor situs gacor hari ini kampungbet 15 slot gacor gampang menang situs slot toto slot toto slot link slot link slot toto slot slot resmi bento4d bento4d

.NET web dev landscape – past and present

Posted March 22, 2016 by rizal | Leave a comment

Around twelve years ago, the .NET web-based tech stack was most definitely ASP.NET Web Forms, and maybe ASMX web services. A few years after that came WCF and its associated SOAP, XML, and endpoint configuration madness. Silverlight made a brief hyped-up appearance then disappeared. Then came ASP.NET MVC, with Stack Overflow being its very successful poster boy.

Nowadays, interestingly, AngularJS (with Bootstrap, of course), has become part of the .NET web dev landscape. It doesn’t hurt that it interoperates very well with both ASP.NET MVC and ASP.NET Web API. More and more, the cool stuff is being done in JS, with C# being relegated to mere data retrieval.

I think that once it becomes easy and straightforward for Node.js to connect to SQL Server, with internet tutorials everywhere, things could start looking very different at the back end as well.