26 karma · joined June 29, 2021
I've been working on native mobile apps in the last couple of years, and I realized the only reason companies want to push native apps is because they can do whatever they want with the tracking and 3rd party stuff in general.
Seriously this native apps world is so backwards compared to the web...
I'll take youtube as an example, on the mobile web app you can block most ads and you don't get the latest stupid features youtube is trying to push for some reason. Sometimes I'm brought back to the native app through a link and I'm shocked. The only reason I keep it is Chromecast support.
I'm not a morning person but I try to find the time for a morning walk and get fresh air.
I take long lunch break to do sports or hike, this is my favorite time of the day for physical activities.
Don't be too comfortable sitting in front of the computer, try standing up or kneeling down. Go take a walk or do some exercise if you feel like it.
I'm amazed at how my brain switches on when I'm taking a break with a little sporty walk.
It's yours to find out what suits you the best.
I see devs freaking out when you use the word abstraction now...
Suggest extracting business logic from a React component and you don't know anymore if someone is gonna raise the "overengineering" flag.
If you start a new project, do you not use any library or framework at the beginning?
Obviously you take decisions according to how much the project/feature is expected to scale.
If your estimation was too low, you might cripple your development at some point, and need a rewrite or at least some significant refactoring.
If it was too high, I guess you overengineered.
What matters is asking yourself the question, and of course as engineers we like to challenge ourselves into building the best possible solution, but we equally need to consider how likely it is that such a solution is never needed.