skysight-inc/HackerNews huggingface dataset:
Well kind of...if you're in the Bay Area, you need to be able to compete for engineers with the likes of Apple, Google, Facebook etc. No perks == no employees. Why should I go work at your crappy startup when I could live the life of luxury at one of the FANGS.
There used to be one more meta key on a Mac keyboard (back when the windows key only opened the start menu; maybe that's changed), and the location of the control key is different in relation to the alt/option key and other meta keys. Also, the windows keyboards I used used to have the windows key only on one side, whereas the cmd key is something you always want on both sides.

There are other minor differences like the naming of alt vs option or return vs enter, but those don't usually matter to a reasonably savvy user.

Windows keyboards used to also come with near-mandatory print screen and scroll lock and page up/down and a couple other keys; dunno if those are still used. (Can you take a Windows screenshot these days without print screen or a custom app?)
Depends a lot on the knock off. Some are terrible. I have a colleague that wears an "Omega" that is laughably bad. Some of the better ones though are much harder to spot.
Ask HN: Open source developers, would you do paid support for your projects?
If there was demand, would you do paid support for your projects?
The funny thing is that appears to makes it even worse - even with the attendent "fired for sparking controversy and making the company look bad" risk.
The idea goes back a long time. There used to be a product called Legato Prestoserve that used battery-backed SRAM. It was available in the early 1990s, maybe late 1980s.

Here's some documentation about the version of it that Sun Microsystems licensed and sold:

https://docs.oracle.com/cd/E19957-01/801-4896-11/Presto.chp1...

It says:

"Each NVSIMM contains memory, a battery, and power controller circuitry, which ensure that the memory is not lost when the system is shut-down or halts because of an abnormal condition."

"Synchronous write requests to disk are intercepted, and the data is stored in non-volatile memory"
Our moon is slowing down Earth's rotation by tidal friction (angular momentum is transferred from the Earth to the Moon).
The effect is rather small with the period only slowing down by around 2ms per 100 years currently (depends on the configuration of the oceans and the orbit of the moon).

But internal changes in the Earth can also cause changes in the rotation period.
For instance the 2011 Tohoku earthquake shortened the day by 1.8 us [1].

[1] https://www.earthobservatory.sg/blog/how-did-2011-tohoku-ear...
> The FDA is not the primary source of regulation in medical software, it's CMS

It's totally dependent on what you are doing. Sure, HIPAA / PHI concerns are the primary issues for people who generally make software for the medical space, but by "medical software" I mean software that FDA might classify as "software as a medical device" AKA FDA regulated software. If your software falls under this designation, as most diagnostic medical AI systems like Watson would, then your primary regulatory concern is the FDA and you are held to much more stringent software development requirements than someone that has to deal with some PHI concerns.

In this context, my bulk de-regulation comment is 100% correct, as the FDA has basically dictated almost everything in the space to be unregulated (all back office products, general wellness products, enforcement discretion products, MDDS, even CDS which almost certainly should be regulated). They have literally gutted Class 1. You basically have to be writing something that is going to provide a diagnosis or treatment plan, control an existing medical device remotely, or mimic an existing regulated medical device in functionality in order to be regulated now. Reasonable people weren't scared to enter the space because they might have to deal with PHI for HIPAA concerns, as it is well known how to do that at this stage; they were scared to enter because there was (and continues to be) some uncertainty as to how novel product classes will be regulated by FDA.

> Your concerns on the sales side also do not mention "RISK" even once. You don't speak even a little bit of our healthcare space. Those doctors want risk management. What happens if/when the software screws up? Whose fault is it that the software is literally response for killing patients?

All FDA regulated software is mandated to have robust risk management planning prior to approval (ie ISO 14971 compliance). Other than that, the vast majority of products that a patient will be interfacing with can't do them real harm if they are buggy. That is precisely why the FDA has chosen not to regulate them.

> You also don't mention what doctors care about: does it meet CMS regs? Does it meet state regs? Will I be able to submit my obscure XYZ state form? Will I be able to submit to BCBS, Aetna, Medicare? Will they accept? Etc etc. You will be writing custom software for customers all over, because the regulations that states and even cities like NYC might impose could be imposed on a single customer of yours only.

I don't mention doctor wants because doctors aren't the buyers most of the time. Payers are the buyers, hospitals are the buyers, or patients are the buyers. How many pieces of software that you know of are sold directly to the doctor?
Reddit is super valuable from the perspective of being able to poll a "hive mind" specialized in a certain thing about best practices and ideas. e.g. I want to learn more about making EDM, more about photography, more about shibari etc. Usually the advice is pretty decent between beginner and intermediate level, for the high end super-custom guidance usually it falls flat.
Newtonian and quantum mechanics deliver different answers, which means that without approximation they are different theories - not different schools of thought. With approximation (in a certain limit), quantum and Newtonian mechanics are the same, and take the same amount of work to find answers - quantum mechanics yields Newtonian mechanics in that limit, doing "room temperature large scale" quantum mechanics means writing down Newton's laws. In this sense it's most accurate to say that Newtonian mechanics is a particular approximation to quantum mechanics that holds under certain circumstances.

This other school-of-thought business (Bayesians vs. frequentists, pilot waves vs many worlds vs Copenhagen, everything like them) means choosing between different sets of words to describe the same thing. You are left with one of two cases: either they can be shown equivalent (in which case people are prone to keep on arguing over which one is better), or they are different (in which case one is wrong.)
Yes, I'm not constrained in any way to not be able to run a 5 MB binary. I was curious if that was an indication of what is to come for large projects...

I guess I was tangentially pointing to complexity and abstraction there.
Cryptocrash is inevitable
The Lost Ancestors of ASCII Art
Fair enough, I agree that avoiding the baggage of Dilbertesque (great word!) corporations was key.

My point was just that all the methods except agile had explicit technical requirements. XP required TDD and pair programming which was incredibly extreme at the time (and still is fairly out there).

These were people meeting up at OOPSLA. They were programmers' programmers. I absolutely think craft and technical quality was important to them. I think it was so intrinsically important that they didn't express it clearly in the manifesto.

But I could be wrong; I wasn't there!
do you happen to know how those nifty ASCII diagrams were created?
> the fact that it comes in the form of a slidedeck makes it hard to do itemized critiques

The slides usually cite sources, so it's pretty easy to tell if the underlying methodology is weak. (And often it is.)

I usually enjoy reading the annual reports, my biggest criticism is just that it focuses on completely different trends each year. It will go from social to AI to messaging to privacy, etc. If something is only relevant and worth talking about for one year, then pretty much by definition it isn't a trend.
The great thing about using a transparently compiled isa is that there is no way you can get arbitary code execution. The only things exposed to the outside will be SIPs and if you exploit one of those, the most you can do with it is make it crash.
The concept is literally as old as apple pie baked by grandma rather than in a factory.
> At least the companies would be risking the investment in college tuition rather than the taxpayers.

I think that contributes to the dystopia. Then companies get more power, controlling who gets educated, the content of their education, the method, etc. If it became widespread, how much influence would companies have over universities? Would research detrimental to corporations be possible?

Democracy is a great thing; it gives power to the citizens. If we cut back government, we redistribute that power to the already powerful people and institutions. (To be clear, there is a balance to be had; government is good for somethings (e.g, defense, justice, education and health care), private business is good for others (e.g., making cars and software).
So, assumptions that are no longer true, and haven't been for a while?
7 year marriage and $30k is still $12 a day.

(My own marriage probably cost $30k - was a decade ago and I forget. But then we had 60 guess, at least half of whom if I employed would cost at least $600 for the day, so the bigger cost may well be lost earnings)
Endurance should be fine, orders of magnitude better than flash. Just some temperature wear.

But the speed and density seems to be a problem. E.g. it's still 2x slower than DRAM, but theoretically should be faster. It could also have 3 bits, not just 2.
OMSCS: a working professional's guide
Except that MacOS does not use ELF, it uses Mach-O.
No need to baselessly suggest autism. There are people who don’t care about these things. Find one of them. It’s not hard. I’ve known several.
Oh, yeah duh. I'm stupid.
My argument is twofold:

Firstly, that merely visually observing the surface of a mountain ("look around when you drove through it") is insufficient to draw meaningful conclusions about the overall geology from an engineering perspective, especially by a non-expert.

Secondly, that even experts have been confounded by the geological features of that particular mountain range.

If you're implying that my referring to an engineering project from approximately a century ago somehow makes it irrelevant, then you'd need to point out some fundamental engineering changes in tunneling and/or demolition (or the study of geology) as they relate to viability thereof, to be an actual argument/refutation.
I'm pretty sure that when he says "the rest of the employees" he means what Scrum calls stakeholders, not members of the development team.
Having a proper test suite and updating when the changes are minimal usually leads to better overall product maintenance.

I dont get these claims to not upgrade unless you're also just as worried about changing a line of code and having it all break too? Make the changes, test the changes, and deploy carefully, just as you would for anything else.
Code reviews are very important, so I don't complain about time spent doing them.
Yeah, I (somehow...) missed the part where the GP explained that the kernel dev's fix was to just rely on the now updated unspecified behavior. I assumed the changed the compiler, but he also memset the structure before sending.
My point is mainly that most these assist systems are meant to work in the case the driver is not actively controlling that aspect of the vehicle. At any point the driver is trying to take a specific action, such as steer, accelerate, brake, etc, the car should cede control to the driver. If the driver is actively using the brakes, it makes sense to the auto-braking system to detect this and not engage. The last thing you want to do is wrench control away from someone that is actively operating a vehicle.

There may be cases where that rule could be relaxed, and the system could engage, but it would need to be beyond all doubt.
You'll also write unmaintainable code. To a large degree, optimizations exist to allow programmers to write maintainable code without sacrificing performance.
For 1, take a look at this guy's blog: http://colah.github.io
Once you finally break free of the startup/entrepreneurial mentality, suddenly the world opens up. The possibilities are so vast (but not all possibilities mean freedom).

Breaking free from the gold rush (or in my case, app rush), you start to realize that huge exits and lots of users really doesn't matter as much as comfort and stability. And then you might even consider doing work that doesn't give you equity or has potential for huge payoffs. That's actually freeing, because it means you're allowed to do your job, then go home and relax. You stop thinking about how much work you could get done if you weren’t relaxing (which usually sucks you back to a computer to chip away at a never ending todo list).

I envy the people who are simply happy in serving others. They may or may not become super wealthy or travel as much, but they usually do not start with the idea of “the only work worth doing is for a company I own”. Instead, they seem more likely to take jobs with an expectation of being useful rather than an egotistical view of time/benefit. They will surely have more boring times, but they also have much greater chance of both being happy (living a normal life) as well as actually filling their years with meaningful accomplishments.
Why wouldn't autonomous ferries be liable to be hijacked?
Also, founders and others with spending power, would you hire open source developers for help using their code?
I've never heard of numcommand before, but it looks super awesome and exactly what I need. I use Linux servers, but am forced to use Windows as my local. So first question, do you have experience with awk/gawk on Windows? Second question: What do you prefer about Awk over Python/Perl? I guess if all your analytics are fairly short it is just easier in Awk? Thanks!
> I also dislike reddit because it's hard to remember a name constantly. It's easier when there's a little profile picture next to the name. You go, "oh yeah, that guy. He's helpful." You remember those posters more often.

To me, personally, I like Reddit because this kind of association is more difficult. I like reading a comment and not having any bias towards the user.
In my experience that tends to only be true in the larger subreddits. The (potentially) more niche subreddits I use don't have that same problem outside of maybe a 'read the FAQs before posting'
> The fare is the same as subway $2.75 but the true cost is $5.60+ per trip

What is the true cost of the subway trip?

Also, I'm surprised a boat is more expensive. Generally speaking, shipping things by water costs far less; that's why access to navigable waterways is an essential economic resource. I could imagine boats in NYC would have all sorts of overhead, but does anyone know what it is?
Kind of.

After Longhorn's failure, they started to focus on COM to be the future of Windows APIs, leading to UWP.

And if masochists can implement COM in C, they need to be quite pain resistant for the UWP update.

In the meantime, the new C runtime was rewritten in C++, using extern "C" entry points.

Windows drivers can be written in C++ since Windows 8, and since then they have been migrating the code to be compilable as the C subset from C++ as well.
"Well, Nobel-prize winners and millions of economists around the world disagree with you, but I'm sure that your personal opinion trumps all of that."

Very few economists would classify what they do as a science, like biology or chemistry.

And no, I didn't mix anything up. I disagreed with you on your point. But because you can't back up your point, you have to resort to petty retorts. The fact of the matter is, what most economists have traditionally believed regarding wage growth and tightening labor markets has been turned on its head, due to many companies complaining about labor shortages yet there not being any real gains in wages.
"Low touch / no touch" sales is also known as "marketing." I don't know you or your intentions so this may not be directed at you, but I've found that most people looking to develop a low-touch sales engine are really saying "Ew...sales...I don't want to have to do that. Maybe if I blog enough and my site looks good I won't have to actually, you know, TALK to potential customers."

I also find that anything above about $70/month MRR is going to require talking to the person. $70 is a limit that most companies will allow to be expensed without much question. MAYBE you can get that number to $100 in the right market. Above $100? Good luck. And if you are selling a $100+ product with no-touch then you are really missing out on TONS of business that could come your way if you just put in some actual sales effort.
I don't know where these numbers come from. I made a gross salary of $140k the year I worked at Google as a senior engineer, and I made some extra money via 401k matching too. $190k would definitely have been more than my entire income, that's for sure. It's hard to imagine that salaries have more than doubled in the six years since then. And... spending only $60k a year, living in Seattle? Yeah, maybe if you live like a monk, or you really enjoy commuting in from distant suburbs.
> I suppose you don't even have to copy it before you jump to it. You could map the pages and then lazily copy when you get page faults.

You could also just map it and not even fault on access. For data that's mostly read and seldom written, and not too much of a hot spot, there would be no reason to move it to DRAM. Depending on the read latency of these DIMMs, that might include a lot of executable code.
From gmail they also have keys to yor website SSL, as majority of SSL cert providers will send those to admin email (form of verification that someone access admin/webmaster account) on file as form of validation (altho there are other options like CNAME in some providers)
>If you refactor your HTML then you’ll be required to rewrite many of your CSS selectors.

I haven't found that to be a major issue. And I don't think the term "refactor" is the best choice here.

jQuery is library that provides DOM shorthand - it isn’t a true application framework.

Of course not. I don't want a third-party application framework. I discovered years ago that they're not worth the extra effort or the technical debt one incurs with them. (At least not to me. I'm not telling anyone what they should think or that they should design their applications like I do.)

My approach for me and the developers on my team is to develop a deep level of understanding of HTML, CSS and JS. Once you have that, the prospect of doing things for yourself that frameworks would otherwise provide does not seem all that daunting. To me, frameworks like React, Angular, etc. don't reduce complexity, they increase it.

And I hasten to note that I realize that many bright, capable people hold a different view , and I'm not saying they're wrong.
But the point is that auditors didn't catch massive amounts of fraud either. Where financial statements did not match reality at all.
Maybe similar happened in 1980s. But I was talking about late 1990s.
Yes, I think this is exactly right (not just in what Scrum/XP says, but also in how it has to be). Separating that role is super important and is potentially one of the friction points in transitioning from a more traditional setup (as evidenced by TFA). In my experience, it is also very, very important that the Scrum Master is not the manager of the team. It has to be someone whose accountability is to the technical success of the team as distinct from the delivery of high level objectives for the team. In a more traditional setup that would be someone like a team lead, senior dev or even a system analyst. XP doesn't define this role specifically and it is probably a weakness -- I've done it as a coach, but usually I appoint someone on the team to do it.

Also, interestingly, I've often had project managers who refuse to do the PO role (I usually call it the "Customer Proxy", but it's the same role). In those cases I try to appoint someone who is accountable for writing stories. They consult with the project manager for the higher level "vision" (but in practice the project manager does virtually nothing -- a state of affairs which they are usually quite familiar and comfortable with, unfortunately). Prioritisation of stories is done by the development manager, PO and project manager (if they are different from the PO). In this case, the Scrum Master/Coach is not invited to that meeting.

To answer the original question: How do you represent the acceptance criteria? Personally, I do not like code based representations of acceptance criteria. Having said that, my entire exposure to them is working on legacy projects where they have gone badly wrong.

The main problem is the same problem with trying to maintain prose documentation of the requirements of a large system -- those requirements are at least as long as the implementation of the system. They are also at least as complicated. We've slowly created ways of organising production code to make it easier to manage. The same is not true for BDD style acceptance criteria, or even prose requirements documents.

At the beginning of my career I spent a lot of my time writing requirements documents in prose. Every 6 month release would include something like 1300 pages of requirement documents. Maintaining these requirement documents was impossible. Very quickly they get out of date and so you no longer have any description of the working code other that the implementation itself.

Based on these experiences, my attitude is that requirements (including acceptance criteria) are ephemeral. They exist for the life of the story and then you abandon them (note: I'm still massively in favour of acceptance tests and unit tests, but implemented as code that is written in a similar way to the production code -- because we have techniques for managing that complexity).

Long story short: I write them in prose on the story and appoint someone to making the determination whether or not the acceptance criteria is sufficient to add the story to the sprint commitment (as nradov explained in much fewer words than I did :-) ).
They kind of do though, the complexity of data sync can now be dealt with entirely separately from the complexity of the app logic itself (which is not true of, say REST architecture)
So they don't have much of a reputation to tarnish in the first place then? That makes this story a lot less news-worthy in that case.
A 5% gain including dividends from 2011-2017 is a pretty bad showing. The market literally doubled on average in that timeframe.
BitBay Newest Fish to Migrate to the Warm Maltese Waters