skysight-inc/HackerNews huggingface dataset:
There's a difference between working hard with balance and working hard to the point of excluding everything else in life.

> when you spend all your free time working/studying, and constantly turn down invitations to go do stuff with friends, people stop inviting you to things.

If we consider a strict 40-hour maximum workweek on one end of the spectrum and what your friend is describing (100-120 hour workweek that leaves zero time for anything else), there's still a huge middle ground.

We don't have to choose between working so hard that our entire lives fall apart or not ever doing hard work at all. Many of us do work longer weeks when necessary, balanced with a healthy dose of social activity and things we enjoy. If someone is working so much that they lose all of their friends and even their social skills, something else is going on. Burning yourself out and withdrawing from society isn't what people mean when they say "hard work".

Like the author said, balance is important. Your friend's struggle wasn't necessarily with hard work, but with a complete lack of balance.
I'm confused: Did you use a revision control system at all? It kinda sounds like your describing the difference between RCS and no RCS.
> claiming that there is absolutely no future in electric vehicles for disabled people

Where does the article say that? Maybe I missed it. The article quotes one engineer saying,

“It’s not insurmountable, but companies have to start working with us now,” Frayne said.
Skill Visualization D3.js
Author here -- I agree that const is better. The perf difference I encountered was due to the static keyword though, which is why the blog post talks about that specific issue.
The argument is whether copyright should exist at all, not if it should be shortened. They are very, very different discussions.
What interesting software could be emulated from when CPUs had clock rates in the 1-3 kHz range, the reasonable performance target for this advanced technology? According to Wikipedia, the ENIAC operated at about 5 kHz.
not true at all. this varies by state.

aside from the homeless, what about all the people making minimum wage who neither qualify for medicaid, nor work enough to get employer supplied insurance?

sometimes the head in the sand attitude here is fucking sickening
I think it's possible to join the compilers field with no previous experience if you can find the right team willing to mentor. Best would be for you to have adjacent skills that are valuable to the team; things like domain expertise, low level programming skill, or hardware knowledge.

Everyone starts somewhere. It's not the easiest thing, but I think can be done.
Same data in Cytoscape:

https://www.thescottkrause.com/emerging_tech/cytoscape_datav...
Not to take away from the MO strong towns publishes on their front page. And the topic at hand. One has to remember that strong towns origins are from a yarning to building human scale towns and not machine scale ones. I think any conversation about investments in our cities should be framed in that context as it paints a personal investment lens through which this overall topic of the success of our cities can be hashed about. Irrespective of whether you believe infra costs are 10% or 100% or other minutia details.

We simply aren’t building cities in America for humans. We’re building space for seclusion bunkers and advertisement and shopping Meccas.
I wasn’t bad with programming BASIC, but the true epiphany came when I went on vacation to Spain (very common for UK kids). I took the programmers reference manual which not only had info about BASIC, which I already understood, but it included info on all the 6502 opcodes and all the c64 registers. It really took me a long time to understand what this was. It would have been much easier to have a mentor to help me through this… it was a reference, not a tutorial.

But at some point, it clicked, and I started writing out the assembly… there was a register to control the screen background color… so I just blasted 0 into that register to make it black. In what was probably my greatest ever fear of engineering, I then hand-assembled my two-line assembly into 5 bytes of machine code. But I had to wait until I got back from vacation to try it.

It worked… it changed the background color, but it crashed the machine… I had forgotten to add ‘return from subroutine’, after that it worked, and that was the beginning of my journey.

I regret not spending more on proper tooling early on. But all the good assemblers were cross-assemblers that ran on pc’s.

There’s was also a really good book by Raeto Collin West that went into more details, and that’s where I got some of the drive register info. There is a command you can send to the printer to dump its memory, so that’s what I did. (To get it’s ROM to see what it’s drivers are doing)

The printer was critical to being able to read through the assembly and annotate it. You learn how to read ASCII in your head, etc.
So all you have to do is accurately calculate/estimate TDEE and calorie inputs?

Sounds hard.
Thanks... The code I was trying was:

10 i = 0
20 print "i =", i
30 i = i + 1
40 if i < 20 then 20

I note that if I use i% to force it to be an integer, then it works. Quite a few BASIC implementation defaulted to floating point back in the '80s if the type wasn't explicitly specified.

This has brought back some memories. =-) AmigaBASIC was rather nice as it had primitives for dealing with the creation of windows and dealing with mouse input events. That and QuickBASIC kept me occupied for many, many hours as a kid.
Most companies seem to be shy about pay and some of those who aren't pay quite inadequately to their profits it seems...

What's the incentive for anyone to work there?
Dude, I don't care about your problems with minorities, you don't have to bring it up in every conversation. It's like you're fixated on it.

> To say that kindness does not factor into NTSB investigations does not mean that the alternative is insensitivity and rudeness.

