skysight-inc/HackerNews huggingface dataset:
Last year, I built a local/regional tech job listing website, targeted at helping 'older' people (35ish and up, of any gender) looking to find work--experienced or not. $100 listings.

Plenty of traffic. Totally failed. Started MVP by pulling in listings from elsewhere, but couldn't get a single listing.

Why did it fail? I think because:

1. Companies had zero interest in targeting 'older' workers in tech, despite them being the second-largest discrimination group (after women) in technology. I got more than one 'why would we target them?' response.

2. I didn't solicit the right people (or in the right way) for listings

3. Inexperience: I'm not very skilled at marketing, and saw a real need but clumsily approached it
You should talk to robert zmrzli, a google engineer and friend how also made wellnuo.com which is an active sensor system for tracking exactly this use case. If your email is in profile ill email intro you guys
oh, I completely agree that certificate transparency is beneficial for that and we have an alert setup. But, that still leaves me not wanting to leak every single subdomain we use internally. Hence using wildcard certificates.
Why 6 Hours of Sleep Is as Bad as None at All (2016)
In Germany I thought it was due to being privacy conscious?
I think I'm missing something. Yes, the VC industry has massively funded many companies. Some of those are not profitable. Some of those are even not viable. That's not a good thing. Maybe we would all be better off if funding was generally better allocated towards viable companies.
If you work in a strictly prototyping or research org, then it is much easier to accept what you are doing is a demo/prototype, and since you aren’t part of a production org, their is little chance of your code going accidentally into production (eg for a UX prototyper/design technologist). These are only things at big companies, however, and even bigger companies often have developers pulling double duty.

Still there is a huge opportunity cost if getting the wrong code up to production quality prevents working on the next prototype that gets you closer to the right thing. And I’m not talking about best coding practices, but putting in extensive comments, doing a bunch of tests, etc...
Is it doxing if they just republished already public information on the virology lab's website?
I think the question suggests another question:

Can an economy feel "irrational exuberance"?
Didnt realize things had become so bad, will keep in mind when I visit.
I have worked for either established and startup companies (admittedly with varying success). I think it has more to do with the composition of the team. As engineers there are a lot of different experiences we can bring to the table, but some of us have had the transformative experience of being on projects where the testing was right, in how to do and the amount, and we have seen how it helps us on a daily basis to move faster and be humbled by the bugs that we'd otherwise have released, or that we'd otherwise would've had to troubleshoot on a remote system rather than fixing them minutes after creating them. I'm now making it a point to expose my team members to the same awesome experience. But I also understand that, as you're building a startup team, and there are many things you have to get right, this may be a skill you would go without.

Also, I'm not advocating 99+% test coverage for new (startup) projects, but one could start with some tests selectively for core functionality or the most complex parts, and already enjoy a great overall benefit.
That's OK, I'd monitor JP Morgan's bets now that they are onboard. I just want there to be real, direct cost (positive or negative) be attached to the probability that the prediction is accurate. That would be vastly preferable to the current situation where there's no downside for the researcher for predicting incorrectly, and no upside to predicting correctly.

In fact, given the purported seriousness of the situation, this should be structured such that "USGS researchers" who are correct most of the time would be "wallowing in cash", and those who are not would be ejected from the field.
Ask HN: I can save companies thou$ands, but how to reach them?
I am opening up my private platform via API.

It provides text messaging services at less than half of current retail price.

To qualify, I am asking my first beta testers
- be small or medium businesses
- have a product that needs to send or receive text messages
- have a well-defined use-case
- have a have a developer that can code against my API

Why is this interesting?
Because I can give you wholesale prices starting at zero volume through a simple API.

CONTACT: 888-885-8548
EMAIL: hi@rek2.net
Right. Commenting on a very specific part of this with an anecdote. I did some integration with a ‘neo bank’ a few years ago where the CTO said testing and staging envs are a lie. I vehemently disagree(d) but they were paying to only test on production. I guess you can guess what happened (and not because of us as we spent 10k of our own money to build a simulator of their env; I have some kind of pride); testing was extremely expensive (it is a bank so production testing and having bugs is actually losing money... also they could not really test millions of transactions because of that so there were bugs, many bugs, in their system...), violated rules and the company died and got bought for scraps.

I understand the sentiment but I agree with 2, 3 and 6 of this article, the rest is, imho, actually dangerous in many non startup cases.

Example; Simple is always better IF you can apply it; a lot of companies and people you work with do not do so simple. A lot of companies still have SOAP, CORBA or in house protocols and you will have to work with it. So you can shout from the rafters that simple wins; you will not get the project. That can be a decision but I do not see many people who finally got into a bank/insurer/manufacturer/... go ‘well, your tech is not simple in my definition so I will look elsewhere’.

