skysight-inc/HackerNews huggingface dataset:
I worked a contract there and the team barely understood how some of those configuration panes functioned. It was always a case of staring at someone else's config and then at yours until you found enlightenment. And the target kept changing, so there was a very bad week where my computer worked for 80 minutes total. I coded like hell during that time, pair programmed with the other contractors or did math on a whiteboard for the rest.

Another guy on the team intimated once in a while that he didn't like the team dynamics, but he played his cards pretty close to the chest. After he gave notice, on what we all thought was supposed to be his last day, we showed up in the morning just to find his computer and all of his equipment in a pile on a desk. We never did figure out if we or he were off by one or it was his middle finger to the team.

All the more mysterious because later that day we did discover his middle finger: The lead dev, who seemed to be one of the more reasonable people on the team, and the resident know-it-all both discovered that someone had fiddled with their configurations in ways that broke the system but produced obscure errors and hard to notice differences (like punctuation).

I took a couple lessons away from that project, and reinforced some that I'd already had. Perhaps the most important of which is: Bragging rights for being first mover are very, very short-lived. Once everyone else has copied it, the most accurate adjective for your version is 'old', or 'primitive', not 'first', and absolutely under no circumstances 'best'. Developers don't like bullshit. Don't pretend like your liabilities are assets.
> Johns_Hopkins_Hospital/Input/Excel/Covid_patientdetails/covid_patient_details.xlsx

Should I file the HIPAA complaint, or has someone else already done that?

(the stupid government website for filing complaints is, of course, not loading for me now)
Lucky! I felt it very early on in iOS and that does not seem to have abated.
Me too! It's an interesting idea.
The Irish tax authority's login portal is completely broken in Firefox. It's the only website I need to have a separate Chromium install for.
You don't want this to be a lawsuit; you want it to be a friendly, bidirectional negotiation.

That's backed by a severe economic impact for Google if they don't play nice.
Why $500 and not just enough to pay for the salary of that person, or just enough to even be profitable for Google?
No argument here!
>Take them seriously, stroke their egos, and take fully responsibility

With academic reviews, I'm a bit split on this approach. It's context dependent, but sometimes being on the offence is a better strategy. You shouldn't be rude, but if you clearly demonstrate that the reviewer is wrong and their understanding is wrong, it can have the effect of disarming them and swaying the other reviewers in your favour. It's extremely likely that 1 out of 4-5 reviewers that you typically get will be someone who puts minimal effort and doesn't get the paper. So this is something that you need to do often.
What I've learned from Google is that you are always talking to a bot, it just happens to be that some of those bots are human. Even though they are walking and talking simians they are executing a conversation script and have no agency and ability to control an outcome spare the most banal common issues.
True. That's fair
Goodness, no! There is no such thing as 'inherence' when discussing safety, that's a category mistake https://en.wikipedia.org/wiki/Category_mistake

I will say, anecdotally, that 25mph can sometimes, or even often, be unsafe on several popular brands of e-bike.

There are lots of reasons for this, but anecdotally, tire thickness, wheel diameter, rider height/stance, and braking system quality all seem to contribute, along with a lot of other factors that are hard to reason about beforehand, but easy to read off crash statistics, if you have data of sufficient quality.

The one factor that is really counterintuitive for me is weight. We learned in the motorcycle course that a heavier motorbike will actually be safer in, for example, rainy conditions, as the weight of the internal-combustion engine pushes the motorbike against the earth, expelling water from between the tread and the asphalt.

E-bikes, however, are often bicycle-ish in weight -- only twice as heavy as a standard bicycle, say, instead of ten times as heavy, which is what a motorcycle is. Nevertheless, they still vroom at motorbike-ish speeds.

This makes e-bikes "inherently" more dangerous in icing conditions, in comparison to an ICE motorbike, as there is less weight holding the business end of your e-bike-tire flush with the asphalt.

