skysight-inc/HackerNews huggingface dataset:
Yeah, it's inconsistent to be honest. I've found that Hitron to not have any sort of firewalls (except for IPv4 NAT if you consider it as a firewall), while Huawei routers (which is not used in the US for reasons hopefully known to you) do have an IPv6 firewall that is only an off or on switch, stupidly their enterprise stuff do have advanced controls, Alcatel/Nokia-branded ones are inconsistent to say the least and the same can be said for Zyxel. I'm actually interested in checking out other routers used by ISPs, but those are the ones I've actually seen.
There's just a lack of ability to own a product as an engineer. Those things are delegated to managers and product owners; lead engineers are really just there to align work - not really to make broad vision beyond suggestions.

If engineering firms wanted to improve they'd ensure that everyone who has decision making power over a product, whether from a business or technical perspective, is at the same level and has the same input. That way refactor is weighed the same as a new feature or service.
We are (of course) also taught to be this way. So much of our education focuses on deconstructive and critical thinking versus constructive thinking.
Our epic treatise on how NAT traversal works (in general, not specific to Tailscale) mentions this. IPv6 greatly reduces the amount of pain for p2p connections, but does not eliminate some of the fundamentals (stateful firewall traversal) if you want it to be zero-config: https://tailscale.com/blog/how-nat-traversal-works/

But until deployment hits 100%, and until ISPs start caring about IPv6 reliability the way they do about IPv4, "just use IPv6" can't be your answer. It's lovely when it works, but you need to do something other than "give up" when it doesn't. (also, as long as the internet is dual-stacked, doing IPv6 right also implies figuring out if NAT64 is in play, and wielding it correctly; so arguably IPv6 adds more complexity to the overall story, for now :) )
I've been in the industry since 1998. Things have gotten worse. Part of it is that in certain ways more is expected of software today but that's not entirely true.

Currently I'm involved in working on a "data intensive" app which munches a few dozen gigabytes of data and presents summarizations through a web based UI. Usually in the form of charts, time series plots, heatmaps etc. Adding small, incremental features to it is an ordeal. The "backend team" needs to mock and then provide the API endpoints, then the frontend team needs to "break down the work on the React components", then DBAs need to oversee the new queries. The security team needs to review risk impacts etc. One change is at least a few weeks of work.

Contrast that with the work that I did in 1998. It was a "data heavy" desktop application that visualized in 3d seismic data collected by ultrasound probes. The data volumes were in the order of hundreds of megabytes up to a gigabyte. The app was built as a desktop app using FLTK and OpenGL. It took about a day or two to roll out an incremental feature once we knew what was being asked. By two weeks it was in all of our customers' hands. While there was no Stackoverflow.com and we relied primarily on offical documentation with the help of "Effective C++" and "More Effective C++" the build/debug/test cycle was much shorter, the tool chain was much simpler and more transparent, the UI toolkit was much easier to grok and even though it didn't have an "elegant state framework" somehow we made it work well without turning it into a mess.

As an industry, we gave up on localized desktop processing in the name of "consumer preference" (or so we were told) while we assumed an immense amount of complexity in order to server the same computation from a centralized place.
> modern Porsches have a 15-20 year average lifespan

Probably because the Macan and Cayenne are not 20 years old yet.

There's a huge functional difference between something like a 911/Cayman and a Macan. While a 911 could be a daily driver for some people, practically speaking, they aren't. They are largely garage kept, driven infrequently during inclement weather, and are well taken care of because many people view them as "dream" cars. Even expensive engine out services are viable on 20+ year old 911s because someone is willing to pay $20k to have it fixed so they can have a "cheap" 911.

A Macan is a nice car, but it's still a warmed over VW crossover. People drive them like regular cars. They will get in accidents during evening commutes. They will see snow, salt, pot holes, etc. They will be driven 12-15k miles a year, versus the 1-2k of a 911. And these things will still be pricey to fix. These will age like BMW X-series: kept for short lease terms by the original owner, for the duration of the extended warranty by the second, then be recycled at buy-here-pay-here lots until an expensive repair sidelines them permanently.
civil disobedience

