skysight-inc/HackerNews huggingface dataset:
> I work at place where these architects, devs wouldn't know how to go beyond SpringBoot 1.x and Java 1.8 but from up there they are introducing Kotlin thinking it would relieve us of all Java development woes.

I actually migrated a number of apps from Spring Boot 1.X to 2.X and also older Spring versions to newer ones, as well as a variety of apps from Java 8 to Java 11 (17 might be in the cards, but perhaps not anytime soon) - it was a total mess and a pretty nightmarish experience.

From what i can tell, all software, with every framework and every stack rots with time. I've actually written more about it (in an absurdist fashion) in my blog post "Never update anything": https://blog.kronis.dev/articles/never-update-anything

Other interesting writing that i've seen online in regards to this is "Green Vs. Brown Programming Languages": https://earthly.dev/blog/brown-green-language/ which posits that our enjoyment and sentiment towards languages depends on how old they are and also how many bad legacy projects need to be maintained in them.

> Well the way things go in companies, by the time it all turns to turd original authors would have gone to other companies to create next generation software.

Ergo, this actually seems like what most developers should optimize for on an individual level: you don't want to stick around for 5-10 years and see your project get corrupted into an ill maintained piece of trash due to ever changing requirements, new features needing to be tacked on but not enough effort being put into refactoring, testing or keeping up to date with dependency releases.

Instead, you might want to stay around long enough so that you can start to feel the consequences of your actions, learn from the experience as much as you can and move on to other interesting and new projects, which will also be nice to put on your CV due to "CV driven development" sometimes being almost a must (or having plenty of personal projects, or just being able to network well instead, which is not attainable for all).

Because of this, i'd advise most to avoid doing what i did - migrating legacy code isn't nearly as flashy as working with new tech would be like. It was also very painful and demotivational at times, especially when the code quality wasn't great to begin with, nor was the documentation.
In your opinion, what are the most important things to look for in a code review?
This is wrong for many reasons, but I'll just give one example: what if you're a gig worker? Here's some guidance: https://www.uber.com/us/en/drive/tax-information/
You can already do your taxes for free! A 1040 form is only 2 pages long. And even if you have a complicated situation, you can follow the detailed instructions it still only takes an hour or two.

But, you will probably end up paying the sticker price on what you owe. When people talk about making them free or easier, they are invariably talking about making it easier to claim credits or itemize deductions.

In which case, it's hard to understand the incentive policymakers have to make it easier for people to pay less in taxes.
+1 FreeTaxUSA
Why do you think it means it was a non-issue? The employee could have sold credentials just as easily as anyone else.
Image Classification with Gradio, TensorFlow and Keras
> In SPA world there’s an API server which is self-contained and has clear boundaries — take JSON payload ish and return JSON payload ish.

In theory yes, in practice I’ve more often than not seen the same team build both client and API meaning they’ve just added a bunch of operational complexity without having anything to show for it.
Especially devs who have years of experience are surprising me when it turns out when I take over that error was abvious and right there in the exception with stack trace.
The article already mentions the alternative of slipping in a low volume of MFA notifications instead as an alternative that is less suspicious. You only need one person to accept. And I think you overestimate how much attention engineers pay to any security or compliance type of training.
Or kids, or a house, or an. Electric car, or a 401k, or an HSA

None of these are hard to track, but they’re more complications that take time to fill out in our current, broken, system.
The Unicorn-ish startup.
These comments are extremely uninteresting. If you care so much, please just create an issue on their bugtracker or something.
One meta question is whether this problem is worth solving at all ? There are places where forests are much easier to grow, and we are cutting them down by the thousands on a daily basis.

For carbon capture, it is much easier to densify regions with already suitable conditions than trying to plant a few trees in inhospitable regions.

Food is a solved problem in the modern era. High cost agriculture is unsustainable in a global market. If non-mechanized farmers in highly arable places (India) are being priced out, then what hope does harsh desert agriculture have ?

Given other 'low hanging fruit' solutions, is the opportunity cost of pursuing such a solution too high ?
I didn't get a smartphone until 2014. It was frustrating how so many people in the tech bubble acted like everyone had one long before most people did and just didn't bother with web sites anymore, leaving me out of so many new things. The failure to peek outside one's own experience is a continuing problem among the people deciding what the world will look like tomorrow.

See also: the internet. People still discussed seriously whether or not it had staying power as recently as 2008. It didn't really take off until the 2008 election pushed so many people to participate in new mediums. 2004 was kind of a prelude with Howard Dean's campaign, but he mostly reached the already online set. I was already on in the 1990s, and it still surprises me when I meet people my own age who didn't get on until the 2000s or 2010s even though it's the more common experience.
Ideally it could be a compiler flag. Even more ideally, you could tell your compiler what the max size you want is and then it would optimize for the best speed at a given executable footprint.
To be fair, other hand dryers only do better on this metric because they don't actually remove the water from your hands.
The domain is, exactly, lossy.
Decimal representations have one really minor advantage: they behave more the way people expect with respect to which numbers are exactly representable especially in the size ranges of every-day numbers, since they exhibit mostly the same behavior as calculators do.

