He had an interview with Google and they asked him to invert a binary tree, which is essentially taking a tree of data and swapping the positions of all sibling nodes.
While most people agreed it was a pretty pointless question to ask at an interview, mxcl had a full “don’t you know who I am” shit fit on social media.
If anyone hasn’t made the connection, mxcl is the infamous Google interview binary tree guy
It depends on your intent. If you’re doing it to keep history clean and linear in the long term, it’s a huge waste of time as it gets splatted into a single squashed merge commit. It also makes it difficult for reviewers to rereview your changes as GitHub/Lab can’t calculate the diff because you keep moving the goalposts with force pushes.
If you’re doing it for cleanliness on your local branch then I guess that’s fine, but I find it anti-social in a multi participant repo.
Agreed. I’ve been trying to explain to someone recently why rebasing and force pushing their feature branch has no benefit when we use a squash commit strategy for merging to main.
Again, tools are not blame, but when combined with a lack of understanding and accumulated “git dogma”, it can be quite disheartening.
Same. I mostly use sourcetree to do quick self-reviews and to discard lines or hunks before a commit.
But I’ve also grown very weary of having to dig people out of git messes they’ve made with sourcetree and the likes.
Visual clients aren’t to blame for that, but they contribute. So many times I’ve asked “and what git commands did that run?” only to receive a dumb stare as a reply.
I think it’s exactly that. They are targeted at bootstrapping projects and prototyping and are, frankly, very good at that job.
Not sure on your use case, but I’ve been using Hetzner for a while and it does what it says on the tin.
That album is absolutely killer and I’ve loved BN since I heard Try Honesty many moons ago.
That said … They have been singing about how young people need to fight the system while having one of the most clean, corporate images I can think of for bands in their category.
Watching a 40 year old man dance around an arena in VANs and Atticus hoodies while telling contemporary youth that their generation is a “fucking joke” is peak cringe to me.
Still love the music though. Wish he’d do more heartbreak songs, they’re his forte.
You win
It creates an ssh tunnel and then sends the file over http, so … literally no advantage to using this over ssh/scp.
Worse in every way, actually.
Which part of that isn’t true
All rise for the German national anthem
I use butterflies
That’s heavy man
Linux 🤝 DooM
Running on literally fucking anything
My biggest problem is office drama. However, wherever I go, there’s always going to be drama, so wouldn’t it be wiser to stay with the bad I already know?
If this is the first or second time you’ve had this issue on a job, then you just need to decide what you want: either you switch job, or wait for the individuals that bother you to do so instead. Neither is a guarantee that things will be any better.
If it’s the fifth, sixth, seventh time … Well as the old saying goes: if everywhere smells of dog shit it’s time to check your heel.
How I approach my career: Never change jobs because of extraneous factors that are not directly related to your career and where you want to take it. People will come and go, drama will rise and fall in equal measure. None of it will matter a jot compared to whether you’re actually satisfied with the role itself, and how it allows you to reach your career goals.
The show and tell page is exactly that, show and tell; not a scientific or balanced comparison.
The original challenge only compared JDK solution in this way. Further down there is a link to another repo that does that same across many languages, and uses the same M1 MacBook Pro to run the tests.
To answer your question about environmental and hardware factors - from the repo:
Results are determined by running the program on a Hetzner Cloud CCX33 instance (8 dedicated vCPU, 32 GB RAM). The time program is used for measuring execution times, i.e. end-to-end times are measured.
They’re advertising on TV in the UK, so guessing they’re at least at preorder stage.
It’s more about scale. Small open source projects might get one PR a month. Your average tech company is dealing with dozens of PR every single day. Review fatigue is real in these environments