Tknl

This makes me think of https://github.com/AutoFixture/AutoFixture

It's not only common you can in many instances force your employer to lower your hours and keep you on.

I've successfully pulled off most of such a majority re-write but a key driver - but not the only was that the legacy language the existing system was implemented in had lost virtually all traction in the local and global market. Mostly only expensive contractors coming out of pension availabile and on top of that the custom libraries required us to recruit the 10 percent of that segment. Any new hires straight up refused to pick it up as they accurately deemed it career suicide.

I second this approach. I've utilized it successfully in an ongoing migration. I also second the need to have engineering knowledge from the previous system available. I was lead for 5 years on a previous system before being tasked as solution architect of new total rewrite to cloud native. The hardest part of such a migration is maintaining sponsor buy-in while you build the parallel run evaluation strangler fig integration with the old system and get some existing flow polished enough to take live. If you happen to have a rule or scripting system in place piggy pack off of it so you can do an incremental migration.

I installed MX Linux years ago and have not looked back. It has been incredibly stable and easy to upgrade. While I had ubuntu and mint regularly get trashes on system updates in the past.

I've found the best way to evaluate the quality of npm libraries is to use Snyk analyzer https://snyk.io/advisor/check/npm

I'd argue that what Match Group did with OKC was bordering on criminal. Everything on it worked and it worked for small, often marginalized groups. It was turned into a worse version of tender.

I would argue that numerous initiative to ban highly dangerous substances such as the Montreal Protocol banning ozone layer damaging refrigerant gasses have been successful in this period. Instead it appears to me that global collaboration actually stalled after the fall the Soviet Union and the end of great power competition.

https://slsa.dev/ gives much clearer explanations about the why of this work. Github recently started offering a SaaS sigstore implementation including support for private reps. https://docs.github.com/en/actions/security-for-github-actio... Anyone working on OT should be quickly moving towards this.

N900 was my first smartphone and still miss the feeling of having a proper Linux box in my pocket. Unfortunately didn't buy the n9 as it was clear it was dead in the water by the time it came out.

Based on my contacts at Nokia it was simply underfunding, believing that symbian would remain dominant in developing countries and seeing the meamo/meego line as a distracting and expensive side project as well as internal competition which people sought to sabotage internally. Some ex-Nokia people blogged quite extensively on it.

Yes, this is abusive as your compensation doesn't grow with your time working. Your salary is based on an x hour work week. This system incentives poor software quality at the cost of your and your colleagues' time. My role and those of my direct colleagues is also salaried similarly with expectation of some overtime without additional comp, but that should be a rare hour or two. I do know of/work with other companies that have similar terms around on-call as yours. My employer does only 1 day at a time per engineer with a repeating 4 week schedule but we also have a support call center taking care of the majority of calls and only escalating to on call when necessary.

In the EU there are definitely companies providing aggregated salary band norms, in fact utilizing them is nearly required by upcoming EU directives as salaries must be justified by HR. In the Netherlands I know Bureau Baarda is gathering and selling data.

Interesting use of tsnet. For new cocktail recipes I regularly check https://cocktailvirgin.blogspot.com

I can confirm it does. Although I moved to a country with more direct auti friendly communication (USA to NL) and only recently realized I'm likely on the spectrum and this heavily motivated my desire to move here where communication is much more direct.

The Netherlands is struggling with a lack of grid capacity due to political decisions to ignore the power network management companies that pleaded for at least a decade for expansion.

As a hiring manager I can understand this view. I'm also in SaaS dev. But in the Netherlands at least most of the raising IT salary demands aligned with inflation, particularly if one includes housing market inflation. People are not going to accept a salary which still won't get them towards homeownrship with dual incomes if they can avoid it.

I usually see this style from people with a mathematics or physics background instead of CS. Their coding style doesn't take maintainability or collaboration with others into account. And these programmers therefore produce code which no one else is able to change when they inevitably leave the company after some technical strategic direction change happens which they disagree with. Allowing them to dictate your coding standards is putting your company at risk. If getting them to confirm to (tooling automated linter) coding standards is impossible I'd personally isolate their code to specific packages with clearly defined interfaces so you have some hope of replacing it after their departure. Make a working agreement with them that coding standards apply to any PRs outside of their pet projects or they'll get rejected.

Don't forget Dutch citizens voted previously in a national referendum against mass surveillance which was promptly ignored and the right to call a referendum repealed.

Your company hires the audit. Interview the to find one that gets zero trust.

Have you tried showing results of code qualify scanning tooling such as sonarqube or sonarcloud? This should show a downward pressure on quality.

The moral panic around snus is ridiculous and causes great harm. The EU has a snus ban that has little scientific basis while Sweden with an exception has the lowest lung cancer rate of Europe.

AWS is noticeably absent in the list of implementations.

Your anecdote is in the basis correct. Very few relationships which start closed and go to open/poly survive as you do not have the required communication skills or emotional intelligence to make it work. This is usually developed over several failed relationships, similar to monogamy. I suspect relationships that start out polyamarous have a similar failure rate to nonmonogamy. Also, it is advisable to find local poly meetups to get social support and hear about what works. I've been polyamorous for around a decade and I don't date anyone that is just learning the ropes. It is too much of a risk to my existing relationships. Some of the skill sets required are covered in the book Polysecure. Trying to become poly to save your relationship is almost certainly going to fail. Do some marriage counseling first and then consider it if you have an emotionally secure base, but be aware it still likely will blow up.

I second this. I've been interviewing candidates for around 6 years and I feel like the number of applicants with very strong communication skills but that cannot perform the most simple programming problems (basic loop, swapping two variables) went up. For my team and most teams at my employer we employ a simple test with a basic programming problem, code review problem and rudimentary system design problem similar to our actual work. We expect the juniors and medior to not succeed at all of these but do want to see how candidates think and communicate if they get stuck, but a junior that can't sort strings in any language of choice is a hard pass. Half of our candidates past initial phone screen fail this test. I do wonder though if this has something to do with the local (NL) market.

Back when I was a junior engineer I made a small system for dealing with industrial printers that took either direct printer language commands or pdfs and exported the printer driver output to a file via the Redmon printer driver output file exporter and then ftped it to the printer over the network. This avoided manual driver installation of hundreds of printers and may still be sold in a new project. It's hacky af but still works and beats alternatives.

At my employer teams are preparing to extensively use hybrid AKS. I'd really appreciate hearing any of the issues encountered.

Probably architect.

American that naturalized after moving to the Netherlands here and I can confirm.

Also, poorly performing engineers will sometimes be promoted into management roles to get them away from the code. Now the incompetent guy in the team is your boss.

I would also add that if companies attempt to give technology specialists higher salaries they will often run into problems with their financial auditors claiming a lack of market conformity.

Docker provides virtually no security guarantees on its own and container rights escalation vulnerabilities are a serious threat vector. The default containers provided by many applications are often insecure and ignore recommended security hardening practices. Seehttps://kubernetes.io/docs/concepts/security/overview/ 4 c's of container security.