I'm working remote since 4 years, and I have had periods spanning weeks where I have moved less than 2000 steps during 90% of the days. When I started working remote, I went from walking 8k steps per day to ~1k consistently for a 6 months or so.
My schedule when I started was 1) Go up from bed 2) Go to computer 3) Sit for ~8h straight, only pause for toilet and making lunch 4) After 8h make dinner, eat, feel like a vegetable in both mind and body.
I've since then re-arranged my day to at least walk 5k-8k steps per day. I've found that the step count doesn't matter much, I need at least 30min high intensity workout every day to not go numb in my mind and body. Luckily, I have two daughters, so I'm forced to do more excersices than I did when I worked from outside of my home.
Thanks! And yes, that's indeed true. There's a fine line between passion and obsession. I found that my motivation and passion easily are morphed to their negative equivalents when I'm under pressure, or when I just need to focus on something else entirely.
Nothing. Strangely enough, I can't think of anything new techy that I learned this year.
I've worked full time remote in mobile and machine learning the last 3 years, but this year is special. This year has required me to set my own motivations and goals aside to really be there for my 18 months old daughter, and for my wife. At first I tried to resist and focus on both my family and my career, but I found it hard to be my best self for them.
I took a step back from the stress and greed. I learned that I need to keep my career out of my head when I'm caring for my daughter. I'm more motivated than ever to do some cool projects in 2019. And I've learned that I need to maintain a mental balance between work/passion/me and my family.
Towards new beginnings, and growing as a person.. :)
Real world use cases might be; Classifying the users mood from mouse movement, classifying the microphone audio. I.e. process real time data that might be too large to upload.
I personally haven't seen any NNs being used in browser apps, but there are plenty of existing mobile apps that has NNs to classify audio/video/etc directly on the device.
I believe it is the same functionality as in Sublime, IntelliJ, Eclipse and others. It's a total lifesaver when editing bulk stuff, like a lot of constants and what not! One of my must-haves in an IDE.
Dagger2 is great when you have it setup, generating the dependency graph during compilation makes it lightning fast during execution. I also like the error messages, as long as you can read Java stack traces all the info for solving errors are in there - I've never seen an unsolvable situation this far.
Kapt does bump the clean build time to about 2min, incremental builds take between 10-60s - although actually launching the app on an emulator/device adds another 20s.
The cons of Dagger2 that I've experienced since it's launch are; The documentation and support is useless. You're on your own of you don't use a 3rd party sample project as a template. No one understands scopes and subscopes, subcomponents etc. The new Android dagger api is arcane and weird, no one wants to use it.
The Dagger2 team should (if they aren't already) create a Kotlin extension for it, I believe there are some syntactic optimizations to be offered.
/s?
React Native seems to be the only alternative to native apps as of today. Googles Flutter might be a viable alternative if they don't drop it, but it's far from production ready..
Our baby goes to sleep between 5-8pm and sleeps until 6-7am.. She makes the rules though, when she finally becomes grumpy in the evening I prepare some food and it's off to bed. Works every time!
I believe all babies are different, so luckily our first have been kind to us this far with her sleeping habits and mood.
It's turned out to become a standard for mobile developers due to the concurrent and async nature of the platform. As a side note, I've been working through ~10 different code bases during the last 4 years - every single one has included an Rx library. Scala, Java, Swift, Kotlin, C++.
80 hours?! I can't believe anyone can work that much, to me 40 hours is the limit. I won't work one hour more than that if it isn't necessary.
If I would code for just 60 hours/week I would only last less than two weeks. My spine and back would probably give up on me before that. Other than that I would be the worst father, friend and husband ever since my brain would be totally messed up between working hours, and in the long run during them as well.
Not to mention my productivity would be dipping to like 30% after a week or so with that pace. Today I have 5-7 highly productive hours out of 8 working remote. Sometimes less, sometimes more. But if I lose my balance and start working an extra hour each day I usually start dipping in productivity and sleep as the days go by.
My thoughts exactly, though it should be noted that the architecture astronauts are more common in customer facing software. In most backend projects I've been involved in, the final state of the project is so well known, all different corner cases are well covered by the chosen architecture. For frontend clients however, the architectural choices mostly end up being tech debt.
Sometimes I prefer "and then, and then, and then" over "sign up async observer, send through our java-redux, oops forgot to implement async actions, hack in an and then and then and then case into it" -solutions.