skysight-inc/HackerNews huggingface dataset:
If cost isn't as much of a motivator, and you just want the fastest way to get into the industry, I would recommend a brand name coding bootcamp instead. The time span is much shorter, many companies already have a sense of your expected skillset, your salary hit on your first job is often not that much (maybe nothing) and should be gone by your second job.

Getting a brand name CS degree definitely has its advantages, allowing you easier access to even higher-paying engineering jobs, and can really help build the foundation for you to become a much better engineer. But it's really just a better starting point (assuming financial aid), and your path from there is much more dependent on how you invest in your own career.
There is a real ethical peril here. You've just created a massive externalities-- the honest poster wasting their time without realizing it, hoping someone notices and tells them, and then having to take it up with you.

Shadown banning is an act of fraud against the user, with the hope that it's mostly against malicious already-banned users and that false positives will get it undone.

But since the cost of shadow banning is on the users and the benefit is on you, there isn't a particular incentive to not miscalibrate and cause a lot of damage to users.

The only backstop is that if you're very far into the false positive domain it'll kill your venue but because shadowbanning is invisible by its nature it requires a truly massive amount of false positives to have that effect.

There are also secondary damages that good users worry that they've been silenced and don't comment. E.g. after my last several submissions to HN received no comments I suspected I might be subject to some kind of shadow ban (since HN engages in that sort of thing) and stopped submitting.
Hi there, for sure! I'll put these companies in buckets:

https://render.com/
These folks are a production solution and have added support for review apps. All that happens is a new deploy of the production app on every PR. There's no support for spinning up arbitrary commits, caching, etc.. Further, its not free.

https://vercel.com/, https://www.netlify.com/
Only supports frontend (and maybe serverless?)

https://www.releaseapp.io/, https://getdockup.com/
These are both more direct competitors. Dockup is no longer around I believe. Wrt/ release we have different outlooks on pricing, as they charge a large initial fee. The product itself is similar, however.

And lastly, Heroku was discussed in threads below, but the general idea is that if you're already on Heroku, using review apps makes a lot of sense! With that being said, they don't support the features I mentioned above such as, restarting runs, comparing commits, caching, etc..

