Harassment: ASML, 1st team: PO pushing features

Tue, Mar 18, 2025 ❝PO relentlessly pushes for new features, caring only for business prestige❞ important I did not want to finish this post. However, I keep being pushed into the same abusive process, over which I have no input, no control, no ability to verify or scrutinize. A process which interferes both locally, i.e. in my home town, and on the internet. Which abusive people time and again push me into without my constent, without acknowledgement, without checking. And that, the way it is presented to me, operates on mutually inconsistent and/or mutually exclusive rules, making it a never-ending process with no proper resolution.

Harassment: ASML, organizing "Knowledge Sharing Sessions"

Thu, Feb 27, 2025 ❝Knowledge Sharing Sessions that survived a cancellation attempt by (supposed) "co"-"organizer".❞ In the first team, around the time we finished a large project (see another story ..), we figured there was plenty of knowledge that needed sharing among the team members. We also recalled the earlier prototype that few people knew the details of, one of the seniors having previously left the team. Meeting to share knowledge During the larger project, we had also had moments where some people were split off to perform maintenance on the legacy applications, while others worked on new applications.

Harassment: ASML, Dependency Injection

Mon, Feb 24, 2025 ❝Attacks over opinions on CDI (or was it about influence?)❞ This story is the root for many attacks, claiming I’m incompetent, claiming I’m starting up discussions to frustrate and delay the (in my words) “generally accepted enterprisey way of doing things”, not capable of understanding CDI, etc. I’d like to set the record straight. Furthermore, without understanding how, several people outside of ASML suddenly commented on this and attacked me over this, so now I want to set the record straight.

Interim: ASML, Proguard

Sat, Feb 22, 2025 ❝Obfuscation done wrong in 7 little disconnected bits.❞ This story is itself not so much about harassment, but is likely a lead-in to other attacks. Even if just for context, I’d like to share this story. At the very least, it illustrates my own attitude towards solving real problems, improving circumstances and ASML concerns. Context and chronology This story also happened quite early in my first year/first team. I’d guess a couple of months in. I started hearing something about Marketing department being frantic about Java applications being fairly easy to reverse-engineer, and probably some of the business.

Harassment: ASML, group lead team composition fuck-up

Sat, Feb 22, 2025 ❝The group lead was asked to compose a team, created problematic team against seniors' advice.❞ My group lead is a Romanian that migrated into the Netherlands years ago and has (apparently) worked for ASML for a while. I started out with another, but he had planned to switch to a different department before we even had the first meaningful conversation. Although I think I would have liked that group lead, it doesn’t matter practically as I had just barely started. On curious thing: this “manager switching away wherever I first join”-thing, is a pervasive “quirk” for virtually every employer I’ve been at.

Harassment: ASML, STI assisting with release management

Thu, Feb 20, 2025 ❝STI department enjoying an oppressive role in application integration and releases❞ Now, this is a rather interesting topic. STI is a department that is supposed to assist developers by tackling integration and release work. However, this turns out in practice, to contain a significant proportion of “policing unit” in terms of interaction with development teams. This article essentially adds onto Interim: manual builds and continuous integration. Introducing STI STI, “System Test and Integration”, is a separate department that tackles system-testing and integration.

Interim: ASML, manual builds and continuous integration

Thu, Feb 20, 2025 ❝Manual builds and continuous integration evolving.❞ In the first months of arriving at ASML, possibly even in the first month, I was asked to assist with building the application and preparing the application for release. This was a manual process at the time, i.e. assisted by Apache Maven for the builds. There was surprisingly little in attacks surrounding specifically these topics, though some connection with Proguard is discussed in another topic. This post is essentially an interim that further describes my contributions.

Harassment: ASML, 1st team: team architect conflicts

Wed, Feb 19, 2025 ❝A team architect role with a lot of overlap with the devteam.❞ Okay, so this is essentially utterly ridiculous. This essentially started as soon as I started working at ASML, with ASML being the customer of the consulting company. This story was forcibly made relevant, because ASML seemed to think it funny to set up circumstances in the third team to eerily similarly reflect those of the “team architect” conflicts in the first team. Except, when I joined the third team in the role of “team architect” (which I always – I think correctly – mentioned is not really or very limitedly an “architect” role, due to the limited scope), by then I had a very clear view of how I would fill it in to not interfere with other team members.

Harassment: ASML, licensing (partial)

Wed, Feb 19, 2025 ❝The licensing mechanism (still?) used by ASML.❞ I decided to make this my first post after the introduction, because ASML has been an integral part of coordinated long-term harassment that has been going on for 20 years. For 6+ years afterwards, I have tried to make things work, while having to deal with persistent, continuous harassment, abuse, and threats about supposed “bad things” I did. Things I never did or never did wrong, that were grossly misrepresented, that were made up, or were malicious fabricated from independent events.

Coordinated harassment - introduction

Wed, Feb 19, 2025 ❝Introduction to a series on coordinated harassment in the Netherlands.❞ So, it has become apparent, mostly by means of persistent years-long manipulation, fraud, abuse and harassment, that there is a pervasive attitude of coordinated harassment. This resulted in being needlessly attacked at various companies, i.e. employers, and an incessant obsessive need of people to deceive and make up arbitrary lies. This has been a pervasive presence in most places that I have been at, to varying degrees. This is my way of documenting all the crap I’ve had to deal with, that will focus for a large part on employers as one tends to spend a significant amount of time in employment and knowingly or not and willingly or not gets exposed to these practices.

Timelessness