radical doesn't mean violence
Check out Gather.town. It helps a bit with audio overlap.
Thanks for responding, greatly appreciated!
That's a valid argument if your threat model only involves other visitors who aren't given access to see email addresses, but it breaks down if you're hiding from the site administrators, an attacker who obtains admin access, and whomever the attacker makes the data available to.
Out of curiosity I googled around for the longest lasting cars[0].

The bottom line is a combination of the manufactured reliability of the car and the maintenance behaviour of their owners.

> Which Car Brands Last the Longest?

> Honda, Toyota, Hyundai, Kia, Acura, Lexus, and Ford all have long-term reliability. Certain vehicles are known to outlast others, however, each brand offers consistent reliability and longevity.
What Is the Longest-Lasting Vehicle On the Road?

> A 1968 Volvo P1800 is considered to be the longest-lasting vehicle on the road with over 4 million miles across its odometer. There are also a great many million-mile cars, including a Lexus, a Nissan Frontier, and a number of others.

> According to one study, however, Toyota’s Sequoia SUV is more likely than any other vehicle on the road to eclipse 200,000 miles.
What Cars Will Last 300,000 Miles?

> According to iSeeCars’ study on longest-lasting cars, Toyota’s indomitable Land Cruiser tops the list of cars more than likely to hit over 300,000 miles. However, it doesn’t say whether that’s the old generation used by many countries’ militaries, as well as the United Nations, or if it’s the newer, more pedestrian-oriented model.
What’s the World’s Most Reliable Car?

> The one you take care of. Just kidding, but not really. As mentioned above, how you take care of your car factors into its reliability. In an official capacity, J.D. Power names the Lexus ES, which shares underpinnings with Toyota’s Avalon, as the world’s most reliable car.

[0] https://www.thedrive.com/cars-101/36055/longest-lasting-cars
Those are some good ideas, I will reach out to you on Twitter, thanks.
How do you know that a geek has a system where they use a unique variation of their email address for each place they sign up?

Answer: Don't worry, they'll tell you about it.
It's always about power and politics when bone-headed decisions like that are made. You correctly identified that _you_ did not report to IT, therefore _you_ were a threat to IT's power. Maybe you could have been re-orged under IT, but they probably saw you as a troublemaker who wouldn't kotow.
this is untrue. (source: firsthand)
> If you are a constitutional lawyer, then it would expedite the conversation if you presented your professional credentials.

We can both save time by reading the draft opinion, which was created by the foremost Constitutional experts in the world.

In it, you'll see relying on a 50 year old decision that was loosely predicated on an unrelated right to dictate national abortion laws, is outmoded. Privacy doesn't cover the sentience of a 39 week old fetus for instance..

I actually think most people are in agreement on the issue, they just don't realize it. A tiny percentage of people support no regulations at all on abortion (ie even an elective abortion at 39 weeks with no medical necessity would be legal), and an equally tiny percentage on the other side who would even be against Plan B or abortions in the first few weeks. The problem though is then that means you have to draw a line somewhere on non-medically necessary abortions (8 weeks? 24 weeks? Something else) and that isn't something that the Roe decision is able to address, so we have to look to legislatures (state and Congress) to do their jobs.
A lightweight Python web API framework
APIFlask released 1.0.0 now.
I’d argue the quality of tools is the problem. I am starting to view every new tool as just a new set of log messages I have to sort through to figure out why things aren’t working.

I spend more time trawling GitHub issues to find workarounds than I do actually using the tools.
I guess my problem with lululemon is that it’s too low quality not so much price
Short term, yes, there's lots of demand for front-/back-end web developers and the lower barrier to entry makes it a solid choice. Long term, though, it's a race to the bottom as more people flood in and eventually web developers become easily replaceable commodities.

