skysight-inc/HackerNews huggingface dataset:
Ask HN: What careers can an MD do?
I'm about to graduate with a United States medical degree matching into emergency medicine. I've always been involved in tech, coding in various projects during school. My goal has been to combine medicine with technology, but I haven't found my exact niche yet. Does anyone in the hackernews community have any insight? Thank you!
I hear a lot about his genius but not straightforward, demonstrable examples thereof.
I recommend Infinite Jest on Audible. There are advantages to it being an audiobook, one being that since you aren't holding the pages, you won't see it coming when a chapter ends. This prevents you from rushing to complete sections, rather, you just go along for a ride while the story is told, not knowing where/when it'll end up.
party.lol looks interesting, thanks for linking it!
bitmapped set is one I don't remember at all. It have another name? A quick google not give me a clear idea of what is or how could be usefull...
In Project Management class I learned about Parkinson's law which states "work expands so as to fill the time available for its completion". That about sums up my life.
I don't really see how you drew the conclusion from my comment that I'm "celebrating the cult of Wittgenstein". I just take issue with this article, which amounts to a justification of a one-word hot take. I don't object to people having an issue with Wittgenstein -- I'm more disparaging of Wittgenstein than most -- I just want people to be thoughtful about it.

I certainly don't think something should be dismissed because it's written in an approachable way: that's a virtue that all writing should strive for. My point is that some ideas are inherently difficult to write about (and some people aren't very good at writing in a clear way), but we shouldn't be quick to dismiss either because of their difficulty.
I don't know.. when starting out or prototyping a new feature I find ORMS useful for moving fast, and the performance good enough.
You can always slowly migrate to pure sql for critical parts of the system.
Now Available – EC2 Instances (G4) with Nvidia T4 Tensor Core GPUs
They need to be able to check in voters on election day even if the polling place's internet connection drops.
How is this standard C# code to work over a list:

var males = from p in context.Person where p.Sex = “M” select c;

Any more imperative whether context represents a C# object or a database?
Exactly. I don't have any evidence to back up my suspicion. If the evidence exists, it exists in a locked safe somewhere at Ft Meade (or other place) and in the brains of a very few people.

I can feel what is known as code smell. So, let's develop a new feature in the most widely used security library. The very first thing that must be done is to sanitize network input. This is the first thing I would expect to be done by a seasoned developer. The lack of this check is suspicious. It could be an honest mistake, of course - we all make mistakes, and I am sure I've made my share of idiotic changes. But this isn't something I would expect about OpenSSL. I agree with @nickpsecurity, "many oddities".

Commit that introduced the vulnerability:

https://git.openssl.org/gitweb/?a=commit&h=4817504d069b4c508...

Fix:

https://github.com/openssl/openssl/commit/96db9023b881d7cd9f...
The simple solution to 1 is to never allow direct database access. Api only.
It sounds like you probably haven't worked on a lot of C code. OpenSSL is a giant security vulnerability pile. It is not at all hard to believe that someone has added a vulnerability by mistake: it would be more surprising to me if they hadn't.
You can't beat the speed of the Concorde either, and it was too expensive commercially. Perhaps if we correctly externalize carbon fuels, people will en-masse choose trains rather than airplanes.

I think the work argument gets pretty weak in modern society, where we have automation and most people could afford significant leisure. Sure, perhaps in capitalist reality it is different but it is still a social choice.
std::bitset is one. But you can just use an unsigned int, or array of them. In C++ or C, set intersection is &, union is |, complement is ~. Cardinality is __builtin_popcount, or std::bitset<>::count(). Membership test for m is (s & (1<<m)). For a larger set, represented as an array of unsigned, it's (s[m>>5] & (1<<(m&0x1f)). std::bitset encapsulates all this, optimally. There are similarly efficient implementations for lots of other useful operations: consult HAKMEM.

Bitsets are useful in more places than you might guess, because they can be used to filter out, with typically a single instruction, a majority of uninteresting cases in searches, leaving fewer cases to be examined with more precise and expensive operations. You record interesting properties of elements of a collection upon insertion as bits in a word stored alongside (or, better, in an index); and then first check the bits during any search. It is easy to speed up an amazing variety of programs by an order of magnitude, sometimes much more, with a tiny change.

For example, you can store an int value for each of a (possibly very large) collection of lines of text, representing the set of less-common letters that appear in the line. Searching for lines that contain a string, you first check it against the set for the string. Any line that doesn't have them all certainly doesn't have the string.

Leibniz (inventor of calculus) used this method very heavily in his own work. Before computers--and even into the 1960s--it was the most important way of automating data processing. Back then, you used cards that had a row of either holes or notches along one edge, and selected matching cards from a stack by inserting a rod through the stack at a selected spot, and lifting.
Controller is usually reserved as the implementation that satisfies an API, regardless of what it does. Operators hide operational complexity via judicious use of APIs - if using it in the broadest sense the ingress API + a particular controller implementation (nginx which is a deployed object vs an ALB which might just be programmed) is an “operator”.