But 'inherently' is in scare-quotes above because it's still not quite right to say that every e-bike will be more dangerous because of this -- and I'm sure the market is already working on mitigations.

Tradeoffs, all the way down
What's a microfiche camera compared to a camera in every phone which is a commonly found every day item.
That sounds like you'd just create an incentive for reviewers to block more apps, and refuse to admit they were wrong.
There needs to be a way to have 3rd party app stores on these platforms. Tired of the private platform argument. Google/Apple works hard to crush viable competition. It's time for laws to be written to step in and fix this.
Heavy industry is extremely seasonal already, though. And in fact highly variable in a bunch of other ways. Existing facilities are already only sporadically used, no one runs metal casting 24:7.
>AWS promotion-per-launch

Can you elaborate? You mean a new service gets someone promoted?
Practice. In mountain bike terms, that means lots of slower/easier terrain, with occasional “soft” falls. If there are skills areas in any of your trail networks, those are great. Trail running can help - you’ll eventually trip and you’re closer to the ground and going a bit slower, so you have a bit more time to react (tuck and roll, hopefully).

That said, broken collar-bones (along with separated shoulders) are one of the most common serious cycling injury. I’m one of the very few of my friends who hasn’t broken one. And several friends have broken or separated each shoulder multiple times.
Ironically this is actually one of the bigger problems to solve for in the generation and is one that has not been solved for.
What would you recommend as an alternative?
What a load of nonsense.

If one reads the article, one would find the absolute majority of the arguments are plain empty claims with little supporting evidence. Citing a single paper, usually over a decade old, is simply proving the opposite; as what they're saying is "out of the thousands of researches done on X (especially medicine), we only found one paper supporting our modern and liberal claim".

And your example of manhours is utterly detached from reality. Only daft personnel think your points are axioms. Of course manhours are a rough estimate! Of course 9 women don't make a baby in a month. Unless you became an engineer last night, I can only assume you are a liberal warrior regurgitating favorable pieces.

What's next, laws on how to think?
I guess it's true that the originally propose 1000 is an arbitrary number, and it would take some experimentation and work to figure out the ideal number of robots per acre to optimize whatever you care about most (yield, power consumption, maintenance costs being obvious contenders). But I think it's easy to say that literally one giant robot covering an entire edible forest is obviously going to be more inefficient and troublesome than a swarm of some size.
Python 3.10 introduced asyncio changes that broke compatibility with earlier 3.x releases. I don't have the details at hand, but as I recall, some code that supported caller-supplied event loops not only broke, but could no longer be made compatible with both old 3.x and new 3.x python versions (unless separate code paths were maintained).

This was frustrating, because I don't expect point-releases to break the standard library, let alone require a code fork to maintain cross-distro compatibility. It was disappointing, because I had never encountered such breakage from python while Guido was still in charge.
> Just because the Great Pyramids were built with slavery

They weren't build by aliens with alien technology? ;-)

SCNR because we are talking about Elon Musk with his space obsession.
This is relatable. I have spent many hours attempting to get someone at the IRS to answer my questions, and the best part is that they have always ended up hanging up on me after putting me on hold, and there is no way to pick back up where you left off with them since it's all done verbally.