Plenty of people find that 0.2 not being exactly representable in binary floating point is not intuitive.
Love this idea, even though I do use a computer for similar things. For me, the big mistake was "the fancy computer can do so many more fancy things, I should use ALL OF THEM." And over time, I realized the better way was thinking -- "99% of what you're doing on the computer can be done on paper, let me treat it like for the most part, and slowly slowly experiment with the things that look like improvements, knowing that most of them will not stick."

Turns out they are pretty much all just quicker versions of things I would do with paper anyway. Hyperlinks instead of rifling through an index; Quick note adding instead of finding post-it notes, automatic date-fill in instead of looking at the calendar, etc.

(this is through zim-wiki, btw)
We are easily 20+ years away from simply adding a conversion kit into a taxi to make it driverless.
Any studies on traffic and congestions with regards to autonomous cars? I’d imagine it would be fun to simulate something like this.
Just when you think those guys can't stoop any lower, they go and surprise you yet again.
Mechanical (or aerospace) engineering.

Fun/easy reading: Skunk Works: A Personal Memoir of My Years of Lockheed (Ben R. Rich)

Textbook:

Shigley's Mechanical Design (recent editions are by Budynas/Nisbett by older editions with Shigley as an author are just as good as an intro)
Useful Shell Prompt (2020)
If the host server is compromised, attackers still will not be able to access secrets.

Vault attempts to mitigate this with its 'seal' functionality, but in practice if an attacker gains access to a running Vault server, and/or the cloud provider account it's running in, there are many ways that secrets could be exposed.

EnvKey allows you to avoid trusting the host server, full stop.
Typical gatekeeping. I like Go, because it lets me get stuff done. You could say the same about JavaScript, but I think Go is better because of the type system. C, C++ and Rust are faster in many cases, but man are they awful to work with.

C and C++ dont really have package management to speak of, its basically "figure it out yourself". I tried Rust a couple of times, but the Result/Option paradigm basically forces you into this deeply nested code style that I hate.
Would you please stop perpetuating flamewars on HN and also please stop using HN primarily for political/ideological battle? We ban accounts that do those things because they destroy what the site is supposed to be for.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
Same here. Actual Sudafed works for me and anything else I think generally only tends to work with whatever NSAID they bundle with it.
Hints for Writing Unix Tools (2014)
That's only 99% of the story. :) Having too many specializations of a C++ template can lead to code bloat, which can degrade cache locality, which can degrade performance.
The future isn't american cities (as they are now). I'm cool with living in cities, so long as they are closer in feel to Zurich or Tokyo than NY or Chicago or LA.
In the browser on Fedora/Firefox, it works too, but maybe it is an issue with the desktop application
I'm a big fan of hybrid, albeit default remote. But this is one example as to why. For most groups, most of the time remote is fine. There will be circumstances where there's no substitute for in person communication. You cite a great example.

For your situation I would imagine in a hypothetical example where your team composition stays steady for a long period of time you'd find that you required onsite less often. And in that case I'd advocate that defaulting back to remote is a good thing.
Those are still secondary sanctions.

Op wants to be able to hire somebody with a history of abuse without google enforcing them
Conversational AI Programming with CodeGen: Let AI Write Code for You
I have a slightly contrary opinion. Systems software is a very large umbrella, and much under that umbrella is not encumbered by a garbage collector whatsoever. (To add insult to injury, the term's definition isn't even broadly agreed upon, similar to the definition of a "high-level language".) Yes, there are some systems applications where a GC can be a hindrance in practice, but these days I'm not even sure it's a majority of systems software.

I think what's more important for the systems programmer is (1) the ability to inspect the low-level behavior of functions, like through their disassembly; (2) be reasonably confident how code will compile; and (3) have some dials and levers to control aspects of compiled code and memory usage. All of these things can and are present, not only in some garbage collected languages, but also garbage-collected languages with a dynamic type system!

Yes, there are environments so spartan and so precision-oriented that even a language's built-in allocator cannot be used (e.g., malloc), in which case using a GC'd language is going to be an unwinnable fight for control. But if you only need to do precision management of a memory that isn't pervasive in all of your allocation patterns, then using a language like C feels like throwing the baby out with the bath water. It's very rarely "all or nothing" in a modern, garbage-collected language.
IoT Core is dead. Can’t recall the details but I wanted to use it and it no longer supports modern platforms.
I, too, enjoy Linus's YouTube channel! :^)

