Hacker Newsnew | past | comments | ask | show | jobs | submit | oscillonoscope's commentslogin

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

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 @`


_Every time I see one of these nifty jj tricks or workarounds I find myself wondering, “why not just use git?”_


How would you do this in stock git?


I might just not be following correctly but committing in git just carries the branch along for the ride, so there's nothing to do in git for this scenario.

IIRC forcing some specific branch name to point to my changes with `jj` was non-obvious and what made me give up and go back to git when I tried it last year.


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 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'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.


Taking ownership is very much egoless! You are doing that for the team.

Ego would be making sure you got "your" sprint tickets done, did no code reviews, skipped the retro. I think few people do that but they will if Goodhart's Law happens.


Pride and passion can exist without ego. I view this as appreciating things for what they are, not who they belong to.


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.


Yes, and not thinking that one is better than anyone else. We are all equal, no matter how much better we are than another, with respect to either some job skill or even the spiritual path. Dunning-Kruger's true-experts are better than the slackers, but we must be humble to achieve that and then not be an ahole about our achievements.

It's a tricky business, being a human being, with its very many pitfalls.


You can never remove ego from the equation, completely. People are placed on different levels of organizations, with different incentives and agendas.

Thus, it's never a balanced setup where everyone's happily working towards a shared vision in equilibrium.

There's always someone having a larger incentive than the other person, overriding their decisions in a haste, in order to reach a bonus objective.

Welcome to the real World driven by capitalism.


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.


> OSS versions (KiCAD) are pretty useable

Until you actually need to route DDR, run any signal simulation model, etc.


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.


You "can" make fire with a piece of string and some sticks in a pinch.

I wouldn't describe this as a "pretty usable" means, however, for the same reasons KiCad is unusable for DDR routing.


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...


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 haven't looked at it in years, but that's what I've been hearing indeed.


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


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: