Obviously things can go wrong, like they did here, but it's not worth discarding the very useful tool of specialized taxes due to cases like this.
387 karma · joined November 5, 2016
Obviously things can go wrong, like they did here, but it's not worth discarding the very useful tool of specialized taxes due to cases like this.
Still an interesting data point, but misleading on its own.
With 2x YoY growth you are always onboarding. You need to be multiplicative with your onboarding efforts. This means writing quality onboarding documentation, mentoring mentors, and codifying parts of the onboarding process (e.g. groups to join, permissions, etc.). Making other engineers effective is a very valuable use of time when so many people are ramping up at once.
It can feel exhausting, but mostly invigorating. There's always a feeling of energy; the hardest part can be setting boundaries to not let it consume your free time.
Is it really way harder to get dressed at the end of the day instead of the start? Is it that much cognitive pressure to feed yourself? Working in the office has its benefits, but working from home is not a crushing experience for a programmer compared to most workers.
The travelling was great. I was out of the country for about 3 months and visited friends for the other 3. I filled my calendar during this and was constantly moving. I was in the best shape of my life by the end of it.
When I was done travelling, I came back and lived out of Airbnbs in the Bay Area until I found a job. This was really expensive, and gave me urgency in the job hunt. I was able to fully dedicate myself to job hunting, and interviewed at a lot of companies. This let me price my labor well and negotiate effectively as a result. No companies had a concern with the time off.
The income bump from the aggressive job hunting meant the 8 months didn't hurt me financially at all. This let me have an experience I'll remember for the rest of my life without much downside.
I use normal select when:
- I want to apply a regex to a specific area, e.g. a single function (vjjjjj:s/my_function/my_new_function/g<enter>)
- I want to cut some text and I don't want to count how many words out it is (vwwwwx)
I use block select when:
- I want to delete a section of fixed width formatted text (Vjjjlllx). Useful for manipulating logs with a fixed width prefix.
- I want to append text to the start of a line. (VjjjjjjI# <esc>). Useful for commenting out lines.
Can't help but feel like this entire class of problem should be avoided with modern tooling. Even in a relatively unsafe language like C++, a static analyzer could have flagged an unchecked array access.
This piece seems to criticize just one subset of psychology - happiness research - and use that to dismiss the entire field. I feel like writing putting one discipline above another should be a bit more vigorous in that dismissal, even if I ultimately agree with the general sentiment.
Of course the short-term profits being lost don't seem so short-term at this point, so Google is surely debating internally on how long they want to continue this strategy if it doesn't begin to pay off.
I'm pretty surprised Twitter didn't see benefit from doing this if they have multiple Kafka clusters with different use cases.
The federal rate is currently 0.25%. They set this rate extremely low to encourage the exact behavior we are seeing here - investments in the US economy.
I have a 1.4x leveraged portfolio with similar reasoning.
/proc is Linux specific, but it's extremely useful. A lot of tools are actually built on top of it, for example ps.
ngarvey@cheapo:~$ strace ps aux |& grep cmdline | head
openat(AT_FDCWD, "/proc/1/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/2/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/3/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/4/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/9/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/10/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/11/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/12/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/13/cmdline", O_RDONLY) = 6
openat(AT_FDCWD, "/proc/14/cmdline", O_RDONLY) = 6Imagine a pool of 100 people. The richest person has $100, everyone else has $1.
There's a total of $199, and the richest 1% have more than half the total wealth with $100.
I'm not saying this is the distribution of the real world, but that statement alone is not a contradiction.
The defaults are a lot saner, and it's easier to pass arguments how you want.
If someone breaks into Twitter, user data is compromised. It's not just the business that pays a price.
Buy a robot, and pay someone remotely to do your housekeeping for you. The housekeeper could even operate it from their smartphones.