His meticulous approach of implementing specifications by writing code interleaved with quotes from the spec has inspired me to adopt the same style.
Zero cost from runtime performance, but you pay binary size for it. It's a trade off between the two...
> Also, remember that this was before smartphones, social media and the attention stealing craze.

No, smartphone already existed at that point, they just were not from Apple or with Android. More popular at that time were PDA and electronic organizers, from Psion, Treo, Blackberry, with Windows Mobile... Small optimized Offline-devices with sometimes optional network-access. Even the attention-sinks already were a thing at that point, but came in form of sms, e-mail, WAP-services.

But, not for the general population. Those things were expensive, and had limited benefit. So this Hipster PDA was the discount-version of those expensive Toys I mean it's even directly in the name...
By that definition, Java is a systems language as well.

I think Go makes a better trade-off than Java, but I struggle to come up with decent examples of projects one could write in Go and not in Java. Most of the “systems” problems that Java is unsuitable for, also apply to Go.
Is it secret? You can just cat file.txt > /dev/random if you want to seed the generator.
Another example. An airplane broke the sound barrier in 1948. Today, we are as far removed from Yeager breaking the sound barrier as Yeager was from a civil war hero being President (Grant). But we still have no supersonic airplanes in commercial service.
The Wikipedia article they link to [0] has a pretty long list of brandnames. Many of them are the "-D" version of whatever the thing is. Claritin-D, Zyrtec-D and so on. I think the version without the "-D" doesn't have Pseudoephedrine?

[0] https://en.wikipedia.org/wiki/Pseudoephedrine#Brand_names
> Certainly DNA sequencing for health has been a really mixed bag.

Ah, the old why bother since it's a "mixed bag" argument. If it wasn't a mixed bag I'd be really worried, as someone has some pretty good snake oil.

I vaguely recall something about sequencing and its role in creating a vaciine that turned out to be pretty useful, something recent maybe?
Recent discussion: https://news.ycombinator.com/item?id=30853836
I support the effort to build a platform-agnostic CI/CD pipeline solution, but I don't want it in the form of yet another platform. Rather it needs to be a protocol that any platform can tie in to. I'm especially wary since this is another VC-backed effort that will eventually need to be monetized in some shape or form.

