wgroeneveld
/
brainbaking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

a few typos

This commit is contained in:
Wouter Groeneveld 2022-05-13 17:22:15 +02:00
parent 34b6a8e3d5
commit 0948ce8d18
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/wmpics/pictures/minutestomidnight.co.uk.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

10
content/post/2022/05/my-programming-language-odyssey.md
View File

@ -26,17 +26,17 @@ During my university years, I dabbled in Nintendo DS development by helping port
## First work years
When I graduated, I had no idea what I was capable of (read: nothing), so I applied for a job as an analyst. Not knowing what I was getting myself into, I quickly changed course and landed on an enterprise Java consultancy job. Ant, Maven, Glassfish, Tomcat, RabbitMQ, more awful enterprise shit, ... I can't say I hated all these things, as they were new and exciting to experiment with. Still, programming at big companies wasn't like they made us believe it would be like.
When I graduated, I had no idea what I was capable of (read: nothing), so I applied for a job as an analyst. Not knowing what I was getting myself into, I quickly changed course and landed on an enterprise Java consultancy job. Ant, Maven, Glassfish, Tomcat, RabbitMQ, more awful enterprise shit, ... I can't say I hated all these things, as they were new and exciting to experiment with. Still, programming at big companies wasn't like they made us believe it would be like. In the early 2010s, I also dabbled in Scala (too difficult) and Groovy (too loose), two hyped-up JVM-enabled languages that also compiled to bytecode.
With back-end stuff came front-end stuff, and I had much more fun exploring prototypal inheritance in JavaScript and doing silly things in jQuery, back when it was a thing and Node, Npm, or ES5 didn't exist. Enterprise session beans, JSF, JSP, it's all coming back, and it's bringing a throbbing headache. Glad that is over.
With back-end stuff came front-end stuff, and I had much more fun exploring prototypal inheritance in JavaScript and doing silly things in jQuery, back when it was a thing and Node, Npm, or ES5 didn't exist. It was the early days of cool (and fleeting) new languages that compiled to JavaScript, such as CoffeeScript. Enterprise session beans, JSF, JSP, it's all coming back, and it's bringing a throbbing headache. Glad that is over.
With the full stack also came responsibility of storing data, and even though I touched SQL before, this was the first time I saw something on a very large scale. Load balancing, noSQL offloading, entity mapping, Hibernate woes, ... All that. Back home, I tried integrating JavaScript unit tests with Java using Rhino. It worked. Within a year, it was old tech. Cool.
## More work years
Another job meant switching to C# and the world of Nuget, one of the worst package managers I've ever worked with. I also learned a lot of developers are scared and even hostile of change. They don't like to admit they don't know a programming language but don't want to do anything about that. Silly Java VS C# debates usually ended in "my language is better anyway!"---without having to admit they never explored the other side of the wall. Meanwhile, I also dabbled in Scala (too difficult) and Groovy (too loose), two hyped-up JVM-enabled languages that also compiled to bytecode.
Another job meant switching to C# and the world of Nuget, one of the worst package managers I've ever worked with. I also learned a lot of developers are scared and even hostile of change. They don't like to admit they don't know a programming language but don't want to do anything about that. Silly Java VS C# debates usually ended in "my language is better anyway!"---without having to admit they never explored the other side of the wall.
Not that it matters much. I did: they're identical. Except that I missed Maven and Gradle...
Not that it matters much. I did: they're identical. Except that I missed Maven and Gradle...
As a developer working a consultancy job, your bosses are quick to push you towards "Java Expert" or something similar so they can charge more an hour, while you don't see any of it. I was "highly encouraged" to undertake a Sun Certification. Out of protest, I also became a Zend certified PHP architect---in vain: I never got a PHP job. Luckily, I quit consulting a few years later.
@ -68,7 +68,7 @@ That about sums it up. TLDR:
8. Prolog (a tiny bit)
7. .NET 2.0
8. Ruby (a tiny bit)
9. JavaScript
9. JavaScript & flavors
10. Java EE
11. Groovy/Scala (a tiny bit)
11. "proper" C#