That's exactly what it means. If you're not being kind, then you're being unkind. Lack of kindness is a property of unkindness, just like insensitivity and rudeness.

"unkind, adj. 1) Lacking kindness; inconsiderate or unsympathetic. 2) Harsh; severe. 3) Not natural; unnatural. 4) Not sympathetic; lacking in or not springing from or exhibiting kindness, benevolence, or affection; not kind; harsh; cruel. 5) Having no race or kindred; childless. 6) Not kind; contrary to nature, or the law of kind or kindred; unnatural. 7) Wanting in kindness, sympathy, benevolence, gratitude, or the like; cruel; harsh; unjust; ungrateful."

Without the properties of kindness, an NTSB investigation would not be able to gather as much evidence. Every hostage negotiator and interrogator knows that you can get a lot more practical information by being kind and trying to be someone's friend, even if they have reason to doubt your motives. Being kind is a great strategy.

But it's not just a strategy to fool someone. It's as practical as it is morally good. It fosters better collaboration and communication, it speeds up resolution of conflicts, it removes barriers. Kindness is an indespensible tool to facilitate work between humans. The fact that it's also the morally correct thing to do is a side benefit.
That is definitely a point that is made by modern ethics and is widely supported, but it’s not necessarily one that should be taken for granted. Q in Star Trek TNG treated us like this, and it’s a serious topic of debate whether we ended up better as a race as a result of his influences.

I think that’s the crux of the debate for me: Are we treating rats as well as our learnings about them are capable of supporting? Would I trust aliens to treat me with better dignity than we’ve historically treated our own ‘lesser’ species, if it’ll cure cancer?

Do we honor their social and thermal preferences? Do we design minimal experimentation and experiment judiciously? Do we monitor their pain levels using whatever means available and terminate experiments, and rats, early and painlessly — rather than force them to endure suffering for the sake of completionism?

We absolutely should want alien experimenters to treat us like rats in experiments, because we should be treating rats with the maximum respect and dignity possible to us. We certainly can’t stop motivated aliens, but we can show them by example that we treat lesser species with dignity, and maybe they’ll do the same to us.

Are we treating rats with the most dignity and respect possible? If not, then we deserve no better from aliens.

This is why it’s important to me to consider the ethics of treatment of rats. Not to end all animal testing, but to ensure that we, with our big smart brains, are able to find it in ourselves to treat well those beings we view as lesser. It sounds ridiculous to discuss it in terms of aliens, but that’s what we are to rats, and that viewpoint makes it a lot less ridiculous to consider.

ps. I would absolutely turn myself over to alien science if the need was great enough, especially if my quality of life was heading downhill, but only if I knew it would benefit the rest of you.
Show HN: List with my favourite bootstrapping tools
Or tension adjuster/release dials--I hope these don't go out of fashion.
I used to use mocks an awful lot more than I do nowadays. I learned to do that style of testing from the book Growing Object Oriented Software, Guided by Tests (the "GOOS" book, which is still well worth a read, even if you don't subscribe to that style of test driven development). I'm still of the view that mocks are extremely useful if a) you're working in a highly object oriented style (where systems are composed of objects that communicate with their collaborators by method call) and b) you're unit testing relatively small units of code at a time. Mocks are very useful if it's important to you that object X must call object Y, do a computation and then call object Z with the result.

There are two key insights that helped me to eliminate the need for so many mocks: a) modern languages that support functional programming allow you to separate the concerns of computation and interaction with collaborators, and it's an awful lot easier to test drive a pure function that it is to test drive a graph of collaborating objects; b) modern hardware is sufficiently fast that it's much more feasible to spin up a whole service (or many services) in order to run tests on them, and you don't need to write fine grained unit tests merely in order to make the tests run quickly enough.
A few years ago, my city provided all residents with low flow showerheads - for “free”. They were even delivered directly to homes.

They included literature around reducing consumption and the importance of that for sustainability.

Enough residents installed these that it led to a city budget deficit, since water consumption went way down, and they therefore generated less revenue.

Their answer to this? Raise water prices.
What annoys me most is that the “infection clause” so often results in a strictly worse user experience. Take Audacity, it’s a fully open source piece of software, but to do lots of common operations in it you need to figure out how to link in FFmpeg. This is something your or I can do no problem in our sleep, but it’s an absolute dealbreaker for someone like my dad, and probable millions of other people trying to get into audio projects using free software. I imagine a large number will simply bounce out and stick to GarageBand or whatever.