Additionally, as someone else here has already mentioned, my mind first went to Dagger, the dependency injection tool (https://dagger.dev). That tool in particular was named as a play on DAG (directed acyclic graphs), whereas in this case I don't think it would apply since there may be instances where you'd want cycles in a pipeline.

On a whim, I clicked on "Trademark Guidelines" (https://dagger.io/trademark) and from that page alone I would recommend avoiding this based on the aggressive language used to try and claim ownership of generic words. According to their own language, it seems I'm violating their guidelines by writing this comment.

> Our Marks consist of the following registered, unregistered and/or pending trademarks, service marks and logos which are subject to change without notice: Dagger; Blocklayer; and other designs, logos or marks which may be referred to in your specific license agreement or otherwise.

> Blocklayer does not permit using any of our Marks ... to identify non-Blocklayer products, services or technology

Which would include Dagger, the dependency injection tool.

Other sections of note:

> Do Not Use As Nouns

(This one just reads amusingly to me, for some reason.)

> Do Not Create Composite Marks

This section seems to suggest that you can't use "dagger" in any shape or form, even as a smaller part of some other word or body of text.

> Websites And Domain Name Uses

>

> ... Any principal or secondary level domain name should not be identical to or virtually identical to any of our Marks.

>

> The website owner should not register any domain name containing our Marks and should not claim any trademark or similar proprietary rights in the domain name. For example, “daggertech.com”, “dagger-group.com”, “Meetdagger.com” are not allowed. Any violation of this policy may result in legal action.

>

> The website should otherwise comply with domain name registry policies and applicable laws regarding trademark infringement and dilution.

This would technically include dagger.dev, which again refers to the dependency injection tool.

---

Full disclaimer that I'm not a lawyer and there could be totally reasonable explanations for these provisions, but they certainly look scary to a layperson such as myself. All in all, the founders seem to be taking a pretty arrogant approach here, but it unfortunately seems to be a common one. I'm choosing not to support it, however.

---

EDIT: formatting
> Dev/CI drift: instead of writing the same automation twice - once in a CI-specific configuration, and again in a Docker compose file, shell script or Makefile - simply write a Dagger plan once, then run it in all environments.

Working on developer tooling, a lot of times I would hear from people that they wanted CI and dev to be 100% the same and wanted a simple "run all CI locally" command to pre-check before posting.

Unsure how Dagger is handling this but my concerns with the scenario I described

- CI normally divides things up into multiple jobs for speed which breaks the shared "do everything" command

- Commands need to scale down to fast iteration as people fix things

- Generally people get the best integration by using the underlying wrapped tools directly due to pre-commit or IDE integeration
> like residential culdesacs and parking lots

Literally the two easiest places it could go into
Except auto& does not prevent errors, and it is a source of innumerable problems, because '&' is too easy to forget.

auto* does not add anything to making code more reliable, either; it just makes code tied to a particular implementation detail (e.g. I could redefine things using my own pointer-like object, and the * would simply stand in the way for no good reason whatsoever.)
> so does its worker run on a native machine, because we need to build docker images using CI/CD, which we can't do easily within a container?

`dagger` is a client tool, which uses buildkit as its worker. Buildkit itself can run on a native machine, or inside a container. Either way, building docker images is one of the most common actions performed by Dagger, and it is very well supported.
In the case of the Uber autonomous car which killed a pedestrian in 2018, Uber reached a settlement with the victim's family and faced no criminal charges (I think the answer to your question is clearly yes). The "driver" behind the wheel of the autonomous car did get charged with negligent homicide in addition to being sued by the family afaik.
Floor and ceiling mirror configurations to study altitude control in honeybees
She had a score of 841, which was broken just 3 months after her record by Neil Gewirtz with 2,349 lines. The record is 5,164 points now.

https://www.twingalaxies.com/game/tetris-dx/game-boy-game-bo...
And this is the only reason the US is competitive in tech, around half the faang employees came through H1B/L-1 to EB. Those visas were designed to be dual intent, no-one was lied to there.

Just do what the EU does and leave immigration to the states, I’d be fine having a California-only green card before naturalizing. No one wants to move to Mississippi or any of those anti immigration states anyway ;-)
First priority is finding flaws. These are mostly objective. There are the obvious ones within the diff like missed edge cases, corner cases and unexpected behavior changes. Then there are less obvious ones, in which you have to think about the change in the context of the greater system. For example, checking for things like side effects, backwards compatibility and rollback safety.

Second priority is finding readability gaps. These are mostly subjective. Things like naming, structure, bad abstractions, over-complexity and intent. These are important, but providing feedback on them is a bit more nuanced. This is where the human element of code review comes into play.
I'm assuming you mean commercial supersonic flight? I'm pretty sure there are plenty of military supersonic planes.
> Also WFH tends to discriminate people doing "less important" jobs

Anecdata but my partner and I have a huge income disparity. I'd say our responsibilities are pretty even. There are things I tend to do and they tend to do. But in my mind at least it evens out.
Underlying cost doesn't matter to markets when it's priced the same as luxury cars. It's the same customers with the same disposable income and different expectations than mid-range.
I got the impression that the extra data is not collected by Waymo, it's collected by ariel photography and streetview cards. However it is in a sense because of waymo - they need to collect this additional data to provide the best maps to the autonomous cars.
Tron still relevant.
Now this is really making me want to find some of these!
> Fully autonomous warehouses has been a reasonable thing way before autonomous driving in the wild.

The issue in warehouses is that even before talking about control software behind automating, we simply don't have hardware for manipulators that are as versatile as human hands. That's why top of the line automated warehouses have sort of converged on automating everything except stations where humans can act like task reconfigurable pick and place machines. Better manipulators than biological hands is still an open research problem.

Automated cars don't have the hardware barrier, and as soon as the control software meets the required error rates, we should expect a rapid switchover to automated fleets.
Google has freedom of association. If they don't want to work with you based on your employees, that's their prerogative. That's not controlling who you can hire.

Really, it's a monopoly problem. You shouldn't be affected by whether google wants to work with you or not
> Facebook continues to be the single greatest threat to Western society outside of Russia.

No it’s not. The greatest threat to any society is its own ineptitude.
> On the other hand, slipping a single MFA notification in during the normal workday seems like a much better approach. Even if the employee doesn't accept the notification, they'd likely assume that it was a tab they opened earlier and closed before finishing the login, not something to report.

This gave me anxiety!
Can't read the article because of the paywall, but just because an accident "occurred while the vehicles were in autonomous mode, or within seconds after the autonomous mode technology had been switched off" doesn't mean the collision was the car's fault. The real question is how many of those accidents would have been prevented if a human was driving.
Qplasma = infinity just means that you have transferred the burden from just getting your plasma fusing reliably to the problem of converting the energy coming out into useful form. That second burden is one nobody has even started on. All indications are that it cannot match the economic value, even, of fission, at any Q.
Hi, we are a successful fast-growing re-seller that sees a large gap in the market for a new product. Currently, we are meeting and doing customer interviews. At this point, we are ready to start to design and implement our MVP. We are looking for a full-stack engineer.
This isn't really an answer, but I'd say that everyone's different. What works for you might be wildly different than what works for me.

For what it's worth, I'd say that it's about being at ease with being uneasy. I find it unproductive to try to get rid of uneasiness.