tarcio

Tools like Kafka and Temporal have been gaining a lot of momentum lately - the former already has some reputation with the latter gaining a quite a following lately.

Usually I go to Thoughtworks Tech Radar to get myself informed but more often than not I find them to be a bit behind or have a more conservative view of what's trending in companies.

So I thought would be a good idea to ask around what people have been using these days that is making their life easier or that solves some real engineering problems or make difficult problems easy to solve, etc

Basically that. I find that inventing something is a mindset - more than a gift - and you either have the drive/creativity to invent something or you don't.

Keen to hear from founders, inventors, musicians, etc - people who come up with ideas to understand how their thought process work in a very ELI5 way.

Thanks

Basically what the title says. The places I worked for all asked for a code test before inviting me over for a face to face. There has been some variety but the Toy Robot simulator (https://codereview.stackexchange.com/questions/96181/robot-toy-simulator) was by far the most used by the industry here in Melbourne.

I'm curious about what other people are using? I've heard of the Elevator simulator (https://github.com/donnemartin/elevator-simulator) and Conways game of life.

What else people are using that is easy to review, a good problem to solve and ticks most of the boxes you use for reviewing candidates?

One the lessons I learned during my years of Java development was that we had one single artifact for all environments. Later on I learned about the 12 factor app (https://12factor.net/) and how other languages/frameworks adopt that same approach which is great.

Especially around using environment variables: one artifact that gets its values from the environment being served on makes sense. For backend.

But for frontend development I quickly realized that doing this nowadays is simply overkill. With most of the projects I've worked on recently we are deploying to S3 with Cloudfront in front of it.

Which makes environment variable substitution part of the deployment life cycle: you generate your assets to the environment they are going to be deployed and that's cool. Any secrets in it (Sentry, Newrelic, Calibre, whatever) gets bundled in.

What are thoughts on that and how do you do your front end bundling?