skysight-inc/HackerNews huggingface dataset:
I have been recommending this article to my teammates:

http://chris.beams.io/posts/git-commit/
150k but including R+D (via https://ocean.builders )
I run EatTheBlocks, a screencast for ethereum dapps / solidity smart contract devs.

I started a YT channel 1.5 years ago, and a paid membership website a few month ago.

Its not paying my rent yet, but its making in the a few 100’s USD MRR. Looking to reach 1000 usd MRR at the end of the year. Seems like the growth has been accelerating, so maybe that I will revise up my target.

For me the rule is pretty simple: more content = more paid subs. My big problem is the cost of production: producing video tutorials takes me a massive amount of time, and at the moment is not profitable at all when you take into consideration the time spent.
Also what worries me is that I dont really see a way to scale this up, as hiring other devs to produce content is almost impossible: Need a very rare combination of tech skills, and presentation/ teaching skills.

The only solution I see to this problem is to break down the process of producing content (generate idea, coding, recording...), delegate some parts, and do the integration myself
Do you have a bus factor plan in place?

I. E. If. You are hit by a bus, what happens?
"Another issue I'd take with this is that it's a lot smarter to focus on cashflow...."

Surely it depends on your aims? If its your pension you may not mind adding money in every month, as long as you get that lump sum/ steady income at the end.
Abstract Nonsense
I feel it reduces cognitive load, like proper formatting of code.

Do you enforce consistent code formatting in your codebase (using CI, maybe)? If so, why wouldn’t you do that with commits?
Author suggests using imperative form commit messages ("add X") as opposed to past tense ("added X"). Past tense should be avoided, but using imperative form sounds unnatural and incomplete. I prefer present tense. Just follow this template and you'll be fine:

Q: What does the commit do?
A: The commit <commit>.

Example:

Q: What does the commit do?
A: The commit adds extra padding to the header.

In this example, "adds extra padding to the header" is your commit message.
It's ready to ship.

Because nothing ever ships without issues. When talking about end products, we're often - if not usually - talking straight up known bugs, not mere nitpicks. Hell, I'm willing to OK known bugs in changelists under some circumstances - like being less buggy than what's currently checked in!

Serious bugs can be a good reason to hold off on something. But nitpicks - say, a minor quibble about function naming is a subjective personal preference that should never devolve into a lengthy debate holding up an important improvement that otherwise checkin. We both have bigger, more important dragons we could use our time to slay. It's worth discussing briefly - maybe we can achieve consensus and find a better option - but if you want to check in your code as is, right now, for pretty much any reason whatsoever? Go for it. We can always make a followup changelist. Hell, please do - those are easier to diff! Even if we're working in "commit straight to shared master branch in perforce" style. If you're using git, but are worried other people about to start refactoring and want to merge into the main work branch ASAP? Go for it. Naming debates can wait. Typos can wait. There's always the next changelist. Just have a general dread of having lots of files checked out? Go for it. Make your commit. The issues are nitpicks, not blockers.

I've seen plenty of good work - changelists that are objectively improvements - die in analysis paralysis and never get checked in because of quibbles over less important details. It sucks. Minor naming quibbles should not be a cause of this. Significant design problems - maybe - but not minor easily fixed after the fact naming quibbles.

"LGTM otherwise!" is also a good finisher to signal "Okay, I've gone through everything, I think I won't find anything else." In more relaxed review environments, it's a signal that I don't feel the need to re-review your change - maybe with minor fixes for outright bugs - before you commit. It is carte blanche to move forwards.
How to make $2400 per week working at home with affiliate marketing
I've seen contracts with hire fee of 25% of the mans salary. They were in pharma. 25%of100-200k per deal.

They both founders got money very fast
I second that. I find that it helps junior dev find the sweet spot in commit granularity.
Tribal politics affect every social interaction. Family tribe, social tribe, political tribe, all of these subconscious imprints play a role in how we interact (or don't interact) with other people.

I would argue that they are not only human nature, but they are emergent from a set of baser tendencies necessary for self preservation in a reality which is resource and time scarce reality.

Tribal instincts will exist so long as individual compete. That goes for social status too.
If that's the case, why have standards when it comes to writing code, e.g. when to use camel case? Why have styles at all for writing in a language like English that tell you how titles should be formatted? Consistent format and structure reduces cognitive load IMO, because it breeds familiarity. Also, Git itself uses the imperative mood whenever it creates a commit on your behalf. Consistency is good.
> there is an AI that is granted supreme power to censor content

Its decisions were overruled by humans. That's not "supreme power".

In effect, some uploads were pre-moderated instead of retromodded. There's nothing novel about pre-moderation, some sites apply it to all user content - if you don't have a problem with that, I don't see how it's consistent to take exception to this.
The way people walk can be used for ID and health checks
Or you could hire a property manager. What's the typical rate they charge?
Sure, it's not the same dollars that I pay in that I'll be getting in the future. That doesn't change the fact that these these taxes have to go into the SS trust fund and is not part of the discretionary budget.

When people say things like "the government spends most of its money on entitlement programs" like it's a bad thing, they're completely misrepresenting the situation. If they weren't spending the tax that's explicitly supposed to fund social security on social security, that would be a bigger story because that would be fraud.
We're a B2B company with a microservice-architecture SaaS that wants to start to sell an on-prem offering. Kubernetes is a no-brainer.

Even if we had a monolith instead, and no plans for an on-prem offering, ultimately I still think that a managed Kubernetes offering makes sense. Efficient resource utilization is all the more important for small companies, and once you have more than a handful of servers, Kubernetes makes it much easier to right-size your fleet by handling all of the scheduling for you.

If you have a couple of servers and that's it, then sure, Kubernetes isn't giving you much. But if you're building a professional offering then you're likely to outgrow that couple of servers pretty quickly.
>> all these people who feel anything else is a viable alternative to Elasticsearch have a dumb, simple, small-scale use case

I have a search use case. I want to create a simple language model where each token in the lexicon gets a unique ID (or ordinal) that I can use to create a more sophisticated model where each document is represented as a vector as wide as there are unique tokens and use clustering and give each cluster a unique ID (or ordinal) so that I can create an even more sophisticated language model, one with built-in semantic understanding. A natural language data structure, if you will, with multiple layers. I want to store the entire WWW in such a model. So I'm building a language model framework that is not build on Lucene because I'm not obliged to use ES in that capacity.

I feel you are wrong to call my use case simple and small scale.
> 1. I think only ~1/150 companies I talk to are actively hiring part-time engineers, so it's unlikely I'll add this category any time soon... if ever. (Sorry!)

Is that not a chicken and egg thing tho? With your visibility, encouraging the values you want to see can be a good thing?

I run an event listing site, and years ago I added a totally optional "Code of Conduct" field. I know that prompted at least one local group to officially add one!

Also, if you do, make it so companies can select both full time and part time. We just closed an job advert where we would accept both, and the number of places that only let me pick one was frustrating.
I actually looked at UWP a couple of years back. To my shock and amazement, at the time the C++ API did not contain anything that would allow you to resize bitmaps. You could resize them for display, no problem, but there was nothing like Core Image available. How this is possible in this day and age on the world's premier desktop OS, I don't know.
Is that the reason? So if your commits aren't getting emailed anywhere, you can ignore this rule (within reason)? I would think only a small minority of git projects have email notifications enabled.
>young people on average measure 40 percent less empathetic than my own generation — 40 percent!

Meaningless without context.
“Tropical tree”, not claiming to be tallest amongst all trees.
Yep, I'm the same - Spark will be stuck on Java 8 until it is rid of logj12, not sure what log4j1 is doing, but it doesn't work on Java 9 and Spark's Hadoop dependencies are riddled with log4j12. What's nice to see is that that log4j2 team have been helping with the work in the Spark project.
This is actually a key mechanism for what's wrong, socially, with pretty much everything these days. It fits right in with the concept of The Long Tail.

We get to selectively apply our preferences now, for our unique musical tastes to hear any artist, and thus only those we like; an infinite choice of movies, and thus never the fixed schedules of centralized broadcasts; we can binge on an entire series in a weekend, commercial free, viewing dozens of hours, watching itall in one sitting; browse unlimited archives of text, applying search appliances to a corpus of text, to randomly access select passages ona whim, in ways notpossible with a conventional library of physical volumes.

So too, now, we apply this tendency to the company we keep. We ghost people. We provide votes to rank performance, and perform to score points in a virtualized hypertext context (it's not really a community, it's just web pages still, despite all you may know about interaction, javascript, live video streams, chat, texts, telecommunications and telepresence, social media profiles, blogs, photo sharing... even AR and VR, and second life type avatars... it's all actually still pretty primitive with leaky abstractions everywhere, to be quite honest). Dating random people has exploded in ways not possible with classified ad sections in print media, or even dating services that played match maker, decades ago.

So it's this impulsive, push-button tendency toward instant gratification, creeping in atthe edges of every facet society. The combinatorial explosion of random access awareness to everything we can expose ourselves to, limited only by the pace we set for ourselves. Far from sheltered in an informational sense, now armed with a much broader context of understanding, determined by whichever choices are fortuitous enough to present themselves to us in an endless chain of relational links or rungs we climb, as we negotiate a landscape of media consumption to learn and inform ourselves. With this awareness, we build the context to pass further judgement, stored in a buffer of medium-term memory, like driving at night, with the high beams on, following road signs, but only ever being led to fast food pit stops, big box stores and gas stations, and hotels. Never a home to reside in. No family to speak of, just strangers on the street, it seems.

So that buffer of medium-term memory dictates which peers receive love, who gets the ranking votes, why we buy junk food from this gas station, but not the other.

It's not going away.

It can't be simply destroyed and directly eliminated.

The void left behind will force something to regrow in its place.

This way of life is here to stay. It's going to harden and calcify in this disposition, unless we find a new way; a replacement to unseat it. To fix the broken parts. A way forward.
"It’s really kind of silly how easy life can be if you start out with a little money and use them wisely."

Could you clarify? Is it a comment on the randomness of life? Because at the moment it doesn't read like that at all.
I can see the value in gerrit's suggestion of including the component name in the header. I'm not sure I see the value in adding the commit type. Where do you see it as useful?
It's also very easy to start playing here: https://online-go.com

Sadly these days there are not so many players on western servers in the higher ranks. But I like the software the most. It's made by one of the github founders I believe.
That's cool, though it doesn't seem to work through a level of indirection. https://d.godbolt.org/z/zkm39N

(I don't know much about dlang. I got the compiler flags from googling and happening upon the test case in this PR https://github.com/dlang/dmd/pull/8504/files#diff-bb6a3ed8a5... )
If you content address your files then you have problems when tracking entities linking to the same file. (like email sender and recipient linking to the same attachement. Same file; different owners)
> I have seen failed projects where the complete lack of commit sanity wasn't the cause, but a very clear sign, of what was wrong.

Clean commit messages fall into the same area as “good git hygiene” for me.

When I was consulting (mostly in the areas of DevOps and CI/CD), git hygiene was the very first thing of any new assignment I would take a close look at.

I joined a project that one of the main contributing factors in its failure was poor git hygiene. The real killer was a mess of branches that everyone had direct push access to. One of their repositories which contained cfengine infrastructure code was branched per environment. The configuration drift between the branches was so great that the dev team decided it was easier to throw away the entire codebase and rebuild production from scratch.

This is how I fell into training developers how to use git, because clean history is a very good indicator of the overall heath of the project.

One of the things I taught myself and then started teaching others is “always keep the head of you branch in a clean working state”. I recognized the common development commit pattern “do a thing” and then immediately afterwards “fix the thing I just did”.

Git never provided an easy way to squash/fixup those commits without popping up my editor, so I made my own little alias which others might also find useful:
https://gist.github.com/philbert/c13ca7220951970225196cbce92...
What in the actual hell.
Usually it puts you under breaking even, esp if you just bought the place. Usually 8-12% according to google. Good for a property with a below market mortgage you don’t want to worry about but don’t want to sell.
As The European working on replacing firmware from another nation (with a little reverse engineering here and there) I can totally understand that attitude. When you make something really polished with best practices or somethng trully innovative, seeing what rushed underpaid/overmanaged programmers do to code evokes only disgust. Specific examples would be several hours of talking.
> Just saying, real estate is a fine thing to buy, with all cash!

The model clearly proves you wrong (even though it's not very realistic in general). If you have cash lying around, you're better off investing in the stock market, or buying houses with loans anyway (just more of them).
> Think of it like a short email that explains to your (future) colleagues and future self

Note that commit messages don’t live with the code. If you find yourself writing why something should be in the new state, consider putting that “explain why” as a comment next to the code, so anyone’s text editor can read it.
Joe Beda (one of the k8s cofounders) just did a livestream on kustomize last week and I learned a bunch of stuff: https://www.youtube.com/watch?v=NFnpUlt0IuM

Full Disclosure: I work with Joe @ VMware
Where's inflation in this model?
> Tribal politics affect every social interaction.

You're broadening your definition of tribal instincts to encompass all of society. Sure, people make teams based on shared social values, but those aren't really tribes in the traditional sense, i.e., you look like me and/or reside near me, therefore I will team up with you.

Under your broader definition, a "tribe" can be anything. It could even emerge based on shared social values of egalitarianism, which directly contradict the more traditional notion of a tribe.
That's great news. I'm personally more a Python fan, but I see all around me how good, stable enterprise problems are solved by Java coders. Last Java version I used was still pre-Oracle, so I can't say if they did a good job or not. But I can say when it comes to open source I have much more trust in Red Hat as a company.
Facebook employs about 35,000 people. The millennial generation includes about 71,000,000 people. How the former can be used by you to represent the views of the later is a mystery to me.
Starting over with a new language has a huge marginal cost. You have to calculate spending the budget on improving the current vs building the new. And its likely that after several years when your new language is production ready - the existing has improved enough. But it might also have become worse.
9, 10 and 11 are following a new release schedule of timed releases (every 6 months), whereas 8 was still a traditional feature release.

I would say that aside of the module system that came with a huge list of now inaccessible internal methods that a lot of dependencies relied on even though they shouldn’t have, there was even more change between 7 and 8 than there was between 8 and 11
That's not what GP was saying. They were saying that given two websites, one that doesn't track and one that does, the one that doesn't would have a better user experience as a side effect, which would give it a competitive advantage in this "department" over the one that does track. So, all things being equal, users would choose the one that doesn't track for the simple virtue of it giving them a better experience.
Secret lab watches for nuclear explosions worldwide
I learned to code in Python, I loved Erlang, I dabble in Elixir when I can, and I loved F#, and I code in Scala, Kotlin,Java, JS and Python in my day to day work, depending on where in the codebase I am.

The things that are hard to beat about the Java world is the ecosystem, the tooling and the package management. Stuff more or less works without too much hassle, there's often a good library for what you want to do, and you're building on decades of previous industry work.

In terms of package management, the most unreliable parts of our project are Node and Python.
Several ways to display the history, like "git log --oneline", or versions thereof that include the author and date, do profit from short head lines.
That's one problem sugarkube[1] aims to solve. But it goes further and allows you to spin up k8s clusters from scratch and install all your stuff onto them. It can bootstrap an AWS account first (e.g. to create S3 buckets for kops/terraform), handles templating files, and gives you a hierarchical configuration. It's still under development but should be very flexible once it's at MVP in a month or so.

The aim of all this is to allow you to avoid tricky in-place cluster upgrades and to just spin up a new cluster, direct traffic to it and tear down the old one. An extra benefit is that it would allow you to give each dev their own k8s cluster in parity with your live envs, but they could select only a subset of charts.

Check out the sample project[2] for more of an idea about how to use it (but the actual sample is probably broken since it's under heavy development at the moment).

[1] https://github.com/sugarkube/sugarkube/

[2] https://github.com/sugarkube/sample-project/
The definition of tribes is a social construct. The existence of tribes is not.

Reformers who seek to abolish tribalism usually find that they've simply redrawn the boundary lines and replaced one set of tribes with another. The dogmatism of the Church gets replaced by the patriotism of the State. Racism gets replaced by classism. Discrimination on appearance gets replaced by discrimination on education.

Sometimes just this redefinition of groups is progress: I'd argue that group boundaries based upon choices or values are more useful than group boundaries based on origins or genetics. But the utopian vision of "and the world will be as one" is naive, and ignores basically all recorded history.
I read the pricing as "1500 webhook requests per minute" instead of the (I assume) correct "1500 per month".
JIRA Las Vegas
It is called Bauhaus style. And is in fact applied everywhere now but with more glass.
Thank you, I can go to sleep tonight now.
Commodore 64 Basic and Kernal ROM Disassembly
Show HN: Inbox evolved: reach new levels of productivity
Then Git would have to be content-aware, as sometimes whitespace is meaningful and sometimes just formatting.

Add different ways to format code in, say, C, C++, Java, and so on, and you'd add a whole lot of unnecessary complexity into a version control software...
>> Hire local poeople and treat them as if you need them.

Wow! What a concept!

alas, that'll never work.
If they did, it would lead to the political will to change the law. Because they don't, we are stuck with the non-uniform application of the law which causes tension in communities. Justice is not dispensed by police, it is frankly not their job. Pointing out that we'd have a lot more people getting ticketed just shows how broken the system actually is in its current form.
I don't know off-hand. The claim that this "is the future the EU has voted for" was made by the article, not by me. I was, for the sake of argument, taking the article at its word on that - and observing that, in that light, its histrionics about Article 13 come across as misplaced.

That being said, even if a speedy review process isn't required de jure, market forces should make it a de facto requirement. Over time, a platform with overzealous takedowns & inadequate appeals process will lose out to any competition which does better on either front.

(Yes, I know it hasn't worked out like that with YouTube. They're close enough to a monopoly that market forces don't really apply, and that's a whole other problem.)
It's actually pretty good reporting. I'd give it a full read.

There's enough details dropped about experiment durations, species counts, and references to the techniques used to measure that if you've already got a background in the field, you can infer quite a lot; and if you don't, you can skip those details.

What good reporting should be, in other words: a summary valid for a wide audience.
Network policies, RBAC, the ecosystem...
Non-Volatile Memory and Java: Part 2
Dropbox ignores user preferences to promote new Paper app
Anyone else experiencing this? I have all notifications disabled for Dropbox on macOS in the app, and just got my second macOS notification encouraging me to "Try Paper today!"

To be clear, this is a system level notification. I have all notifications disabled for Dropbox.

Dropbox support said "if you have notifications enabled then this can happen". I do not have notifications enabled.

I don't care if they email me about Paper, but pushing notifications to my OS is gross.

https://developer.apple.com/design/human-interface-guidelines/macos/system-capabilities/notifications/
Briljant angles, compositions, and colors in these photographs.