186 karma · joined December 23, 2023
What was interesting to me was the self-fulfilling prophecy of dysfunction: because there was so much manual process and red tape, the cost of fixing a particular problem is larger than than the benefits (i.e: time spent on the task exceeds time saved by automating it).
But because the tasks do not get automated, the amount of time required to fix things increases bit by bit due to the processes in place. The cost of fixing a task increases marginally every day, and so the cost/benefit ratio increases every day, becoming further justification NOT to fix things. At a certain point you have to look at the bigger picture and recognize that there is a much larger problem in your company than a few excel spreadsheets that could be better automated.
Unfortunately, the European economy has been stagnating for the 16 years since the financial crisis and median salaries are FAR below American ones. I would not gamble on the EU economy holding up as demographic pressures and regulation push productivity and GDP into negative territories. I also wouldn't bet on the healthcare systems getting any better from this point on. Europe is in for some rough decades coming up
Also The Windows API pattern is typically:
1. Initialize a "descriptor" struct
2. Pass that descriptor struct by reference to a "create" function
3. Get ComPtr<> for resource
Where a ComPtr<> is a smart pointer that manages the lifecycle of an object across different processes
Also Windows built UTF-16 support into their APIs 30 years ago, so a lot of API calls involve constructing UTF-16 literals
Perhaps if you work on very small projects
The total number of employed people goes up because the population goes up. The labor participation rate has been steadily declining for a while, only really increasing since 2020 as a correction to return back to pre-pandemic levels, which were still on a decline.
There is a myth that displaced workers will result in a higher unemployment rate. The official unemployment rate (U-3) shows people who are looking for jobs and cannot find them. In actuality, displaced workers often leave the workforce entirely and manage to survive in ways not registered by the Bureau of Labor statistics (often through government entitlement programs and welfare). Men, in particular, are more likely to drop out of the labor force when they've been made redundant. A whole generation of young men are declining the enter the labor force at all, opting instead to live with their parents long term or use school as a way to avoid getting a job.
People who worked in blue collar jobs and agriculture and were displaced over the course of the 20th century didn't all get "better jobs", many of them languished in broken communities and died deaths of despair. The coal miners didn't learn javascript
But that can be mitigated by aliases and tab-autocomplete. I usually start typing the verb ("Start-", "Get-", "Convert") and then just tab through the nearest results. Windows Terminal also has pretty good auto-suggestions from your history so commands I run frequently get remembered.
You've also got all of .Net at your disposal; I've created cmdlets that connect to a postgres database for debugging purposes
But what I like most of all about Powershell is that everything is properly typed instead of dealing with streams of bytes. I noticed when I worked in a company with mostly macbooks that most of the engineers weren't really doing the unix "pipe-everything-into-different-commands" philosophy, but were mostly just putting log files into jq and then running all of their queries with jq's language. With powershell, you can convert json (or csv, or yaml with plugins) into a native structured format and then do your queries directly in powershell instead of relying on third party tools
It took some getting used to, but I can't imagine going back to bash or zsh now