I shall now go read The Metamorphosis.
Riding an electric skateboard up and down the hills of San Francisco was one of the most dangerous and exhilarating things I've done, and was only made possible by the years of skateboarding and snowboarding experience I was lucky to have. I completely agree with your take, it was akin to a full day of snowboarding in terms of the athletic load it put on my body, and constant danger I seemed to be in. There are so many opportunities to hurt yourself and only a few ways to safely navigate the random situations you encounter. I'm glad I got out without serious injury.
Your use case might be fine for their app store only, but it doesn't mean thats true for others.
Hiring managers have a lot of latitude at Amazon, so there isn't a consistent standard. I don't want to share too much PII but I was in a similar situation. I was able to transfer teams after an informal chat with a few engineers on the team (discussing past projects, the new team's product vision, etc.). There was no whiteboarding involved.
Why do you think it's hyperbolic?

If I had to go through this, I think it would become the most angering experience I've had. I've have bureaucratic problems but nothing approaching this, and no personal conflict has ever gotten that bad.
Even worse: PHI.
>Have you ever stopped to think what "acceptable" means in that sentence?

No, but I don't know how that would affect outcomes given a mass of voters. My sense is that it would all "even out" because no one would be forced to choose a single candidate, or to rank their favorites.
I'm pretty happy with what it says about my critique, too. For instance, my side of this "debate", such as it is, will never spend $100,000 funding a tabletop role playing game aiming to educate people on the dangers of asteroids.
Genuine question, which one is easier:
- convince editor
- write something that reviewer will understand
Nice! I can't find where I ordered mine from but I remember trying to go through the anberic website and it wouldn't successfully add things to my cart.

I found the Retro Game Corps YouTube channel to be a big help when getting everything setup.

I ended up modifying the behavior to hide everything on the launch screen except for 1-2 games I'm playing and made them always launch from save states on boot.
Why so much indirection and abstraction when it can be done more simply and directly?

const newData = notificationData.map(ev => {
return {
username : ev.username,
message : ev.message.replace(/</g, '&lt;'),
date : new Date(ev.date * 1000).toGMTString(),
displayName: ev.displayName,
sender : `https://example.com/users/${ev.username}`,
source : `https://example.com/${ev.sourceType}/${ev.sourceId}`,
icon : `${iconPrefix}${ev.sourceType}${iconSuffix}`
}
});
If you didn’t know “Bending Spoons” was an organization, the title would come across a bit differently.
You have to admit it’s not a great example, though, and it comes off as verbose for no reason.
Static analysis tools and runtime checkers would also be considered a form of AI, no? Those find bugs.
I did not assume the smaller drones would be simpler than the tractor. In fact I'd expect them to be similarly if not more complex.
There's a The Smile song called "You'll Never Work in Television Again." Last week I said "play <name of song>" and Alexa responded that it could not find a playback method called "television." I tried to annunciate more clearly and it replied "OK, playing <song name> on repeat," because the song title ended with the word "again."

Nothing reminds you about the difficulty in cleanly parsing human language more than trying to work through a voice interface. I'm not sure what is missing precisely, but I'd say "an ability to use semantic understanding" might be helpful. All of our AI works explicitly with no understanding of semantics, but it's becoming clear to me that the ceiling that places on their "intelligence" puts them still leagues away from the world of true AGI.
I think this is a neat solution for an engineer working on their own and wants to go back and look at the data from various experiments.

I don't see this scaling to many engineers working in a team, who would want to see each others experiment data, or even store artifacts like checkpoints and such. And lastly, in many cases ACLs are required as well when certain models trained with sensitive data shouldn't be shared with engineers outside of a team/group.
There needs to be some sort of termination disclosure law, where they have to demonstrate why they locked you out of your account.
I think this is a very interesting and clear manifesto, and almost certainly the right thing for Amazon at the right time (and presumably was part of what led to AWS). However, at one of the previous companies I worked at we got an ex-Amazon person as CTO and he grew the company from 50 engineers to 500 in 2 years, and pushed microservices everywhere. Very impressive, and I think all-microservices made sense at one level to handle that sort of growth, but it doesn't make sense technically in a lot of cases.

Essentially I think we've gone too far: service-oriented architectures turned into "micro" services, which come with a lot of complexity and distributed systems issues. I think for most small companies monoliths are right, for medium-sized companies (say 50+) it makes sense to carefully introduce a few separate services, and only for large companies (say 300+) does many services (which may or may not be "micro") start to pay off. I've heard it said that "microservices solve a people problem, not a technical one", and I think that's true.
I'm amazed that you've never seen an overhead electric caternary, be it for a train, tram or light rail system.

https://www.openrailwaymap.org//mobile.php?style=electrified...

Everything except the black and pink is overhead electric, and I guess I hadn't realised how little of America is electrified.
Ah! OK, now "dark magic" I can totally understand. Pipelines _is_ a little opaque, which is a totally fair criticism. In my experience it does _most_ of the things that you would want if you know a few fairly common (and easily searchable) incantations ("How do I add a new stage to this pipeline?", "How do I put tests after this stage?", etc.) - but I can definitely sympathise with the feeling of "this tool is doing a bunch of stuff for me and I don't understand how it's doing it". Thanks!

One point that I've found _really_ strange after transitioning from Pipelines to other CI/CD (I'm using Drone and Argo, but I think this applies for Flux as well) is that infrastructure-definition repos define the _image-version_ that they deploy to a particular stage, rather than just defining the source repo (and automatically deploying the latest image-version which has passed all preceding tests). That seems...odd. Unless you hack together your own automation[0], that means you need two actions to get new App Code out to an environment:

