skysight-inc/HackerNews huggingface dataset:
In my experience and opinion I think no employer will ever look down upon a particular technology that you know.

What they might look down upon instead are some characteristic traits that they might find in you. For example: passive, not enthusiastic, no ambition etc.

If you show enthusiasm and passion for what you do, the employer won't hesitate to hire you because everything is learn-able if you have the will.
In my amateur economist models, I adjudicate over-saving as a symptom not the disease. It is clear that money issuing does not have a neutral effect (not the same as private firms investing, or private firms being taxed to fund a government project). In the end it comes back to the utilitarian-keynesian view that the government will be more efficient spending that money, or that such a thing would not have long-term effects on the exchange rate, savings, etc.
JSonnet looks cool! I look forward to seeing your project also.
Makes me think of electric cars. Just a few edits: "Electric cars were first seen as a Maker project or "a rich man's toy", but Elon Musk worked hard to change that perception. He said electric cars are for anyone. They can be used to go to work, to visit family, to go sightseeing."

Given that they're being built with autonomy in mind, wouldn't they qualify as robots owned by regular people?
This is the self effacing, perfectly humble, PC thought enabled droid who knows that creating an impervious wall of humility and picking their battles gives the impression of infallibility and leadership to the non-technical and management. I like the 'customer first' item. Where did that come from except the brown noser and CYA workbook? Reference to Cantrill is superfluous. We all know Cantrill is first paragon in the SV culture of perfectable technical humanity and that Linus Torvalds is the exact opposite of what 'we' should strive to be.
I also spent time on the streets. It's _not_ just a home. Many of the kids I hung out with ran away from "homes". A home can isolate you from your family (other street kids) who are the only other people you care about at the time.

