So I added categories. This allows people to read my blog specific categories if they want to.
Now I have to figure out how to make my header navigation bar.
Hacked together with tutorials from Webjeda and Azure Patterns.
Edit: And reading the jekyll theme docs.
Steve Yegge already say this better than I do.
Also, looks like google site is where old blogs migrate and archived
"What happens when engineers run a charity? They write detailed postmortems, of course, so they can fix their mistakes." - apenwarr
Engineers Without Borders: Failure Reports
I find this one particularly funny.
"The election planning committee indicated that we could collect votes ahead of time, and then submit ballots during the election period. My team created a Google form clearly indicating that in completing the form, they were giving our campaign team consent to submit a vote for me on their behalf. As such, we could not only account for every supporter’s vote, but also control when it would be cast in the race. Since preliminary results were to be released each evening in the election period, our plan was to submit votes slowly at the beginning of the week so not to give away our strong position in the race. We would then work around the clock in the last 48 hours to submit the majority of my votes.
We failed to see that to someone that wasn’t in our chapter, this looked like a failing campaign that led to a desperate attempt to stuff the ballot box. Consequently and unsurprisingly, the candidate that lost by a mere 15 votes called for a recount. After a long, three-week ordeal, the election was awarded to the latter candidate due to inconsistencies discovered with the votes I had received.
Looking back, we realized we had developed tunnel vision; we failed to be cognizant of the fact that we had to be accountable to the LYAC’s election procedures and what was expected of us. By not consulting the election planning committee about our campaign strategy, we took the committee and the runner-up by surprise. We had lost sight of our original goal of forging meaningful connections with youth in our community behind a shortsighted, singleminded desire to win a race"
don't know if real, but here's the comment:
"The footnote to this interesting learning experience is that the candidate that Joyce lost to actually ended up backing out of her role due to the required time commitment. Thus, Joyce un-un-won an election, an accomplishment that may truly be first-of-its-kind."
More can be found with danluu's archive of HN comments
For those who work inside Google, it's well worth it to look at Jeff & Sanjay's commit history and code review dashboard. They aren't actually all that much more productive in terms of code written than a decent SWE3 who knows his codebase.
The reason they have a reputation as rockstars is that they can apply this productivity to things that really matter; they're able to pick out the really important parts of the problem and then focus their efforts there, so that the end result ends up being much more impactful than what the SWE3 wrote. The SWE3 may spend his time writing a bunch of unit tests that catch bugs that wouldn't really have happened anyway, or migrating from one system to another that isn't really a large improvement, or going down an architectural dead end that'll just have to be rewritten later. Jeff or Sanjay (or any of the other folks operating at that level) will spend their time running a proposed API by clients to ensure it meets their needs, or measuring the performance of subsystems so they fully understand their building blocks, or mentally simulating the operation of the system before building it so they rapidly test out alternatives. They don't actually write more code than a junior developer (oftentimes, they write less), but the code they do write gives them more information, which makes them ensure that they write the rightcode.
I feel like this point needs to be stressed a whole lot more than it is, as there's a whole mythology that's grown up around 10x developers that's not all that helpful. In particular, people need to realize that these developers rapidly become 1x developers (or worse) if you don't let them make their own architectural choices - the reason they're excellent in the first place is because they know how to determine if certain work is going to be useless and avoid doing it in the first place. If you dictate that they do it anyway, they're going to be just as slow as any other developer.
Probably deleted the post, but I followed this guide by David Federman to get the initial setup for this blog.
Guide to get Previous and Next on Jekyll by ByteDude
Blog of Avery Pennarun at https://apenwarr.ca/log/
This guy was a L7 at Google. His best is his post on bug triage and system design so far.
I can't quite understand his IPv6 posts yet.
Wish I can get into TailScale (his new company).
I love her
So I've noticed that I read alot, share what I have read a lot, but I don't store them anywhere for searching later. So I'm using GitHub Pages to do it. Should be fun.