skysight-inc/HackerNews huggingface dataset:
And sometimes the reality is that the realistic answer to a time estimate is "If we are lucky it takes me 30 minutes, if we are unlucky 30 days".

E.g. when it turns out to your surprise, that a part you had in your hardware design was replaced with a part that was 5 cents cheaper, but uses a undocumented protocol that someone has to re-implement, so a goal that was trivial in theory has suddenly involves hardcore reverse-engineering in a high pressure environment. A thing all engineers love.

The only time someone can give you reasonably accurate estimates is when they do something that down to the tiniest detail they have done before. The problem with that is, that in software things change constantly. A thing that was trivial to do with library X and Component Y of version 0.9 might be a total pain in the rear with Library Z and Component Y of version 1.0.

But yeah, unexperienced engineers are going to be optimistic that it is possible, because in theory it should be trivial.
Yes, now do the math, if you owned a company, how much monthly revenue you must get per month to pay everyone at a similar salary level, plus government related taxes, office space, electricity, water.
Those issues are largely red herrings. Get into actual policy details and you'll see the consensus disappear.

Marijuana legalization is a great example. It's been consensus that it shouldn't have been as illegal as it was for decades yet it's only been consensus to treat it mostly like alcohol in a handful of states.

The consensus of "something should be done" can predate the consensus of "this should be done" by years or decades, especially nationally.
Into 10 years into the career, I have found that in the end its all about the people.
Most of the comapanies suck making life easier for software developlemt, with useless standups, lack of documentation, proper testing, quick tasks, and on top of it micromanagement, un-productive meetings and with no foucs on culture. To me, all this energy drainging activities.
It is hard to find the real joy for the job, in such cases.
I have ran Hound in my current co for about 2 years now, it's fine but the search experience is far below the SG one. SG is a far superior option but it is prohibetively expensive. I thought about hacking on Hound to be honest to rewrite the UI at least because half of it is broken.
> guidance with GPS

This sounds like a major liability, GPS is an extremely brittle and vulnerable system--you'd only need one or a small handful of nuclear warheads detonated in space to knock it out completely.

https://www.scientificamerican.com/article/what-happens-if-a...

OTOH it would be so much easier now to develop a celestial navigation system that works optically than it was back in the 1950s.
>If you have two analog guitar amps of the same model, it is legitimately possible for one to behave so differently from the other that you would hate to swap them.

This bug can actually be a feature even if it's just some random reason it sounds and plays remarkably better than the ones other players have :)
> "...all prior contract terms to the contrary are hereby void"

I don't think this second part you suggest is something the state can just unilaterally do if there's an existing valid contract and the other party doesn't agree. You could mandate that no contracts may be renewed and all contracts should be terminated as soon as the terms permit.
Very interesting. A couple of notes here on the C# version.

Its using the old format where the Program.cs file has an actual class, whereas as of .NET 6 thats not required.

You said barebones, but for any real server you would want to use the generic host https://learn.microsoft.com/en-us/dotnet/core/extensions/gen... which gets you a lot of the boilerplate and enables you program to be wrapped in a windows or systemd service.

Finally, parsing can be simplified since ASCII is a proper subset of UTF-8, you can just parse the entire string as UTF-8. IMHO I am disappointed that the AI didn't point that out.
I've always felt like I was missing something obvious for why there weren't submarine-launched SAMs or ASMs.

Seems like a really good way to target AWACS/tankers and valuable softer shipping, provided you have missiles with active guidance and can deploy launch pods under the sea, scoot, and then they launch when you've left the area.

Granted, much harder to do before networked unified sensors, but not nowadays.
Houston is actually a good example of this: the city has no zoning laws and so the workplaces are relatively evenly distributed across the metropolitan area. It may not be ideal, but you don’t really appreciate this aspect of the city as a visitor.
Yeah at least I want a mouseover to see the real timestamp, and the column to be sortable.
There's a "inZOI: Character Studio" demo in the Steam page that just allows you to create a character. Beyond that, this page just seems to be a marketing page to get people to join their discord/newsletter and to wishlist the game on Steam.

Mod suggestion: change the title to "PUBG developer Krafton is developing a life simulation game inzoi"
Belated lagniappe (for those no longer familiar with the folkways of the old country)

https://youtu.be/okJtUACFmcA

(Underrated channel, btw)
If you're pro-war and support this kind of shit, you should know that every fight has two possible outcomes: you can win and you can lose. This is the same reason you don't wanna be a police officer or go to the military if you're not ready to die. After all the pain people have experienced in eastern Europe, Gaza, Middle East, it's sad to see this has been funded by YC.

It's pretty obvious it's the same "defense" system as AK-47. While it's easy to justify, it will be used, highly likely, to kill people.
Peter Lowe's Blocklist
Thanks everyone for the feedback regarding the issue with readability in light mode. I completely missed it!
Garden leave hurts everyone if key people are disallowed from working in their peaks years of their societal contributions.

