I use copilot on a daily basis for programming. It has made me much more productive and it’s a real pleasure to use it. Nothing overhyped about it.

Curious to see what it will bring for other domains, e.g. for dealing with emails.

I do agree that there’s a lot of filtering happening. Not a huge deal for more applications. Luckily you can run your own models that are not filtered. I can definitely see a future where you run your own models locally. Afaik Apple recently did some stuff around that.

I can strongly recommend the SponsorBlock extention (also available in revanched).

Netherlands too. Amsterdam is even planning to change major inner city roads to 30km/h (minor roads already are).

Check out the Law of One for some funky spiritual stuff. There might be something in there that makes sense of this reality for you.

It knocked my shoes off

Definitely dead here.

Absolutely true, although imo not necessarily as a conscious choice. It’s simply earth’s feedback systems. We cram all kinds of animals together and accidentally breed highly contagious viruses, which come back to bite us in the ass. We destroy biodiversity and now people in certain parts of the world have to manually pollinate crops, because the insects all died. Etc.

If all goes well, earth will find a balance again that still favours life (possibly not human life). If not, earth might end up like Venus. Not a big deal for earth, but a bit of shame of all this life we currently see here.

That’s very broad. Do you mean by some force outside our universe, or actors inside, possibly on earth?

Oh, it should absolutely be the team’s decision and you’re also totally right that Kanban requires a more mature team. People indeed need to be able to recognise and ask for help when they’re stuck (which means being vulnerable, but also simply being able to formulate the right questions). People also need to be able to give feedback to their team members when they feel or see that someone is struggling or not delivering enough.

To facilitate I always have some form of retrospective in my teams, even when doing Kanban. Sometimes only once every other month, sometimes every two weeks. Highly depends on the maturity of the team and customer.

I work in a company where we say that everyone is an expert (and to a very large extent this is really true). We create teams of experts, including more business savvy people. Everyone respects each others expertise and makes sure they can apply it as best as possible. We don’t infringe upon each other’s expertise. We might ask another expert about the why or the how, but we should not assume we know better. Obviously this happens sometimes, but then we remind each other that we’re all experts and that an engineer wouldn’t like to be told by marketing how to do their job either.

I think this fits nicely with ‘stay in your lane’ and actually makes it easy to remind people to do so. It’s in the core values of the company that people excel in their lane and cooperate with people in other lanes.

I would even argue that points, stories and sprints are not things you need. If you go kanban, you don’t need sprints. You still need to be producing and you probably want to get a feel for complexity so you can prioritize, but that can be done without points.

Stories are also very scrum specific and you can turn them into whatever format you want. I usually still call them stories, but they’re basically just a little card that describes the context (why do want something) and the deliverables (what will be implemented to meet that want).

I started a little over half a year ago with Go, coming from Python like the author. I definitely enjoy working in a strongly typed language and Go is usually quite fun to work with. This week I’m actually implementing a concurrency pattern for a ‘real’ problem, so eager to see how that works irl. I’ve yet to come across something where generics really make sense, but definitely curious to explore that with a real case as well.

When smart watches came about I thought it would be cool to be able to look at your watch when a notification comes in. Never ended up buying one and when I see how some people behave, I’m glad I never did. Some people will just glance mid conversation at their smart watch, which imo is just as bad as grabbing your phone mid conversation.

I’m happy with my cheap Casio. Looks heaps better too.

I work in IT and we have truly self steering teams without formal hierarchy. Not everyone is used to it and IT people can be interesting characters, so it’s quite a process to get the team to perform well.

I see some tourists wear one in Amsterdam. Very rarely a local, of which I always assume they’re ill themselves or easily get ill (immunocompromised and what have you).