That is the exact point the article is making. When you are junior you think that code style is the most important thing but it isn't. (Also it can be handled automatically as you say)
They might mean at customs? When you go through customs you have to get your bag and then recheck it but they do have a place to drop them off without having to go through security again so it's not that much of PITA.
All of this is why my primary use case for ebooks is actually borrowing them from the library. It's super convenient because I don't have to worry about returning it on time -- it'll just disappear from the my device! But if I'm going to buy a book I almost always want a physical copy. (I've bought digital of a few of my favs that I often re-read on vacation but I do own physical copies of them too)
You might currently be working a job that is 50 hours a week -- or 60! Also with the example of a single parent they often can't make room for yet another 10 hours of a work in a week because they need to spend time with their children/take them to activities/cook dinner etc. Manageable when you are working 40 hours a week but it quickly becomes unreasonable. To me a job that wants me to work for them before I have an actual job offer is a red flag. I don't even work for them yet and they don't respect my time. What's it going to be like when I do work for them?
Have you used flow at all in the past? If so what would you say the major differences are/how difficult was any process to convert over? I'm a huge fan of having the types defined just from a documentation perspective nevermind bug catching and debugging and all that. I feel relatively agnostic about the particular thing we use to do it so I'm curious as to what the differences are.
But yeah it really has improved my day to day immensely and I really feel the difference when I'm working in legacy portions of our apps that pre-date the flow adoption.
48% I'm happy with that cause I'm pretty bad at actor names and such. There were a few that when I hovered over the tooltip I was like 'Oooooh yeah, I know that person' but I only clicked the checkbox if I knew without double checking.
Really? We have spike tickets all the time to go and explore a problem and see what edge cases we can find, explore possible solutions, and stuff like that. We usually scope spikes to a day or so. But we've had a couple where we were given almost a full week. The minimum I've spent was an afternoon and that was mostly because I actually found a lot of info a lot faster than expected.
agreed -- being able to verbally set timers is very valuable to me. Also I have Lifx bulbs in my living room and it is much easier to tell Alexa to turn them on/off/change brightness than it is to get out my phone. I only use the phone app for that when I want to set up some custom color thing (which is pretty rare tbh)
I actually see people using facetime in public all the time -- I think its one of those things if you aren't looking for it you won't notice. I've actually used google hangouts on my phone a few times -- recently I was in the airport w/o my computer on my Dad's birthday so we did a video call and other scenarios like that one.
Also, I lived abroad for a few years and I used video chat extensively with my parents and other friends back in the states. (TBF though a majority of the time it was on my laptop -- but sometimes I did use my phone!)
> Mostly teenagers yes, but them being the next generation of adults I doubt they'll just stop once they're into their twens. It'll just become the norm.
That one is potentially true although I'll say based off of our interns they seem to be pretty good about not being on their phones all the time when the situation calls for it. I think like most things its super individual because of my coworkers the person who is on their phone the most is actually a middle aged guy.
well to be fair it is how it normally works with humans. If someone has your physical address they can send you as much junk as they want in the mail. It's not really different online.