I ran into 5 and 7 in a Flink app recently - was parsing a timestamp as a number first and then falling back to iso8601 string, which is what it was. The flamegraph showed 10% for the exception handling bit.
While fixing that, also found repeated creation of datetimeformatter.
Both were not in loops, but both were being done for every event, for 10s of 1000s of events every second.
> documentation survives when it lives next to the code.
15+ years ago, this was pretty much the standard. Every decision - whether major or just a hack to handle a corner-case - used to be recorded in the code itself. Then tools like Jira and Confluence came in and these things moved to undiscoverable nooks and corners of the organization. AI search tools like Glean and Rovo have improved the discoverability, though I'd still prefer things to remain in the code.
I loved their dry seasoning [1]. Bought some when I visited the bay area several years back and used to use it on everything from toasts to pasta. Sadly, haven't visited US since to be able to pick up some more :-(
Obviously there is a ton unsaid in this blog post, but I just wanted to answer your question because it's exceedingly common for companies to be sold, sometimes for lots of money, and for common stock (which is what employees hold) to get wiped out. If the startup was sold for $350 million, but it received $350 or more million in funding, the investors get (some of) their money back, and employees get nothing. This happens all the time.
Again, I don't know what happened in the author's specific case, but think it's important to know that lots of startups have exits that can look big on paper but still are a wipeout for common equity.
reply