* Push the App Code commit (and have a new image-version built)

* Make a change to your Infra Code, updating the desired image version

Am I missing something?

---

I'm surprised to hear that you consider AWS to be Java-oriented. When I think AWS, I think TypeScript - to the extent that the primary reason I started learning TypeScript was to be able to write CDK more fluently (and, then, to write Lambdas without a whole bunch of Java type boilerplate - though Python also works there).

[0] Which I've done, but the fact that I had to hand-build it suggests I'm doing something that the tool author's discourage
If the ferry uses 150-200 kWh/day, that's two Tesla batteries assuming no recharging during the day (so realistically, you could run it on one, since the ferry presumably isn't constantly moving).

Of course, the fixed cable avoids having to replace the battery every couple years, might be lighter/cheaper etc. - but it could absolutely be implemented using batteries.

(This assumes the numbers are accurate, the 100 liters of fuel vs. only needing 200 kWh seems odd.)
Yes.

Judo and parkour both actively teach falling and body-awareness. Gymnastics does, though it’s not generally as formal/explicit - you just get the body awareness from beginner-level tumbling.
You've chosen to redefine a common word (scarcity) rather than engage with my point.

I have nothing more to say.
If you could supply the mules like electric trains are supplied, you might just as well replace the powerful mules with lightweight power pickup runners that the boats connect to with a cord. Boats would only need a few minutes of battery power for situations that aren't as easy as running straight along the canal.
If you're gonna grift rich fólk, may as well do it to billionaires.
Heck, i went over the handlebars of a razor scooter in Palm Springs (bad place to ride anything with small wheels) in my early 40’s. Thankfully, i just came out bloodied (i still have the scars). I would hate to try to do that with something at a higher speed.
I'd really like to see a bugs.txt as well. The amount of large sites I have repeatable bugs on with no way to report the is frustrating.
It seems like an algorithm evaluates your app and the support guy simply sends you the result. He has no saying in the process. It's dumb I know, but it's what looks like.
The editor reads the reviewer comments and replies also. In most cases replying to the reviewer like I suggest will allow the editor to realize it was the reviewers mistake, and they won't even bother sending it back to the reviewer... but if they do you've targeted both strategies with one response.
That's the sad thing about this story, it really just sounds like Goodhart's law in action, a certain % of apps need to get rejected/reviewed/appealed each month.
You are much too late. The woods are already full of people who escaped.
There is a lot of "over-demand" for RPis because many companies and universities mistakenly think it's the only way to do embedded Linux. The truth is that there are many cheaper alternatives out there that are more appropriate for embedded projects (ADC, PWM etc.)

Edit:

Forgot to add a link to this article that goes through some of the alternatives:

