skysight-inc/HackerNews huggingface dataset:
thanks for your comment.

I definitely wouldn't phrase it as an ultimatum in the hiring process.

I would say something like, "I'd like to understand what I'll be working with. Would you be up for letting me sign an NDA so that I can view the codebases on which you'll be having me contribute?"

If there's pushback on that and they are asking me to do a puzzle, I might then frame it as follows:

"I understand that you need a strong signal about the skill of engineers you hire. I also need a strong signal about the technical elements where I'll be spending the vast majority of my time. How can I gauge this without looking at some of your code?"

And just go from there, depending on their answer.

Perhaps I'll edit to reflect that.
"...things like SOC compliance." This is an important point. If you work in a regulated industry or work with software used in a regulated industry you need a "paper trail". Having to document and follow a process is often frustrating to people who work or have worked in industries that don't require it. That said, a poorly implemented process in a regulated industry is even worse. As you're overloading teams with busy work and likely still failing to meet the requirements of the regulations you're following. Regulated software is not a place to "move fast and break things" that's what prototypes that never see the light of production are for. Build it without regulation to figure out how to do it and then build it again following the documentation process. It may sound odd but having a second chance to correct errors of assumption from the first time around is quite valuable, buying information when done right is a great tool.
What I am illustrating is that MILLIONS and MILLIONS$$ of dollars go into the design of these "environments" -- every major Architect on the planet will continue to do such, while claiming to be LEED/GREEN/etc...

Gensler is famous for such.

My job was to ensure proper installation and implementation of said designs in conjunction with all trades (Not the stairs per se...)

But - these types of designs are not going away.

