oscillonoscope

I think it's less a middle path than a third option. I see the type of thinking the author is commenting on whenever there is a tight requirement on a feature. Especially when you know you have to add some custom magic to meet the requirement. People tend to psychologically buy into a fully custom solution early on. So they either hack in a custom solution using abnormal data paths or known bad solutions or they fundamentally rearchitect the system around it. The third path is sketching out the feature so that it's modular and can be replaced. That way you can start out with a standard solution which gets you 90% of the way there then replace it as development progresses.

If I need to move a 'branch bookmark' around a lot, I usually just tie it to an empty commit and then rebase changes before the bookmark.

Congress is completely nonfunctional. It doesn't work. Americans are just too dedicated to American civic religion to admit it isn't working.

It took a small company I worked for months to get new licenses due to AMD just not responding. I'm not sure they have the ability to actually handle this in a timely manner

This might have made sense for the original 13 colonies but after westward expansion, it clearly does not. Most of the western state borders were formed for administrative reasons

There is no legal mechanism left that could correct course at this point. You would need to have a constitutional amendment to drastically reshape government and that's DOA. All that's left is snow decline and eventual dissolution

That might be what you intended but saying "outperforming the academic nerds with zero experience" comes across as bitter and arrogant.

Why are people who don't have degrees always so weird about it?

Language really isn't the difficulty. That's why there's a thousand alt-HDLs that have been used for little more than blinking LEDs.

Its both depending on context. If HDL becomes custom silicon then it needs to be treated like hardware. If you can easily deploy field updates to your device then it's no different than any other firmware

You are mistaken. In the workflow I described, I am making changes on top of all branches at once and then deciding which branch to send the new commit to. This allows me to make changes simultaneously to both branches without friction.

I more or less use the method described [here](https://steveklabnik.github.io/jujutsu-tutorial/advanced/sim...) for branches. One thing I do change is that I set the bookmark to an empty commit that serves as the head of each branch. When I am satisfied with a commit on head and want to move it to a branch I just `jj rebase -r @ -B branch`. When I want to create a new branch it's just `jj new -A main -B head` and `jj bookmark set branch_name -r @`

I worked in nim for a little bit and it truly has a lot of potential but ultimately abandoned it for the same reason. It's never going to grow beyond the founder's playground.

I don't really agree with that unless you redefine the ego as being synonymous with 'being egotistical' or 'sinful pride'. You need a sense of self to feel pride and something more than base passion.

For practical purposes, if you don't acknowledge how good and bad behaviors can both spring from the same base emotions/thought processes then it's harder to grow out of the bad behaviors. You need to be able to reframe how the ego interacts with your work, not just try to kill it off.

I'm not entirely convinced that ego-less is even a better way of doing things. Sure, the ego can go overboard but it also gives a sense of drive and direction. It isn't just the bad stuff. Without it, there's nobody taking ownership of the design or it's just designed by an apathetic committee.

I think that's hyperbolic. There are several designs advertised as being designed in KiCAD that have DDR which means there are way more not being advertised.

https://www.kicad.org/made-with-kicad/categories/Single-boar...

You can route DDR in KiCad and there are some online reports of people doing that. KiCad is not as nice as the paid software and there are shortcomings but I think 'pretty useable' covers its status accurately.

It's also tooling. Professional grade PCB design software can be acquired for a few kilobucks per year and OSS versions (KiCAD) are pretty useable. Professional grade IC design software is hundreds of thousands per year and open source competitors are barely usable in comparison. I do share your hopes though, democratizing IC design even a little would be a huge boon to hardware development.

It's partly because you're not paying attention. Next time you're out in the woods, try to still hunt for a while. It's a hunting method where you move extremely slowly throughout the woods from cover to cover while watching for animals. You'll find that it takes a lot of mental focus to maintain that level of vigilance.

If you haven't checked it out, nim sits at a really good middle ground for ergonomics, safety, and speed.

I don't know enough about LLMs to understand if its feasible or not but it seems like it would be useful to make certain tasks hard-coded or add some fundamental constraints on it. Like when making footprints, it should always check that the number of pads is never less than the number of schematic symbol pins. Otherwise, the AI just feels like your worst coworker

There are schematic analysis tools which do that now just based on the netlist

It also depends on what you're the go-to person on and what the promoted position is. Being the expert on some low-level technology isn't necessarily going to help you get promoted to a managerial position or the upper tiers of technical positions.

While full bandwidth applications certainly exist, it is rare. Most direct sampling schemes are used for having a purely digital RF front end within the Nyquist range of the ADC/DACs. It's cheaper and easier to develop firmware/gateware than debug analog RF issues and respin hardware.

It's very rare to actually utilize the full bandwidth of the ADC to do any processing in these. The data gets immediately decimated down.

I have noticed it is harder for getting people straight out of college used to a professional working environment. However, I haven't noticed any difference in getting them up to speed technically.

This type of debugging is fine for people just starting out or hobbyists but won't be useful if you're trying to design HDL professionally. You really need to be able to create accurate simulations so you're not debugging on hardware the entire time. Hardware debugging takes a long time (builds can take hours) and you're more limited in terms of how many signals you can view/how many samples you can take.

I've had Intel sales people tell me that the entire low end of some their marketed FPGA/ASIC products have never and likely will never be sold

Part of the purpose of the document is to sabotage surreptitiously. If you always take shortcuts and something gets messed up, it's easy for people to see that you were the cause. However, if you always insist on doing things through the proper channels then it's a lot harder for people to see that you're the problem or argue against your methodology.

It's a slow beginning. Tolkien focuses a lot on Hobbit culture as it's important to the morality of the narrative but it picks up very quickly. Oftentimes important events are only briefly summarized by one character to another as they meet up or narrated in brief chapters. That said, his writing style definitely isn't for everyone.