A Postgres operator could manage Postgres instances in pods, or it could program AWS RDS. Having a deployable entity isn’t really required. The thing reading the API and updating those objects is definitely a controller.
So there is a debate about whether a license should be able to have "field of endeavor" limits and still be considered open source; how much control open source authors should (or can) have over it's use.

What is going on here does NOT seem to be simply a case of the government using open source code.

> "While I understand that many of you and many of our community members would prefer we had no business relationship with DHS-ICE, I have made a principled decision, with the support of the Chef executive team, to work with the institutions of our government, regardless of whether or not we personally agree with their various policies," Crist wrote, who added that Chef's work with ICE started during the previous administration.

So it seems what happened here is Chef the company went beyond writing FOSS that happened to be picked up by ICE, they have some business relationship with ICE where they get paid.

I thought chef was open source, so was confused about what selling the code would entail, but googling discovered that it was "open core"... until apparently April of this year when they released all code apache? https://techcrunch.com/2019/04/02/chef-goes-100-open-source/

Which leaves me a bit more confused.

Vargo was a former employee of Chef the company... who maybe also made open source contributions to the project after he no longer worked there? Unclear.

But this quote from CEO Crist is just garbage:

> "My goal is to continue growing Chef as a company that transcends numerous U.S. presidential administrations. And to be clear: I also find policies such as separating families and detaining children wrong and contrary to the best interests of our country," he wrote.

And you determined there were no ways of "growing Chef as a company" that didn't require aiding and profiting from activities you yourself consider wrong?

Does he really think this is a sentence that makes sense and makes him look good? I think he simply told us he prioritizes money above his own values, basically that he is a moral coward unwilling to stand by his convictions.

But yeah, the article doesn't give the open-source-geeky details we developers interested in open source want. What exactly is the relationship between Chef Inc and ICE? Of Vargo to Chef Inc? Vargo stopped being a chef employee when, and.. continued to contribute to chef after that? What is this "revert to a previous version" going on, to what previous version, a version before Vargo even had any contributions, or what? Which came first, Chef Inc. or chef as a community open source project?
One of the biggest reasons why I don't use ORMs is because I try to avoid using objects at all unless there's a really good reason to do so. And when I forget to follow that principle it has always turned out to be a mistake; de-objectifying has consistently resulted in simpler, shorter code with fewer data bugs.

My working principle is to have data spend as little time as possible being thrown around within application code. I tend to find that the longer data spends being sieved through layers and tossed around inside your application, the more data bugs you'll end up having.

And when it comes time to display data to the user, it's rarely inconvenient to write an SQL query that fetches exactly what you want to display in exactly the right format and exactly the right order—obviating the need to have any "objects" that "understand" your data model.

The problem is that far too few programmers realise how deep the SQL rabbit hole goes; it's treated like a little side-hustle like regular expressions, when for so many programmers it's the most valuable skill to level up.
Or perhaps it's a "theft" to justify some other effort to further restrict people's voting rights - like, I guess it's time to make everyone re-register, except for those right-thinking folks that they're already sure aren't cheaters...
This is correct. An in-house solution is a solution developed in-house for your specific problem, which no one else has ever had exactly. The more specific the need, the more the benefit of the made-to-measure solution. The alternatives are something your organization didn't develop, which may be better, but you don't know how to use it, or may be worse, but you don't know that when you pick it, or may be slower, but you don't know that when you start using it, or may have vendor lock in, but you don't know that when they sell it to you as "open", or may have hidden pitfalls, but they aren't in the glossy brochure, or may be unmaintained by anyone except your org in ten years, but you can't know that until ten years from now, or may be full of security holes because it was developed by idiots, but you can't know that because you didn't see who wrote it, or might be full of solid security features and a great design cleverly compromised by a hidden flaw placed in a specification you haven't read by a nation state, but you don't see that because why would you, or... etc etc etc. <sarcasm>But don't worry, at least you didn't have to understand the problem space well enough to be able to sit down and solve it yourself, so you sure saved some effort there!</>
This is the polar opposite of my experience. Not to mention that you undercut your own argument by admitting SQL’s tediousness: tedious code tends to lead to more tedious code, as subsequent developers fear breaking something, so they just add a layer on top of it, rather than addressing root causes. So that SQL view you had now has 10 inner joins in it, a union, and is being used by five other views now, each with their own similar levels of complexity. Trying to do any refactoring on this is almost humanly impossible, because you can’t keep all of it in your head.

And this is an extremely common situation to find yourself in. Code bases which are of middle- to large-sized, and which are inevitably touched by various hands of various skill levels, tends towards complexity.

