1,278 karma · joined October 1, 2021
You're a fan of NIMBYism because NIMBYism is for people like you, who have no reason to worry about the price of housing. Any tradeoff whatsoever of "character" for affordability is bad from your perspective.
Cities and towns change when more people want to live there. They either change by adding more housing, or they change by getting much more expensive and driving out people who can't afford it. If you can always afford it, and "character" to you means the buildings in the area rather than the blue-collar people who used to live there, naturally you prefer the latter.
(And who shall I say is calling?)
What the DDG link illustrates is that when someone searches for information about that codepoint, DDG's autogenerated answer section accidentally _uses_ that control character (reversing the answer text) instead of just printing the codepoint.
This is odd... Did none of the working class smoke (surprising), or were there vast differentials in price between different kinds of cigarettes?
TLDR: The problem is the `% In`, and specifically the `%n` - when printf sees that, it tries to store data in memory. Failing to do so, it crashes.
Yes, a study failing to replicate is not in itself evidence of fraud. Nor is it definitive evidence that the effect shown in the original doesn't exist, since a replication can be messed up too.
But science needs replication because we're ultimately trying to learn about the world, and an effect we can't reliably produce is usually an effect we're not sure exists. Replication sometimes catching dishonesty is a bonus: failure to replicate calls the effect into question, which calls the method used to find that effect into question, which sometimes calls into question whether that method was actually used. (Or in the case of bad statistics, whether it was chosen to dishonestly show a certain result.) It's the appropriate propagation of doubt.
> a recent paper ... put forward a “new view” of robots, saying that “the direct effect of automation may be to increase employment at the firm level, not to reduce it.”
"At the firm level" is quite the caveat! If a company can produce two widgets per worker instead of one by adding robots, it'll succeed and grow as a result - at the expense of its competitors. But if every widget maker adds those robots, and there's no more demand for widgets than before, a lot of factory staff will be out of work.
They touch on a related point near the end:
> Mr Aghion and his colleagues add that even if automation boosts employment at the level of the firm or industry, the effect across the economy as a whole is less clear. In theory robot-adopting companies could be so successful that they drive competitors out of business, reducing the total number of available jobs.
...but it seems to me like a major problem with the whole framing of the article, not just a "by the way".
> Suppose you have a target that is half red and half blue; you are aiming for red. You would have to be very very confident in your dart skills to say there is only a one in a million chance you will miss it. But if there is a target that is 999,999 millionths red, and 1 millionth blue, then you do not have to be at all good at darts to say confidently that there is only a one in a million chance you will miss the red area.
> Suppose a Christian says “Jesus might be God. And he might not be God. 50-50 chance. So you would have to be incredibly overconfident to say you’re sure he isn’t.” The atheist might respond “The target is full of all of these zillions of hypotheses – Jesus is God, Allah is God, Ahura Mazda is God, Vishnu is God, a random guy we’ve never heard of is God. You are taking a tiny tiny submillimeter-sized fraction of a huge blue target, painting it red, and saying that because there are two regions of the target, a blue region and a red region, you have equal chance of hitting either.” Eliezer Yudkowsky calls this “privileging the hypothesis”. [0]
> There’s a tougher case. Suppose the Christian says “Okay, I’m not sure about Jesus. But either there is a Hell, or there isn’t. Fifty fifty. Right?”
> I think the argument against this is that there are way more ways for there not to be Hell than there are for there to be Hell. If you take a bunch of atoms and shake them up, they usually end up as not-Hell, in much the same way as the creationists’ fabled tornado-going-through-a-junkyard usually ends up as not-a-Boeing-747. For there to be Hell you have to have some kind of mechanism for judging good vs. evil – which is a small part of the space of all mechanisms, let alone the space of all things – some mechanism for diverting the souls of the evil to a specific place, which same, some mechanism for punishing them – again same – et cetera. Most universes won’t have Hell unless you go through a lot of work to put one there. Therefore, Hell existing is only a very tiny part of the target. Making this argument correctly would require an in-depth explanation of formalizations of Occam’s Razor, which is outside the scope of this essay but which you can find on the LW Sequences.
[0] https://www.lesswrong.com/posts/X2AD2LgtKgkRNPj2a/privilegin...
Maybe if you were allocating resources across the world's economies, it would be better to invest in solar panels in Shanghai than capture carbon in Billings, but that's not the actual situation.
> Was securing a job afterwords part of the problem?
Assuming that's a typo for "program", yes, it was. There was some job search training throughout the three months - doing a toy problem at the start of every day, being tested on your ability to talk about the projects you'd done there as you would in an interview - but the week or two focused on job search strategy and preparation. After you graduated, there were career coaches you could talk to and mock interviews you could sign up for. The network was the most valuable thing of all, IME: recent graduates who stayed close with their cohortmates (to swap advice, support, mock interviews) were markedly more successful than those that didn't, and having alumni at many companies was a big networking benefit, and the alumni Slack groups have been amazingly helpful to me to this day.
Until I got my job, I paid $750 a month for a shared bunk bed in a shitty SRO just outside the Tenderloin district. Not great, but I was never there because I was so busy. I also got one of the three-month TA positions offered to recent graduates, so that let me spare my savings while job searching.
Going to a bootcamp was the best decision I ever made, but that doesn't definitely mean it's the right one for you. You already know how to program and have a job, so it may not be necessary for you - and they're expensive, and risky, and many of them are not that great. (I can't even attest to how good the program I went to is nowadays, since it's been acquired twice since I left.) But for me, it was enormously helpful for getting my foot in the door of the lucrative tech industry, and once you have even a couple years of experience you're a very hot commodity.
(Also, if you do decide to go to a bootcamp, don't go to Lambda School/"Bloom Institute of Technology". They have both a lot of hype and a pretty bad reputation.)
What I would stress is that for a first job search, the coding is the easy part. You don't get a chance to demonstrate whether you can code at all unless you get past the resume submission and to the first tech screen, and as you've noticed, that's a very hard barrier when you don't have any experience. Job searching was brutal for pretty much everybody in my bootcamp cohort, even though a great number of them are very successful now, and this was entirely standard - the second half of the bootcamp was primarily dedicated to training people for job searching, and people generally spent 3-6 months job searching full time afterwards before landing lucrative jobs.
I have lots of things to say about this, but here's a few factors that I think are important off the top of my head:
1. Given that you have limited experience, you really need to focus on presenting it to best effect on your resume. You maybe have something of a leg up because you have actual work experience as a dev, as opposed to me and my bootcamp classmates, but it needs to sound as impressive on paper as you can make it. (And you need to be able to talk about it in the same way.)
2. Cold-applying through general job search websites like Indeed where you fill out a form is incredibly low-value - you're near-certain to get filtered out that way. There are a number of specialized job search sites for developers, some of which aim to skip the resume step in lieu of an up-front coding test (e.g. Triplebyte). Even better is networking, even kind of crappy networking: I got my first job, at an ~80 person startup, by cold-messaging one of the founders on LinkedIn.
3. If your resume isn't very impressive and so you won't get many tech screens or "onsites", you really need to train to pass those. I won't try to get into how to do that, since that's extensively covered elsewhere, but it's a totally artificial screening process that you absolutely need to put effort into.
People have mentioned that salaries are very different in the Bay Area than they are elsewhere, and that was certainly true when I started my SWE career - but given the enormous number of remote roles available, I think it isn't nearly as true any more.
Happy to give more info here, but if you want to email me, check my profile for an address.
It's a screwball idea, but I wonder if there might actually be health benefits to reliably killing pathogens without filtering them out of the air - sort of like low-dose inactivated-agent vaccines for everything you would have actually been exposed to otherwise.
The other factor for me is that job searching is not like coding: it's a series of separate tasks/decisions/evaluations, rather than me trying to immerse myself in a problem or system, so interruptions or distractions aren't nearly as costly; I'm not going to go into flow state from job searching. And a lot of the difficulty comes from the emotional aspect, so I found having someone to talk/vent to about it very useful.