More generally, in high turnover industries, we're taking out x% of the workforce and paying them to not work, not develop skills, etc.
If you're on a Mac (at least, I assume Windows too), you just plug them together, they automatically get link-local IPs, you click "enable" on File Sharing (SMB) and boom you're sharing files.
> It’s fun because fixing self-contained, reproducible bugs like this is what so many of us enjoy the most about software engineering in the first place.

Do really "many of us" enjoy that? In the "day-to-day business", not interviews.
Wait until it gets released

The character creator demo is available for this week https://store.steampowered.com/app/3092450/inZOI_Character_S...
This is common in many interviews, not just "bug squash" interviews. I recommend having a plan for it if you're interviewing. Perhaps dedicate a virtual desktop to interviews if your system supports it.
> where the join is ambiguous

Join table that maps to an entity in the middle.

You can even have multiple columns that have foreign keys against various tables, like some_table_id, other_table_id, another_table_id with only the needed ones being filled out.

And in practice, this will be way more manageable than the dynamic mess of the OTLT pattern (table_name and table_id): https://www.red-gate.com/simple-talk/blogs/when-the-fever-is...

It's not like you have to particularly care about the fact that most of those columns will be empty in practice, as opposed to making your database hard to query or throwing constraints aside altogether.
The absolute worst are ones like “last month”, “last week” or “earlier this week” - almost absolutely useless! Especially for logs of things that happened at work, I extremely frequently want to know the day and date something happened, but that style obscures that sometimes to the point where you can’t even tell which week it was!
Second Life meets Sims?
Yeap. Venue shopping for political appointees who legislate from the bench.
Shielded on the inside and baked in an oven for a day or two. Surviving specimens were deemed of the military grade and passed QA.
I’m having a hard time following how such naive time handling became part of a Google product. Pick an epoch for timekeeping. Timezones are a display issue.
On the Apple end of things, Thunderbolt was always sold as essentially the next generation of FireWire
Why bother living?

Anything I like doing is dangerous. Meeting people is likely to give me COVID, having sex likely gives me VD, wine rots my liver, fat fucks my arteries and clogs my brain, eating fish gives me mercury poisoning and micro plastics; even vegetables contain poisonous alkaloids. Now even a little red meat each day is likely to give me diabetes (and I've not even gotten onto the matter of the dangers of sugars or their artificial counterparts).

I'm fed up with being lectured about what's going to kill me if I dare indulge.

Perhaps we should start at the end and say that life is a fatal condition and anything we do—especially anything enjoyable—will bring its fruition forward.
Last miles booster rocket or no enginr after climb?
1. No, it doesn't react to file additions/deletions at the moment, but as there's support for this in fnotify which is handling file change notifications [1] I'll add this shortly. wd-41 is still quite early in development.

2. This was my initial idea as well: to simply inject the ws-load script tag on the fly. But it would require basically writing a static file server from scratch, which I didn't feel like doing (I have a blog to write, not static file servers!).
Currently the solution is based on the go standard library fileserver handler [2] which makes the solution simple and effective. So i decided on the mirrored approach with the idea that the result for the end user should be the same, apart for the temporary directory where the mirrored files lives. I haven't yet detected any speed-issues in the mirroring process or the file-watch process, which I think is the only downside (please correct me if I'm wrong).

[1]: https://pkg.go.dev/github.com/fsnotify/fsnotify#hdr-Watching...

[2]: https://github.com/baalimago/wd-41/blob/main/cmd/serve/serve...
I've settled on devd (modd) for the past few years.
https://github.com/cortesi/devd

It's a single file go executable.
Supports CORS too.
I use it via direnv & nix-shell.
Judge tosses FTC ban on Non-Competes
He said "I think" implying that he is not fully sure about the etymology. There is a history section on wikipedia for refactoring if you are interested.
I understand a junior dev as someone who's missing (or does not have at a greater level) of maintainability, readability, longevity of a solution.

I don't know what companies pay for and I don't care, because if we go by that, every definition of every word is arguable (because there's everywhere someone out of the range of the definition)
>If you can, but don't want to or you opted for hybrid

How many really "opt for hybrid" in these times where so many places are forcing RTO?
https://archive.is/Hv3aZ
The workflow goes like this: I’m working on a React application where users make API requests and send data. I need to capture the user’s public IP address before storing the data. Currently, my method returns the local IP address, but I need the public IP address instead.
Pieter Levels: Programming, Viral AI Startups, and Digital Nomad Life [video]
Try making that argument on the other side and come back and report how well it goes afterwards...
It's really silly how few trucks you see with 8 foot beds anymore. Half of the stuff built now has a shorter bed than one of my S10s (6-7ft), and loading sheet lumber in a shorter bed really really sucks (you've either got to leave the tailgate open or prop it up on the tailgate, and either way you've now got a pretty serious liability that you've got to strap down real well). The trend towards unibody trucks is also strange since it means you can't pitch the pickup bed for a more useful flatbed or a Reading bed. I used to wonder why trucks didn't come off the lot with at least a tommy gate and a ladder rack, but I've since come to realize the vast majority of people (especially people purchasing half ton trucks) would never use or even know what to do this those.

