457 karma · joined March 31, 2015
I passed my driving test 30+ years ago and then took the HPT as part of a motorcycle test 15 years later.
Paying attention (to the kid bouncing a ball at the side of the road, to the cyclist when it's windy weather etc) is a key part of road craft and I hope this made it much clearer with some (contrived) examples. TBH I just wish they let you click earlier (for _potential_ threats - i.e. before they step into the road, not just afterwards).
I'd except there to be a fairly strong obligation (probably on both parties) under GDPR to ensure that EBT destroyed that data.
I'll be following up
e.g when you need to restrict a set of users to run only certain applications with certain other users. sudo can do this (even if the config format can be painful).
Today: "Brits to bask in 20C sun" (that's 68F) Yesterday: "Yellow thunderstorm warning..set to spark travel chaos"
Just a tad over the top! Genuine weather extremes in the UK are pretty rare :)
- the onus is on _you_ to "prove" that you don't know it or have forgotten it - you can be told not to reveal that you've told them the password
Anyone administering systems might want to think about this, governments aren't known for good security.
The greed of companies will be their own downfall.
Attempting to be 100x better "than the rest" strikes me as a _very_ unhealthy approach. To paraphrase an answer I read somewhere else:
"The best way to be a 10x developer is to make 10 of your colleagues twice as effective"
Note that _you_ don't achieve anything more - you've just unlocked the potential elsewhere. It's also immensely satisfying - much more so than being a "rockstar" developer (also known in many circles as the "a*hole").
Looping back to your question:
- look around you - solving a key problem currently ignored could be the best thing you can do for the company - compound interest - invest in making repeated actions better (automation, cookie-cutters etc) - improve efficiency - IMO docs, single source of truth are typically seriously undervalued leading to questions and mistakes both of which waste a lot of time - take a healthier attitude - it comes across to me as a rather immature "look at me, aren't I _amazing_" desire which will rub people up the wrong way. - learn at every opportunity - senior devs don't know everything - I've also learnt from kids still at school, sales people, friends...
- Try and become a child again (when I didn't have these worries/frustration). Concentrate on what's in my control. Don't worry about things outside my control.
- Stop reading the news. A family crisis after the shit-show that was 2016 clarified what _actually_ affected me.
- Stoicism. "Meditations" by Marcus Aurelius (recommended many times on HN) helped. That what he wrote 2000 years ago is so relevant today made this stick.
- Appreciating how fortunate I am (good job, health, life). I'm mostly happy, I try and act this way. Cut myself off when I'm going off on a rant. "Thinking happy thoughts" in other words, it's not nice for anyone else listening to doom-and-gloom. This also helps with the next topic:
- Friends. Putting in some effort with (not yet friends) at work, on walks, meetup etc - sometimes you end up with a few more friends.
- Distraction. Keeping busy with other things. Preferably creative or in-the-moment things.
You aren't going to fix the worlds problems. By _all_ means help and do your part, however getting angry and upset is only going to make you unhappy.
e.g. with all war in Ukraine, yes it's horrific. Perhaps you are in a position to help - offering a home, help or financial support? Sympathy and understanding for people you know who might be affected, reach out to them.
In terms of rollout it's more like releasing new drugs - initially it's very small groups that will be tightly studied, over time these groups are increased in size (and monitoring is probably reduced in scope).
The use of feature flags to control rollout and "blast damage" from unexpected behaviour or bugs is really useful. Let me give a real example I was involved with - mobile app development.
You can never test everything (not every Android phone variant, nor every 3rd party app which may interfere). Being able to roll out a new feature gradually and then revert (or in our case even blacklist certain models) is key to increasing quality and reducing problems. It also accelerates development and (in my mind a _key_ benefit) reduces stress/anxiety for the developers.
A few timers on other devices to turn off bluetooth speakers overnight. Over the ten years I lived there it was a decent saving.
Given the generally dire security of home routers (and understandably low security of most home networks/users) it feels a little like giving people far more power than most can safely wield.
Yes, email and ticket systems have drawbacks, however slack is almost an anti-knowledge base in it's current state.
Distraction - do something else, keep busy. I also have some "interview notes" I built up which I refresh _just_ before the interview. These notes are reminders for common questions (e.g. "describe when had to reach out to other teams").
Have several interviews - if you are interviewing at several companies then there's less pressure on an individual interview. You'll have many opportunities - even if you don't get into Meta now, I'm sure they'd like you to retry later.
Lastly, take it as a reflection of the company interviewing you. Some interviewers are more interested in tripping people up or showing off how much _they_ know rather than getting the best from the candidate - I'd just avoid those companies. Others bend over backwards so that you can shine, putting you at ease (detailed info about the interviews, conversational style interviews, friendly interviewers, relaxed surroundings etc). You may have the option to perform a take-home exercises which I certainly found less stressful (but take more time).
He covers a lot of programming principles and good practice with realistic examples (i.e. _not_ "class Animal")