It is a nice utopia and maybe it will happen when all legacy gets phased out in 50-100 years.
I think mutually assured destruction works well enough to prevent all out nuclear war between multiple nuclear armed states. Riskiest scenario there is a nuclear state attacking a non-nuclear state that cannot retaliate in kind.

With a pandemic there's no one to negotiate with to come to an armistice.
It's basically what has been announced here, though, no? There's no technical impediment to a CA continuing to hand out 2+ year certs. The only reason they would not do so is that webpages will start breaking if they're accessed from Safari.
I always liked Basecamp's approach on this, which was that every team working on a widget (or part of a widget), had to be composed of 2 developers for 1 designer, so the designer was continually involved in whatever they were working on to give a UX perspective.

https://basecamp.com/shapeup/2.2-chapter-08#team-and-project...
Indeed OpenDistro is a great option to have. Currently using ODFE Security plugin with X-Pack basic (minus X-Pack security module).

Still waiting on these guys to review my perf patch though:

https://github.com/opendistro-for-elasticsearch/security/pul...
True, but I think OP was talking to me. There's nothing I can do about any of this, so why stress myself out by regularly reading about it.
I spent several years reading books on interpreters and compilers back in the days, but it wasn't until I discovered Forth that I managed to get a language of my own up and running.

While simpler than the books I had to force myself through, there is still plenty of stuff in here that's not relevant for a first language, nor fundamental to programming languages overall.

Once you have a feedback loop to play around with, you have a better idea where you're aiming and can go look for the theory you actually need to get there.

https://github.com/codr7/gfoo
Really then just power off the device and there you go, zero worries :)

Now really, I've had a look and it seems there are a variety of cloud baby monitor apps, that would allow for the occasional check.
Go was so obviously designed by Googlers, for Google. After the initial release, outside adopters would frequently report issues where Go undermined their productivity. And every time the core team's response was the same - complete disbelief.

"Dependencies? What? Do you not vendor every single library you depend upon in your monorepo?"

"Advanced type system? Why? Do you not hire thousands straight out of college, and expect employees to stay put for 2-3 years (give or take)?"

Every single issue that was raised in the past 10 years was met with such incredulity.

Rob Pike, Robert Griesemer, Russ Cox - they've done a tremendous job. A great, stunning achievement for their employer. The more of the infrastructure transitions to Go, the less money Google will need to spend on people in the long term. Those three have earned billions for their company, no doubt.

And none of that means Go is a great language for your 12-person team working on a CRUD web app.

The Zen of Go is not reducing your problem to "can it be put in an array?" or "can it be put in a hashmap instead?"

The Zen of Go is looking at individual persons and deciding whether it's net positive to cut them now, or 6 months from now, after their next performance review.
They acquired Mint years ago on the premise that a free consumer app selling financial products would make a great return. That didn’t work. This smells similar, with a dose of consolidation of the tax software market.
(Pocketsmith investor)
I do support constant deployments to the QA environment (also a no-no apparently). That can keep the QA team involved at all times. I wouldn't suggest waiting on large changes before having QA do a pass.
There is a desperate need for a publicly backed, ethical digital infrastructure hub. Just like NPR,PBS are the alteratives to profit driven CNN,NBC,Fox... we need an NPR for digital services: alternatives to Gmail, Facebook, Twitter, Dropbox and maybe even Google search.

If one were to run the above services at cost, and publicly fund the costs, we'd all be a lot safer
I think what people usually mean in these situations is that you’re forced to think about the error.

Programs in C (and many other languages) have the problem that you can ignore errors accidentally.

Exceptions “solve” this by forcing some level of your stack to at least acknowledge that an error occurred. The problem with that model is that you still don’t have to think at any given level of the call stack what the appropriate handling is for any kind of error. You can just let it propagate up further, deferring responsibility.

For some code that might actually be appropriate, but often it results in code higher up that cannot possibly know how to deal with every error that can happen farther down the call stack just swallowing errors.

One thing I frequently see is mixing validation code with processing logic. By separating the two you can have the validation code deal with errors and the logic simply assert that it’s input is good (because it should have been validated by the error handling code before being passed in).

I think models where you are forced to think about errors at each level but have a simple mechanism to make them propagate up are probably the best single model if you have to choose one model for a language.

In any event, error handling is difficult and frequently doesn’t get the attention it deserves in the design and implementation of libraries and large systems.
If all of the people who thought that way voted, it would matter.
Not only that these are at high levels the city is exploring a program to pay (using taxpayer dollars) for window replacements for such victims, which is both right and wrong at the same time...
This is a wonderfully curated resource! Thank’s for putting it together.

As you look to put things into practice from the resources you find here, I’d love to offer myself up to help in your learning journey. I run a 100% free mentoring service for live 1:1 conversations with managers and leaders. In the past 12 months, I’ve met with over 100 managers, and I’ve held over 150 sessions. I do sessions 5 days a week, and I’ve met truly wonderful people from this community through this service project.