SQL is the worst source of unmaintainable and difficult to refactor code. It’s difficult to unit test. Error messages are more often than not inscrutable. (I’m looking at you, Oracle.) There is no idiomatic way to break up complex SQL into functions or classes. There’s no type checking. You don’t have the equivalent of Ruby Gems, Python’s pip, or Swift’s CocoaPods. IDE support is limited to syntax highlighting Compare this with something like Eclipse or IntelliJ where you can just Ctrl-click on something and go to the definition. Want to rename a public method in a statically typed language? Pretty easy. Want to rename a column in SQL? Yeah, good luck. Not impossible, but you don’t have any guarantees that something won’t break until runtime.

So yeah. ORM has its place, and modern ones work very well at abstracting away SQL’s weaknesses.
There's a difference between thinking something might be worth understanding in spite of its inscrutability - which is what the parent poster was saying - and thinking something might be worth understanding because of its inscrutability.
Is there a link to the code somewhere on the website that I missed?

> function like email. When two users’ email clients support Tildamail’s protocol

Does tildamail support pop/imap? If not, do you intend on creating plugins for mail clients to support some other protocol?

> Tilda protects your privacy by encrypting your messages and metadata. Right now, email services like Protonmail can read your metadata, and they can see your subject line because it is completely un-encrypted.

> Also, they're closed ecosystems that don't interoperate that well so there's a chicken-and-egg problem (i.e. your friends need to download Signal).

So tildamail can send mail to non tildamail servers/email addresses? Is tildamail just using regular email and encrypting it like you would use gpg to encrypt e-mails?

(Sorry for dumb questions but the website has zero actual details and looks like a ploy to grab as many e-mail addresses as possible)
FWIW, I think the sweet spot for most web apps is to use an ORM on top of database views. This gives you the power and performance of SQL, but avoids the impedance mismatch of the ORM, since you’re defining what data will be on your objects at the database level.
Even with rumbling stripes before shoulder accidents still happen. And they will continue to happen, the same as security vulnerabilities in code.
Who people voted for is, but not really the other stuff. In my country, name, address and occupation on the electoral role are public-ish information that anybody can look up in the local library. The law requires it to be made public, though also disallows any bulk copying of it, so theft of the whole database would still be a problem.
The website does mention this:

> A distribution being “simple” has many different interpretations. It may mean simple to use, simple to develop or simple in its implementation. Further, the phrase “simple to use” may differ from person to person.
>
> Users with prior knowledge of Linux and basic programming skills will find this distribution simple in all three examples given above. A user without prior knowledge may see this distribution as the exact opposite.
ORMs that I've experimented with tend to fall into one of two categories: either they treat the object model as prime, or they treat the relational model as prime.

The former almost invariably spurt out inefficient queries, or too many queries, or both. They usually require you to let the ORM generate tables. If you just want to have your object oriented design persist in a database, that's great.

The latter almost invariably results in trying to reinvent the SQL syntax in a quasi-language-native, quasi-database-agnostic way. They almost never manage to replicate more than a quarter of the power of real SQL, and in order to do anything non-trivial (or have things done in a way that lets your database server scale) they force you to become an expert SQL anyway, PLUS an expert in how your ORM translates its own syntax into SQL.

And once you become more expert at SQL than your ORM, it's not long before you find the ORM is a net loss to productivity—in particular by how it encourages you to write too much data manipulation logic in code rather than directly in the database.
I would rank it probably as:
1) TSMC
2) Samsung
3) Intel

AMD now divested into Global Foundries used to be on there as well, but they're pretty much dead in the water at this point. Both AMD and Nvidia use TSMC now actually. It's kind of funny that Intel is the only remaining foundry within the United States at this point except for maybe Texas Instruments, which lets be honest, doesn't really count.
Colorado Techcast
You can set up plants in you bedroom like that today.

Why haven't you done it?

The yurt changes nothing, it's just a normal bedroom.

If you don't want to install a skylight it'd be possible with leds in a subtle/attractive/fancy way, go the HN angle

Anyway, point is, they have added bedroom porn to the yurt to hack you brain, you go wow awesome bedroom, but it has nothing to do with a yurt.

If a yurt actually interests you look at the shell and costings only. Not the interior design.

The plants will also be dead soon enough, is there a Tumble of these plant gardens after a year? Hard to setup, but impossible to keep going. There's a startup idea, pretty indoor/vertical gardens that don't die.
This is more of computer science issue with languages insisting on being turing complete. I suppose governments could incentivize language designers to produce and support languages that eliminate ever larger classes of vulnerabilities by only buying software that is written in those kinds of languages.
If you have a gnarly query, encapsulate it in a database view and use an ORM to interact with that instead.
Raymarching in Unity
Having to use Doctrine with Symfony and PHP was genuinely one of the main reasons I quit using PHP and went with Python.
5. It's MITM'd by Google's servers.

