skysight-inc/HackerNews huggingface dataset:
Would it? I could see Amazon arguing that you're reselling the book, not the annotation storage/syncing -- and as a consumer I generally wouldn't have a problem with that argument. The book is the thing I want resale rights on, not Amazon account features.

I'm curious, what does the Kindle do with 3rd-party book annotations right now?

On Kobo, 3rd-party Epubs that are loaded onto the device are treated differently than books bought through your account. They won't be used for recommendations, and as far as I know, nothing syncs anywhere. If your device breaks, you can't re-download your 3rd-party files unless you personally backed them up somewhere.

I don't care, I buy most of my books directly from independent sellers/authors and side-load them. But it is admittedly a pain, and I have on occasion bought from Kobo's store just because I wanted to be reading right now instead of hunting around for a USB cable.
Got it.

To be honest, what I really wanted here is to force the commenter on agreeing
that whatever the architecture/framework/etc., there is no magical solution,
and saying that it will "be compensated-for at a higher level" just hides the
only 2 real possibilities:

- Kill the process and restart it somewhere else (no swap)

- Wait for the process to finish anyway (using swap)

Both choices have their own pros and cons, as discussed in other comments. But
arguments such as "it's better to have predictable process termination", and
"under tight latency requirements then paging can push you over that boundary"
are exposed as much less meaningful once the problem is stated in simple terms.

If the process indeed uses more memory than planned, then you have no guarantee
than restarting it will work this time. Worst case, you can even have to
allocate urgently a new node to handle that 1MB of memory above what was
available. Not sure that is really the best solution "under tight latency
requirements".

My experience would indeed be the reverse: if you are faced with unexpected memory
usage growth, then having some swap on the side to allow your process to finish makes
for a much smoother production system than having to restart it all from scratch
somewhere else/at an other time.

In my experience, production is not the place where you want to enforce ideological
concepts such as "a process shall not use more memory than what was planned".
Production is the place where you make compromises and account for everything that
slipped through these concepts, because you have no choice: it _has_ to run.
Staging would be a good place for this though, as it's much less critical if
something fails, and you have more time to fix and account for it.

I really don't want to debug/profile/release/deploy a program in a hurry just because
somehow it ended up using more memory than planned. (or convince infrastructure to
deploy a new node type ASAP to handle that new memory constraint).

Now one could argue that such unplanned memory consumption should have been caught
earlier in the development process, to which I would reply:

- Not everyone is able to properly test programs in a production like environment,
especially when dealing with resource-hungry processes. In our case for instance
a typical staging machine would be a downscaled version of the production one (less
cores, less memory, less bandwidth).

- I tend to plan _also_ for what should _not_ happen (because it will happen). Even
with a perfect environment to calibrate programs before a release, there will be
releases in which the memory usage was not accounted for. Guaranteed.
If you want to make a product, use what ever tool is most productive for you.

Unless you're writing an IDE, you're not going to lose users (you care about) over not supporting Emacs bindings.

People will put up with a lot of garbage if your product fills a need. And non-native UI is not even inherently garbage, just sub-optimal (and even that depends on the product)
Apologies - we only need to get user account info (to get the twitter username). Will go and remove those permissions now - we had this Twitter integration set up ~3 years ago and didn't review it - No excuses! :) Sorry for scaring you (and other users of course).
> TODO, as the name implies, should be things that must be done.

A lot of people use them for things that "could" be done.
I’m afraid you constructed a strawman to argue against that doesn’t occur in my comment at all.

I’d like to hear more on your thoughts about Google’s IC track and implementation, especially if you’ve worked there. Care to provide a compare and contrast?
I agree. Presenting on Protego doesn't seem like a good idea – the information given in this talk could aid terrorists.
> Linux has no roadmap, no product management team scheduling features, no nothing.

I would bet large money that Linux has a great many of all three of those. They are just handled in a distributed manner by the various teams working on the different features.

Bazaar doesn't mean disorganized. It means there is no central planning authority. There are many individual planning authorities with their own agendas.
Very apt. I think people are also forgetting “the bad old days” where you worked on a large-ish cpp or java app for a year, nothing worked right, schedules slipped, and then the whole thing was scrapped and teams disbanded to work on other stuff. That was very common. You can’t count on having a team of Carmacks work on your blub app.
Here's a link: https://scipy-cookbook.readthedocs.io/items/ParallelProgramm... And a quote in italics below.

And, more importantly for us, while numpy is doing an array operation, python also releases the GIL. Thus if you tell one thread to do:

print "%s %s %s %s and %s" %( ("spam",) *3 + ("eggs",) + ("spam",) )
A = B + C
print A