https://freemanagermentor.com

Hope to talk with you soon!
There must be something else or something wrong, because you indexed one of my small repo (~100 stars, ~20 forks, ~20Mb) and not the bigger ones (~500 stars, ~100/150 forks, ~150Mb)
There’s also land.
I write every line of code as if it were going out the door.

But that's actually a fairly good idea (use a different language).
Interesting. This may be a dumb question, but I wonder what happens if you run an EDA simulation on this circuit. Would it still be random?
In regards to your edits, let me also mention that Let’s Encrypt does not offer (and indeed can not offer) “Extended Validation” certificates, due to things related to the two “bad things” you mention. However, extended validation certificates don’t in fact prevent fraud the way they are intended to — indeed, a security researcher managed to get ahold of a certificate for Stripe, Inc. simply by legally registering a corporation under that entity name elsewhere and purchasing a certificate for that legal company.[1] This issue with EV certificates — the fact that they are issued to a company as opposed to just a domain name — cause them to potentially pose a greater risk to web users.

[1] https://arstechnica.com/information-technology/2017/12/nope-...
These viruses have a reservoir in bats and they jump to humans through an intermediary animal. In the case of the virus that caused SARS[1], which was another coronavirus within the same family as the current virus of interest, there is some evidence that it went bats -> palm civets -> humans. Palm civets are/were sold at wet markets in China. It's not definitive that the palm civet was the source, however, as they subsequently found the virus in other animals.

For the current virus[2], the time and place of transfer is unknown, but the current thinking seems to be that it followed the same chain as SARS (bats -> some animal -> humans).

There is absolutely zero evidence from credible scientists of any kind of "escaped from the lab" or "bioweapon" source. These are just conspiracy theories.

[1] https://en.wikipedia.org/wiki/Severe_acute_respiratory_syndr...

[2] https://en.wikipedia.org/wiki/Severe_acute_respiratory_syndr...
Has anyone used this for a long time? I wonder how the camera (and phone in general) will deal with being on 24/7.
Credit Karma recently opened a decent sized office in my city and is continuing to expand. There are still 26+ engineering roles posted. I visit the office frequently and know a lot of the director levels and up working there. They aren't going anywhere or stopping anything they are doing.
For a topically related effort see the oft featured and outstanding book at http://craftinginterpreters.com. (I'm not affiliated.)
Show HN: Create free about me or professional CV|Resume website
If this were to be offered by an actual company (a first party solution), there are some features that'd be expected that make the problem space a lot harder. Here's an "intro to search" article that's a good read, and I'll use it to highlight some of the things that'd be different in a first party solution - https://medium.com/startup-grind/what-every-software-enginee...

(See the "Theory: the search problem" section)

Size: This is only indexing ~500k public repos. A first party solution would be expected to index all of it, public and private.

Indexing speed: This can take up to a few days to index. A first party solution would be expected to have a much lower index latency - seconds to minutes.

Query language: This can (and does) have its own simple query language. A first party solution would need to have support embedded into and not break backwards compatibility with the current query language.

Context-dependence: A first party solution would be expected to index private repos as well, and now the query context (logged in user) becomes another variable in an already multi-variate problem space.

Latency: Gets harder with scale, and a first party solution would likely provide a SLA/SLO around latency.

Access control: Same issue as context-dependence, with private repos being included.

There's also unknown but likely considerations around compliance and internationalization, which are quite tricky problems.

Note - I don't mean for this to be critical of the author at all. This is an awesome and useful tool, with a fantastic UX. I just want to make it clear that search at scale is a lot harder than it seems at first glance, especially as the feature requirements increase.
I wonder if anyone uses greenhouses as carbon capture for traditional power plants, rather than running their own mini-power plant mostly for the CO2 output.
This depends on the doctor, patient, location, and reason.

I have never been turned down for additional medications.
My roommate just got a 3 month supply of all of controlled painkillers upon request.

Also, If you have a life-sustaining medication and can afford it, it is probably a good idea to have a supply even if you have to pay out of pocket.
I'd questing even saving any time, let alone 5%. I guess the supposed time would be typing and thinking of a good name?

Maybe you save a bit of time during very initial prototyping, when you're just trying to create the exact algorithm for something (eg working with a dozen or so lines of code).

As soon as it's actually used, even if in a "proof-of-concept" prototype, you'll easily spend double that time on cognitive overhead (eg, the next day/week, trying to remember what that variable is) or just in typing out comments. If other people are ever looking at or using the code, it's easily 10x the work you're creating.