(Glass' primary material is effectively "free" from the earth (not in energy or manpower etc))

---

So we can call out all we want, but this stuff is here to stay.
I understand what you are saying, but a request/demand like that would be a hard pass for me as a manager. I’ve worked at companies that require a high level of security clearance and we wouldn’t be able to show you anything before you are cleared. No NDA will fix that. What I’ve done before is to show cases or examples of fake code/work tasks that looks like production examples but are very different. This is for the candidate to get a feel of what they will work with.
This is, of course, an argument against a strawman. I wish the author had not mentioned certain folks by name, because the analysis is interesting on its own, and makes some good points about apparent simplicity. However, by mentioning a specific person, and then restating that person's opinion poorly, it does a disservice to the material, and basically it just devolves the whole thing.

My understanding of Jon Blow's argument is not that he is against certain classes of "safe" languages, or even formal verification. It is that software, self-evidently, does not work well -- or at least not as well as it should. And a big reason for that is indeed layers of unnecessary complexity that allow people to pretend they are being thoughtful, but serve no useful purpose in the end. The meta-reason being that there is a distinct lack of care in the industry -- that the kind of meticulousness one would associate with something like formal verification (or more visibly, UI design and performance) isn't present in most software. It is, in fact, this kind of care and dedication that he is arguing for.

His language is an attempt to express that. That said, I'm not so sure it will be successful at it. I have some reservations that are sort of similar to the authors of this piece -- but I do appreciate how it makes an attempt, and I think is successful in certain parts, that I hope others borrow from (and I think some already have).
The article talks about the unfriendly way a raw RSS feed is presented in the browser and how users do not know what to do with it.

This is easily fixed by adding an XSL stylesheet reference at the top of the RSS XML. The stylesheet not only contains HTML markup to format the XML in a friendly manner, but can also be used to inform the user what to actually do with the RSS feed.

The BBC do exactly this on all their RSS feeds.
You can do anything badly. Like point one, no you don't need to plan out exactly two weeks. You estimate what you want to get done in two weeks and then at the end you see how close you got.

It's supposed to be a reality check to see how well estimates are matching up to actual effort. Which I don't really see why you shouldn't do something like that.
Some previous posts:

https://news.ycombinator.com/item?id=30120457
76 points|breck|4 months ago|18 comments

https://news.ycombinator.com/item?id=624695
22 points|Maro|13 years ago|4 comments
Well the clients are still quite nice and you can use them with VaultWarden for free and get attachments.
That tells you absolutely no information a stacktrace doesn't. It's actually worse than just passing the err! Like, foo knew you failed performing foo, that's why you have the error, because foo failed. You don't need to reiterate that foo failed while performing foo, because the machine and user already know foo failed. See how annoying that kind of repetition is.

I've seen people that do that and it sounds nice until you end up with

Failed foo on x: failed bar on x: failed doing baz on x: failed to do quux".

You've created a worse stacktrace! I now have to search for a string and hope I can guess where the %s (or v or q) was instead of just grabbing the line number.

Or I do none of that, pass errors around directly, and just use the stacktrace.

The issue with your claim is that we only care about errors in two places, where we create them (like where the file was unable to be read) and where we handle them (when they are either swallowed bc the behavior was expected or passed to the user).

You don't care about them in all the intervening code, and exceptions handle that better.

> And why not have the most basic conditional take the role of that syntax?

Because it bloats your code and you end up with in practice more lines spent on verbose, cookie cutter error returning than actual logic!

Like, you don't need additional human readable context except in very particular cases. Go proves this in practice as almost everyone just returns the unmodified error most of the time, and it works great. Except for the annoying syntax.
What I like is that I can generally run `gpg --encrypt --recipient andrew` and it will search keys by a few different "fields" to find matches. I don't need to remember where I put the key file or even always the person's email vs name. Some people I can remember handles more easily than real IDs and that works just fine with the gpg database implementation.
Short of having benchmarks and standardized sysctl and web server tuning specific to your platform and network I would say generally but not always the latest as it will receive the most recent improvements. With improvements and bug fixes will also be a risk of new bugs. This answer is specific to your question but not my preferred answer.

My preferred answer would be the latest of the LTS series as you will have fairly recent improvements in network and storage performance with the least new and exciting bugs. Any time one is pushing Linux/Hardware to the limits they may be one of a small group of people to discover a new behavior. LTS kernels will have a bigger community of people and higher odds that others are doing the same thing and would have already experienced and submitted related bugs.

In summary, short of benchmarks that match your specific cases the answer depends on your risk tolerance.
There are engineers that don’t actually do engineering at many companies and they accrue many years of experience. Very common in defense companies in the US.
I think a properly framed response that politely conveys its bullshit and I don’t do bullshit could result in the hiring. But I think you miss my point (because I did not elaborate enough), being true to oneself is what lands you in a place where you are happy.
Isn't that always the case and the reason we "Can't have nice things"?

Most people are "honest and law-abiding", but you have a few rogues, either civilians or in government, etc., who spoil it for the masses of well behaved people?
I'm surprised and kind of impressed by the level of vitriol in this comment, especially given the relatively narrow focus of the comment of mine it's replying to, which didn't really consider the merits of macOS itself so much as the differences that give using it a very different vibe from using Linux for people who are used to desktop Linux.

I'm not going to reply to the ‘substance’ of your post but I will say that nothing you've written here is in fact news to me. A more curious person, or maybe just a person who is having a better day, might wonder what they're missing rather than lose their shit, when someone writes something that surprises them on the internet.
> One thing missing in a lot of suburban places is the ability to walk to do chores. ... what destinations do you have within 15 minutes of walking? Can you buy milk? Go to the bank? Have access to a coffee place? Etc.

This represents in part a terminology clash, I think, and I think it impacts the discussion a lot. "Suburb" means different things in different parts of the country. I live on the edge of what you'd call "suburbs" around Boston, and yes to all of these; my morning routine is to walk about 7-8 minutes down to the nearest convenience store for a morning beverage and maybe a bagel. It's next to my bank, across the street is a coffee shop and a couple of nice bars. Maybe five minutes past that is a liquor store, an Indian food market, and my auto mechanic.

I can be in downtown Boston, by train, in 30 minutes, but unless I throw on a backpack and walk 2.5 miles round-trip I'm not going to the hardware store or to a full-size grocery store. Which I do, when I have the time, but here's where the overlap with more conventional "suburbs" happens: when I'm walking somewhere, nobody else is. It's totally doable and totally reasonable, even in bad weather, but the locals don't have that mindset, so they don't do it.

Much of what folks like Strongtowns talk about is actually represented pretty well in my New England town, but we're the "burbs" because we're outside the city proper. On the other hand, I've been to places like Des Moines, IA, and the suburbs are just car parks as far as the eye can see.
The DOM timeline you describe would be pretty straightforward to create using a MutationObserver [0]. It's available in all major browsers.

[0] https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...
I submitted this with the time stamp for the relevant part of the video, but that seems to have been stripped off. As an experiment, I submitted it again, with the timestamp again, and that has again had the timestamp stripped off, and then, for good measure, marked as a duplicate.

So I deleted that.

For reference, the link as submitted is this:

https://www.youtube.com/watch?v=zzKgnNGqxMw&t=104s

When you include the timestamp it takes you directly to the most interesting part. You can "rewind" and watch from the beginning if you like.
Why would someone not spell that out in the title, I wonder.
Waterluvian says >"We cannot even begin to comprehend how people raise larger families with less. It seems impossible given how we barely get by at a socially acceptable standard."<

This is a bit snarky but your "comprehension" is seriously lacking! You're looking right at the situation and not seeing it: people do with less by spending less. They "make do." You don't need to "comprehend"; you need to meet some people who aren't as well-off as you and socialize with them.
I don't know what to tell you. You're describing a highly dysfunctional organization with no autonomy and extreme micromanagement. The right answer to all your questions is "leave, and try to work for a good manager in the future."

It is useful to do project planning and task tracking at a high level. But it's counterproductive to open a ticket every time you want to take a breath.

I lead a highly productive team in a challenging technical area. I know roughly what team members are working on in a given week, and that's enough to do coordination. Individual engineers write good pull request messages, and supplement it with design or usage documentation when necessary, and that's more than enough to understand what's going on.
> Curious to see what, if anything, is running under translation

There's a useful app called Silicon Info on Github (https://github.com/billycastelli/Silicon-Info) and also on the Mac App Store.

It adds a menu bar icon that switches according to the currently-focused app's architecture.
This seems similar to nfsd, which is only present in many UNIX implementations to prompt the kernel to service NFS requests.

A lot of (local) filesystems seem to do this as well (XFS in particular).
My guess would be: not that much.
But I work in the field of numerical mathematics and computational physics, so I could have some bias. :-D

The more nuanced answer would be that taking the raw radar data as input to e.g. a neural network and train that to output the predicted timeseries of future ship motion is not feasible. It would take a giant network and too much compute to train for very unreliable results.

This problem consists of a lot of subproblems, most of which are pretty well understood. For example how to translate the 6-dof motion of a ship to the vertical displacement of a heli platform on that ship is just some simple coordinate transforms. You don't gain anything by including that in the neural net. Potentially some data science techniques could be useful to handle some of the less understood submodels. Sort of like it is done in CFD with NN as a turbulence model within an existing PDE solver.
Is being an Amazon employee as bad as some people say it is?
> He describes things like compile time and runtime hygienic macros like they're a new invention that hasn't existed in Lisp since before he was born.

I suspect that this is where some of the inspiration comes from, because he mentioned being a fan of Scheme at a young age. At the same time he wants strong static typing, fine grained control and power (non restrictive).
If you could replicate tablet computers essentially for free, I wonder if in fact the concept of multitasking would fall by the wayside. Why bother switching between apps if you can just make another tablet.
Taiwan is a core interest of US for it's a choke point to deep sea access path to Pacific. Ukraine was never a core strategic interest for US.
how else would init get started?
This is basically why I opted out of any leadership role at my company. I'm not interested in being more involved in scrum/jira/whatever. Absolute hell and bringing in a dedicated scrum master makes it 1000x worse.

I hate that I have to hear about deadlines as they relate to scrum and not business objectives. Or rather, the only business objective is to get something done in a quarter so we can show it off.

We also can't start work on something mid-quarter if it won't finish in a quarter. Outcome is the same EOY but getting there sucks.
Responses like this from C-levels in crypto make me glad I moved from the space after 4 years. Everyone is so egotistical. Blaming it on mental patterns of the employees without accepting it could be some really shitty management from your colleagues instead is toxic. Have a good hard look at the people named in this petition.

Here’s a link on your CPO:

https://www.teamblind.com/post/Coinbase-product-team-culture...
> This response was very reasonable, and I liked the "apolitical" stance the company took to focus on its mission, not political activism.

That's a pretty funny statement given that the "mission" of the crypto world is an explicitly political one, overlapping significantly with extreme libertarian and anarchocapitalist movements.
Slave is a bit extreme, but servant leadership is what I think they were trying to get at.
Much less likely. It's possible, but a very unlikely explanation.
I and many others strongly disagree with the statement’s assumption that infants are not conscious, so it’s not a completely uncontroversial statement. Sure, they have very limited I/O, but I understand that as orthagonal to consciousness.
We have Software Asset management tools that manage those assests, This also tracks renewal dates, and various other aspects of Software management that makes password managers not a good fit.

Our password manager is just a password manager, I suspect many other organizations are the same.
Their brand name is probably worth less than 0 at this point. Outside of crypto circles, they're unknown. Inside crypto circles, they're known for freezing people's accounts at random and not having any customer service when it happens. Their market share is going down too. https://cryptoslate.com/ftx-trading-volume-surpasses-coinbas...

They had a nice IPO, but I hope you sold at the top.
I totally understand regarding the security clearance.

I updated my comment in terms of framing it as an ultimatum - that's not what I would say in the interview process.

Showing examples of fake code seems like a possibly great middle-ground here. As long as that code is an accurate reflection.
Then why are burn-out so common in the SW industry?
They are exceptional the harder it is to make them, and the result is documentation full of minor grammar mistakes or unclear things.

As an example for where it works great, I have made a small documentation fix PR to the Rust standard library 2 days ago and I didn't have to create a github issue for it or anything (but I had to notify a maintainer to review it because the PR fell through the cracks it seems). That maintainer told me they have reviewed 5 other similar pull requests that day. Over time, you get a really nice code base that way.
There's a lot of good cinversation about this.

At the same time, Keeling Curve is 430. In 2040 it will all too lilely be 500. We definitely should attend to particulates, volatiles, oxides... is there anything we can do to locally reduce co2?

Maybe that trend could help. If we can personal size co2 scrubbing, let people knoe they can clean their home, maybe that can make a dent in the need to carbon capture? A downside is that scrubbing is probably less effective at lower co2 density. And it's scrubbing a more oses system. Someome trying to keep their home under 350ppm in a city where it's 440ppm is going to suck less carbon out than an open air plant where it's 500ppm.
An intro to tagged PDF files: internals and the challenges of accessibility
It’s always the case in the US, but certainly not the case in many other places.
>clickbait title of a clickbait article

The third tweet in the thread literally says: "Quit and find a company to work at that you believe in!"

Do you know what "click bait" means?
Our pointing sessions sometimes last 1.5 hours and involve the whole team regardless of expertise. Just imagine how much money we are wasting to determine: is this story a 1 point or 2 point story.
Short answer: No.

The desire to be "identified" incorporates the desire to be identified as "Self sovereign," which is an appeal that only other people can fulfill. Your identity is sovereign thus depends on their collaboration in constructing and maintaining a space where such an identity is even possible. You cannot be self sovereign because the mandate to make that identification is not entirely reserved to yourself. Unless of course you impose it on others by force, in which case you're no longer self sovereign but sovereign, period.
> Schultz has said in the past Starbucks didn’t need unions...

Of course not. Unions aren't for the corporation, they're for the masses being screwed by the corporations.
So tired of people proclaiming RSS "dead". Some of us have been using RSS all along and never stopped using it. There are still plenty of native RSS clients. Google Reader is not RSS. In fact it's better that Google doesn't control RSS; no company should control it.

You can talk about how Google killed their RSS support. How Twitter killed their RSS support. How Apple added and then removed RSS from Safari. But RSS lives on, it can't be killed.

Many news sites continue to publish RSS feeds, you just need to know how to find them.

How many death proclamations does RSS need? At this point it's become a joke, like the old Saturday Night Live Weekend Update, "Generalissimo Francisco Franco is still dead."
Or blocking a curb cut. This is endemic in my city, and can at times make intersections basically impassable in a wheelchair.
Tell HN: Microsoft forgives malware? Node-ipc virus writer not banned GitHub
A few months ago there was a supply-chain attack involving the npm package node-ipc, in which one of the maintainers sabotaged the codebase to delete files on thousands of people's computers.

https://arstechnica.com/information-technology/2022/03/sabotage-code-added-to-popular-npm-package-wiped-files-in-russia-and-belarus/

I just wanted to bring up the fact that the perpetrator behind this cyberattack, "RIAEvangelist", is currently not banned on Github. Hours after publishing the malware code on Github's node-ipc repository they appeared to have temporarily locked his account. But given the fact that his activity remained shortly after, it means Microsoft didnt opt to punish him very long (or at all?).

Malware author's profile: https://github.com/RIAEvangelist

What are the broader implications of Microsoft's inaction against a clear case of computer sabotage? Could their inaction against this user be interpreted as negligence? Could it be interpreted as a relaxation of company policy restrictions against malware being hosted on Github? Discuss.
holy popups+ads, wow
I am a paying customer, but a refund in this specific case is like spitting on a dead body.
The fact that they designed it like that and never warned the users is treacherous.
To all BW employees that keep rationalizing this and downvoting my comment: it’s all funny and stuff until there is a great damage. And then the shit hits the fan..
My comment above is describing a place that is all autonomy and no micromanagement to the extreme. Its a place I worked before I understood the value of upfront documentation.

The situation Ill describe as a good place to work is, you have tickets that are created (by engineers / product / business whoever) that are evaluated ahead of time, and the team determines if it will add value to the business /end user, scoped appropriately, and set up for success with timeline and work.

As many decisions as possible should be made by the team doing the work, and they should be empowered to change their process as necessary.
Out of curiosity, have you watched/read Alan Kay's team work at VPRI ? They managed to make a kind of desktop OS in less than 1MLoC, tangling DSLs to generate the boilerplate from very succint rules (or parsing RFC specs for the network stack). They wanted a 100kLoC but couldn't do it, but I believe it's still doable.
Other than the computational cost, why would you want to use stats when you have an analytic model right there?
> Most engineers when "empowered" and left to their own devices without much accountability go off on their own side quests that often add no value to the business, but scratch that engineer's curiosity. These side quests also tend to not contribute to business aligned goals.

At my last job, there was a strong bottom-up engineering culture where ICs were empowered to work on what they thought would deliver the most business impact. This was actually quite effective because there were performance incentives to ensure individuals and the organization had aligned goals.