1,379 karma · joined March 10, 2024
It wouldn’t take much to just sound like jumbled noise.
Hearing aids have come a long way but all of the ones I’ve used still basically suck when it comes to understanding speech. Part of it, I think, is that my loss isn’t bad enough that fully closed ear pieces are recommended and as such background noise is still free to obfuscate conversation.
It basically makes conversation in anything but a quiet room extremely difficult. My brain works overtime trying to fit possible words to what I hear. Sometimes I fail with pretty humiliating results.
It doesn’t take much before you just stop trying to talk with people. Especially with the younger crowd because they tend to speak the quietest. It varies by individual, but at least older people who’ve had some loss themselves will speak louder to compensate.
The worst is restaurants. Usually I can guess what’s being said by the server, but not always. Accents increase difficulty.
I used to be pretty out going, joked a lot with people. Now I avoid most conversations when I can.
The most common type that is used would probably be logical equivalence checking. Proving RTL and a netlist are equivalent is useful for catching synthesis bugs.
Or proving two netlists are equivalent after inserting test functions directly into a netlist, or some other netlist edit.
Property checking is what I use the most. You can check these during simulation which I wouldn’t call “formal” but you can also prove them using tools that use SAT solvers and whatnot to prove things mathematically.
As always, the tricky part of verification is writing the correct test or model. With formal we can use SystemVerilog assertions to write properties and sequences, but the difficulty in getting them right goes from trivial -> inscrutable very quickly.
It’s extreme easy to write assertions that pass and never realize your assertion was not doing what you thought and you weren’t proving what you meant to.
I haven’t used some of the more advanced tools so maybe they have ways to make this easier. But because of this I tend to just write assertions that are pretty easy to understand at a glance, and therefore closer to the trivial side of things.
If a peer has to solve a sudoku puzzle in their head to understand your work, then it’s unlikely the peer review will be worth anything. So I do what I can to make my work understandable at a glance (from a competent peer in the industry).
Of course making something simple can be quite challenging and often takes more time than leaving something complex and opaque.
I’ve never been involved in the foundry side of the work, and for ASICs, that is often half of the schedule.
But it doesn’t matter. Those historical parties have nothing in common with their namesake parties today.
I don’t remember if my computer at the time had built-in Ethernet or if I had to buy a card.
I have been always-online ever since. Wouldn’t have it any other way.
But I do still miss the BBS scene.
It’s not a step I’ve seen discussed very much, so it was kind of neat to see it discussed front and center in a lay article like this.
I mean you can get good stuff out of it if you know what you are doing and guide it, but if you just say “here’s a regression suite. Write an implementation that passes” you will get something that works for a while but ages quickly and will need to be thrown away.
I drive too even though there is a risk of death. The juice is worth the squeeze.
Except even armed with positive identification, the police won’t do anything. Laws with enforcement are worth nothing. Stalking and whatever else has happened with the data is already illegal. But who gives a shit without enforcement.
The other states I’ve lived in haven’t been so straight forward.
But I don't tell my team what they have to use as long as it's compatible. The last thing I want to do is try to teach them a different VCS when they've spent time learning how to get by with git.
I've told them about JJ, what I like, what pain points it solves for me. They are all adults, they can make their own decisions about it.
JJ is for me. It helps me unwind some rather elaborate problems we've had with rebasing, or dealing with conflicts from bringing some old support branch up to date, or back porting some particular thing. It helps me create pretty clean MRs, break things up into smaller reviewable chunks, etc. You can do all this with git, but it's easier in JJ. In particular if you have to do shuffling and rebasing and conflict arise. JJ lets you solve conflicts asynchronously to rebasing. Git stops you in your tracks. There's some rerere thing that is supposed to help but give me a break. Git's a train wreck of dumpster fires. But it's still been basically better than everything else since svn.
Until JJ IMHO. Valid arguments can be made for other things like maybe mercurial or even fossil. But JJ is the most pain-free vcs evolution I've seen.
Mercurial's big failing was making too many critical things optional. It's the same screw-up riscv is going through now in the chip architecture space.
Cook joined apple in 1998. They were not a behemoth. His first year, their net income was 300 million for the entire year.
JJ is just so low friction. The seamless and painless shuffling of commits, working up and down the commit chain without explicit rebasing, unchanging change-ids. The min identifiers in change-ids being highlighted. Being able to make commits and worry about the message later. Snapshots of changes while you are working serving as a tool agnostic undo.
Painless and sensible cli args that are vastly more consistent than git.
Superior conflict handling.
You can “jj undo” anything and it works perfectly.
It’s fabulous.
> "@--+::"
I have no idea what that means and I’ve never had to type anything remotely like it.
The rev specification language is pretty elaborate but you don’t need to know it.
With regard to how visual the minds eye is, I have this anecdata:
For me, when I’m visualizing mentally, usually with a memory, replaying something, I stop registering what my eyes are presently seeing. No visual memories form of what my eyes were seeing while I was absorbed with reliving the memory or visualizing some idea.
I have to be careful about this when I get bored while driving.
I feel like I’m reading reviews of wines. This font has chocolatey overtones that bring the reader to a meditative state of hyperflow.
Maybe if we have some breakthrough in how to get equivalent ai capacity out of less compute it’ll seem crazy in retrospect.
But the magnitude of flops per token on SOTA models is mind boggling huge.