Location: London, UK

  Remote: Yes, also open to hybrid and office

  Willing to relocate: No, longer term maybe (EU passport)

  Technologies: Ruby, Elixir, TypeScript, JavaScript, Node.js, Python, Go,
                Shell, Bash, SQL, PostgreSQL, React, Svelte, HTML, CSS, Git,
                Docker, Git, Kubernetes, Linux, CI/CD, Rails, Phoenix,
                AWS, data pipelines, RMQS and other messaging/queuing systems

  Résumé/CV: https://github.com/dideler/resume

  Email: ideler.dennis AT gmail.com

  GitHub: https://github.com/dideler

  Gists: https://gist.github.com/dideler

  LinkedIn: https://linkedin.com/in/dennisideler

  About: On a technical sabbatical and not actively seeking employment but open to opportunities.
         Over 10 years professional experience, primarily in backend roles but am well-rounded.
         Enjoy wearing different hats. Practice agile/XP but guiding principle is being pragmatic.
         Have worked in various industries and teams, including highly effective product focused and data-driven teams.
         Good at seeing things from different perspectives and knowing when to challenge and when to disagree and commit.
         Have held director positions in small companies, and consulting positions in medium companies.
         Can zoom in and out for small/big picture views, know how to lead and work with stakeholders.
         Mission-driven and proactive in my work, with an emphasis on clear communication and accountability.
         Preference for part-time or reduced work week (with relevant pay cut) as I'm a new dad.

1: https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...

These are people who see two levels of hierarchy requesting something for months and then builds a prototype over the weekend that solves 80% of the problem. Who sees two teams arguing for days back and forth and gets them together to make a decision with them and moves on. Who sees the hours wasted every day on bad tooling and bloat and makes the bold decision to cull and simplify. Who sees a product team losing a quarter building the wrong thing and is not afraid to shut it down with the boss. They know how to hire A players and raise the bar. They know when to hire. They know when to let people go.

They are not 10xers relative to 0.1xers, these are everyday 1xer situations.

They consistently have multiple magnitudes of impact. That's not easy. For most of us that happens a lot less.

But I will say that I sometimes appreciate hearing it when I'm overcomplicating things. It reminds me to keep it simple.

E.g. not having the authority, being the wrong person and sending you in another direction, putting the onus on you to move things forward, not responding to emails and calls, ignoring questions and selectively answering, not making contact details or policies available, and so on.

What's the most disturbing for us are people on on scooters, motorbikes, or cars with modified mufflers or engines and excessive revving. Much more frequent, and they love cruising at all hours of the night.

The fingers and palm were analysed in the photo. There's a better photo here: https://www.merseyside.police.uk/news/merseyside/news/2021/m...

Without any image processing, we can already see palm prints and the ridges and lines in the palm and fingers. These are unique biometric identifiers. In fact, palms have more identifying characteristics than fingerprints.

They are almost certainly telling the truth in this story.

For many, including me, it's not some inconvenience that we are okay with. We see it as a selling point.

I've tried them all and Apple's balance of openness/security/quality is the best I've experienced. If they follow the direction of others, I'd probably jump ship.

What other iconic works are there that give you an idea of what's happening in the world?

Time, New Yorker, ...

- kill services with low usage

- downgrade instance size

- downgrade instance type

- merge databases

- schedule services with obvious usage patterns to shut down when not used

- use EC2 spot instances

Most importantly, it requires an aggressive culling mindset. If drastically reducing the AWS bill means staying afloat, then make bold choices.

Bad linters are expensive. They add complexity to workflows and pipelines, slow down iteration speed, and create a nitpicky culture where most discussions miss the point. Multiply this by a whole engineering team, yikes.

Yet there are some good (parts of) linters, such as catching actual issues rather than preferences. If we bet on linters, they should increase our value multifold to be worth it.

rubyfmt for Ruby