skysight-inc/HackerNews huggingface dataset:
MS always seems to have had a schizophrenic relationship with API-exposing automation.

It's like they have "Make it easy to manage" as a priority, then don't talk to admins with non-MS experience, and then build features in a bizarre way.
There was a lot more to it, of course. I took that from his book "An Astronaut's Guide to Life on Earth".

Maybe this particular bit of philosophy wasn't the reason he became a commander on the ISS, but it seemed to work for him. It isn't to say you let people take advantage of you, or that you don't make hard decisions, or that you never attempt to innovate. It is just to say, don't be a minus one. It is sort of like comedy in that you can't decide to be funny and then everyone will think you are funny.

The context is also important, he mostly used this to illustrate how he approached things as a new member of a team learning the ropes, even as the commander. He is thrust into a new environment, and he is the commander of the operation, but he didn't immediately impose his authority, he stacked and organized and learned how things were going before making executive decisions. So the whole -1, 0, +1 thing is as much a leadership style as it is his idea on how to be successful.

I think also the environment of a fighter pilot then astronaut does not tolerate showmanship or overt "I am smart" cleverness. It likes consistent hard work and problem solving that is well thought out. Showmanship gets people killed in space. Endeavoring to be a +1 for any of the very numerous wrong reasons just ends up taking away from the mission.

Anyhow, perhaps that adds some context to the idea.
Apple Music executive Bozoma Saint John plans to leave the company
I believe Windows 8 hit the same problem as Vista. Too ambitious plans for the available time frame so engineers did not have time to get things right. For example the Modern UI was actually pretty neat idea, but of course the version that shipped with Windows 8 was completely useless. They should have waited until the screen splitting was working and figure out a way to easily split the screen between traditional and modern apps.

What's the main issue with registry or what would be better alternative? I think this kind of database oriented way of storing the settings with transaction support is actually pretty good approach.
It's a fib that rich people like to tell themselves. "They're getting me rich, but I'm paying them what they're worth."

Unfortunately it's also true. Life isn't fair.

The solution is to ruthlessly threaten to leave, without making it a threat. If the scientist did that, he probably would've been able to get equity. You have to be sure you're as irreplaceable as you think you are, though.

It's something that took a long time to grok. Honor in business simply does not exist, and nobody will look out for you except you.

(Also, woo, this downvote hiding mod is so nice. I have no idea whether I'm being upvoted or downvoted and it's wonderfullll. I can say whatever I want. Toasters are ugly. There, I've just offended everyone who likes toasters. HN hasn't been this pleasant in years.)
VCs don't like ICOs because they expose how irrational raising money is. They hamper the whole narrative of VCs being "experts" when the truth is it's all a casino financed by the Fed. VCs are used to controlling the narrative of WHY a company deserves money.
Excellent idea, but one step further would be to find some amenable Uber / taxi drivers to drive them around. They'd be likely to get coverage of a fairly broad area for a more continuous period than a private driver
That's really the easiest part.

We use Stardog, but there are a bunch of other databases you can use including Oracle Spatial and Graph, Fuseki, GraphDB, Virtuoso, AllegroGraph, MarkLogic and Blazegraph.

Many of these database will answer queries in json-ld, but since you are likely to want to have a backend anyway you can use Apache Jena or Eclipse RDF4J (previously Sesame) with Java to connect and extract data. Both Jena and RDF4J will let you output that data as JSON-LD.
These are super interesting and I would love if you submit to HN a cool video, slide deck, blog post or paper about systems that optimize a large task across machine boundaries!

But normal people consider the output of a compiler to be a single binary (or bytecode meant to run in a single possibly-forking process) and the optimizations the compiler is allowed to perform in the "as-if" principle do not change the output of strace of the resulting binary.

I would be very surprised if a compiler ever changed the externally-visible IO operations my program performed, even if for the better. What I call a compiler cannot change the file format or the serialization format or the indexing or the way data is written to a socket or things like that. It can only change computations and memory accesses between syscalls as long as the same syscalls are performed.

For systems where the task is defined at such high level that choosing the file format is up to the "compiler", I would want to use a different name than "compiler".
While working on AWS, we had data corruption caused by a new feature launch. Deployments took ~6 weeks so the solution was to use GDB to flip a feature flag in memory for about 120k servers.
Yeah, another case of "blame the person" instead of "blame the lack of systems". A while back, there was a thread here on how Amazon handled their s3 outage, caused by a devops typo. They didn't blame the DevOp guy, and instead beefed up their tooling.