During the print operations and the % formatting operation, no other thread can execute. But during the A = B + C, another thread can run - and if you've written your code in a numpy style, much of the calculation will be done in a few array operations like A = B + C. Thus you can actually get a speedup from using multiple threads.
Update: Strange idea: What if this is the pattern that atoms, or rather, centres of atomic force (call them by whatever name you will) are laid out inside of elements?

In other words... what if this is the patterning of space that creates elements?
For years my go to option was nvAlt[^0] with a hotkey and some expansions set up with typinator to do all the repetitive stuff. Unfortunately that broke down for me when upgrades to macOS started to make it less reliable and I was transitioning more and more toward entry from mobile. I haven’t been able to come up with a solid workflow to replace that and it’s a pain because it worked so well for a long time.

[0]: https://brettterpstra.com/projects/nvalt/
Physicist Proposes Radical New 'Stellar Engine' That Could Move Our Solar System
Ask HN: Where would you go to hire a Python and Django tutor?
I’m about two years removed from doing a bit of web development work with a tutor. We built an MVP for an idea I had at the time using Python + Django. The switch to Python 3 and the newer versions of Django are different enough that a tutor would help me a lot again.

I’m looking to hire a tutor for 2 hours a week at $30/hour. I’d like to prototype a web application that lets suppliers list themselves, let’s users purchase a membership, then let’s consumers select options for who they can speak with after they subscribe.
Not for the sake of cleanliness - for the sake of storing the information in a useful format.

If you want the bugtracker or documentation to be checked into the same source repository, that seems entirely reasonable to me. I don't know good tools beyond text files for doing this for bugtracking (although I think Fossil does this, kind of, and I'm sad that Simple Defects never took off), though if your work is uncomplicated enough to go into code comments, it's definitely uncomplicated enough to go into a separate todo file, as I mentioned.

It's very straightforward to do this for documentation. Probably the right thing is to use your existing patch-contribution workflow for this, but make it lighter-weight for docs (reduced or nonexistent code review), but you can also hook up your docs to something like Ikiwiki if you prefer: being in a wiki and being in the source control repo aren't at odds with each other.

And for seeing what was in the dev's mind six months ago - use git log and git blame for that. Even TODOs get refactored away, or moved around enough that they no longer make sense. Good commit messages will show you the whole change that was being made, in context, and what the programmer was thinking when making that change.
What's the time period?
> embedded IC is given free reign to spend time helping other teams organically