I’m conflicted on this, on one hand I think FFmpeg is a brilliant piece of engineering and I want the creators to receive credit, but on the other I think Audacity and its built in components as listed in its “third party licenses” document are brilliant pieces of software that do receive credit. Further, I believe the one of the primary purposes of technology should be to enable the masses to create, and this licensing places an arbitrary yet powerful restriction on that for folks who aren’t already computer-proficient.
Great write up: a precise problem that digs into the internals pointedly to teach a simple concept. This is exactly how I tell the junior devs where I work to do lunch talks that give people some concrete, memorable piece of learning that makes them better in their practical work.
The Verge’s tagline should be “Your Daily Anti-Tesla Stories”

All their stories are opinion pieces, missing out critical facts to suit their narrative.
>I haven't thought about whether an actual blockchain is really the best solution...

Most likely not. But the tech behind FBA (Federated Byzantine Agreement) distributed ledgers would make an extremely reliable system that can handle malfunction of hardware and large outages of nodes. And since this is a write-only log and only some entities can write to it, it could be implemented with permission so that the system doesn't have to deal with attacks that public blockchain would face.
How active is the armed resistance in Srinagar today?
The opposite position also exists. Essentials are expensive because people work a lot. By "a lot" I not only include the hours worked but also the productivity gained through external factors like agglomeration in large cities. You can earn more and spend more. The difference in spending power between jobs is driving gentrification.
Author here -- just to be clear, I agree that marking the variable as const is the "right" thing to do here. I reported the investigation as-is because removing a static declaration made the code slower, which I then narrowed down to the isolated bit of code.
Yeah, I posted a blog post [1] that explains my motivation in curating this list. Seeing the broad range of companies that do this kind of work was really helpful early in my career.

[1]: https://www.mgaudet.ca/technical/2019/12/10/compiler-jobs
Yes, all-you-can-eat restaurants which serve meat should be banned before vivisection.
Wow, didn’t think you’d check back! Good to know the effort wasn’t wasted.
>However, Copilot generates verbatim code, and it generates novel code. That is, it both contains the plain text of the original (recitation and redistribution), generates derived code (transformation).

So are you saying that because the language model was trained on a GPL code that even though it spits out novel code, that code is derived?

That seems like a pretty expansive view. I’ve read some GPL code in my life, and I’m sure it has influenced me. Does that make all my code “derived”? I wouldn’t say that. To truly be derived it needs to be a nontrivial amount, otherwise every time you type “i++;” you’re in violation. This is hard to prove.

A clearer cut case is including code it suggested when that’s verbatim. That would be a GPL violation if it’s included in someone’s codebase, but that’s not what it seems you’re arguing. You seem to be arguing that Copilot is in violation simply for suggesting the code.

This means you’re asserting that somehow storing the code in a language model is somehow different from a database, but you haven’t told me why that is.

Databases have a query execution system and a database file. They are separate pieces. The query executor can work on any database file, and swapping out the database file will give different results, even though the execution code is the same.

This is exactly the same case for language generators. You have a language model, and a piece of code that makes predictions based on the given text and the language model. Swap out the language model, you get different results.

The storage formats are different but doesn’t matter. The data and the code are separate. Given this information, why — and be specific — is a language model not like a database?
It's about 10 mins and reading those large high contrast nutrition labels on your food.

If you actually do find that too hard, pay someone for pre-portioned meals or go to a nutrionist.
Tic-Tac-Toe with a Twist
> NOTHING: A powerfully affecting book whose premise is that nothing is happening. The author is highly original and the writing has a dreamlike quality.

This sounds like artifact description from Dwarf Fortress. Now I want them to include GPT-3 to make these descriptions :)
Just a note that 32-bit support was also ditched in popular Linux distributions (Ubuntu, Fedora, Red Hat) in the same year as MacOS.
Async Data Options in Vue's Nuxt.js (2018)
Exactly why I dislike some forms of sarcasm directed at an unknown audience.
I’d believe they were right if the free speech extremists actually showed up to defend groups they hate when their voices are attacked. What I observe is a desire to provide just enough rights to defend established groups but not enough to defend agitators seeking transformative change around topics like racial justice.
All the things you need to know about the GitHub Copilot
Don’t you dare point out their hypocrisy!!! It damages the narrative and impinges on their inalienable right to be sanctimonious and holier than tho! /S
No, 99% of the times you just need to do a computation twice on different hosts. You don't need quorum or other form of distributed consensus.
It was joke. Your position looks rather like the true Scottmans fallacy to me.
If you distinguish the ‘response’ from the result, then I agree. Typically I think of the result as denoting the effect, and not the response message.
Yes I have seen idempotency keys generated on the client that were comprised of the date and amount of money used to make a payment. Don’t do this. Just use a randomly generated request ID when the request hits the API. The idempotency key is (usually) there to prevent things like an RPC or event (in the backend) being retried causing duplicate side effects. Presumably you still want users to be able to intentionally submit two payments for the same amount on the same date (csrf tokens are more appropriate to prevent accidental duplicate submission)
You mean the one from 1985 about those oldtimers bathing with lifegiving alien artifacts? Such memories! Also ofc I found it in one google search.
Reading the boxes will establish my TDEE? How does that work?

