gamma3's comments

Some projects have been using Slack or Discord lately.

I've had almost all my questions on Stack Overflow answered, usually very quickly.

If you frequently get 0 answers, work on the quality of the question - clear, short, include clear code snippets.

This makes sense. However, what kind of company culture does this set? If the company is OK with people being not passionate, what kind of signal does that give to the colleagues who want to be eager, passionate, driven?

Over the years I worked on native desktop apps, mobile apps, a Scala backend.

Now I work on a complex React app in TypeScript with a GraphQL backend in TypeScript. I can build a feature end-to-end. From domain modeling to an API to UI with animations. Optimising SQL queries.

There are people like this. Software engineers who have experience across the stack.

I don't do devops but I've met someone who can do full stack app development and devops pretty well too.

Having both the frontend and backend in TypeScript helps.

Looks good to me. Nice UX. Normal users don't care about the URL and you can still copy the full URL if you want to share a link.

Whoa, those are some ugly earphones.

> Why should someone ever need to offer a bug-fix bounty!?

Author expects bugs in open source projects to get fixed for free, by someone else.

We need to support open source maintainers instead of shaming them. I'm excited about Open Collective and made a monthly donation to a project I use.

Also compare to some European countries, like the Czech Republic, where all the top universities are free of charge.

Training for a trade job is free of charge, too.

(Paid by the government.)

I got my education there and later joined a Silicon Valley company as an engineer.

Really nice! The Result reminds me of Validation from Scala.

In Scala you return a Validation that is either a value or an error, and can pattern match on it. Also: trySomething().orElse("Default value")

One way would be to share the article with them and explain that replies directly in a channel make it harder for you to catch up. Saying that threads make it easier and quicker for you to decide what to read.

I usually start by proposing an idea to a small group of people - e.g. my team or people at the company I think might like the idea. Only after a few people say they like the idea and start using threads, propose the idea to more people and say "look, a few of us are using threads and it works".

They should cc you so you get a notification. Or talk to you on person.

They shouldn't assume everyone will read every message. If it's important, they should make sure you definitely saw it.

If you ever feel like you missed and important decision, go and politely tell them to always get you involved.

I've worked at a company that did the sprints, planning, retro, Three Amigos etc.

So glad we don't do any of that at my new company! And it turns out we ship stuff much faster.

I've done the same - replace social media with Kindle. It's so good.

And lock screen notifications are off for all apps. I only see a notification badge when I decide to pick up and unlock my phone.

It's possible to have structured conversations by always using threads.

I've convinced everyone at two companies so far (50 and 20 people) to never reply directly in a channel, and always use threads:

https://medium.com/@martinkonicek/how-to-slack-6f5bf9be71ba

I close Slack and focus on coding. I take short breaks from coding every 1-2 hours, and check Slack.

Replying to someone 2 hours later has never been an issue.

If it's urgent, people drop by my desk.

Definitely don't have slack on my phone, and when Slack is closed, I don't get any kind of notifications.

Being able to focus is important. In the end it matters I deliver on the project, not that I reply to every question immediately.

I've interviewed engineers on computer science problems on a whiteboard and those who did great turned out to do great on the actual job.

That's a one way implication. It is possible there are people who do poorly on coding interviews but great on the job.

Whiteboard coding is simply a quick test that has few false positives in my experience (around 40 interviews).

The more values I select, the more matches I get. This should be the other way around.

It should be an AND filter on the values.

I've learned TypeScript and introduced it at my company. It's awesome.