Then, by definition, they wouldn’t be an “embedded” engineer, no? In fact, what you’ve described is not at odds with what I’ve described.
That was just one example of a case (I just picked it because it's close enough to Hacker News that most people here probably remember it), and notice that Sony got everything they asked for before the case was settled, including some incredibly unfair things (like the list of people who had legally downloaded the legally-created software of Hotz). The reason it was settled out of court was seemingly just so Hotz could avoid a felony.

There are plenty of other Sony cases that demonstrate the rule.
Question at the meta-level: what software/platforms are producing, analyzing, modifying & consuming this data?

Is it possible some legacy systems that produce and consume these massive files on-site would more sensibly run in the cloud, directly & selectively accessing the data chunks they need over fast backbone connections?

Also, is there any room for an rsync type approach, sending compressed deltas rather than naively sending huge files that may be redundant?

Not to say disintermediating a BigCO expensive patented vendor-locked-in MLPOS (Market Leading Piece Of Shit) doesn't sound exciting -- it does. I'm just curious and a bit skeptical that it is always necessary to mass-copy all this data over and over.
I'm curious how much the observed speed of Aspera on the Internet might rely on "nicer" protocols (TCP) backing off as Aspera causes congestion^H^H maximises link utilisation.

Do you think the protocol might cause problems if it were more widely used?
Sorry about that! Didn't realize this would hit the frontpage, infra should be upgraded!
Yes, the comment struck me immediately as off because in typical conversation involving real people, tragedy usually implies the person is blameless.

Now that I think of it though, even in this other use implying a flaw, you are supposed to relate to and sympathize with the flawed character. In this view it seems harsh and inhuman to complain that every calamity might be seen as tragic. A mature person can often sympathize with human suffering even if the sufferer did something "bad" to get there. We shouldn't be 100% in punishment mode or gloating at comeuppance. Forgiveness is a thing. Sympathy for imperfect people is also a thing.
>Because INAL I can't give a definitive answer, but here's how I understand this.
Firstly regarding the example: One can't compare selling (digital) goods and some subscription service. That are two quite different subjects.

You don't need to be a lawyer there is no difference in their view between sub to view and buy to view, or between movies, tv-shows, ebooks and games it's all "audiovisual content".

>Secondly: The EU wants to further extend this "one digital market" thing as soon as possible. The aim is to regulate exactly things like Steam. So the law will be more precise in the future.

Precision doesn't have anything to do with it, there is the issue of copyright law differences between various member states, EU copyright directives, conflicts with primacy issues, bilateral agreements of the EU and individual member state with other jurisdictions and the entire existing industry.

You also need to understand what unjustified geoblocking actually means, if you run an online store in a memberstate you are not obligated to ship to the entirety of the EU, to provide service or support to other member states or in languages other than your own. You however cannot arbitrarily discriminate by for example refusing as a Polish shop to ship to a shipping address in Poland if someone is paying with an Estonian debit card with an Estonian billing address it does not however mean that you have to ship to estonia, have to have to provide support in estonian or have to warranty the product in Estonia if an Estonian buys it in Poland and goes back home.

People tend to really exaggerate the implications of some of these EU directives if that was the case there would be no fucking business in the EU anymore other than Amazon... read the full instructions don't extrapolate from the widest possible interpretation of a headline.
Surely Ben Thompson (Stratechery[0]) must be one of the most profitable single person businesses / publishers around. One person, email distribution, multiple millions in revenue per year.

[0] https://stratechery.com
This is really interesting! I’m really glad you mentioned the telegram connection, looking forward to digging further into it
I very much agree that if you really want to get to the todos they should be tracked in your issue tracker and prioritized with all other work with the team. What's the alternative? Take a random afternoon to do a random Todo item instead of prioritized work?
Related: high school trains expertise in following.
You didn’t contradict anything I wrote.
Buy a supported device from eBay and then install AsteroidOs (AsteroidOs.org)
Multi-Patterning EUV vs. High-NA EUV
Interesting. Any examples of this kind of lower valued work?
The Problem with Letters of Recommendation
+1 for Roam Research, as far as a daily log goes it's wonderful.

> I haven't quite figured out if I'll make it my todo-list/gtd solution yet, for that I'm fairly entrenched in kanban/issue-tracker apps like trello.

I believe both will have to tackled sufficiently before Roam really takes off.

For example, I'd love to be able to:

* Filter for TODO items between $start_date and $end_date

* Filter for TODO items ranked by number of connections (further arbitrary weighting would be really interesting here)

* Filter for TODO items at the intersection of two terms (haven't found an elegant way to do this yet)

> Also wondering how to use it alongside bookmarking tools like pinboard (or if the longer goal is to have better bookmark features).

I'd love to be able to see all the stuff I want to read for #term - this might include books, articles, etc.

Which brings us to content: I really want to read all of this stuff inside of Roam, but there are two approaches right now, neither of which are super comfortable:

1. Copy the whole thing into Roam and process it chunk by chunk. Nice but formatting is a gigantic pain, front-loads a lot of work. Benefit is it saves the content in case it disappears. No easy way to see only the highlights from a certain article as they're all mixed in.

2. Copy metadata and highlights/annotations/quotes into Roam after reading it and creating them elsewhere. More compact but annoying to access original content. Requires yet another tool.
Your work is amazing. Great job! I'm super impressed. I used to do a bunch of 3D stuff but then I switched to web/mobile dev and that was it for 3D. I can see why your software is successful because it solves a very exact pain-point that is very costly and time-consuming.
It looks like it's built in house.
On some devices it may be easier to enter a long password from a restricted character set than to enter a shorter password from a richer set.

For example, I've seen TVs that allow using a numeric keypad on the remote for entering digits in text and password fields, and require use of a clumsy on-screen keyboard for entering letters or punctuation. The on-screen keyboard is navigated with the up/down/left/right/ENTER buttons on the remote, and might have multiple shift states for case and punctuation requiring navigating to and pressing a shift key whenever the password has adjacent characters that need different shift states.

On such a TV, I'd rather enter a 39 character all numeric password than a 22 character alphanumeric password. Entering 39 characters on a hardware numeric keypad is way faster and way less error prone.
I've just kept using my pebble. consistent week long battery life, it gives me notifications and tracks my activity, not much else needed.
It could be a red flag or nothing depending on the development culture around the project and how they assign meaning to these comments.
Type hints and dataclasses are a game-changer for Python. Much easier to reason about programs that use them.
The use of tarot decks for divination dates back only to the 18th century, well after magic stopped being useful (because all the skilled or talented magicians rebranded to "scientists" or "naturalists"), so I'm skeptical of its value as a system of symbols and motifs. (You will find preachers condemning it much earlier, which is often cited wrongly as evidence of its use for divination, but they were condemning card games, not divination.) For me, it's like squeezing blood from a stone, despite the cool illustrations that look like they should form a symbolic system of Rider-Waite (1910!).

If you're serious about your magic, you should probably cast the I Ching for this sort of thing (imo).
For anyone interested, I wrote a piece last week taking a look at the 2k+ TODOs in the Kubernetes source code as well: https://medium.com/@augmentable/looking-at-kubernetes-2k-tod...

Most were from over a year ago.

I don't think TODOs are bad practice, and I've seen a diversity of opinions on them in the comments of various posts. I think they are notoriously forgotten, and major codebases like linux and k8s are no different.

Aggressively stale TODOs though are likely an indicator of an area of code that should probably be revisited or cleaned up.
Creating an app is quite easy. There are many cross platform solutions available like Flutter, React Native and Xamarin and you should be up and running quickly. I personally prefer Xamarin since I am more comfortable with C# and really like its layout engine.

Though I know quite a few backend developers who have built apps and struggled with the following issues.

1. UI/UX - UX and UI are critical for an app and you might have to hire a designer to create those interactions for you. Backend roles usually involve no/little UI/UX work and it's easy to only focus on the functional bit of it.

2. Updates - It's easy to rollback a backend codebase from production or revert it to it's last state when something goes wrong. When deploying an app you have no such option. Android updates take about a week to reach 80% adoption. And if you encounter a critical bug in that time period, you have to halt the rollback. You end up with some users on a new buggy version and some users on an older version. This can be tricky to manage.
I agree. If i contract to have a house built, I understand there can be over runs, but those are treated as a special case. I still know, with fairly good certainty, what the final cost will be up front.
I agree with you on this 100%. You do absolutely need somebody with you in the hospital 24/7, as a lot of things happen that should not. This is unquestionably true in the United States. However, everybody should have a friend or family member with them at the hospital 24/7, anywhere in the world.

While what you said is absolutely true, there are serious breaks in continuity of care that allow for these things to happen too. Not having a true standardized health record (versus something that is effectively a billing machine) that can be accessed anywhere, by healthcare professionals, and without obstacles is extremely disastrous.

This needs to be studied more.

What I am trying to say is that staying in the hospital 24/7 as an advocate may be a necessary and needed remedy, besides being something that should be necessary in general.

But only works as a remedy in the most basic sense.
My money is on in-house.

Express based webapp on Heroku. If it's a plugin, I would start looking in NPM
People that want to control P&L necessarily want accountability. I’m not sure why it’s difficult to imagine someone who’d want that? Every founder of a company, by definition, is seeking and taking accountability.

Your second point is spot on. A natural tension arises as ICs move up the ladder, and if one values being an IC, then one must maintain their boundaries.
That's standard practice for Amazon (the author of the introduction being listed as an author of the book). It's confusing and annoying.
Ask HN: NF; Lost in Space, S2:E1, 15:30 and Reinforcement Learning
What say you?
That’s a LOT of venom directed at Joe Rogan.

I occasionally listen to episodes if the guest appeals to me.

Clearly, the article author views Rogan as a political partisan adversary with the non stop attack.

If I had to guess, Rogan is center-right politically, but with a pretty wide left to right issue-based range.

And I think a lot of Americans in the middle would prefer an adult conversation over individual issues rather than being forced to choose a side.

And I think it’s hit piece content like this that is far more likely to create active resistance to it, rather than passive support for the points raised.

One of the things I credit Rogan with is providing me broader and deeper understanding of Tulsi Gabbard and Jordan Peterson.

I really like Tulsi as a person and a holder of elected office.

I reckon Rogan’s popularity is due to the fact he mirrors the beliefs of many(maybe half?) men 20’s to 50’s who listen to podcasts.

Many average in the middle-ish, but support a broad range issue to issue, who enjoy going down rabbit holes.

It’s like listening to a clone go down an internet rabbit hole for 2 hours.

Perhaps the author is really attacking Rogan for his fast growing social influence and financial success out of anger that the author’s more traditional medium is losing relevance and financial sustainability.
This is how an industry sets itself up for disruption.
TODO see issue X is also a great way to link the two together.

Is the issue still worth fixing? Well the file was completely rewritten 1 year ago, the TODO removed, and no one requesting this now/pushing for it? Close it.

Have an issue but not sure if it's relevant so it stays open forever? I've seen issues outlive the code their for by decades because investigating the lots priority issue wasn't a priority, quick "see: function" references are similar, easily searchable terms which makes old issue review very fast to close.
This also ensures the backlog is reviewed periodically
It gets worse. Vincit is known for putting sexist jokes into their press releases, external communications–even in their financial statements. These have been reported by the press: Their jokes are juvenile. ”Kympin pitäjä” which means “great village” turns into “pimpin kytäjä” or “pussy place”. The Finnish Stock Exchange criticized them for this, but their response was to tell them to “lighten up a little”. On their quarterly results video they again made some appalling puns: ”surkea töihinottaja” became “obscene blowjob” and refers to the only woman on the management team–the head of HR!–as “cunt babbles”. People in Silicon Valley know that a CEO would be fired for that, but weirdly, nothing happened.

Yes, excellent culture. Sounds real pleasant. Pass.