I wonder whether that single difference - blame the person vs fix the system/tools predicts the failure or success of an enterprise?
Replacing passwords is incredibly difficult. Nobody has done it, many have tried. UAF is already supported in a wide number of hardware and applications.

You can verify PayPal transaction right now with UAF. Not exactly a small fish.

UAF does not jet have much browser support yet, everybody is waiting for Web Authentication API that is in standardization right now.

> Correct, once first layer is fixed and password-related attacks are mitigated, there's no need for u2f as it doesn't stop malware.

That's just stupid. If you use a finger print sensor as a convenient first factor then you might as well still want a second factor.

The idea that there is never a use for a second factor is just total nonsense.

> Even something as basic as hmac(masterpw, domain)-app would do better job than FIDO stuff altogether.

The security of that would be far, far worse. Not to mention tons of other practical problem with that idea.
This sounds like a really interesting project, I reached out at the link below.
Its a pretty gross error to me to have direct db access. Obviously in any stack you could push code that affects the db catastrophically anyway, but in dev mode you should never connect directly to production database, not only for this error but for general data integrity.

CTO needs to put a theatre to not get fired, because he is ultimately responsible.
Front End Performance Check-List for Production
In that case don't you think they should informed him that this is a production environment so don't fuck it up?
Giving your junior dev a front seat on your production without proper communication is a disaster waiting to happen.
Firing the guy seems drastic but understandable. Implying that they are going to take legal action against him is ridiculous!
I agree that it can help with debugging but it puts that other "load" into your brain. Which dispatcher do I want for this event?

If you're using C++ or another strongly typed language then it's probably fine because you'll get a compiler/IDE error about your types. If you're using something more "loose" having a central router helps.
Especially the transients are a problem. IIRC certified-for-automotive parts have to endure >100V input, which e.g. may happen when the battery connection is flaky and the engine is running, due to the sudden load drop.

What's missing on this setup imho is a) a solid power connection (those 12V sockets are known for being loose because of wildly varying manufactoring tolerance) and b) the lack of a supercap+diode setup to prevent brownouts during engine start.
I just don't understand this.

A national currency is an irredeemable medium of exchange, made valuable because it's -- by law -- exempt from capital gains tax (it measures capital gain), and because it's been given legal tender status.

Why would anyone trade an irredeemable currency issued by a private corporation? "Currency" is surely a misnomer, because no one would want to buy or sell goods and services in exchange for it, which makes it more like irredeemable equity, which makes no sense either.
Nothing wrong with pursuing material success, but the glassdoor reviews don't speak that highly of Leprino either.
Or in other words, don't buy a bespoke suit jacket and vest, then pick up pants from Walmart right before your wedding.
Agreed. Several years ago as a junior dev I was tasked with adding a new feature- only allowing a user to have 1 active session.

So, we added a "roadblock" post auth with 2 actions- log out other sessions and log out this session.

Well, the db query for the first action (log out other sessions) was missing a where clause...a user_id!

Tickets started pouring in saying users were logged out and didn't know why. Luckily the on-call dev knew there was a recent release and was able to identify the missing where clause and added it within the hour.

The feature made it through code review, so the team acknowledged that everyone was at fault. Instead of being reprimanded, we decided to revamp our code review process.

I never made that kind of mistake again. To this day, I'm a little paranoid about update/delete queries.
>Developing a moral core should be prioritized.

I just can't see how over the long term an AI will not evolve out of the human moral code we want. Humans evolved into our, very wide ranging sets of, moral code. There is not a consistent one across all cultures. The base set of morals we do follow are generally based on that we humans are made of squishy meat that suffers pain, and minimizing that pain is a priority goal.

We may be able teach AI about our weaknesses, but as machine intelligence meets and then exceeds human intelligence and capability, said AI will see both our strengths and weaknesses and that puts us in a precarious place. If an AI without human morality outperforms AI with human morality it stands to become the dominant form of AI.
Donate to Environmental Defence Fund get matched by tech investors 1 for 1
Video compression is not understood well enough throughout the whole stack yet.

I recently got a 1080p projector for home use, so now movies / TV series in my home are viewed on a 100" screen. Content is mostly from Netflix and Amazon Prime Video.

Netflix does a really good job with encoding. I cannot say the same for Amazon Prime Video; even with their exclusive (in UK) offerings, like American Gods or Mr Robot, the quality of the encode is quite poor when viewed on a big screen. Banding, shimmering blocky artifacts on subtle gradients, insufficient bit budget for dimly lit scenes - once you become aware of the issues, it becomes really distracting.

