The whole channel is great. Even something I thought I knew all about, “How a Jet Airliner Works” [1], was fun & revealing.
2,264 karma · joined February 8, 2011
write a little at hoho.com
elsewhere: @mik3y
The whole channel is great. Even something I thought I knew all about, “How a Jet Airliner Works” [1], was fun & revealing.
The pitch: Want to run stuff on Raspberry Pi, but dread having to remember how to set it all up again when the sdcard fails? Try this homebrew-like interface for common stuff.
Backed by docker + docker-compose + a template system. Not really a package manager but has similar qualities. You can see supported apps at [1].
I've been using it for a couple years to keep by ADS-B system running, but it's half-baked since it never reached any adoption = limited set of packages.
[1] https://github.com/berrypatch/berryfarm/tree/master/apps
According to their FY2021 990 filing, they had $442k of "other" expenses.
It seems like they're required to disclose what those expenses are on the Schedule O form if they exceed 10% of all expenses, which they do, but I don't see the expenses enumerated there. (edit: oops, now I see)
I am, err, not a tax professional so I stopped here..
One of the things they talked about was System 6 or System 7, and an example of how it was different from Windows 3 in one of many ways: The system bar—“File”, “View”, etc.—was at the top of the screen, not each window. This consistency made it easy “throw” the cursor to the top of the screen and get to the thing you needed, a consistent experience, no matter what app you were in or what the window layout was.
This “consistency of experience” point always stayed with me as such a core principle of good design, whether in computer UIs, quick serve restaurants, or here, I guess, ski map visual style.
First, while shopping the company, the CEO represents to potential suitor JP Morgan that they have 4.25M “users”. JPMC bites and asks for proof eg during diligence, and so CEO asks a Dir Eng to fake it. They refuse. So she gets a contractor to build it, sends it through a “vendor”, and the deal goes through.
I think this dataset must be de-identified randomly-generated junk, something like signup dates and fake IPs, because then theres a second fraud: Post acquisition, JPMC starts asking “hey about all those users we paid for, we’d like to market to them now”, and now CEO is in a bind because she needs names and emails. So she commits a second forgery, purchasing a list of 4.5M (name, email) records from a data broker.
Outrageously brazen if proven. I wonder if at any point while the deal was going through, this founder knew this house of cards would someday fall apart.. As usual, you think, “what on earth was the plan?!”
Fair feedback, thanks!
I wrote that with myself as the listener in mind -- I often need the reminder that is the post's title -- but I can see how the delivery would sound abrasive to another reader. Gave it a light edit.
Yes, those things are always important (if not critical); it's not meant as a defense of bad architecture, merely to try to make those decisions through a product/customers-first lens.
(I did try to connect quality/reliablity, perhaps unsuccessfully, later in the post, e.g. in goals: "If the system is unreliable, we won’t ship as much product ... If we don’t replace this system, more and more customers will experience a broken product.")
The point was more that layoffs can take out big slugs of staff without considering the individual, in a few different ways: initiatives we can just cancel completely (self driving cars); people we will likely need later but less in the shorter term (recruiting); or places where we consciously take on added risk (losing security).
I do think that for the company that sacked their security team, the executives may very well have had a full understanding of the risks it created — but couldn’t easily say so publicly (“we chose to 10x our risk of a security incident, so we keep 1 more product initiative staffed which might save us”). Just speculation. Not a situation I think many of us would be comfortable in.
"Ideally", your layoff strategy dictates some cuts regardless of performance: Say we're shutting down the self-driving car division, folding up recruiting, or choosing to accept the risk that comes with getting rid of the whole security team; sadly, the performance of the individuals involved isn't really considered.
Tenure, seniority, and comp are also factors that can come into play & are straightforward to establish without lower-level involvement.
> If you hit a ceiling (without growth) then you may want to consider looking for/accepting outside capital.
One other option at this point is to sell the whole business. For bootstrappers allergic to VC or lacking the drive/skill to scale further/faster, can be a nice outcome.
Seems to be a growing number of firms specializing in small saas acquisitions too (Tiny Capital comes to mind - no affiliation).
Main question to ask is whether you have considered the overall potential threats to the business, and what you’re trading off against by not taking VC; and if you are comfortable with those risks and tradeoffs.
There’s no universal answer, but there are better answers depending on the business / those risks. For example if your business is at increasing risk of a better-funded competitor eating your lunch, a bigger war chest might be prudent.
Keep in mind that there are a substantial set of skills you will need to develop, and responsibilities you will need to make time for, when taking VC investment. Not necessarily a negative, and for me it was desirable. Fundraising, managing investors (eg updating the board quarterly), hiring faster, and scaling the product faster. I’m hand waving here, but as you’ve guessed it’s likely not just take money and keep on operating exactly the same way. Big checks will come with certain expectations, and meeting them can dramatically change the culture and lifestyle you’re trying to achieve.
Lastly, there are ~boutique VC firms out there that specialize in smaller SaaS with good trajectory. The VC that is knocking may be the wrong match for your goals, but it’s OK to shop around a little.
Quick thoughts but feel free to find/dm me if you’d like any addl advice or anecdata. And, congrats!
It’s nice to have a single roll up for all of the knobs — “what was the state of the environment” — to tag in things like crash logs.
(It’s also something we can’t easily tool ourselves.)
2) One click dashboard rollback button. Didn’t realize how much we missed this from Heroku.
3) Meta: Public roadmap and feature request tracker. Fly has a habit of surprising, usually pleasantly!, but it’d be nice to know how close or far off something on our wishlist is. (Render seems to do this well.)
One of those low key, behind-the-scenes, hidden masters of silicon valley (and silicon design more specifically), Nick had this larger-than-life personality with normal guy humility. Just reading a random mini bio of Nick's [1] gives you vintage Nick, a "seriously, don't make me talk about myself" kind of guy. Also the kind of guy with numerous oddball surplus vehicles and heavy machinery in the Santa Cruz mountains, which he'd happily fire up and tour any visitors around in.. I have fond memories of being "dumped" from a literal dump truck by Nick.
I wasn't sure the HN crowd would be familiar, but interestingly Nick had a post on the YC blog at some point, "An Engineer's View of Venture Capitalists" [2]. I don't know the content, but knowing Nick I'm sure it's pure "engineer's engineer" sort of stuff.
Nick's business cards -- "wars fought; bars emptied; used cars; also MEMS" -- were infamous, and were just another reason he inspired me very early on in life to.. not be bland. I'm still trying. Nick, you were an inspiration, one of a kind, and are very missed.
[1] https://www.computer.org/profiles/nick-tredennick
[2] https://news.ycombinator.com/item?id=6369357But I could imagine how distressing this would be for a business more dependent on search. And you can find lots of small business owners and indie hackers with such stories if you start looking..
What I sought was someone to escalate the details in a ticket & get eyes on a likely false positive -- from a very friendly/technical customer (me). The buddies I asked, admittedly not on Ads risk engineering, looked around, hit walls, and gave up.
A sudden ads suspension arrived, with no explanation beyond "suspicious payments". This from the same billing account used with GSuite, Domains, GCP; and from a business that was having no trouble running ads on FB, Twitter, and Reddit. "How silly, but I'm sure we can get it fixed".. I thought.
Like OP I'm also a Xoogler, so after two rounds of unsuccessful appeals through the front door (including updating my payment account to a hard card, providing articles of incorporation, and so on, to no avail), I figured it was time to call in my first ever favor. Surely one of my old-timer engineer buddies could thunk a ticket somewhere and maybe we'd help them fix a bug in some automated system in the process.
But the Google of 2022 is far different than the earlier days. It seems individual employees, even well-placed engineers, have incredibly and increasingly limited agency to fix things outside their immediate purview; a wiki about internal escalations for ads suspension stated they were no longer accepted, vaguely for reasons of "compliance".
On the bright side, the whole episode made me rethink and ultimately diversify our technology dependency on Google. I was naive not to do so more seriously and earlier.
I moved several valued domains to Cloudflare registrar precisely because I assumed that they'd be better in "rare but extremely unpleasant" domain-loss scenarios, such as account takeover (by a third party) or account suspension/termination (by them).
Contrast with Google domains, where I could never shake a worry that uploading the wrong music in a private YouTube clip could one day randomly cascade to my whole domains account being closed without recourse..
Quick scan, it looks like the average episode of "Space Rocket History" verges on ~60min, where "The Space Above Us" is about 20-30 minutes. For me, the shorter length has made it more "snackable".
It's written/hosted by a systems engineer and a spaceflight enthusiast; has tight production with no ads; and often focuses on interesting or obscure aspects of space and shuttle technology or operations, that are often relatable to the world of (more terrestrial) software.
I’ve built, and than managed teams building, apps of large scale and complexity. Your outline looks like a goldmine of practical and essential advice, especially for folks just ramping up on mobile. I’m excited to give it a read.
I think it would be fun to build something like that though, the AIS equivalent of adsbexchange.com.
On adoption.. I think your hunch is at least part of it. I think another part, one that is very solvable, is there are not a whole lot of instructions for DIY hardware & software setups out there.
My impression is most AIS hobbyists use kits & proprietary hardware shipped from commercial providers (eg MarineTraffic), while rtl-ais is pretty obscure. Documenting what I can as I go to change it.