Sorry to hear about your unfortunate experience. I bet everyone would get shaken up after getting an opportunity like that taken away, AFTER it was already confirmed that you're getting it.

One thing I'd like to touch upon is you saying that it cost you 5-7 years of your career. Is that really the case, though? Hear me out. I've been employed in a couple of workplaces where I've had similar experiences: employer dangling a shiny thing in front of me in the shape of a promise. "You're nearly there, it'll come soon enough. You just have to work hard." As you can imagine, the shiny thing never reached the palm of my hand. The first time it happened, I worked insanely hard with my rose-tinted glasses on. Took me a while to realise that I'm wasting my time. Once I made the decision to leave in search for better things, I was well equipped to jump higher than before. I already had the skill set AND the internal bullshit detector was calibrated. The second time it happened, I didn't waste any time. Jumped ship, got employed at, what I consider, a dream job.

The point I'm getting at is that you never truly waste time unless you're coasting. The experiences you've had add up to the person (professionally and personally) you are now. It might've taken you longer to achieve what you've set out to do but you got there in the end. You must be happier that you're the CTO at the company you're in now rather than the one you mentioned anyway, right?

The ol' cliché "the journey is the best part."

> One thing I'd like to touch upon is you saying that it cost you 5-7 years of your career. Is that really the case, though?

My decision not to sue certainly was. Note: my decision. I'm taking responsibility, not blaming the company. I'm not going to get into more detail simply because I've gone over it quite enough for this decade in my previous post.

We use it exclusively in CI/CD to provision/delete resources. It keeps track of everything created via Pulumi (or imported from outside of it) in a config on the cloud. Haven't experienced random resource deletion apart from genuine user error.

I've been using Pulumi for the past few months as a person who's never touched infrastructure-as-code before. I love it. It has its downsides in the documentation. Mostly around limitations in resource name lengths.

Apart from that, it's an amazing tool to work with. The company I'm working at right now uses it extensively. All of our microservices have Pulumi in the CI/CD pipeline. It's an extremely powerful tool and I'd even use it for personal projects over provisioning resources through a vendor like AWS.

Yeah, it has been a while since I used it, but I remember having to fall back on Terraform docs more than once. But it really is nice being able to ditch Terraform DSL with your language of choice.

And when I used it they also had quite permissive pricing for personal use, where you could store your tfstate or equivalent on their servers which is nice as well for solo devs, who doesn't want to build or shell our for a storage platform or CI for terraform.

The only thing I had some problems with was errors, which wasn't the easiest to decode. But it wasn't too bad.

Agree with the errors but I believe they've gotten better/you get used to their true meaning after a while. It's a complex piece of technology so I don't bash them for it too much

How do you add it to CICD? Does it pull down and create infra every new push to the master branch? What does the workflow look like?

I always had this issue but never thought about looking it up on the CRA side of things. Thanks for the drop of knowledge!

There are more countries in the world than just North America, though.

Location: UK/Lithuania (EU Citizen) Remote: yes Willing to relocate: no Technologies: C# .NET & .NET Core, React, SQL Server, AWS, Azure Résumé/CV: available via email Email: raulis [dot] masiukas [at] gmail GitHub: https://github.com/Kunigaikstis About: Software engineer with multiple years of experience, leading a team in my most recent role, looking for a new role. Capable of working in a team or autonomously, care about the quality of code being pushed to production. Most of my experience comes in .NET and React but I'm really interesting in moving into a role that allows me to work with Go.

Following the DDD practice at my current workplace. Hard to get into initially but it forces you to write modular code. Ramp up has been slow but nowadays, unlike previously, I'm able to write whole services with tests before even running them. And feel comfortable that they'll work. But that might not be solely down to DDD.

For a couple of years now, I've been developing features for a product that hasn't found product-market fit. Features that nobody _really_ gives a shit about. I can talk directly to one of the cofounders, bring them evidence based on analytics or the past failings of the giants upon whose shoulders we're standing on. His response is, majority of the time, "yeah, I get that. We promised this to a few customers and I really think it'll work". It hasn't worked.

You need to ask him to define success and failure for the feature. Under what conditions will he accept it has not worked

It's an iterative process. Our conversations have gotten better over the years. He has the connections and market knowledge so I have to respect his wishes most of the time. I make it sound bad but it's because I'm, like many of us, tired.

There is website for that : http://tired.com

People like that are often immune to objective measures.

How would I apply?

Oh yeah, forgot that! Let me update..

I gotta say, I'm really loving all the websites built with Tailwind (assuming this is built with Tailwind UI). It's like going back to 2011 bootstrap everywhere days but so so much better.