skysight-inc/HackerNews huggingface dataset:
This gives me ideas.

My commits are usually short and sweet - to the point.
I document my code very well, however.

One of my strengths in a previous life as a Master Automobile Technician was the ability to document the entire process -- from duplication of a concern, to troubleshooting, to correction, to verification...it's literally how I got paid (which I never understood why so many automotive techs took short cuts while documenting, especially for warranty concerns where you deserve to be paid (by the manufacturer) for everything you did that was necessary to fix the concern the first time).

I could be mistaken (life-long coder, former network engineer / architect for nearly a decade, but I'm currently in my first-ever role as an actual backend developer). I think I was told to keep commits to one line unless absolutely necessary. I'll have to bring this up though. I like the idea of searching through the git logs for specifics, as opposed to having outlook search through the git commits for actual pieces of code changed, or error codes which might not actually be there.

In either event, at least more descriptive, yet still short, messages such as what strictfp suggested "Replace invalid ASCII char. Fixes rake error 'invalid byte sequence in US-ASCII" Although I really like having some reasoning and logic - or how/why in those easily-searchable logs as well.

I think some people remember everything and some people don't (although we're all probably roughly similar logically). I have a hard time remembering what I ate for lunch yesterday - that's why I count on good documentation to function as efficiently as possible in the future. I've worked with people who have an absolute uncanny ability to remember 'stuff'. That's impressive, but I do not have that ability myself.
Looking forward to seeing this as a requirement in projects that already require npm, phyton, cmake, gradle and ninja to compile :(
It only works with Python 3. Thanks for reminding me that I should add a note to the Readme.
Three Number Systems
How often are non-breaking spaces purposely inserted vs accidentally? And the tools might handle them fine but will produce strange results or errors. An example is inserting a non-breaking space in a document or string. It will prevent word wrap, which might not have been the user intent. A linter that requires these spaces to be explicitly set in encoded form would avoid these issues.
Is this the same for pigs and possible related to African swine flu difficulties?
I also agree that Premium Economy is the "minimum tolerable" - it's still not exactly pleasant for long haul, but at least you have enough space to be relatively comfortable. Sleeping is still pretty difficult though.

I have the same Premium Economy rule nowadays, but I now have the luxury of being able to do that; earlier in my career, I didn't.
Since it’s their money, it seems pretty reasonable that the should be able to invest in whoever they want, for whatever reason.
I think this article offers some very good advice about the need for different types of documentation to support software. I am far more likely to try a new piece of software if it comes with clearly signposted online documentation covering how to install/use the 'ware, and why to use it, in addition to a well presented technical reference.

In my view, getting the documentation balance right is critical - having too much documentation (I'm staring at Google and AWS here) can be almost as bad as having too little of it. Making the documentation easy to navigate is as important, for me, as making sure the information supplied is accurate and up to date.

My personal experience - principally from attempting to document my Javascript library[1-6] - is that generating the documentation is just the start of the process. Keeping that documentation accurate and up-to-date as I developed the library across minor and major versions soon became a massive burden which eventually led me to put further development on hold; the latest work I have done on the library remains in a branch on GitHub while I think of better ways of developing and presenting the necessary documentation around it.

[1-6] - My different attempts to document my Javascript library, as a demonstration of how messy the whole process can get:

[1] - http://scrawl.rikweb.org.uk/ - the Tour page, with "marketing copy" which attempts to sell the library to potential users.

[2] - http://scrawl.rikweb.org.uk/tutorial.html#HTML5_page - the "Simple Docs" page is an excellent example of confused documentation as it tries to combine tutorial, how-to and explanation in the same document.

[3] - http://scrawl.rikweb.org.uk/demos.html - I added the "Demos" page to support the "Simple Docs" page; in fact the demos were (are) the visual testing regime I developed for the code base.

[4] - http://scrawl.rikweb.org.uk/docs/ - the "Technical" documentation - generated from inline comments in the source code. I chose the wrong tool to do this, as it expects the code base to be object-oriented; the library's Javascript (v6) is procedural/prototypal, and decidedly not modular.

[5] - http://rikweb.org.uk/wp/ - at one point I decided that a good way to supply "how-to" information was through blog posts. This was one of my less clever decisions and quickly abandoned.

[6] - http://scrawl.rikweb.org.uk/learn.html#lesson001 - my best attempt at supplying potential users with tutorial documentation. Embedded Codepens make the experience a bit more interactive, but the results are probably too primary school given that my target audience for the library was more experienced front-end developers.
My pet peeve is auto-generated documentation from configuration files or source code. It is absolutely useless and I would rather prefer no documentation than auto-generated.

Some time ago Swagger (nowadays OpenAPI) got really popular and many projects "had an API" and pointed users to their green autogenerated API documentation clusterfuck. When time went on this green page would become an indicator for me, that the project does not work and I should be very sceptical - I am sure there are projects that do it better, but for me no-content auto-generated documentation is a real code smell.
How San Francisco Is Killing Its Restaurants
> A vibrating star is a star that is literally moving back and forth relative to an observer

What physical process would cause this? Have we ever observed it?

Large bodies of matter don't just "move back and forth" of their own accord. Try shaking any heavy object, it takes a lot of energy.

Do you mean ringing like a gong or a pond with ripples? Then "moving back and forth" is a confusing poor choice of words. Do you mean "orbiting a black hole in such a way that it comes nearer to us and then further again?" Then why not say so?

How would the mode be out of synch with our own, whatever that even means?

> The jargon of science is one of her bugbears and she is trying to demystify it.

By introducing new and incomprehensible jargon that is literally mystical?

> oscillating in a mode which is out of phase with the motion of the detector

Are you saying that undetectable EM radiation exists because of modes / phases? This is complete hand-wavy mysticism.
Unlikely, in my opinion. More likely the government can come along with national security letters or other means we might not even be aware of and just take what they need.

On the other hand some companies have been shown to be very willing to sell data to any buyer, not just the government. Phone carriers come to mind.
I’m not sure it is very common that the next round investors buy shares from the first round, seems to defeat the purpose of raising money. IPOs are a different story though, cf We, Uber.
European countries don't do any of the things described in GP yet most of us drink cheap milk everyday so something must be off in your analysis
PyPy v7.2 Released
The point was that drinking milk is something humans have only very recently in our evolutionary history have adapted to doing, so we are still adapting and a lot of us can't do it very well at all.

At least, a lot of us do it a lot worst than we realize, and there are a ton of people with recurring mild digestive issues which should not be consuming dairy daily at all, but keep doing do due to the public perception that its a healthy thing to do when in fact it's not.
I know literally nothing about Bach except he had a lot of children (I think?), and yet I think his music is easy to appreciate.
I think it was also weaker than modern beer.
At a guess, https://github.com/danielmiessler/SecLists/pull/155 ?
Why ‘compensation’ not ‘payment’ involve in surrogacy?
Announcement link from that thread: https://lists.tildeverse.org/hyperkitty/list/tildeclub@lists...
Excessive brain activity linked to a shorter life
"Documentation needs to include and be structured around its four different functions: tutorials, how-to guides, explanation and technical reference."

I'm a sysadmin and most of the documentation I write is... well it's for me! I do something once and I know I'll do it again, I copy and paste everything I did into our "docs" area so I can just copy and paste it again. I guess that falls under tech reference. My theory for these docs is if I'm not around, someone else should just be able to copy and paste things and not need to learn my job. Doesn't apply to EVERYTHING, but it helps for all the little things.
Punched cards are for me one of the most reliable mediums ever, in terms of proven to last without media decline (though keep away from snails).

So be thankful they didn't reinvent those, only using plastic instead of paper based card. Though plastic punched cards would last a very long time and also be imune to EMP, water...many things that other forms of media fall foul of.

Just don't get the storage capaicty there and if they are using systems that fit data on a floppy. Well, a CD based media would perhaps be overkill.

As for CD quality, that can vary a lot with some lasting since day one, others - rusting away (literally I have old CD's from the early days, some fine, others have rust holes due to impurities in manufacture).

But like most things, you don't appreciate the quality of the product until time has past and it still just works.
If "hyper-rational atheism" were the "Times New Roman of metaphysics", you'd think it would be far more common than it actually is.

Going with your n=1 "I meet people like this all the time." theme, I know far more people of various religious flavors than I do atheists of any kind, "hyper-rational" or not.
This is a nice article (though i think a bit too wordy). Note that what it calls "tutorial", "how-to guides" and "explanation" is sometimes called "guides", "howtos" and "rationale".

As an application of this, I always thought that the Windows API help, especially those around Win3.1/95 had one of the better approaches for an API/library: the API is split in functional parts/groups (windows, fonts, messages, fonts, controls, etc) and for each group there is an "overview" section (e.g. Windows introduces the windows concept), then a reference (often split in several parts itself) and finally one or two examples (though that was optional).

The help itself didn't have "howtos" or "rationales" but those were available through MSDN (later at least) as knowledge base articles.

(modern winapi documentation is a mess on that regard, especially if you do not already have a vague knowledge of what you are looking for, because even though it is largely the same text, they have split and moved things around too much and put irrelevant distracting links everywhere)

On the Unix world, the original X11 documentation follows a similar pattern, though for other more recent projects there is usually a very one-sided approach: as the article says, most projects only provide API references and perhaps a single (often unfinished) tutorial.

GNU projects usually have documentation in texinfo which is laid out as a book and is often very good (most disagreements come from the default GNU info viewer, not the source documentation system that allows for HTML and PDF output nor really the info format itself that has more usable viewers like tkinfo). It also has a similar approach as the Win3.1/95 docs, though i think the lines between "guide" and "reference" are often blurred. This largely depends on the project though (e.g. the glibc manual has these better divided, whereas the bash manual tends to be more "blurry"). Also i'm not fan of GNU's style of function references - i prefer the more common/manpage-like style where for each function/macro/struct/etc you have an isolated page a very brief description about its purpose, its declaration, a list of what each parameter (for functions and macros) does, its return value (if any), a detailed description (if necessary), any requirements (e.g. headers, for APIs with multiple headers) and links to other relevant functions and guides.

Also i find examples for each function to be nice though this is even more rare than guides.

As a sidenote, i loathe autogenerated documentation and "docgen comments" in source code (and not only because they tend to enforce the "reference-only" approach). I think those should be totally separate and not pollute the code with documentation (especially headers as that makes it harder to read the headers that also act as a quick overview for an API).

Though having a tool to automatically check docs and sources for mismatches (missing functions and/or functions with wrong declarations in the docs) is helpful. But i'm not aware of anything that does that.
5 and 9 and 14 Eyes are all apparently focused on signals intelligence:

- https://protonvpn.com/blog/5-eyes-global-surveillance/

- https://www.reuters.com/article/us-china-fiveeyes/exclusive-...

Which I think means watching data move across the lines.

If you'd like to pull your tinfoil hat even tighter: Germany, Netherlands, Iceland are listed above as broader members of signals intelligence sharing partnerships, as well as members of NATO. They have a discussion here of their policies and activities related to Cyber Defense:

- https://www.nato.int/cps/en/natohq/topics_78170.htm

If a government wants to take your hard drives it will. Unless there's explicit laws against the seizure of physical media, you're mostly relying on them either not having a sophisticated enough internal intelligence capacity that can do it quietly, or trusting in social reaction to a mostly boring, questionable infringement of property rights.
The first three are more or less the same thing, and could easily be handled by a native app if there’s internet.

The last one seems completely unrelated to the choice between browser and desktop. If anything it is harder to make nice UI in the browser.
I really, really wouldn't. That's Andrew Gelman's gig, and he's been doing that since the 80's, when ML/AI was all about expert systems. I think of that as a statistical technique, not an ML one (and for some weird reason, many quantitative people in insurance don't like Bayesian techniques).

But then, our disagreement here just highlights the difficulties involved in getting consensus on what ml vs statistics actually are.
True story— the launch codes were 00000 for decades.
Java Hello World takes 0.132s on my Macbook pro. If I turn on -Xshare:on to use class data sharing, then it drops to 0.119s. Ergo, Java startup time is non-factor. Graal could make this even quicker, for example, a GraalVM AOT helloworld can be reduced to .008s startup, see https://github.com/graalvm/graalvm-demos/tree/master/java-ko... for example.

"time bazel" returns 0.098s

Running a null build took 0.84s, but Bazel does significantly more work, as it's working on a big monorepo, as both a build tool and a package manager.

In short, it is not a problem. But I've had npm take many many seconds for simple operations. "npm list" takes 2.9 seconds.

Python can be slow, depending on the tool. Waf sounds like it is simple and fast, but there are lots of other examples of slow python frameworks out there.
That belies the effort that went into the fix
Would they pay for a subscription in order to do video editing in the browser though?
> One thing implies the other, as it's impossible to produce enough dairy for so many people using the methods you mention, that is why most dairy people consume comes from factory farms in the first place.

This is simply not true. What you probably mean is it is not possible to achieve the same results while not caring how it is done (ie. going about our lives).

Throughout the history people relied on dairy way more than today. In some places it was almost life or death as during winter grain and dairy was the only feed available.

Of course, today, you don't want to spend your entire day tending cows and the field.

But don't try to imply that our way of life is the only one possible.

There exists whole industry of keeping cows and producing diary in humane way. It costs more, true, but not nearly as much as to make it impractical.

It is simply our choice -- people choose the cheapest product the cows be damned.
Just set the password to 00000000 for now and we can change it later....

https://en.wikipedia.org/wiki/Permissive_Action_Link#Develop...
I work with a very large, complicated piece of software which has quite a comprehensive API but it's basically CRUD on top of a database. There is zero documentation about what happens when you update an object - only OpenAPI. To find that out, you would have to dig in to the database triggers. Half of working with it is trial-and-error and the other half is hope-and-pray.
Mounting a VDI File in a Different VirtualBox Guest
“When I started working professionally in IT this division [the schism between 'systems' programmers and 'applications' programmers] was still quite visible.”

I think you nailed a rather fundamental trait (spectrum) in programmers that carries on, morphing along with times.

From systems to business logic, or from the 'container' (pun not intended) to the 'content', and dare I generalize: from a strictly technical eye to a strictly goal/business mindset (again, this is a spectrum, everything in-between exists, all flavors contribute to make a world).

The cliche would be your low-level C/Rust guy versus some frontend Flash/Js person; but this is oversimplifyling (C person might be very goal-driven with a business approach; Js person might be a performance expert). Reality speaks more of an engineer's world view so to speak: from "bottom -> up" (those that assemble elementary pieces, that need to crack the puzzle by understanding each component, like Lego) to "top -> down" (those that rather manipulate large abstract/complex entities as 'black boxes' and rather work on their structure, the graph, dimensions, and shift behavior thusly with surgical cost-effective changes).

Oh just my 2cts I'm probably rambling. I just know that these two extremes on the spectrum are what we battle with for every decision we make, if we are aware enough of both sides. (Is that a blessing or a curse?.. you tell me!)

I think it's why, deep down, we still (and might always) search for 'the next C' (cue Rust, Go, D, depends on use-cases I suppose), or why some people are almost principled advocates of the WebAssembly paradigm in complement or replacement of the Js ecosystem. These are the technical people of the spectrum. The high-level engineers are more about pushing for interoperability, available skill pool, maintainability.

It's just that 'programming' as a skill now pertains to three dozen very different jobs so the general line is much fuzzier than in the 1950-60-70's; but I think it's a product of human intelligence, whether how we think or how we build our tools, our machines. Historical parallels, yadi yada.

The mainframe situation, I think, is even more telling. Every programmer under the Sun has thought of ways to replace COBOL, and there are decent candidates. But the business side of us, of above, of reality, has mainframes still running on COBOL. Because as a 'black box', it works; the benefits of a rewrite have not yet justified their cost.

I know a solid team usually requires at least 1 of each 'sides' of the spectrum, keeps everyone else honest (as engineers in a problem space).
The worst thing about Gitlab and Github is that commit messages are not immediately editable in a PR/MR conversation. You can find conversations like this all over {gitlab,github}-dot-com but you cannot find them in commit messages anymore.

Closes #123456

instead of actual background.

It's bad for your codebase.
“ drink fortified plant-milk”

“ You can get all the nutrients that you need, calcium included from a plant-based diet. The only thing you need to supplement is B12”

Plant based milk is fortified with calcium carbonate. You just told us to take a calcium supplement added to a liquid.

That’s admitting it’s not possible to get enough calcium from plants.

With that logic there’s a lot of food we don’t need.. everyone just needs a multivitamin.
looks like the Archive Team is on it: https://archiveteam.org/index.php?title=Yahoo!_Groups
Still the majority of the world population is lactose intolerant and should not be consuming dairy at all.

The ones that can digest it, do it usually less well than they think they do. Mild chronic diarrhea is prevalent is western countries, and a degree of dairy intolerance could very well be one of the factors.

It gets worse for most people with age, as elderly people can become lactose intolerant, fully or only slightly. This does not happen overnight, its a progressive thing, many people gradually stop being able to properly digest dairy.
When tax payers foot the bill it's easy to spend entire morning on a single line commit.

For many or most guys out there, reality is way different. For one, it's an actual reality, not VC or government funded Utopia.
> Just eat a well-balanced plant-based diet and you will be absolutely fine.

Well that settles it then. Now all we need is to get everyone to do this.
Like $20/flight guilty, which you then promptly offset at Atmosfair or a similar service.

https://www.atmosfair.de/en/
Based on studies (ie: resumes with different names, etc.) the baseline is for hiring decisions to be racially motivated against minorities.
When there is no money in it nobody will be developing the exploits that make it easy. There is a large difference between buying a recent vulnerability and exploiting it vs finding a vulnerability.
The real-time notifications to cell phones in Japan are faster than the actual seismic waves, so if it's a decently sized earthquake a little ways away, it gives you a 5-15 second head start
Because we pay for it. So it should be run without egregious cost overruns, huge administration costs and old technology.
Occidental? If anything this is an issue in the Orient, not the Occident. Japan has excellent schools, plenty of money and a very hard working population, but struggle to create startups because the willing to take risks is so low.
Trump and the Revolt of the ‘Somewheres’
I'm willing to bet that this problem was actually caused by readr, as base typically doesn't do crap like this.

Completely agreed with the rest of your points though.
That’s often the case if your file format evolves without taking a mmap use case into account. But for a format that’s designed with mmapping in mind, it is often ridiculously faster and more effective.

But most languages and environments don’t let you do that easily.
The Real Reasons I Don’t Hire You
I’ve built and launched nearly a dozen sites using Gridsome + Netlify since 0.5.0. It’s a fantastic tool and is a joy to use.
Yes, this is critical stuff!! I've seen a lot of effort put into unguided documentation efforts that put out huge, unapproachable times that helped nobody.
The main thing that was frustrating for me early on, especially when digging around in the iex console, was immutability.