Felix Mulder

With certain tools you can't afford to later realize your mistakes. I don't want tools like that.

Such beautiful error messages https://twitter.com/tpolecat/status/1086657490052206592 …

PostgreSQL has so many neat features - this piqued my interest today: https://www.postgresql.org/docs/9.1/sql-listen.html …

This is the only way I'm going to introduce my work now - "I write code for Snoop."https://twitter.com/jmglov/status/1086139489939013632 …

Show us you're excited about technology, humble about your flaws, willing to put the team first - we'll get to the rest of the things, I promise

We're not in the business of hiring rock star programmers. We're hiring someone who's great at working in a team. If you've got mad tech chops, that's great - but if we don't think you'll be able to collaborate and get along with your peers, then that doesn't matter.

Dev claims that pair/mob programming is only *good* if the participants are at the same level. A senior dev should expect to be both teaching their team and being taught.

Dev tries to prove that they know everything. Most people haven't worked with all technologies and that's OK. Point that out by saying "I haven't worked with X, I'm eager to learn"

Dev takes a really hard stance on a technology choice that is highly subjective. Shitting on something does not show your best side - I promise.

Junior devs, ya'll got the least to worry about when interviewing. Senior devs have a lot higher demands, and a lot of times people feel that pressure and act in weird ways. Here are some examples:

If your company is using a library and you're missing something - consider contacting the author and paying for the feature. If you don't have time to do it during your paid hours as a dev - why would someone have that time during unpaid hours for something they didn't need?

We have a refactoring exercise as a part of our interview process at Klarna. Yesterday, we added Haskell as an option to do the exercise in. So we wrote the most repetitive, horrible code we could - and the mess is still shorter than nearly all the reference solutions.

Why am I writing a production Haskell tutorial? SMH...

Forgot to update pacman's pgp keys before updating Removed chrome before, no browser on computer Search for answers on phone

But I'd happily trade some snappiness for a type system

That being said: tooling and error messages are really helpful. Expo works really well and the feedback loop is rather snappy

Playing with React Native for a pet project, it's pretty cool. I enjoy the workflow of instantly getting my app pushed to my device so I can see the changes -- but the lack of even the smallest guarantees is appalling. Stringly typed logic everywhere.