Homeless kids need hope, they need time with people who will actually stick with them and really help them see the benefit of a job, going to bed on time (the shelter's had a curfew), how to be respectful, help getting off drugs (or staying off them).

If you give homes to homeless people as they are, I think most of them would get trashed and abused until they are no more liveable than a park bench.

Then what, evict the homeless people from their free homes? Give them another free home all fixed up?

It really is hard work without a simple answer.
Yes, one thing I've noticed is that good code has application-specific invariants. You should think about it at a higher level than lines of source code and the values of individual variables.

Of course you can verify these invariants with a debugger. But when you hit a bug and immediately start digging in like Pike says, that tends not to be what you're thinking about.

Debuggers are great for putting in the minimal hack in a production codebase that doesn't disturb the code. But they're generally bad for developing software, because most (all?) software should have some invariants that allow the Thompson style of debugging.

You step back, think about what invariant could have been violated to cause the bug, put in a print statement somewhere to see if it was violated. Then you take another step back to think about how to fix it, possibly with a fundamental change to the data structures. That is, you design your software differently to avoid the bug, rather than just putting in the minimal hack.

-----

The other problem with debuggers is that once you've used one and modified the code, then everybody who modifies the code later probably has to use one too. The code has become subtler, but not in a good way. This makes development slower.

-----

I think it also relates to another thing Linus said [1]:

Bad programmers worry about the code. Good programmers worry about data structures and their relationships.

It's easier to diagnose problems in data structures (by printing them) than to diagnose problems in control flow (which is greatly aided by a debugger).

One weakness of debuggers is that they don't print things in application-specific formats. You have to write debugger plugins, and those aren't set up for most projects, and they don't behave the same way on all platforms, etc.

So basically having a bug that you can't figure out without a debugger is a sign that you may be using too much CODE and not enough DATA. It's a smell that indicates a problem with the software design.

Of course, in the real world, sometimes you have to swoop in with a debugger and fix something. But I do think that there is something wrong with living in a debugger for months on end (which I have experienced on one dev team.)

[1] https://softwareengineering.stackexchange.com/questions/1631...
"How do you know you're not just a victim of unknowable facts?" is a bad argument.
If you have the time and money, some cargo ships rent out additional rooms to travelers.
(Via reddit) There is a way to get around the paywall for all articles with no limits. WSJ considers links to articles from Facebook to be advertising, and allows full access. Next time you find a WSJ article you want to read, simply paste the following address BEFORE the address of the paywalled article in your URL bar:

http://facebook.com/l.php?u=
The number of people being subsidized is not that large. I'd wager that it's aproximatly made up for by non-homeless people who leave the destination states and then advocate for public policy that exacerbates the homelessness problem in their new cities/states. The spread of severe homelessness problems (i.e. the difference between homelessness in Baltimore and homelessness in SF) northward up the west coast but lagging CA's level of homelessness by a couple years seems to support my hypothesis.
It definitely takes it's toll, I had a one bedroom near "Oracle Park" and while I can't complain about it's quality or location, you knowingly paid for it. 8 Years ago It was around $3500 and I was frustrated and decided to get out, I looked up the price now, around $6k. It's just crazy.

Then there was the process of getting the place, Print out credit score in advance, show up on the spot (hoping to get in on the early rental showing, prior to the publicized showing) and be prepared to put down 1st and last months rent and 1 month deposit then and there.

It's simply not feasible for most americans to do that. Even the tech-oriented jobs aren't all paying the crazy rates you read about. The fact that the Department of Housing and Urban Development now states that $82k a year puts a single person in "Low Income" is just preposterous. As ahead of the curve as the city likes to project itself on social issues, it has a lot of do as I say not as I do attitudes among the NIMBY crowd.

I think it's turned it into a situation of in your early 20's, go to SF/Bay and experience it, then in your thirties start looking elsewhere for quality of life.
I use print with python for small scripts, if I'm doing a big app I use the logging module and set log level to debug when debugging, because that's what log levels are for.

Debuggers are nice for big apps that you don't truly grasp the scope of, I know debuggers have saved my bacon several times when dealing with quirks/bugs of UI frameworks. Just being able to inspect variables and check the call stack is a great way to find out why/when shit hit the fan.
It's also quite useful in caches, though still novel to do so:

http://highscalability.com/blog/2019/2/25/design-of-a-modern...
Job hopping. Gaps in resume. I know this from experience. :-(
I would say, see the world while you still can. Your individual carbon impact either way makes zero difference, and aviation is responsible for 2% of human carbon dioxide emissions. We're either going to solve this problem on a grander scale than everybody riding bikes, or the world you currently have a chance to see is not going to be around much longer in its present form.
Adding layers to the middle of trained network without invalidating the weights
I would use ray tracing to get a non-linear camera, specifically so I could have a wider field of view with less distortion than the linear camera & wide fov. Back on Q3, everyone would use 120 or 130 degree fov because that was the best compromise between seeing things to your side and everything getting squished into the center of your screen. If I could have played with 180, I would have.

Your lighting point is reasonable in the sense that this demo was made to demonstrate the dramatic lighting without respect to gameplay. On the other hand games are already clearly going toward HDR and physical and dramatic lighting. If Quake had HDR lighting, it would look just as good but it would be less distracting because it would have been directed and designed to support the gameplay.

This version also has dynamic adaptation which would have been awesome to have back in the day - some of the dark areas are too dark and it’s great to have the lighting automatically adjust so that at least I can see.
hard to say, as i haven't dug into it at all. on the face of it, using their stronghold in venues/marketing (livenation) to get their way on ticketing (ticketmaster), or vice versa, seems like it would be ripe for abuse as well as regulatory scrutiny.
3-month and 10-year US Treasury inverted today
How do you guys compare to logojoy?
South Korean government is not against anti-nuclear. It's CURRENT administration of South Korean govt is. Once the president and his cabinet members leave in due time, anything can change.

Pros and cons of a democratic government I guess.
Sailing is great if you don't mind (extremely) slow travel. I bought an 8m from 1972 for about 2 months' worth of rent and have since moved with it from the UK to (nearly) Spain.

I did it for different reasons than you, but it sounds like it might be a nice fit. Although now that I've said that, there are admittedly another set of environmental problems from the anti-foul paint, so perhaps it's just trading one issue for another.
The advent of the internet was supposed to put instant access to information at everyone's fingertips, and be a net positive for facts and science.

However, people have ignored the same technology's ability to instantly gratify reinforcement of falsehoods, and the spread of misinformation.

You can see a correlation between the rise of the internet and continued rise of:

1. Radical religion

2. Anti vaccination

3. Flat Earth conspiracies

4. ....
yea this is just standard
Why would a "simple landing page" require a complete library like jQuery? No need for React or Vue either. The few things that would require JS (if any) should be easily coded from scratch by any competent coder.
I had a realization the other day when I rented a sports car on vacation. In the future you will just show up to a garage and scan QR code to view and accept contract for car rental. It would charge you by the minute so you can drop it off whenever you want. Also, if something came up and you wanted to leave the car somewhere else or switch cars, the cost to transport the car to another "share garage" would be easily calculated.
There are a bunch of laundry startups:

* https://www.rinse.com/

* https://cleanly.com/

* http://www.washclubnyc.com/

These startups employ people to do the laundry of their customers. If they get big enough, those startups might invest into automation.

Your dishwasher, washing machine, dryer, etc. is sitting around most of the day being idle, with its utilization being really low. Industrial laundry robots don't need to be mass produced in order to be profitable, they can be hand manufactured. This allows lower capital expenditures and allows for faster iteration. And you could pay some person to watch 5 robots and correct them when they do something wrong, something similar isn't possible outside of the industrial setting. So those services will greatly help with the invention of automatic laundry robots I think.
What you are describing sounds more like ray casting than ray tracing.

Ray casting is the old Wolfenstein 3D look: https://en.wikipedia.org/wiki/Ray_casting

Ray tracing is what Pixar uses for Toy Story, Monsters Inc, etc... https://en.wikipedia.org/wiki/Ray_tracing_(graphics)

And then the new hotness for offline rendering is Path Tracing, which is a form really good but really hard to accelerate form of ray tracing: https://en.wikipedia.org/wiki/Path_tracing

And yes fundamentally all of these are "shoot rays out from the camera", hence the very specific terminology used for each to disambiguate which approach to shooting out rays from the camera is being used and what happens when rays hit a thing.
You and me both. I want something I can actually feel like I'm in control of because it not only respects me as a user but also is built on simple metaphors that map well to reality, allowing me to actually understand how it works without untangling a horrible spaghetti mess of legacy systems patched together with spit and rubberbands. Something meant to help me make my life better instead of making someone else a bunch of money making me miserable.

Sadly, I'm not aware of anybody working on such a project. Most people making "OS"s these days either just make yet-another-linux-distribution and confirm that old saying about the definition of insanity, or they're content to make some completely academic kernel that no one can use for anything but academic purposes. I wish I had the skills to start one myself.
I wonder if someday we'd be able to trigger small earthquakes to release pressure gradually and prevent larger and more destructive earthquakes.
Or just not eating meat. :P
The fact that organizations rely on job titles to measure/understand their capabilities is the problem. Sure, it’s simpler to think in labels/titles, but the strength is in the individuals. Look at team sports as a counter example where the thinking is in terms of the individuals, not labels.
The latter freezes your program for non-trivial amounts of time which can be problematic in some cases.
It's complex, and defies simplistic explanations (so don't believe simplistic explanations if you see/hear them).

An attempt at a nuanced explanation (which undoubtedly misses a ton of factors):

Huge disparities in overall wealth and income, coupled with geographic segregation and isolation of a lot of the black population in areas of concentrated poverty, and the associated lack of access to social goods, such as public safety and good schools. The combined effects of poverty/segregation/isolation are specifically reflected in the fact that 78% of homicides involve people who know each other [1]. People who know each other killing each other is a result of the breakdown of community structures that would disincentivize that behavior. There have to be powerful incentives for someone to kill someone that they know, considering that the potential consequences are so severe (incarceration, violent retribution, etc). Often the perpetrators have very little (in wealth, community, etc) to lose, which also increases the incentive.

Another group that are similarly economically poor, Latinos, but due to a different history, have more intact community structures, don't have as high a rate of violent crime.

[1] https://www.bjs.gov/content/pub/pdf/htus8008.pdf (Table 8)
That's an incredibly narrow definition. Why does the backend's capabilities matter? If a site has comments set up through its own backend vs through Disqus, the UX will/could be pretty much the same.
Counter example: LiPo phone batteries
> "As for why the height of Americans has plateaued, while the Dutch continue to grow like weeds, Dr. Komlos theorized that it is because of differences in nutrition, health care and spending.

“Average income is a very misleading indicator,” Dr. Komlos said. “It depends on who gets that income, and how it is used. If you’re healthier, if you go to the doctor regularly, you’re likely to live longer. And you’re also likely to become taller.”
> But when I’m working on large software projects or certain external libraries I tend to encounter bugs or design issues where I realize I made the wrong assumptions about how someone else’s code works in the first place

This. A few days ago, I spent a couple of hours trying to get a Jest+Enzyme test to open in chrome inspector, (apparently there's a bug which causes debugger statements in Jest tests to be ignored), because I hit an edge case bug in a method in the Enzyme library. If I had been able to step through it in the debugger, it would have taken me minutes to figure it out, instead I spent a couple of hours going through the codebase and figuring out where to put the log statements.
Ask HN: Please Help in Choosing Internship Track
I have got an internship offer with the role of Data Science Intern at a reputed organization and another offer where my role will be dealing with Hadoop based technologies at another firm. The internship period will be for a quarter. I will be looking for ML Engineer role during Full Time which of the above two roles will be more relevant for ML Engineer?
The city of Santa Monica created a better solution - easy access to public toilets with an interior that is completely metal so its easy to hose down to keep them clean. For the most part they keep these very clean so while you see these outbreaks downtown you don't see them in Santa Monica because they do have public bathrooms. In downtown LA its impossible to find a public bathroom often the metro stations don't even have bathrooms. The assumption made is that bathrooms attract the homeless but in reality creates a situation where no one can wash their hands easily downtown.
So what if you don't connect with the local culture? What if that isn't your point of traveling?
Maybe. It's hard to know if a later earthquake would have happened or been worse; it is normal for crustal rock to store some level of stress that is never released. You would need to know if the stress was changing, and how fast. If it wasn't changing pretty rapidly, it's possible it would have just sat unreleased for a very long time from the human perspective. Major earthquakes are rare; stress is not.

There is also the question of what happens now that it has been released. Rocks are all connected, so a release of stress in one place might result in movement somewhere else eventually.

BTW it is difficult to measure stress in crustal rocks remotely, without releasing some of it. So all of this is hard to know, and therefore hard to account as risk in new hydraulic injection projects.
Why are you giving your functions uncertain data?

The first point your code sees uncertain data is the point that it needs to clarify what it has.

The only way you get the errors you're talking about is if you ignore the above practice.

Garbage in. Garbage out.

For code i write, there is usually only one option for what is in a variable, the type of the data i out in there. This is true for dynamic languages as much as static.

In some situations I will also allow a null value. All that means is that there was no data, and no default is wanted. Usually, I want a default.

Closing off all entry points for uncertain data you need to make assumptions about is the first port of call when dealing with other people's or legacy code. It's the way to reason about code without a debugger.

If you can't reason about code without a big question mark above every piece of data you need a debugger.
GoFundMe Bans Anti-Vaxxers Who Raise Money to Spread Misinformation
But give it a humanoid form, a menacing mechanical voice, a bad attitude, and a zap gun, and the skepticism is much reduced!
Best way to find out is to look at the top companies in your metropolitan area, and see if there's someone in your LinkedIn network at any of those companies you could reach out to and ask.

Stuff I've seen consultants getting hired for:
- Salesforce implementation
- Sharepoint implementation
- AWS/Azure implementation

Again, depends heavily on what issues companies in your area are facing, that they're not looking to hire FT for.
“An alternate DNS can be used to create an alternate reality for the majority of Russian internet users.”

"Russian users are likely not to notice, unless they try to access a website that’s censored. For example, a user trying to connect to facebook.com could be redirected to vk.com"

"Many observers see the move as part of Russia’s long tradition of trying to control the flow of information between citizens."

"Just this week, Russia's government signed into law two new vaguely worded bills that make it a crime to 'disrespect the state' or spread 'fake news' online. The new plan to reroute Russian traffic is an escalation"

[1] https://www.npr.org/2019/03/18/704600310/russia-criminalizes...

[2] https://www.themoscowtimes.com/2019/03/18/putin-signs-fake-n...
I use a Logitech M720. No complaints.
I prefer traveling over holidays, although I not alone since I'm with my wife. We have often seen places in their much more natural state. Plus, there is a whole host of other things to do since it's typically winter. Ice skating in Budapest and then going to a steam bath was a great experience.

http://budapestchristmas.com/budapest-outdoor-ice-rink-in-th...
I don't have Facebook and don't want to be tracked anymore. It's just paying with extra steps.
Is this relevant to the discussion? Does it change anything of what I wrote and referenced? Why do you keep bringing it up?
So apparently a lot of people seem to equate debuggers with single-stepping through code.

You can pry my debugger from my cold-dead hands, but I don't even know how to step through code in my favorite debugger[1].

In my opinion, the only right way to fix a bug is to build a mental model of the code, and a debugger is a massive force multiplier in doing so. For any code that wasn't written by me in the past 6 months or so, the code itself is a mystery and while reading the code is a big aid in understanding how it works, it can also mislead you. In particular there is a class of bugs that are when how the code actually works diverges from how the author thinks the code works. A good author will structure the code to guide a reader into how the code works, but when the author was mistaken, this can be very misleading (in particular I will actively avoid reading comments when I know there is a bug in the code, because comments are the one part of code that are never tested).

Another way of putting it: The source code is very good for telling you how the program is intended to operate, and a debugger is very good for telling you how the program actually operates.

1: I'm sure it's listed how somewhere here, but I've never felt the need for it: https://common-lisp.net/project/slime/doc/html/Debugger.html
well there's this 40k thing
As someone who has never participated in that market, I've no idea how logos are valued. If, in my ignorance, I would look for the cheapest option in a legit looking place, I wouldn't expect to end up with a result that I couldn't use without breaking law.
It's not exactly challenging to have prints only show up in debug builds.