Another way of saying this: once your code exists for more than a couple hours, it should have good (not necessarily perfect) variable/function/token names. I agree on the ide vs text editor comment, and add: another nice thing about using a good ide is you can rename the declaration and let the ide update everything else.
tldr; use "ebola" elbow bumps instead of handshakes, don't touch your face, there should be an app to count the # of times you touch your face, tell your friends not to touch their face when they touch their face. Did I mention not to touch your face?
AT&T Closing DC Comics If 5th Gen Reboot Fails
Lease.ly, a common app for apartment rentals.

- In SF (a seller’s market), prospective tenants only wanted to use it if their prospective landlords asked for it, or if it gave them an advantage over other prospective tenants

- Landlords have their existing process that works, and didn’t want to change it. Things like comparison views for tenants, pulling in social media info, and automatic credit reports were helpful, but since for most SF landlords getting new tenants is low frequency (unlike, say, NY), the value was low

For each, the value prop was unclear.

If I were to try it again, I’d try to understand the market better and find the right subset of landlords and tenants, and the right geo, to focus on first.
We've changed the title to the original now, as the site guidelines ask: "Please use the original title, unless it is misleading or linkbait; don't editorialize." (https://news.ycombinator.com/newsguidelines.html)

(Submitted title was "Genomic analysis suggests seafood market was not SARS-CoV-2 source". )
> This guide is clearly intended to focus on the ops-side of ElasticSearch.

What's your point? The ops side of anything also covers security. In fact, you cannot have ops without effective security.
> I may be biased because it's pretty easy to use

Seems like a good reason to be bias.

I’ve used it for a while as well. Initially it was cheaper than TT but I have to guess they are comparable now.
how did you survey people? if you dont mind me asking
> make sure the people using throwaway code understand that even though it kind of looks like it works, it cannot be maintained and must be rewritten

I couldn't agree more with this. Not that long ago I inherited a project which on the surface looked shiny and nice. I was however aware that it was a mess underneath. Mind you, I was completely unprepared for the utter crap that awaited me. In all fairness it is the worst thing I have ever seen by light years. It took me two almost 2 weeks to find where a bug was coming from (it was written in a way which no debugger could trace it back, no logs, everything was surprised). After fixing it eventually, I decided to scrap it and build the whole thing from scratch. At the end it took me just over a month (Saturdays and Sundays included) and another 2 weeks from another developer to get a replacement project from an empty file. And here are the two painful truths about the whole endeavour: it took us collectively under two months to build, document, test, and run it in production. A grand total of around 20-30k lines of code. It took the people before us 3 and a half years to make their version which was anti patterns, top to bottom and in those 3 years the company invested around half a million Euros in salaries alone. If argue that this is the most painful thought. Not even the fact that this has been my first weekend this year in which I'm actually relaxing and not working. So my word of advice-if you end up in a similar situation, scrap everything, do it from scratch. Take a piece of paper, write down the business logic, draw a diagram of the structure of your application around it, pick the most appropriate stack and go for it. Avoid shiny new toys, profile everything and remember that sometimes it's better to let an application crash in order to find it's weaknesses.
React + TypeScript seems to be to frontend JS as JEE was to Java.
> It didn't pick up the traction I was expecting, guess this is not really something people need.

Or maybe they just use https://pingdom.com
Thanks for your comment! But I don't think all legacy will ever get phased out.

Today's code will become tomorrow's legacy.
I wish the full jira implementation wasn't only available in the most expensive plan. We would rather use gitlab but the cost would be more than double of what we pay for bit bucket.
That might work for video games, but in a web company I've seen so many throwaway bash, perl or python scripts wrapped in an `system(*command)` that are unmaintainable and sometimes cause RCE or injections bugs.

I feel that this advice only fixes the symptoms and not the underlying root cause. This is a culture issue, not a technical issue.
Wouldn't it be a better idea to use alternate domains instead of subdomains? You could use something like [any subdomain].atdie8e73bhdbdie93ruhe.[any tld] for obfuscation?
I suppose that’s fair, the only thing I know is that the advice is listed is accepted right now to be the best for most people at this time.

Maybe there is something better! I, along with your average uninterested person, won’t be the ones to find out.
So where are we on Data Lakes vs NewSQL [1].

[1]: https://en.wikipedia.org/wiki/NewSQL
The Lost 110 Words of Our Constitution
Someone else mentioned news outlets having low integrity ratings and I have to agree that many have crossed that threshold.

I remember channel-flipping past all of the outrage on daytime talk shows (Jerry! Jerry!) because they were trash, but that low-quality/short-sighted outrage somehow made its way into the news cycle over the decades. AI/ML filters will be a boon for information curation. Bipolar insights have no value whatsoever.
It's not a black/white thing, really. My code tends to be somewhat repetitive and terse while exploring new ideas.

Once I know where I'm going I'll gradually refactor and spell things out to the level I'm aiming for, which is different depending on context.

Polishing code that should never go anywhere is a waste of life, and once you've spent all that effort it's more difficult to keep an open mind about the design.
Javap.yawk.at: display Java bytecode interactively