- Zachtronics has an excellent game(?) Shenzhen I/O which is such a good simulacrum of an embedded SDE; reading datasheets, coding, and sending emails, that I couldn't play it!
But I highly recommend it, if thats not your day job - or if you are curious about making it so!
- Posting the same link 4 times in 18 days, by the author, certainly seems like self-promo, but somehow allowed? I don't see any URL manipulation, and it certainly took off today. (I found it interesting!)
A&B testing of post names seems to lead some useful information ;)
I don't see your reference to "Georgetown students..." in either the website link or the user's submissions? Was it modified?
- That one Apple is still allowed to collect fees on (which I'd love to see the provided justification for!).
Per the article: "Apple can no longer collect a 27 percent commission on purchases made outside of apps or restrict how developers can direct users to alternate payment options"
This now allows folks to direct users to alternate methods. Before this the Kindle app would just say something along the lines of "you can't get a book here, please use the website".
- People leaving is definitely a step-function of negatives as the responsibilities get shared between the (now smaller!) team.
I think GP was more saying that improving retention, at a % level, is a slow ship to steer. (At least what is available at the manager level.) Decreasing retention across the org in the long term doesn’t happen overnight, and it can take a while to observe whether the effect is trending downwards or upwards. (And also depends on what signal you use - people actually leaving, or people talking about leaving!)
- FWIW to avoid the plugging in (which I hated) Calibre can be configured to send emails as well, which works well with the email to kindle feature, and with a little fiddling you can bridge the gap to have Calibre auto-email you. (https://www.mobileread.com/forums/showthread.php?t=314401)
- Don't work for Google, but been to the Toronto office (it is on the smaller side).
It is in the heart of the Toronto downtown, near Richmond & Spadina, next to the old & new City Hall. Definitely disagree with GP, I'm not sure what better area you would pick (but I love downtown). Similarly in Taipei, the Google office is right in Taipei 101 (like having an office in CN Tower - very cool.)
To be fair, Amazon's office in Toronto is next to the CN Tower and has a great view of it - so maybe Amazon takes the cake here. You have to pay for the cake though.
- I'll agree wholeheartedly that the analogy needs some work. Tools are different - we have our literal physical tools that we don't generally dive into (keyboards, mice), we have tools that are maybe more battle tested and rarely examined (cat, grep, find).
We have do have tools like the hammer - there is one design, everyone more or less agrees on it. There is still high quality and low quality, but it has one job. We have tools like a bulldozer - complex, numerous parts, requires constant maintenance, closed source.
As the parent said - it is not uncommon to have to maintain old equipment, as well as design new tools as new requirements pop up.
Sure, our rust is a little bit different - time wears on software in a different way. Use wears on software differently. (Changing product requirements leading to a new tool is probably common.)
The maintenance may be trickier - but I'm sure changing components on a tool when a certain component is no longer available is not easy, thats where shim layer comes from!
- It looks like the Intel out-of-tree driver is carrying around some legacy HAVE_PAGE_COUNT_BULK_UPDATE option that is making their porting efforts difficult.
This commit in upstream ends up getting split in half:
https://github.com/torvalds/linux/commit/8ce29c679a6ecefb88d...
With only 3 lines of it getting pulled into i40e-2.13.10:
https://github.com/dmarion/i40e/blob/master/src/i40e_txrx.c#...
https://github.com/dmarion/i40e/blob/master/src/i40e_txrx.c#...
(Can't link git diff line for 2.13.10->2.14.13 because diff is too big, annoying!)
And the final line getting pulled into i40e-2.14.13:
https://github.com/dmarion/i40e/commit/135d6d885aa4704180e10...
Best thing I can find in i40e_txrx.c where a single patch in Linux upstream got split across 2.13.10 and 2.14.13. Not a smoking gun exactly, still some exercise left for the reader.--- if (unlikely(!pagecnt_bias)) { +++ if (unlikely(pagecnt_bias == 1)) { - The favicons are certainly functional - as a sufferer of 'too many tabs' syndrome, at the very moment, the only information I have about each of the ~30 tabs currently open in my Chrome browser is the favicon.
This packs far more information into the 48x48 (or whatever resolution) then trying to squeeze in a title like "Am" or "Ha" for Amazon or HN.
(Totally agree on the complexity, seems like it followed the iOS Store model of interface design!)
- Interesting - I felt this way about Project Euler, which within the first few problems was exactly as you described - heavy mathematical literacy. I haven't gotten far into an Advent of Code since 2015 (~18 days), but have done the first 5 days of 2020; no mathematical literacy needed.
For 2015, and 2020 so far - its mostly text parsing, data structure building and basic iteration/permutations.
- Thank god for Wayback Machine!
https://web.archive.org/web/20131120212107/https://www.goo.n...
Pretty close, same dense pack of information, tiny photos. Seems to check most of the list.
- Very interesting to check out how different POS systems handle the rounding!
I share GP's assumption, assuming that businesses would re-price based on the final cost. There is a financial incentive to get the transaction to round up, and financial incentives are usually pretty motivating.
(Given the max incentive is 5 cents per transaction, I might guess a focus on one-off transactions like a bag of chips, vs. the complexity of attempting to get the average grocery bill to end in the right #!)
Would be interesting to see if the after-tax prices of potential single items (chips, water, pop) changed with this rule. Anything that was 99 cents, now that HST is 13%, comes to 111.8 cents, rounds to 110 cents. Bumping that to 100 cents even, rounds to 113, rounds up to 115. Profit of 5 cents on '99c/1$' item for 5% difference. Hard margins to give up!
- Super interesting post. Following blog links, the timeline in https://slack.engineering/all-hands-on-deck-91d6986c3ee also offers a look at the play by play.
However, as far as I can read it, they have somewhat different views on the root cause?
"Soon, it became clear we had stale HAProxy configuration files, as a result of linting errors preventing re-rendering of the configuration."
vs.
"The program which synced the host list generated by consul template with the HAProxy server state had a bug. It always attempted to find a slot for new webapp instances before it freed slots taken up by old webapp instances that were no longer running. This program began to fail and exit early because it was unable to find any empty slots, meaning that the running HAProxy instances weren’t getting their state updated. As the day passed and the webapp autoscaling group scaled up and down, the list of backends in the HAProxy state became more and more stale."
Maybe a combination of the two?
- The article drops some names and, I guess, expects you to have heard of them. I have heard of Namal, so that is an instant indicator to me what they mean in this case by 'great'.
I'm not sure that I buy the 'this will scale when floodgates are open' follow up though. Although with the recent 'famous person goes live on Facebook and interacts with fans', it might work!
- I've only made it to Rule #2 in the book so far. But it is thought provoking. (Not strongly, in a Plato sense. But reflective.)
It mentions studies (or parables? Who cares?) of people taking better care of their dogs post-surgery than they take of themselves. It rings true, and speaks to anyone who thinks or knows they aren't taking good enough care of themselves.
Has certainly been an enjoyable read so far.
The original post states "I am seeing Codex do much better than Claude Code", and when asked for examples, you have replied with "I don't have time to give you examples, go do it yourself, its obvious."
That is clearly going to rub folks (anyone) the wrong way. This refrain ("Wheres the data?") pops up frequently on HN, if its so obvious, giving 1 prompt where Codex is much greater than Claude doesn't seem like a heavy lift.
In absence of such an example, or any data, folks have nothing to go on but skepticism. Replying with such a polarizing comment is bound to set folks off further.