---

I don't know if you are being accidentally or purposefully misleading.

No one has a problem with simple HTML. That's never the dispute. People have a problem with Google servers seizing control of the client <-> server relationship.
https://youtu.be/8455KEDitpU you should watch this
The process should be 100% transparent here. I'm curious why the budgeting, invoicing, cannot be looked at transparently to discover what is going on here?

Can the contractors hired not be held accountable to their proposed budgets? 2-5x multiple seems about right as a fudge factor - but 10x?
Building a Piano with Flutter
When you put money into the market, but take bonds (which are a guaranteed future cash flow) out you are injecting liquidity temporarily, effectively trading current cash for more future cash.

It's not the same thing as printing money and spending it and suggesting otherwise is either disingenuous or ignorant.
I get that. But you could always fallback onto another way of reaching the server (LTE/4G) or even a direct connect to some central server close by. I mean, this is sensitive data that is essentially being replicated across the whole state onto devices that are not heavily guarded apparently. Surely there are better ways to handle this? And as connectivity gets better, I think there should be a push to adopt client-server architectures for critical infrastructure.

How would remotely wiping an iPad help? What if the stolen iPad is never allowed to connect to a network?
As far as I can tell, what happened here is Chef the company went beyond writing FOSS that happened to be picked up by ICE, they have some business relationship with ICE where they get paid. I'm not clear on the nature of it, from this article.

Seth Vargo, was a former employee... and maybe also kept contributing FOSS after no longer being an employee? Unclear.

It's not quite either of your situations, but more like the bespoke software I'd say.

At any rate, if I wrote FOSS that happened to be used by ICE in a significant way, I'd feel really sad and confused and not sure what to think or what to do -- I'm not sure what the solution to this situation is, but I wouldn't feel good about it.

If I worked for CEO Crist/Chef Inc. -- I'd quit. Cause that shit is disgusting.

If I was Vargo, doing some combination of writing code for an employer on the job, and maybe also just contributing open source to the project after that, maybe cause it was a cool/interesting project/community he liked... but then discovering that Chef Inc. and Barry Crist were _using the code I wrote to make money by helping ICE with their information systems_....

I'd be fucking mad as hell.

I'm not sure anything can be done about it legally in the long term, if the code was released open source. But I understand the anger and attempt to be as disruptive as possible. Cause Fuck That Shit.
Can’t tell if this is about ethically hacking the government for the good of the people or about making four cylinder Japanese cars sound like a dying mouse.
I'm sure the security community would love for these things to get fixed, but it's a constant fight trying to get developers to learn the correct way to do something. I've had developers tell my manager that having to fix security issues I report is putting them behind, so they wanted me to only be able to report security issues when they weren't working on anything else. Luckily my manager has my back and told them security is a top priority, even if it means fatures come out late.
I have used more than 10 languages now, but I'm moving to Rust. Apart of that:

- PostgreSQL + Sqlite. I try to use both for everything: Log analysis, reports, dashboards, etc + obvious crud stuff.
- Python3 for scripting
- If have not choice: HTML, JS + Vue
- Simple vultr/digital ocean vps

Rust allow me to get rid of docker (just deploy a binary! Like in my Delphi days!) and other complex stuff. I'm near "copy-paste" deployment now.

My only fancy tech now is using azure pipelines for compile across platforms (like android + ios).
These “omg privacy!” flavor of off topic post seems predictably standard for anything with “google” in the title.
not only this looks super awesome but this is also the first time i have seen a shell program architected in such a nice way.
> That cannot be "just replicate"d for javascript extensions.

This is false too. If extensions aren't allowed to communicate with the internet and can't auto-update themselves, then they also can't run arbitrary code without the user's consent.
I see. Sorry.

high five
Maybe Don't Write That Test
Most perfectly viable database schemas in the real world are trivial by your definition of trivial. Trivial designs aren’t necessarily bad designs; sometimes quite the opposite.

Thanks for the condescension though.
Although an ingress operator could be even higher level and ensure one or more ingress controllers were actually deployed (if you had an IngressController resource that made it easy to deploy them)
The problem was a shotgun parser. LangSec 101. Use a formal parser.
ActBlue seems pretty good. They centralize all donations and clearly present all recurring charges in a management page.
It should be easier to (a) buy a home and (b) rent somewhere else but still commute to a job. We probably agree on that.

But that doesn’t change the fact that renting is fundamentally unstable, and a short-term contract comes with risks. You seem focused on shooting the messenger.
The MITM happens at an application level. Not from your backend. A client chooses who to get the AMP content from: Google or You. Users who don't want Google's edge caching (MITM) can use software that doesn't talk to Google servers and still benefit from the plane HTML.