Also, just keeping track of calories is a lot of work. I've done it before, it isn't hard in a mechanical sense, it's hard in the sense that you have to do it all the time, for everything you eat, for quite a while, before you really have a reasonable picture.
I love it, it's very good. It touches a lot of things I went through when writing this book: https://venam.nixers.net/blog/internet_communication_narrati...

I think people agree on a lot of the dynamics in this space and what needs to be done.
>no you haven't
This is a fantastic article, but one nitpick:

> The reason for this is that most fonts have been designed for gamma-incorrect font rasterizers, hence if you use linear space (correctly), then the fonts will look thinner than they should.

That's not true at all -- fonts are mostly designed for high-resolution printing where gamma is essentially irrelevant.

Fonts in small sizes can look overly thin on computer screens when rendered "correctly" as black-on-white because 1) bright white surrounding a black letter can "bleed" into it in our vision, 2) we've become accustomed to comparatively bold fonts in computer interfaces and so fonts designed for print look thin by comparison, and 3) when stems are less than a pixel wide and therefore render as gray, this also introduces contrast problems (less of a problem on retina screens).

None of these have anything to do with gamma. However, changing the gamma used in rendering actually does work as a "hack" to make letterforms darker with more contrast -- but it's actually entirely incorrect.

Also with regarding small fonts, font designers have long known that the smaller a font is, the thicker its strokes should be proportionally, so some fonts come in optical sizes. "Text" or "book" weights are "normal", while "display" designed for larger sizes is thinner, and the occasional "small text" size is even thicker (often intended for classified listings, historically).

If you look at typefaces actually designed primarily for computer screens rather than print, like Georgia and Verdana, you'll see they are indeed thicker, much like "small text" fonts.
Well, I'm making that comparison because Audacity is - historically - an open-source app created by volunteers (originally created by a CMU professor and grad student). That's why I think it's a culture thing. (Emacs is a GUI app too, so the line isn't quite "GUI apps." Or maybe consider Signal vs. Facebook Messenger.) Is it part of the culture of open-source programs like Emacs and ffmpeg, or is it part of the culture of closed-source programs like Photoshop and Facebook?

I do actually think Firefox is a very interesting comparison here, because despite coming from the open-source culture, they collect extensive telemetry and they do work in a model where they can't expect user participation. But they in fact have no clause about data necessary for law enforcement.

(I'm also not defending Firefox as perfect, and a complication of Firefox is that it's designed to be used with an internet connection anyway. Audacity is an app that makes perfect sense to use offline. So was Photoshop, for that matter.)

In any case, the clause itself is not the interesting part; the interesting part is the implication that they have enough data to be interesting to law enforcement. Adobe and Facebook certainly do; whether or not it's used, it's there, and there are so many other reasons to be concerned about the data existing (rogue employees, hacks/leaks, etc.). The developers of Emacs clearly don't. I would guess the developers of Firefox try to avoid it, which is why Firefox doesn't need such a clause.
Docker has made most mocking nonsensical considering how easy it is now to use the real thing... But I would disagree with the premise of mocking as being non-starter. Often times you want to unit test and don't really care if you're using the real "thing" but want to hit code that's got zero to do with that dependency. Good example, we use Okta to authenticate... We want to run unit tests that test how a component in our UI works within our application, we mock Okta to get around our authentication for testing that very thing. When we want to test authentication with Okta, that's what we do.
Thank you for the excellent breakdown. Is insurance really that expensive in the US? Mine is something like $200/year.
This is honestly where I think good git GUI tools help, and for those I go to Git Extensions, or did until I had to use a Mac for work.

I learned enough using it that I can work through most issues in a regular and natural way nowadays.
There are people today that understand the problems with judging the past based upon the standards of the present.

Even if we allow the hypothetical that NPR is beyond critique today, I wonder what criticisms people 250 years in the future will level against NPR.

Yes, the authors of the declaration of independence were flawed. 250 years later, humans are still flawed. The point being that we are living in a culture that allows self-introspection. Thus we can learn from our mistakes and move forward.

However, the regressive, navel gazing, self-pitying, often vain, if not condescending, but always divisive and accusatory sense of historical guilt doesn't advance our cause. Instead of tearing down our fore-bearers we should celebrate the framework that set the stage for those advances.
Exactly. One of the biggest things I keep in mind these days is that most people, myself included, are bad at knowing what's most important to get done. It may seems that more code is more work is good, but the banter with colleagues improves communication and cohesion which can have a much higher impact than writing that additional code. If a higher up tells you to do something, you can be pretty sure it's important (at least to your report chain), otherwise it can be tough to identify relative importance of work activities.