Let me know your thoughts, happy to keep the conversation going!
Reproducibility is just a side effect of lack of specificity, which is the major difference and the entire point of my critique. Design docs don't tell you enough to actually build the thing you want to build.
anecdotally one of the few things I remember about my maternal grandmother was that she implored us to take care of our teeth, and that she died of colon cancer :(

Wonder if she was on to something?
This is a point Peter Thiel brings up regularly on a larger scale, i.e. the circular, narrow nature of modern innovation, where instead of improving the physical world around us, we're way too heavily invested in this self-perpetuating "world of bits" that increasingly reduces total innovation in the world.

Incidentally, a great talk that includes that point here: https://www.youtube.com/watch?v=SO_00POR-Po
I've been trying to do this for a few years (admittedly failing).

You can come up with complicated models as some do, but I prefer simple models (3 dimensions or less): What do you want? What are you willing to build/iterate on for years? What can you find feedback on fast?

(1) because if you're using it you'll build something nice and have a lot of insight internally.

(2) because you'll need to work hard, fast, and for a long time to make something great.

(3) your reward systems depend on feedback.

Sometimes answering these questions isn't straightforward so I recommend building a lot of smallish things without an outcome in mind before answers to these questions become clear. You tend to know when you're well suited to something because you can't stop yourself from coming up with ideas and working on it.

Example: I spent a long time building/understanding http://choremate.co because it's something I NEEDED. Despite finding insight, (1) I found the work hard to do because it was boring (I don't enjoy CRUDing web apps), (2) I'm not innately interested in the research domain (behavioral and institutional economics), (3) feedback is best found living in a large shared household like a coop or fraternity and I don't live in that situation.
Hashicorp sentinel
Stop using someone else's domain and server space to act like that is where you deserve unhindered free speech. I'm so tired of hearing the bitching about Facebook or Twitter on HN lately. The future of the web will be decentralized. It never made sense to use your real identity and then go and post totally private conversations, unencrypted, on someone else's machines! Create your personally hosted cheap blog and post your thoughts there, where YOU control them. I think Facebook should start charging like $50/month to use it so it would wake everyone up to the simple fact it isn't your service. It isn't your server. You are choosing to be moderated in your "private" conversations, because you choose to do so. We should have millions of personal websites and blogs that are solely controlled by the individual but instead, millions of people flock to private web servers, for free, and act like they own it!Absurd.
Keep in mind Jorbs' bread and butter are particular types of games, in particular deck based roguelites and strategy games in the vein of the new X-Com series. Also before that he came from a poker background so a lot of his analysis of games comes through those lenses.
That's not really helpful. Let's assume you have a distributed system; you probably don't want all of your system components connecting directly to TimescaleDB. You also probably want to have some layer that implements queuing and handles back pressure if it can't insert into the database at the rate that events are coming in. You may want to batch insert data.

I'd assume that most anyone building a system like this at scale has to solve these problems; does everyone roll their own?
One of the things that I always find missing in these libraries/collections is a date/time picker. I know these are available via many separate projects, but it's nice if one picks a collection like that, that all inputs are homogeneous.
By doing what XML-with-schema did 15 years ago: give compile-time type checking, making sure at least the syntax and types are valid.

Ever had CloudFormation yell at you because some function like "Sub!" only accepts alphanumeric characters? Created complicated constructs because there are no variables, and very limited conditionals? Copy-pasted templates like an insane person because there is no way to abstract anything?

Not my idea of fun. All of this is solved by using a proper programming language.
Not really. Afaik integer multiplication still usually has lower instruction per cycle throughput than addition and obviously even if it were faster that would only apply to 32 but 64 bit etc integers not big integer multiplication.
"Things have always been getting worse."
Finished FFNM, Smooth JavaScript Intro for Web Designers
unbelievable, but sadly based on this experience I can see how that would happen and empathize
When I was a master's student, we used Nielsen and Chuang in our class. I found it to be pretty good.
It's not species extinction that makes life undetectable, it's extinction of the civilization. For a civilization to be detectable it has to be at least at our level, or maybe a century beyond our level. If our civilization collapses it would mean that we were only detectable for a couple of centuries and then it could take millennia for us to get back to our level, especially if we've extracted all the easy to extract natural resources making it harder for our ancestors to rev back up, or if large parts of the planet become uninhabitable.
This hasn't been my experience, but would love more info if you could provide it.

I'm actually surprised how slowly most tech companies shed staff. In general, it seems the industry is pretty hit-driven, and if you're attached to a good product that's still making money, there's rarely much attrition, even when perhaps there should be. Conversely, a lot of great people get let go when a product isn't working (misses the market or no sales). It all seems kind of arbitrary and random. It's a lot different than, say, a restaurant with really tight margins where you're a day away from getting fired if you aren't perceived to be pulling your weight.
Netflix was started in 1997. This conversation is about companies started a decade ago versus now. The rise post 2010 startups seems much more focused on creative interpretations of laws instead of actual innovation. The whole gig economy is a way to circumvent employment laws.
Hi there, yes this was discussed in a couple threads! Happy to answer any other questions you have :) .
Here's the reason I think it would be a problem for an imaginary, abstract incubator (because I don't think YCombinator actually does have this) to have a rule "To apply here you need to have alive parents, who like you, with a spare bedroom".

I think that the 10-20% group you are talking about is likely to have more than its share of not-white people. Maybe it's a small divergence, if we imagine the population of the US to be 50% white and 50% not white, maybe the group of people who can't go back and crash with their parents is 49% white and 51% not white.

OK, so imagine there's a different imaginary incubator with a rule that every applicant has to roll a 100 sided die. If they're white they have to roll a 50 or higher to get in, and if they're not white they have to roll a 51 or higher.

I wouldn't like the "roll a die" rule, I think a lot of people probably wouldn't, but it's ultimately not a heck of a lot different than the "crash with your parents" rule. You are still more likely to fall afoul of both rules if you are not white- or (if you change the dice game) gay, or poor, or marginalized in other ways.

(yes the probabilities are different, not the point)
> When poorer folk take the "same" risk, they can be ruined for decades.

In the vast majority of circumstances that's an extreme exaggeration.