https://jaycarlson.net/embedded-linux/
This seems to lie within the Rio Grande Rift, a plate tectonic feature dividing the mountainous West from the more stable parts of eastern America. Clusters of earthquakes can precede a larger earthquake or indicate the motion of lava at depth perhaps leading to an eruption. In geological time the Rio Grande Rift has experienced both.
Some of these results seem to be picking up on general abstract concepts moreso actual visual cues. for example, one sample has bright colored wooden park benches as input, and some generic brown wood furniture as an output. Perhaps a strange artifact of training biases, but a little disturbing at a glance. Extracting current visual data out of one's brain is one thing, but being able to potentially identify abstract thoughts is a whole different level of invasiveness.
This is a large amount considering it is corporate.Do they do the fly in, fly out hub deliveries?
Can you share more about your experience with android?
Most of didn't have to run into someone to learn this thing, but I'm glad you know now.
> but you don't store your savings on a crypto exchange... No one reasonable has their savings in crypto exchanges.

Many, many, many people have absolutely bought into the crypto dream, put their savings on an exchange and absolutely ended up entirely destitute. There are swathes of evidence of exactly this.
Mkultra was not just drugs. Look into it more. You know another term for brainwashing? Hypnosis! Which is something psychiatrists also do.

Not only did mkultra brainwash people but some survivors forgot everything about their life before the experiment.
So a 30% rise in home value is not much, in real terms.
Your ideal market, of course, proving why we cannot have nice things. As the moment somebody puts in the work to engineer a package so hella cheap that anyone can afford it, and start to actually do so, ideal market theorists pour in undoing the entire thing, lest money be left on the table.

Demand that outstrips supply does not necessitate a price increase must happen. Sometimes, the entire point of such an arrangement, is to render something accessible to individuals otherwise priced out.

Let us not trouble ourselves trying to justify economic's desperate attempt to legitimize greed as a virtue.
https://www.youtube.com/watch?v=iEInNZ0oB-E
The first a unit of energy. As in total output from an input (building the panel).

The second is a unit of power because the silver isn't used up (it's made very very hard to recycle in the NPP, but it's still technically possible after a few decades), the issue is how much is occupied by the equipment.

If you can't understand the distinction between power and energy maybe we shouldn't consider your position on power and energy credible.
I left about a year ago, but the universality of tools and stack was not a thing in the ~3 years I was there. Retail and AWS are split and use different stacks. Additionally, the company was in a drawn out multi-year process of deprecating old tooling (including Odin), so you had teams or orgs that were in-between these old internal services and new internal services (or off internal services altogether and on "native AWS"). If cross-team interoperability demanded that certain tooling was to be used, many times you could inadvertently hold back or screw over another team by deciding to stay or move to the new tooling.

Not to say it was all bad - some of it was certainly necessary. Especially for security - IMO the systems of Amazon are great with security, but not necessarily the spirit of the company. Without all that bureaucratic annoyance, there 100% would be existential leaks or breaches coming out of Amazon with how fast and loose everybody treated security in the name of "Deliver Results" .
I just laid myself off from Amazon too after 2+ years. I just couldn't take the janky-as-shit internal tooling, the myriad pointless/redundant meetings, and pointlessly stressful and toxic work environment anymore.

Also, I enjoyed my first two managers at Amazon, but my third manager was a tool, which is a systemic problem at Amazon.

I'm glad to have Amazon in the rearview mirror of my career.
> So you think there’s nothing wrong with blowing through a school zone at 150mph?

I have said no such thing. Do you really believe that the law is the only thing that defines what's "wrong"?

> Speed limit laws are clearly flawed in many ways but there is a clear reason why they should exist.

No, what is clear is that the law should be written to penalize actual harm. Speed limit laws don't do that. They penalize people who have caused no harm, and because they can only be enforced arbitrarily--who gets stopped for speeding has nothing to do with actual risk reduction--they reduce people's respect for the law in general.

A properly written law for "rules of the road" for speed would be something like this: The posted "speed limit" on any public road is advisory; you cannot be stopped or ticketed simply for driving faster than the posted limit. However, if you are in an accident and it is found that you were exceeding the posted limit, you are presumed to be at fault. (You can still rebut the presumption, but that requires going to court and presenting evidence and having the judge rule in your favor based on that evidence.)