The kei trucks aren't really a good replacement even for an S10 since so far as I can tell they won't run at highway speeds, but they're really good replacement for the Canam and Polaris money pits people buy (and are certainly way more capable of real work).
Why would that be difficult?
DONT get me wrong. What you're saying I actually support. If this allows that company to have quality staff I'm all for it. The less time we both spend on each other the better. So just offer async processing.
I apologize if this is an offtopic but if you're looking for an alternative, then we have tried Mattermost and it was almost identical. Importing slack data took some time and tweaking but in the end, everything went through without any major issues.
Good luck!
> The most promising approach I've seen so far is... DST! First we simulate a system, we generate a bunch of timelines, then we see if those timelines are valid behaviors in the TLA+ design.

That’s just testing again. That’s not linking the code to the design.

DST feels to me like the way people treated memory access before Rust came around. Doing things properly was also seen as too costly then but now that it’s trendy everyone is fully behind lifetime tracking. Same here, formal proof is “too costly” but spray and pray approach like DST is somehow acceptable. Anyway, keeping with the Rust example I guess I just have to wait two decades and the next generation might finally see the light.
In my mind, the association is with a sitting dog that has its tail wrapped around it.
Do you realize there exist other types of businesses?
You are making the argument that Americans would consider it inhumane to live in Swiss apartments because they are too small?
It was originally created to enforce antitrust laws and prevent "unfair methods of competition"

Here's US code Title 15§45(a); note that the subsequent acts have broadened the FTC purview rather than curtailed it. Later clauses in the subsection limit the FTC's power for foreign commerce, and define "unfair or deceptive acts or practices" but do not define "unfair methods of competition":

(1) Unfair methods of competition in or affecting commerce, and unfair or deceptive acts or practices in or affecting commerce, are hereby declared unlawful.

(2) The Commission is hereby empowered and directed to prevent persons, partnerships, or corporations, except banks, savings and loan institutions described in section 57a(f)(3) of this title, Federal credit unions described in section 57a(f)(4) of this title, common carriers subject to the Acts to regulate commerce, air carriers and foreign air carriers subject to part A of subtitle VII of title 49, and persons, partnerships, or corporations insofar as they are subject to the Packers and Stockyards Act, 1921, as amended [7 U.S.C. 181 et seq.], except as provided in section 406(b) of said Act [7 U.S.C. 227(b)], from using unfair methods of competition in or affecting commerce and unfair or deceptive acts or practices in or affecting commerce.
My honest experience in a skilled team has been that people more or less start off thinking "OK, what indices do we need to make this performant", work off of that, and then in the end try to have queries that hit those ones.

I understand the value of full declarative planning with heuristics, but sometimes the query writers do in fact have a better understanding of the data that will go in.

And beyond that, having consistent plans is actually better in some ideologies! Instead of a query suddenly changing tactics in a data- and time-dependent way, having consistent behavior at the planning phase means that you can apply general engineering maintenance tactics. Keep an eye on query perf, improve things that need to be improved... there are still the possibility of hitting absolutely nasty issues, but the fact that every SQL debugging session starts with "well we gotta run EXPLAIN first after the fact" is actually kind of odd!
The significant lump sump is often expressed in months of salary per years worked, which is not that much, compared to how much a house costs.
> I hope that practice doesn't catch on.

I got news for you, they invented something called websites and all they do is remotely disable what appears in your browser. Next thing you know, they place them in webviews and show "Your browser is not supported because it's running on a 8-year-old device."

I don't know how else to tell you that they did not break something that works, but simply stopped serving an old web view because supporting it DOES NOT come for free. Do you still ship IE6 views for the lone monthly viewer too?
Vitamin D is probably not the only benefit derived from sun exposure:

https://www.nature.com/articles/s41598-023-43653-2#:~:text=L....
What do you think about using btrfs snapshots instead of ostree similar to openSUSE MicroOS or SLE Micro?
And the final step is component standardization at the dimensions and interface level.build new cheap systems on the fly using automation and cheap standardized subcomponents. 3 batteries, 1gyro, 1 motor,1 cpu, 1 explosive , wrap it in shrinkwrap,firmware + mission upload and every one can buy it, every can use it, end of world, MOSAICs