Speaking from past personal experience with poverty (ie being "poorer folk"), you can default on every possible type of debt - wait about seven years (can vary slightly by state, but it's typically around that), and you're free from it. My credit rating went from 800, to 480, back to 760 in that process over eight years, without requiring any special effort. I defaulted on numerous credit cards, I defaulted on medical debt; it all vanished, one after another as time ticked by, and my credit rating jumped as each item fell off. Every negative mark falls off your credit report after N years.

It's very unpleasant to have your credit rating wrecked for years. To say that it will ruin you for decades, that's reaching into the land of absurdity. I'm sure it happens, some people get stuck in a vicious cycle for ... decades, however it's not rocket science to properly utilize the negative mark credit cycling to your advantage and reboot. It doesn't take more than an hour or two of reading to self-educate at zero cost about how the system works.
> As someone working in security, the phone is an extremely leaky thing and very bad for privacy to begin with.

Compared with a computer where every program can steal all your data?
There's a huge difference between pure "unnamed sources" that are highly partisan and publishing the pseudonym someone publishes under rather than their actual name.

Also, most of the credibility loss has been because a lot of those anonymous sources flat-out lied to them, but that's another story and I have yet to see them write about it.
Just went through the examples. Seems really intuitive and looks like it would be a good approach for homegrown linters. Would also love to see some plugin support for editors.
Is this actually a valid (albeit not feasible, but theoretically valid) answer to the question though? I didn't capitalize the I in my question, but I should have, because I do mean for it to be interoperable / peered.
I find design docs really useful, even if no one else reads them, because they force me to clarify my thinking before I start the (more expensive) process of implementation.

However, I've also noticed a couple of very common problems with design docs:

- Many design docs don't clearly state the problem that the design is intended to solve. Often the best response to a design is "that problem isn't important to solve", or "there's another system that already solves this problem", or "there's a totally different approach that you should consider", but without a clear statement of the problem and why it's important to solve, it's hard to determine those kinds of things.

- People often focus too much on the details of a design, vs. the important decisions that need(ed) to be made, the alternatives and rationale for those decisions, and the assumptions that they were based on. In a year, you probably won't care that much about the details of the parameters of some API, but you probably will care a lot about why you chose that API over some other one, and it's useful to have a record of that decision.

It's useful to view a design doc as a distillation of the thought process behind a system, vs. a high-level description of how to build something.
The traditional method in the article looks a bit different from how I learned it, which was this way https://www.wikihow.com/Do-Double-Digit-Multiplication,

The overall description of it looks right, but in the picture the order of operations would be more like B, C, D, A not A, B, C, D
what are you calling semi-random? A lot of enemies have semi-hard coded patterns with certain parts of it having multiple options (I think this last part is as much to make the runic dome a bigger penalty as anything)
New Relic Open Source: A Website for Open Source Projects
The big problem I see is discussed at the end of the article. Language is difficult to interpret and many times we misinterpret one another. When communicating we have a certain amount of assumptions we make about the other person's argument. If these are in good faith these tend to go smoothly, although there's always hiccups. The problem I see is that we're in a hyper partisan environment so the assumptions we are making about others' opinions are extreme. For example there's two assumed positions on immigration: let everyone in vs kick everyone out and build a wall. Of course the vast majority of people believe something in between (because both extremes are pretty unrealistic) but that's hard to determine without good communication. If you're pro DACA and you talk to someone that is pro restrictions you are likely to assume the person holds the extreme version of build a wall and kick everyone out (as in White Nationalism) despite that they probably have a more nuanced viewpoint. I believe this is happening because 1) the news is showing us these extremist people because it generates more hate, and thus more views/clicks and 2) people are co-opting some of these terms to dog whistle so it is hard to distinguish who is dog whistling (aka a white nationalist) vs who is oblivious to this context and using it in earnest. Which if it is latter, presuming they are the former makes it more likely that they turn to the former because you back them into a corner where that's where they can get support from.

This all, I believe, comes down to a phrase I have been finding myself repeat more and more.

> There are three components to communication: What is meant, what is said, and what is heard. They don't have the all be the same thing.

So I think we need to better train ourselves to try better at hearing what was intended and trying to say what we mean. In addition we need to stop turning to this reactionary based news, I believe this is why many (including myself) have turned off social media. Having lived in many parts of the country what I've learned is that everyone, no matter how simple their education is, has a nuanced view on everything. But I've also learned that trolling people, exaggerating arguments well beyond their merit, and "winning" have become more and more acceptable. There's a lot of people who just want to "get 'em" with a sick burn instead of having a conversation. I believe this is where we have broken down (and yes, I do think this is all related to the cancel culture).
I'd think that assuming knowledge of the seeds isn't an interesting question from the perspective of the player. To me the much more interesting question, and what I presume 1 is asking, would be "Assuming true randomness, is there are strategy that achieves 100% win rate in slay the spire." (True randomness meaning ignore pseudorandomness and assume that if the game makes something happens 5% of the time, it could do so from any valid starting state.)

Really what the question is asking is is there a strategy that for any theoretically valid game of slay the spire would, if followed, result in a win.

Given that the article did prove that there are theoretically unwinnable seeds with A20 silent, the answer is definitely not that am optimal player could win 100% of the time on all rule sets. Does change the question to "For a given StS rule set, what is the winrate the maximally efficient strategy would achieve."
Blog post: https://www.fsf.org/blogs/community/sign-this-petition-for-f...
I absolutely, 100% regret not studying computer science in college, or at least learning CS fundamentals earlier in my career.

I spent years struggling to write quality code, and I couldn't figure out why: I knew syntax inside and out, but still struggled with tasks my peers could do while watching YouTube videos and chatting with their friends.

It's like I could spell but didn't know the first thing about grammar.

I eventually went back and took some classes online to fill in the gaps, but I feel like I would be much further in my career had I just went ahead and done it in the first place.
Dad Who Pays His Son $1 for Every Book Read Divides the Internet on This Tactic
You're not thinking about it the right way. It doesn't matter if they have "enough" applicants. They're trying to fill the positions with the best candidates out there - who they will just have to compete for. The more barriers they put up, the shittier the candidates they will get.
> And: need was decidedly critical in the UK's computer engineering and science development during WWII (Alan Turing, Colossus)

It's useful to note here too that UK's work in WWII was started by desperate Polish need, and there is indication they got somewhat further ahead than people tend to credit them for. (It's interesting to wonder if Poland may have been ahead in computation if it wasn't, you know, invaded, and forced to kick the ball over to the UK.)

It's also worth noting the different approaches to "war time secrets" the US and the UK took. Where Alan Turing had a strong practical head start on computation in WWII, his work was locked under confidential and secret designations and he was not allowed to commercialize it after the war. Worse, he was almost entirely stopped from building practical machines, and it's a wonder he managed to contribute as much to computing theory as he did even with the restrictions he was under. (Also don't forget his own government lead him to an early suicide.)

The US in its contractor-based approach (including IBM's involvement) didn't hamstring commercial interests anywhere near as strongly (despite declassified hindsight now telling us they were straggling behind, comparatively, UK's efforts) so much after WWII by locking things into a "classified vault" and the US did not try stopping the people who had worked on computation from continuing to work on computation.
Customers are fickle and it wouldn't take much for them to start moving to another chat solution.

Case in point - we use slack at work, but when we need a call we'll typically use discord instead, as slack is horrible for calls (blurry text when screen sharing, often doesn't always let everyone on the call, etc). If everyone in the company started using discord for text chat as well, there would be very little reason to stay on slack and keep paying, as it wouldn't be worth it. Slack don't have something like office 360 to keep companies interested if chat fails to deliver, so all of those customers could evaporate pretty quickly.
Azure Fundamentals – Learn from Conventional Infrastructure
Mobile app idea #77: Stress Defactor
Statements of feeling don't admit of agreement or disagreement.
From experience, I'll suggest all serious security researchers to never, ever, sign any agreement with the company whose products they are researching.

This particular case is also outrageous for other reasons:

1) They are only doing this now because Corellium has been selling virtually the same thing for a while already.

2) They are doing this to try and hurt Corellium financially, while they're already suing them in parallel.

3) Agreeing to their terms here, effectively makes you a glorified Apple QA engineer. Only you don't get a salary, but rather, a bounty for whenever you find a bug. For most people that would be way, way less money than just being employed wherever.
If you require the user to hook into iTunes/Xcode, flip the device into recovery mode, click a few buttons, and agree to a "You're hecked if you break it now" policy, it'll be enough to scare off 99.9% of people from getting owned. After that, just have it work like the current profiles/supervision system where Settings makes it clear that non-verified code is running and has a big "make it go away!" button (sideloaded IPAs show up in profiles with a delete app button, and that works well enough except for the time limit).