> I don't see circuit-as-code taking off with humans anytime soon
I don't agree with this. Circuits aren't really anything more complex than anything else humanity has had to figure out. Most knowledge in this area seems solvable.
Maxwell's equations have been known for a century.
For whatever reason, Software Engineering and Hardware Engineering even though they rely upon the same fundamental physics, are so very different? And apparently can't be reconciled? No. I don't believe it.
PCB layout is as much art and black magic as it is science. I'm not sure why you dismiss the complexity so easily, this definitely is not just a matter of applying Maxwell's equations.
The big problem is kinda the same as what happens in push polls -- in that they ask misleading or suggestive questions trying to boil the issue down to a good and bad answer.
The reality for many of these questions is pretty complex.
I'm not saying it's not worthwhile, but I'm saying forcing users to choose on some topics aren't black and white.
It's maybe worthwhile getting information on things like people who aren't knowledgeable, people who don't care or have no preference, or people who don't want to answer because the answers are skewed towards one side.
I think you’re correct in that lots of things aren’t black and white, but the reverse is also true. Lots of arguments end up being over-litigated when a black and white answer (even if imperfect) will suffice.
As with most things like this, you get out what you put in. Ask a biased question, and get a biased answer. At some point, the responsibility has to lie with the user that if they want something like this to be interesting and unbiased, they need to think about ways to use it to accomplish that.
Like, someone comes with a problem, great. They suggest 2 options. Lets assume one is super biased. The asker is just fishing for compliments. The jury decides on a third option of 'No, actually, your dilemma is terrible, we need to re-word this'
Then you get some people to recraft answers for it. One person gets to craft one answer, another the other answer. Then a third person to adjudicate that both are acceptable. Then it goes to the jury.
Annnnnnd like the game 'Werewolf', we're expanding this to have all kinds of fun little jobs. Because of course we're going to need a bailiff, and a court reporter, and a stenographer, etc.
For getting this off the ground, yeah, there needs to be a 'send this back' button. But once it does get going, then more fun little jobs will be good to have as updates to keep people interested.
What's weird about reading this post is that tailscale itself is over-engineered (at least on linux anyway).
I was shocked to find the number of netfilter rules in place, all of which made the normal linux routing table useless.
I think a lot of what they're doing is neat, but when you're trying to debug forwarding rules on a box running docker as well, it kind of becomes a nightmare.
Docker messes heavily with the forwarding tables as well. One or the other is fine, but mixing the two is kind of a nightmare to sort through.
The previous version wasn't "flood" routing. Because flood routing would have worked better. I called it "spray and pray" routing.
It was something like this:
1. Router repeats first
2. Weakest repeating device by signal strength next
What if both of those options are in a basement, or say have a damaged antenna, or are miles in the opposite direction of where you want the signal to go?
By simply putting up a router somewhere you might be severely impacting the comms of people at your edge.
Meshtastic's routing system (up until this last version), wasn't great. I haven't tried the latest version, because it's gonna need to take a while for people to update their firmwares.
Also, a lot of nodes tend to flood their battery state for the entire network, which uses up the airtime for something that could be more important like routing information, and also wastes their battery.
Even though things like AlohaNet have been around for years, Meshtastic chose to reinvent the wheel. The primary difference is that Meshcore started with "routing" first, and then save the airtime and therefore battery for routing messages.
geerlingguy did a video on it, and it's highly worth while checking it out. I think he was kind enough to use the term "Beta".
Supposedly the new firmware from Meshtastic fixes a lot of this, but it's gonna be a while for people to upgrade, and I'm not too keen on wasting time again on something if it's not fit to work for it's stated purpose originally.
What's interesting from a legal perspective (to me anyway) is if his call list and contacts are protected by attorney client privilege.
I think maybe the correct answer is to backup your phone in the cloud, and then factory reset it before coming back into the US.
You might also try to mail the phone back to a friend in the US with a tracking number, then you'll know if it got seized in customs, and you can fight it there. You might have to pay a tariff on it, but the tariff might be worth it to avoid trouble at the border.
> Customs and Border Protection (CBP) asserts a very different principle: that your privacy rights disappear at the border. CBP policy gives officers the right to seize and search any electronic device that passes through customs. While the agency claims that copies of any attorney-client documents will be "destroyed" after a search, it doesn't recognize limits on its ability to collect and copy those documents in the first place.
1. Any government agency can assert anything they want, until a court strikes it down.
2. CBP/ICE don't just operate at the border (which is problematic). They are an arm of the government seizing people without warrants. (Which is also problematic).
It's really a beautiful little show. Quaint, funny, and warm-hearted without being cloying or saccharine. Manages some mild drama and even melodrama without feeling forced or annoying.
Wholeheartedly agree, and the two leads, Toby Jones and Mackenzie Crook (who also is the writer) are both exceptional (both in this and elsewhere). Really worth checking out. Also fun fact: Diana Rigg who played Andy’s girlfriend’s mother was her mother in real life.
I think maybe a better approach I saw was to sweep and vacuum up NY City sidewalks for gemstones that have fallen out of people's jewelry.
It's similar to the idea of sweeping up the edges of high travelled roads looking for palladium. But I think the palladium recovered wasn't worth the effort. But the gem stones might be, even if they're tiny.
Fixing other's shitty code doesn't push the needle -- particularly in an industry that strives to get customers to open their wallets and shell out hard currency.
If a company's ultimate goal is to extract money from people, then developers who can extract money faster (even if their rendering/loading algorithms suck) will get rewarded better than those who don't.
That's why enshittification is a thing (and actually come to think of it, not new either). It might be a dev that learned from product leadership that, "I could fix these 13 lines of code. But you know, our company could also sell a 'PRO' version subscription for $5 a month which provides the fix..."
Yeah, it's sad but this is the reality. Caring about your craft is for your passion projects / hobbiest endeavors.
Once your beautiful software meets the reality of the real world and business it all falls apart— you can either take a mindfulness approach and just come to accept it or let it drive you mad.
The goal is to write not-bad code. You're not trying to do shoddy work on purpose but good enough is good enough.
Lots of development shops care about UX/DX. Many Indie games are crafted with love and often many are successful -- even releasing bug fixes and updates years after it entered the shop on steam. Many high level developers learned how to write good code quickly, not just for themselves, but for the people that came after them.
If presented with a good argument, most people will agree to logic. Unfortunately, many business decisions are made behind closed doors to avoid dissent -- or even any discussion of alternatives.
I don't agree with this. Circuits aren't really anything more complex than anything else humanity has had to figure out. Most knowledge in this area seems solvable.
Maxwell's equations have been known for a century.
For whatever reason, Software Engineering and Hardware Engineering even though they rely upon the same fundamental physics, are so very different? And apparently can't be reconciled? No. I don't believe it.
reply