HNHacker News
TopNewBestAskShowJobs

HereBeBeasties

316 karma · joined March 30, 2016

submissionscomments
HereBeBeasties··on CarSized: A way to visualise car dimensions
Spare a thought in your enormous hatchback for those of us who can't even see through your back window to the road in front, as you tower over us: https://www.carsized.com/en/cars/compare/lotus-elise-2011-ro... ;-)
HereBeBeasties··on Ask HN: Do you test in production?
Good testing is an exercise in pushing I/O to the fringes, as that's what has stateful side-effects. (Some might even argue that anything that tests I/O is an integration test. The term "integration test" is not well defined and not worth getting hung up over IME.)

Once you're into testing I/O, which is ultimately unavoidable no matter how hard you try not to, you either need cooperative third parties who can give you truly representative test systems (rare) or a certain amount of test-in-prod.

Testing database stuff remains hard. You either wrap things in a some kind of layer you can mock out, or dupe prod or some subset of it into a staging environment with a daily snapshot or similar and hope any differences (scale, normally) aren't too bad.

Copy-on-write systems or those with time-travel and/or immutability help immensely with test-in-prod, especially if you can effectively branch your data. If it's your own systems you are testing against, things like lakefs.io look pretty useful in this regard.

And yes, feature flags, good metrics, and load balancers that you can send a small percentage of traffic through a new version (if your traffic/system allows such things) all help.

HereBeBeasties··on Waymo's collision avoidance testing
I created some 3D models of a real world building and surrounding environment using photogrammetry from 20+ megapixel DSLR photos and decided the accuracy was totally inadequate and the artefacts were too hard to manually clean up.

I then hired a dude with a LIDAR scanner and did it properly. The difference in quality/accuracy is like 120x80 ASF video files in 1996 compared to 4K footage today.

Anyone who thinks you can build "HD" virtual worlds using the crappy cameras on a Tesla needs their heads examining. Maybe with thousands of passes and some epic compute and signal processing, but why bother? Just LIDAR it.

My Tesla can't even decide if a traffic light is a single traffic light or not on a sunny summer's day from a distance of twenty feet. Almost every time it is either dark or humid or winter (road grime) it tells me one or more cameras are obscured. But only after I've already started driving, obviously. This supposedly cutting edge AI driving machine frequently thinks I'm leaving the carriageway on UK B-roads (it's almost dangerous) and is significantly less reliable at distance cruise control and lane-assist than my Skodă. (I presume VW just quietly bought a black box from Bosch or whoever to do this.)

Tesla are barking up the wrong tree IMO. At this point the camera-only stance feels like a religious thing, not based on sanity or the real practical world. I imagine that someone came to Elon and said "reconciling conflicting radar and camera signals is hard" and he applied his considerable genius and issued an edict to "let's not do that then!" like it would magically make all the actual hard problems go away.

Heck, Teslas can't even seem to reliably parallel park themselves, frequently getting stuck halfway, or hitting kerbs. If they can't solve that highly constrained problem, I'm hardly going to trust taking my eyes off it at 70mph.

HereBeBeasties··on Improving code review time
I think your main issue is having "two blocks of meetings" a day as a developer. That sounds absolutely nuts to me. Even two meetings a day is likely too much for a dev, let alone two blocks of meetings! I'd start by reducing that.
HereBeBeasties··on Show HN: I built a goal-oriented task manager
Have a look at https://fibery.io

You might be able to build your perfect todo app with it.

Don't like workflows? Don't add a workflow field.

Just you and no team? Don't add an assignees field, etc.

Want unlimited nesting? Set up a relationship that lets you do that.

Need recurring tasks? Set up an automation that reopens or clones tasks with a recurring field you've added, every week or day or whatever.

Want to know which tasks are "available"? Set up a formula field for that which looks at start date, the task statuses of any blockers, and whatever else you like (time of day even).

It's very cool.

HereBeBeasties··on Show HN: DivestOS – Long-term support for end-of-life Android devices
Actually support for 1st gen iPhone SE this ended on 12 Sept, along with iPhone 7, which they only discontinued 3 years ago.

They only supported the 5C for two years after they sold the last device.

https://endoflife.date/iphone

HereBeBeasties··on Multiple assertions are fine in a unit test
I bet if it were in monospace and you were reading code in context rather than on HN you'd have noticed.

That said, NUnit has much better syntax for this, where you put parallel/multiple assertions like this in an explicit block together: https://docs.nunit.org/articles/nunit/writing-tests/assertio...

Much less boilerplate duplication in the actual test framework, too.

HereBeBeasties··on Multiple assertions are fine in a unit test
NUnit isn't much better. You'd think that they would have good test coverage and therefore high confidence to make changes, especially to fix actual bugs, but I gave up trying to get patches in because the core devs seem so afraid of breaking anything, even when it's an obviously-isolated private, hidden bug fix or performance improvement.

"We can't land this tiny fix because we have a release planned within three months" sort of thing.

HereBeBeasties··on It looks like I’m moving to Mastodon
It has cost Musk a lot of money, but the critical point here is that it has also cost Twitter a lot of money: Because it is a leveraged buy out Twitter owns the $13bn debt that was raised to buy it out.
HereBeBeasties··on It looks like I’m moving to Mastodon
There was $13 billion of debt used to finance the buy-out. It's a leveraged buy-out, so the target company owns the debt, not the buyer.

How do you think that debt ends up getting paid off? It'll be close to $1 billion every year just to service that debt.

Given that:

* Twitter has only ever made a profit in 2018 and 2019

* That the profits it made in those two years were $1.2bn and $1.4bn respectively (only just enough to service this new debt)

* That for 2020 and 2021 other tech companies were comparatively minting it, but Twitter burned ~$1.3bn

* The world is generally in the early phases of what is likely to a deep recession, with ad spend and consumer spending already well down

It feels like a bit of an interesting purchase, to say the least.

It should be noted that the plan to charge users $8 per month for a blue verification badge wouldn't even service the debt if 25 times more people bought it than currently have it for free.

HereBeBeasties··on Uify: One Workspace
I can highly recommend https://fibery.io. They have a comparison of Fibery vs. Airtable if you are familiar with the latter: https://fibery.io/blog/fibery-vs-airtable-we-connect-your-ba...

The only thing it's really lacking is granular (per-field/entity) access controls, which is on their roadmap (although it's worth noting it's been on their roadmap for quite a while).

HereBeBeasties··on The Framework Laptop Chromebook Edition
After spending £2k on a high end HP x360 only three years ago, and suffering since from horrid thermal throttling, crazy loud constant fans, terrible battery life (2.5 hours at almost idle light web browsing usage) and a spicy pillow battery, followed by being ghosted by their tech support (three attempts to contact) and finally discovering via YouTube that they don't even supply battery replacements for this model, I can only recommend you stay as far away from HP as possible.
HereBeBeasties··on Why you might want a domain-specific database like TigerBeetleDB
I'd be fascinated to know what sort of things it is hard to write Postgres extensions for and how that interplays with their existing architecture choices, if you have the time to give some examples.
HereBeBeasties··on New MacBook Air with M2
If you're not fussed about a bit of extra CPU usage and you are not playing games on it, you can use a DisplayLink-capable hub to run two 4k screens @ 60Hz. E.g. https://www.sonnettech.com/product/m1-mac-dual-displayport-a...
HereBeBeasties··on Tesla Autopilot Almost Steers Model 3 into Oncoming Train
That might be what some weaselly lawyer argues it means in court, or what someone deeply familiar with it all would infer. But in no way is that how any reasonable lay person would read it.

"Improve functionality over time" implies that the basic functionality of full self-driving is there already, and that it will be improved. No reasonable person would take it to mean "does not exist yet, and may never do".

They would also take "capable of" to mean "right now", not at some nebulous point in the future, especially given the context of the feature being a paid upgrade.

The definition of "full" is "not lacking or omitting anything; complete". One might reasonably expect "full self-driving" to mean a human does not need to intervene or monitor. I.e. What the industry commonly calls autonomous driving level 5. They clarify what they mean elsewhere on their web site:

> Autopilot, Enhanced Autopilot and Full Self-Driving Capability > are intended for use with a fully attentive driver, who has their > hands on the wheel and is prepared to take over at any moment. > While these features are designed to become more capable over time, > the currently enabled features do not make the vehicle autonomous.

So they don't even claim level 1 autonomy.

Even with your version, the hardware may very well never be capable of full self-driving at all. There's no evidence to suggest it will be - hopes, dreams and promises don't count. And they've done an upgrade on the earlier-gen Model S cars already, where they presumably made similar claims.

The whole thing is misleading at best, downright trading standards fraud at worst.

For what it's worth, my Model 3's carriageway departure warning kicks in randomly and the amount of phantom braking it does even on basic cruise control is terrible. Autopilot is worse. I find monitoring it in autopilot mode significantly more stressful than just driving the car myself. I wouldn't trust FSD at all, and certainly not enough to want to fork out the silly money it is.

HereBeBeasties··on GitHub Code Search (Preview)
GitHub code search has been terrible since forever. They keep braying about preview stuff, AI search, etc. but when will this make it into their mainstream (let alone their on-prem) Enterprise product? (This has been in preview since December last year, but https://github.blog/2018-09-18-towards-natural-language-sema... was posted back in 2018 yet is still to be released.)
HereBeBeasties··on Lapce – Fast open-source code editor
LAPCE == Lightning-fast and Powerful Code Editor

I.e. Lightning-fast comes before Powerful.

HereBeBeasties··on In praise of --dry-run
Terraform does frequently suffer from the lack of good separation here though, depending on the provider in question - a plan can often succeed where a subseuqent apply will fail. Too much external state / not enough validation, generally.
HereBeBeasties··on In praise of --dry-run
These observations speaks volumes as to how testing is often done badly. It's a bit of a generalisation, but if you move your reads/writes to the periphery, the core tends to be pure functions that are easy to unit test without side-effects. If you don't move your reads/writes to the periphery, everything becomes an integration test, with the accompanying brittleness, lack of performance, and resistance to change. TL; DR: Stop designing/implementing things such that you have to mock everything; DI is just a tool, and as such it is used for both good and evil.
HereBeBeasties··on Tesla Autopilot director contradicts Musk’s self-driving timeline
I think we'll crack fusion power before level 5 self-driving cars. And that's been ten years away since 1950. :-)
HereBeBeasties··on Go is a great programming language
It depends greatly on the task.

If it fits neatly into the built-in data structures or smells quite systemsy and C-like, it's probably fairly easy in Go.

String and array manipulation are similarly painful to C. The lack of generics can be a massive pain in the neck, meaning you end up copy/pasting things, and other people's code doesn't tend to be very easily extensible without actually editing it to add the appropriate interfaces or whatever. The lack of OO is sometimes fine, sometimes not. It's really not a very expressive language. (I appreciate that's a rather fluffy/vague thing to say, but I feel it's true.)

On the other hand, you can cross-compile stuff trivially, you get nice self-contained binaries, it's generally sufficiently performant, and it's simple in the same kind of way C is, only with a garbage collector and easier threading (goroutines are pretty nice).

There's no more ceremony really compared to something like Python+Flask, but the business logic you end up running behind your web API calls _may_ be a bit more verbose and feel clunkier. Or if you're lucky it may not. It's very much dependent on what exactly you're doing.

HereBeBeasties··on Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script
But you don't understand. 100x less code than k8s means that using it must reduce my own codebase by 99 million lines of code! Who wouldn't want that?
HereBeBeasties··on Bitcoin is not a Battery – it is a Sink
Your argument does not hold water: Gold consumes vastly more energy and produces vastly more CO2 to produce and move it than Bitcoin does. Or does the pollution from gold somehow not matter?
HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
But this is exactly the philosophy in the NPM ecosystem where things like left-pad are rife. And NPM is generally considered a dumpster fire precisely because you need 8,000 deps for relatively "simple" projects like a basic create-react-app project.
HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
It probably doesn't. But are you saying devs never updates their dependencies?
HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
This really doesn't help when devs just upgrade everything. Or if they simply install the latest (p0wned) version of something. Pinning hashes really isn't the answer here.
HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
I just don't think that's realistic for the JavaScript ecosystem, for the majority of projects. E.g. The weight of something "standard" like create-react-app.
HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
How does it work in practice, though? For example, create-react-app in NPM has a bajillion deps. Do I trust 8,000 keys? Which ones are OK?

I get that you could in principle namespace things (at least for package managers that support this) and insist on a small set of company-internal signing keys for those namespaces. But managing all that isn't easy and what about for package ecosystems that don't really have namespaces (e.g. PyPI, NuGet)?

HereBeBeasties··on Dependency Confusion: How I Hacked Into Apple, Microsoft and Other Companies
A good look at their (public) bug tracker might change your mind about how surprising this is.
HereBeBeasties··on Element (Matrix chat app) suspended from the Google Play Store
In web terms: - Element is like a browser - matrix.org is like a bulletin board

In e-mail terms: - Element is like a mail client - matrix.org is like a given community of mailing lists

In IRC terms: - Element is like an IRC client - matrix.org is like an IRC server/network e.g. Freenode.

← PreviousPage 2 of 6Next →