OTOH a really big screen is a fantastic ad for high quality high bitrate content. Anything less than 2GB/hour is noticeably poor.
I was accused of being ignorant for asking a very basic, highly fundamental question, which apparently nobody has yet to answer sensibly. Honestly I have zero respect for these people.

Sycophants, could someone please address my question?

- I work in Python as does 80% of the infrastructure world.

- I want to tweak a config setting in your precious config file.

- I want to do it without linking against a compiler

- I want to do it without XML/XSLT (what the actual fuck, someone really suggested using another more practical data format to tweak/introspect code?)

- I want to do it without writing a tree-walking routine

- I want to do it without writing regexes

- I want to do it while preserving whitespace and comments and similar user edits.

Come on, this should be easy and practical, right? After all, you're obviously correct. Note I can do all this with XML, not that I'd use it, but it's still a better solution than config-as-code.
I also mentioned Series 90, aka Nokia 7710.

Although I do concede that if it wasn't for iPhone's success, OpenGL ES would probably never had taken off, as Symbian was one of the very few mobile OSes that had some flagship devices with hardware support for it.
If you follow the Apple dev community, there is a group of folks that make their living on books and speaking. That's fine, but they are using the platform differently than someone shipping software. They are also often the authors of some of the more ideological, less pragmatic proposals. This has a large impact on the disconnect the author describes - which incurs a cost on folks who ship software. I do wish the Swift team said no more often, but as with any dependency, you're never gonna get 100% alignment.
Even in Europe it's pretty lenient for the first period. Different countries obviously have different maximum probation periods but day 1 would fall into it in most (all?) of them
Interesting. I do like the question from a general 'do you like thing X' perspective, but as critics seem to rightly argue, you should not use it alone.

Another question I like in the same vein, "Would you recommend other people to work here?". I think it is just one of many measures of "engagement" though.

Also, I have to agree with the general sentiment against NPS. I have seen teams forced into UI enhancement death marches because their app got a low NPS. It was plastered on billboards and there was a huge push to get the NPS up. It became a bit of a running joke. That anecdotal experience made me really wary of it in general, even though I like the concept as a general engagement measure.... maybe you shouldn't base management decisions on just that :)
I don't know why you would say this but this is simply not true. Our confidential information was leaked, there is an incoming lawsuit, and we are trying to find the right course of action. The government department was tarred the moment they leaked our application to our competitor.
... where it's a type variable.