Forgot the camera. Basically push a cellphone into standardized brick, not to unsimilar too industrial plc bus cards.

ps:in picture a bigdog like system built by lego of death:

https://github.com/PicassoCT/MOSAIC/blob/master/luaui/images...

pss no reason to not build cruise missile like systems from the same lego.
Is there a small and portable one you recommend?
Sonoma's unfinished business: exclaves, conclaves and the kernel
I agreed I have gone so far as to replace strings in HTML with the date in the <time> tag, but it is not always available in that tag especially now with Javascript frameworks taking over. Further your wording makes it clear to me why date formatting is hard, what is most significant is clearly subjective.
Live bug squash is better, imo. I was part of the production support at my $DAYJOB. My work was literally finding and squashing bugs all day. And yet, if you were to ask me for interesting stories, I won't be able to tell you anything. Maybe I'll remember the latest bug I solved but most of the time, once the bug is resolved, its off my mind. I will have to go through my jira and github history to first see which bugs I even worked on, then filter for the interesting ones and then try to remember the story instead of just the root cause.
It's so on brand for YCombinator to look at all the problems facing the world and finding that the issue that needs fixing is that destroying hospitals in the middle east could be cheaper.

I hope everyone involved is rewarded as handsomely as Perilaus was.
Love that you’ve kept the workspace support from Rye. Is there any support for workspace _builds_? That is, resolving the graph of interdependencies between packages to build a wheel/Dockerfile/whatever?

Fwiw I’m building a thing [1] that does this. Current docs suggest Rye but will s/rye/uv/ shortly. It’s basically just some CLI commands and a Hatch/PDM plugin that injects needed stuff at build-time.

[1] https://una.rdrn.me/
I’m guessing salaries are higher where non competes are banned since you are able to leave for a better paying job. So it’s good for the worker but bad for the employers.
In the universe in which I "know" what index to use (an assumption that can be contested!), you saying "well silly you, the planner is too stupid to figure this out" is not a great defense of the system!

My serious belief is that all the SQL variants are generally great, but I just want this to be incremented with some lower-level language that I can be more explicit with, from time to time. If only because sometimes there are operational needs.

The fact that the best we get with this is planner _hints_ is still to this day surprising to me. Hints! I am in control of the machine, why shouldn't it just listen to me! (and to stop the "but random data analyst could break thing", this is why we have invented permission systems)
Thanks for recommendation. I just finished my rounds of interviews, gotten a decent offer (SF company), being 20 years in industry. I have my own rules, and luckily they align very well with industry standards. So I never had any issues not following the scenario when I need to share something to land a job. I also don't do any take-home assessments, and moreover, I only use one programming language while interviewing. Never had any issues with that.

I think I don't need a plan or virtual desktop. I just say "no" if it doesn't work for me. Unless I am really desperate, I do not share.
yay

you know we’re going to have this Supreme Court’s law of the land for the next 50 years, instead of focusing on what’s impractical for you have you considered shaping the country in ways that are practical?

Genuinely curious because thats what I don’t get about the SCOTUS dismay crowd. Isn't there some agency out there you hate? Some regulation thats set you back? Go after that one. Focus on what you can control instead of what you cant.
It does make me wonder how many bugs like these exist in the average codebase. In this case there was an "unusually large" amount of reports, all coming from the same timezone, all filed at the same time.

But imagine getting a single bug report, which doesn't provide a timezone or timestamp and essentially boils down to "I swear it said the wrong date yesterday but it fixed itself!": how much time are you really going to spend trying to reproduce it before closing it with the conclusion that the user was probably just imagining things?
COTUS needs to explicitly grant the power to federally regulate and homogenize employment contractual terms with the Department of Labor because, right now, they are a patchwork and vary state-to-state. Currently, every large multinational employer has to maintain potentially up to 56 different employment agreements to cover every US state and territory, but more typically it's around 6 to 20.
So if I go and work for Iran's missile program it's fair game then right?

Best guarantor of peace is their large stockpile of weapons too.
Show HN: Extension to transform GitHub timestamps > duration b/w timeline events
Sure, but advocates are talking about multiples of increased productivity, and how can that be defended if it doesn't scale to a project of some size and complexity? I don't care if I get a Nx increase on a small script or the beginning of a project. That's never been the pain point in development for me.

If someone said that, over a significant amount of time and effort, these tools saved them 5% or maybe even 10% then I would say that seems reasonable. But those aren't the kinds of numbers advocates are claiming. And even then, I'd argue that 5-10% comes with a cost in other areas.

And again, not to belabor the point, but where are the in-depth workflows published for senior engineers to get these productivity increases? Not short YouTube videos, but long form books and playlists and tutorials that we can use to replicate and verify the results?

Don't you think that's a little suspect that we haven't been flooded with them like we are with every other new technology?