(Don't take that the wrong way; it's not criticism of web development. It's just what generally happens when there's an oversupply of anything in a marketplace. We've been in a boom for web developers for a long time and what goes up must come down.)
Rustgo: Calling Rust from Go with Near-Zero Overhead (2017)
I wanted sleep tracking without a fitness band or watch, so I got a sleep mat from Withings. It works as intended and is also great for bedtime triggers.
If I were you, I would stick with applying for senior or management positions if that's what you're looking to do ultimately. Are you interviewing or are you working on your resume?

If you have any long-term clients in your portfolio, maybe break those out as subsections within your resume under freelance/contract work. Instead of having many bullet points for freelancing, you have it broken out by company/project.

I'd suggest working on the proof of concept projects in your downtime with the language you're interested in working in. Unfortunately, I do not see many PHP jobs (that I'm interested in, at least). Still, I'm seeing many Go, Python, Ruby, Java, and .NET jobs, and you seem to have familiarity with most of those languages.

I think an excellent senior developer can understand the core concepts of what's going on in the application even if they're not an expert at writing the code, so I would lean on the fact that you bring prior experience with several different languages, and over many different industries. You'll be able to share pain points you've run into, best practices you've learned over the years, etc.

Best of luck in your job hunt; stay focused and keep your head up - don't devalue yourself!
Ditto, but the fact that they still can’t handle more than ~300k files is a long-standing problem they have yet to solve. I have close to a million syncing files and startup time for the app takes about 20 minutes on a brand new MBP, and CPU and overall energy usage is ridiculously high. All while they keep pushing me to backup more files.

I pay over $700/ yr for their business plan and would like to have better performance for it.
Good points. I haven't thought a lot about it, but I still don't see how this new system is radically easier to learn. Looks like I have to be concerned with notes partially on lines, an irregular staff, two notes occupying the same "space" on the staff, etc. Then there are clefs with numbers...now I have to remember what "number" octave I'm in. And for piano, you lose the white key/black key distinction, which is obvious with accidentals in traditional notation. (This is specific to piano, and maybe not terrible.) I just don't see any tremendous reduction in cognitive load.
Kanboard, Grocy and Lychee:

https://kanboard.org/

https://grocy.info/

https://github.com/electerious/Lychee
I'm also curious about the picture of Bedroom 2 on that listing. It seems to have its own set of stairs. That seems to be between the third and the fourth floor since it has the open section in the smaller area.
Gname – mailing list archive since 2002 via NNTP
Walking hills is the best walk.
At my previous employer, every quarter we were supposed to update an elaborate spreadsheet describing how we measured up against the numerous criteria for the next level on the career ladder. I hated it.

That said, there were lots of people who obsessed over the process, looking for shortcuts or ways to game the system.
I don't think so. Not anymore than playing a video game is a "social experience". Someone who enjoys a choose your own adventure would probably enjoy solo role playing.

Someone who enjoys solo role playing would probably enjoy role playing with others.

Why is solo role playing any different than playing a video game alone?
That only addresses half the problem, though, right? Can't Tailscale still add any nodes they want to one's network?

Also, it doesn't address the individual case, but that's fair enough: Tailscale isn't a charity.
Can Boeing’s Starliner finally get off the ground?
Your peers are rewarded for accomplishing their goals. In the best-case scenario, the incentive is to find ways to synergize your goals so you are all benefitting.

In the common-case scenario, you figure out how to bribe / cajole / coerce them into putting time in on your project and don't really care about how things are going on their project, because we're all responsible engineers who can time-manage ourselves, right? So you get your promotion and they get screwed because the work they did to deliver on something valuable to the company isn't reflected in their OKRs.

It degenerates what should be a collective goal of accomplishing the company's objectives the best way possible into a slotting game of making sure you're always listed on paper as being on the right project, because your work won't have value if you applied it outside your bullpen.
Mr Ciechanowski's articles are themselves complete works of art. Another brilliant article and collection of interactive animations.

My favourite escapement is the detent escapment. I saw a cutout model at the Imperial Science Museum in London. Even after staring at it for ages I could not figure out how it worked!
Those days are not gone. Forums mated with IRC and became Discord.
I agree, though I think you're missing most of downtown and west oakland, jack london square, plus the oakland hills, most of marin, almost all of the peninsula, albany and el cerrito, san jose, and maybe now even santa cruz.

It's difficult to downplay that when you go to almost any house party in those places, it's literally what this guy wrote. Like down to the overconfident assertions that one person already knew about the other person's super niche point about some obscure faux-spiritual tech concept. “Of course it can, that’s the whole point of Buddhism." I'd bet someone said that exact, absolutely terrible phrase within a ten block radius of Haight & Ashbury within the last 18 months, for sure. And they name drop some partnership they have with a new startup thing with someone on its board who once worked for the esalin institute as its like vp of sales and mindfulness.

Still, I do think there's just as much diversity on the far periphery of the Bay as there is in say the outer borroughs of NYC. You don't get this in Vallejo.
The author of the TFA isn't criticizing the language, he's criticizing a particular example, and he's claiming that hash tables are generally really useful.

In the example, maybe the static size of the table is fine, and maybe not being able to remove items from the table is fine, but unless maybe it's some sort of cache, it's almost never ok to assume that there will never be any hash collisions.

I mean, if you don't want to include hash tables in your language or library, fine, but using a bad example to attempt to justify it after the fact is.. not good.
Ah thanks. Sounds like I need to re-think my video player UI to make that more obvious.
> I think the market is always right.

How long does it take to be always right? A lot of these comments at best imply significant lag, and at worst imply the market is perversely wrong.
Try having a family as a sole earner on 200k in the bay area. Or new york.
Aha, I didn’t realize this use case other than web based use cases, thanks for the sharing!
With no discount, one A100 is about 3$/hour, so we are talking about 600K$ for a full training. Probably closer to 1M$ since in practice you never train successfully to the end on the first shot.
I think the problem with the promotion culture is that you can't demote someone after they've been promoted. If you just focus on showing impact and cross team projects, your engineers will naturally build more complex projects than needed to hit those targets. The key is to track the long term maintainability and quality of the systems built. E.g. time to land diffs, incidents, performance metrics, etc. If a system starts to quickly fail these things or don't last then it is a pretty good sign that the project wasn't actually built well. Things aren't always under a single person's control but a lot of people will work on a big complex (seemingly good) project and then bounce after they've gotten their promo.

I do think there is a balance though because at a lot of startups the incentive is to just crank out a lot of product code but not really think about multiplier type work.
Lifestyle branding is aligned with specific emotions about status.

Ralph Lauren brands men who own horses and play polo as aspirational, that doesn't go against tradition.

Lifestyle branding that associates "eco" with status... well that makes the front page of HN.
Not everywhere is like that. Smart small companies will eschew this unnecessary complexity to get more done with less.

For example, we have deliberately stuck with a single Node.js/Next app in a single repo using Postgres running on Heroku. We are 5 engineers now and plan to keep it that way for the foreseeable future, even as the team grows.

There is some complexity we probably don't need – the JavaScript ecosystem is notorious for this – but what we use is all reasonably boring tech at this point, and it allows us to stay productive as a team, focusing on delivering value instead of just maintaining things or chasing trends.
Mitsubishi Electric faked safety and quality control tests for decades
Pretty sure TypeScript discriminated unions don't work unless you have a type field you can switch on.
It's a bit dismissive to just focus on scaling as a cloud advantage. You also have lower maintenance, easier redundancy, lower chance of outages, easier backup and more such non-functionals. A 200GB DB costs about $50/month on AWS (other providers are less), that's not an interesting amount of money for most businesses.
I've never had a "works on my machine" bug when dependencies are managed per project. The only time I have ever had them is with global/os-level dependencies. And I've used cargo/npm a lot in the last few years.
Just a quick google search of the author. I guess he died on that hill and got resurrected to being an internet icon, feel free to DM him your thoughts.

https://twitter.com/martyweiner
Now add labor cost of a person to stand by the tee box all day and validate potential winners.
Then a 3rd-party app is the most-likely route-of-compromise, as it could explain a tweet without a password-compromise or password-change.

If you regain even read-only access to your account, check/trim those first.
Vaultwarden and Jellyfin
One thing I like about the sigils is that they make bad ideas hard to type.

Want to pass me a hashtable of lambdas that return arrays of alternating functions and regexps?

Go ahead. Show me how to invoke it. I'm waitng.

Python (which has all of the type safety and expressivity of perl) allows such abominations to hide behind clean looking syntax.

Sigils also improve readability. Bad Perl looks like serial port noise. Bad Python looks like good python.

(In Python's defense, it has a nice ffi.)
Yeah I get it. But that is an issue with technical management making a long term decision without planning correctly.

Sounds like your managers are either looking at those trendy tech jobs too (and want to have the buzz words on their resumes) or they think the trendy tech will attract candidates.
I've integrated keycloak for SSO in our apps, we have a one-to-one mapping between keycloak realms and the tenants in our apps, works great and it can glue together many disparate IdP/auth solutions: onelogin, LDAP/AD, etc. At one moment we needed to implement a custom OTP method, so we developed a plugin by implementing a simple SPI (the auth flow is configurable).
It is a very stable piece of software, we have a combination of Terraform+ansible scripts to deploy it, and once it is done we forget about it until we need to upgrade the version using the same scripts. The biggest drawback IMHO is the documentation quality ...
Take a look at Algorand. 1000+ TPS (going to 10000 within a few months), blocks in 4.5 seconds, fees less than one penny.
Things I’m really looking forward to seeing from Tailscale / projects I’d like to tinker with:

- Better iOS battery life, there have been many improvements but it’s still too much to leave running 24/7, I understand they’re making improvements here

- Their in built SSH server which seems to be in development

- Using Tailscale ACLs to control access to Kubernetes ingress resources, they recently released an nginx auth plugin so I imagine this is now possible if you attach a Tailscale sidecar to the nginx ingress controller

- Arbitrary ACLs which also seem to be in progress, it would be awesome to define in ACLs who has access to different parts of e.g a backoffice application

- Official support for DNS extra records, already using this with the Headscale self hosted control plane for personal projects but it would be great to use it on Tailscale too

- Kernel Wireguard for the data plane, I think this is on the roadmap?

Overall a fantastic piece of software which I use for both personal and professional projects.
- Emails (Postfix, Dovecot and their friends)

- Nextcloud (files, contacts, agendas, picture sharing),

- Invidious

- WordPress I guess for the few websites I maintain.

- PeerTube (to host videos for my choir)

- Trivabble [1], a network Scrabble game I started, which is used quite a bit, so I guess it counts, but not by me (because I don't enjoy playing Scrabble).

I probably forget something but those are the most used.

[1] https://trivabble.org/demo/ | https://gitlab.com/raphj/trivabble
I don't know GScript, but wouldn't it be enough to know which methods are declared in GScript (and not allow overloading for these)? Then type inference can work fully most of the time and only give up when calling non-Java code.

Also, why does this complicate the parser? It looks like you're interfering some type information from later usage (the `foo( someVar )` example), so handling typing in the parser seems a bit strange.

As for the bytecode, it's not just methods: Fields likewise are identified by name and type and can be overloaded. I'm just happy that Java itself doesn't allow field overloading - I'm not the biggest fan of method overloading either.
You can go to rei and try on excellent socks from smart wool or darn tough that are equivalent
Why Do We Have WiFi Passwords?
I feel you 100% on this. I wish I could use something like Discord for work as it has nested threads, channels, etc all in an intuitive way.

Right now, my main teams are using "Teams" instead of Chat and everything is so painful to have a discussion.
There would need to be something big to override individual interest.