After using Prettier to format my code and turning on format-on-save, I pretty much don’t use the tab key anymore. This doesn’t invalidate your point, - I am merely guessing as to why the tab key seemingly has been reassigned.
Their time line UI was really good: Go back in time to see emails and texts. Go forward in time to see upcoming events and weather info.
I was never in doubt about was button to press. I have had my Apple Watch for many years now, but still fumble around with basic stuff like turning on the torch light.
You could select what apps you want to also trigger notifications on the watch. And easily pause notifications for an hour or for the rest of the day.
If your kid is having troubles leaning to ride a bike, I would suggest trying one of the bikes from Woom (https://woom.com/). Especially in the smallest models for 4-5 year olds, these bikes much lighter - almost half weight - than a lot of the alternatives. They also cost a lot more, but the high resell value makes up for some of this.
This is one of the biggest hurdles to getting kids to enjoy riding bikes too. If you think about the weight of many cheaper kids department store bikes they are a significant weight compared to the child. Having a lighter bike makes it much more enjoyable for the kids.
Also recommend Islabikes and Frog bikes for two companies that offer lighter offerings. Again you have to pay for it, but they can often be resold and a decent value later. Especially if you keep the bike clean and loved.
I have a mechanical engineer friend who's deeply interested in bikes, he recently designed and welded his own DIY cargo bike, he gave me an hour long lecture on the evolution of frame geometry and alloys when I asked him to help me pick a second hand bike, etc—and he's very, very impressed by Woom bikes. I got one for my kid and the engineer will just look at it, admire the parts and go "oohh yeah now that's a bike."
Yeah, I agree that StackOverflow it but a shadow of what it used to be, and that this is a shame. But I don’t think that AI is to blame for this - all the interesting discussions had already migrated to GitHub issues. AI is just the nail in the coffin for SO.
My personal experience is that you have to blame the people and not the method.
I would define my current project as very agile in the sense that we only have details plan for what to do a week ahead at the time. Each week the team has an hour long meeting where we present what we have done, and discuss if it's good enough. If something like a hover region is found to be wrong it will get fixed for next week. If you find this issue while working on something else, you make task and PR and just fix these smalls things. I feel like this way of working is what what meant by the people who invented the idea of making software development agile.
I agree. The best interview experience that I had was to be sat in front of a small app that had lots issues, both big and small, and also a lot an not-really-issues-but-still like inconsistent code styles and names, and code comments and code that weren't aligned. This was a great starting point for both me and the interviewer. The interviewer had a list of things to ask into about the code, so that we didn't get stuck.
https://publiccode.eu/en/