I think we can blame the use for lifetimes entirely on the Rusties.
We had a program manager on our team who used this app. She didn't understand that it flags repeaters and boosters which we have in our building and made the claim that we were running an illegal OpenLTE network as part of our security research. It was an uncomfortable situation to say the least. Ultimately I don't think these tools are very useful to end users and am encouraged by the SeaGlass project because they are collecting lots of data and correlating it with professionals analyzing the data.
plot twist: the dev attempts to off himself, and the company stops "laughing off".
I always had the impression that the biggest gripe with Vista were the incessant UAC dialogs asking you to approve every little thing (I think Apple even poked fun at it in one of their 'Hi, I'm a Mac' ads). And that this problem was actually a consequence of the (sensible) change from having all programs running with full privileges to limiting them and asking users for escalations only when needed - but since most existing programs were not prepared for this, they caused UAC dialogs left and right, where they could and should have been avoided. And understandably it took a while for all the 3rd party devs to catch up to this and change their code to fit well within this more restrictive security model. But the way I see it, this is much like pulling off a band-aid that's been on too long - it'll hurt no matter what, so best just get it over with. I imagine that if Windows 7 had been released instead of Vista and at the same time (and AFAIK it has pretty much exactly the same security model) then it would have born the brunt of all that negativity stemming from all those UAC dialogs. In other words, Vista had to take that bullet, in order for Windows 7 to go on the scene later as the hero.
So she got paid preposterous amounts of money to ruin other businesses so she could use their workforce to fool investors in to propping up Yahoo when it was noticed Yahoo was no longer useful and was falling in it's goals?

Capitalism: 'optimising' markets by giving all the value created to individuals who destroy the means of value creation.

It's like some sort of economic terrorism, destroy any hope of economy and flee with the money.
Obviously not the new engineer's fault. Unfortunately, aspects of this are incredibly common. On three jobs I've had, I've had full production access on day one. By that, I mean everyone had it...
When America was more deservingly called the "land of the free" in the 40s and 50s, they were also heavily unionized.

(Well, then it was "land of the free, blacks excepted")
which are all moving to whatsapp and wechat.

yahoo could have retained some of those eyeballs if they had more than two developers working on IM. To list a single example that a toddler could have came up with. saying that nobody could have done better than MM is a huge stretch of imagination.
As a lot of companies I bet they HAVE backup, just never tested if the backup process works. It is absurdly common...
Wow, really?!? I've never granted access to prod databases on day one, junior or not.

I thought that was just SOP.
You are forgetting a very important factor, politics trump technical achievements.

As for note, all modern mobile OSes have languages with runtimes, regardless of AOT or JIT compiled, but they all required architects with guts to push them through.
Swift on iOS and Kotlin on Android are a great update from their predecessors both in terms of syntax and safety, (Optionals etc.), which I really appreciate. I also like how they both provide just enough functional tools to be interesting and useful, yet at the same time remain firmly in the familiar OO land, makes the adoption cost a lot lower.
I worked in a potato chip factory for a little while and they made lots of store brand products. That doesn't mean they were all the same though. It was more like contract manufacturing. They produced a product to the specifications of the customer. It wasn't just repackaging the same product in different bags.
I'm not saying anything is wrong with holding the lawyer accountable. I'm saying that it's ridiculous to hold ordinary people accountable for complex consumer contracts. Even if you're a lawyer, you need either some familiarity with the relevant law or need to do some research to understand these contracts. We'd say it would be reckless for a lawyer to advise a client about such a contract with no background knowledge of applicable law. But we expect ordinary people to do it all the time and pretend like they understand what they're signing.
EPIC Motivational Video – Don't let them define you
In both cases the story seems like it can be summed up as "spec'd rewrites of major subsystems, and worry about implementations of how people actually use them later".

E.g. all the missing Win 8 basic Windows functionality, where the underlying system existed but no GUI had been written to expose it

And how Windows Explorer search is still a cluster$&#@ that's regressed in functionality since XP (available operands to specify search params, scope, speed, etc).
PowerISO 6.8 Full (x86/x64) Final and Portable [Get Here]
i think everyone knows poison is bad, but the question is, how much is proven to cause problems?

chlorinated pools are also full of poison but that isn't really an issue.
It's good that news travels fast today, or else people who didn't wash their hands after handling carts could be in for a surprise when they ate. That's the same chemical used in air dusters to stop them being inhaled deliberately.
One of the questions I asked my manager during the interview process was how did he feel about mistakes?

I knew I was being brought in to rearchitect the entire development process for an IT department and that I would make architectural mistakes no matter how careful I was and that I would probably make mistakes that would have to be explained to CxOs.

Whatever the answer he gave me, I remember being satisfied with it.
Omni was the magazine Wired aspires to be.
> I think in startup land - where devops takes a back seat to product - it's probably very common.

Not focusing on devops and putting your prod db credentials in plain sights are VERY different things. It's really really easy to do, especially if you are using Heroku or something like that. Same thing goes with database backups. I worked at multiple startups (YC and non) and they all had the basics nailed down, even when they were just 3-5 employees
So, since nobody mentioned that, i'll ignore your edits and try to answer your original concern. Generally speaking, this is S-Expressions (as others have said) and S-Expressions are trivial to parse and edit - you can write a parser in C that converts this to a tree easily. Note that the comments and such are a problem regardless of the config syntax used but the solution is the same: instead of rewriting the file, edit it in-place (to do that a simple way is store the index range of each node's value in the code buffer when parsing it and when you modify the node's value update the buffer's contents - make sure you also update the other nodes' ranges if the value changes length in characters).

All these assuming you want to implement the thing yourself. Which is fine, S-Expressions are one of the easiest tree syntaxes to parse. But there are already libraries that can do this for you (including full Lisp/Scheme interpreters) and some of them can even 'pretty format' the code like the quoted snipped above.

So generally speaking this wont be a problem in practice.
Just sent for the Junior role, it would be a blast! (Phoenix is WONDERFUL in June. I really liked it when I was there last year)
Plot twist: CTO or senior staff needed to cover something up (maybe a previous loss of critical business data) and arranged for this travesty to likely happen permitted sufficient number of junior devs went through "local db setup guide" mockery of a doc.

Either that or this is a "Worst fuckup on the first day on job" fantasy piece - I refuse to acknowledge living in the world where alternatives have any meaningful non-zero probability of occurring.
Sure, there exist reasons to do that. It's still a bad idea, but, ok.

But there is no reason to write the production DB credentials in a document, especially as an "example". That is monumentally dumb. It amounts to asking for this to happen.
earned =/= was paid, IMO this is an important distinction.
The frequency of 60/1001 Hz and the situation where we are stuck with it basically forever is a shame upon the entire profession of video engineers.