skysight-inc/HackerNews huggingface dataset:
I have used gitflow successfully for some time (starting when it was first announced and there wasn't anyone complaining about it). I've always done "develop is always deployable to production" and the only thing we used master for was rolling back (extremely rare), and the only thing we used release branches for was demos or documentation before a release went out. We had CI built against develop but also every feature branch and every PR. We also leveraged static analysis the same way, and at one company even ran automated pen tests on develop and PRs.

I don't know if I fundamentally misunderstood gitflow but this was my take on it from the beginning and I've never had issues with it that made me want to jump ship.

We didn't use hotfix or support branches, and we never really used tags for anything either. Not using them didn't cause any noticeable overhead.

The nice thing about git-flow in my opinion is that you can implement it without all of the CI stuff, then add that later over time. This is a godsend when you take over a legacy product with little to no test coverage and no CI pipelines.

I've also never run into a ton of merge conflicts, but the largest team I've had is 70 people so maybe it breaks down at some point that I haven't experienced yet.
I almost drowned when I was pretty young (I wanna say 6 years old) might be older though but not by much, when we went on a pool trip when I was in day care or something, can’t really remember what grade you’re in at age six. I went to a deeper end and wasn’t able to grab the edge to pull myself up.

A girl a few years older than I was was able to swim across and push me up. I remember there were two “chaperones” who were just a few feet away from the edge of the pool but they were both facing away.

Terrifying experience, still remember it vividly. Parents kind of laughed it off but I definitely could have died. Definitely teach your kids to swim properly before letting them go to a pool unsupervised is all I’ll say.
That's why everyone should still use SVN (or even something distributed but friendlier, like hg or bzr) and git should be a minor-but-important player that's used where needed (like for managing the Linux kernel, which is what it's actually for).

But of course we've cargo-culted it everywhere, and anyone who objects runs up against the pervasive attitude that there are no bad user interfaces or difficult-to-use software, only stupid people.
I'm not an economist or a laissez-faire capitalist, but I don't think that's the ordinary mechanism of market pricing. My understanding is that the individual actors on the market independently price their goods in competition with one another. In this case Uber is the sole authority in setting the price of rides, while in a market this would be more distributed. To quote Wikipedia on the free market:

"In a free market, the laws and forces of supply and demand are free from any intervention by a government or other authority and from all forms of economic privilege, monopolies and artificial scarcities."[1]

[1] https://en.wikipedia.org/wiki/Free_market
Or better yet, oscillate along the path of the beam. And they would naturally have another flock to swap out when they tire plus another flock available as a hot swap in case something unexpected happens. :P
> I suspect that a lot of anxiety comes from too actively predicting future negative outcomes

Is this not the definition of anxiety?
Totally get what you said IF the artists of this day and age weren't shilling for money. If it was pure art that was an expression of their self, sure, I agree it's art. But peddling mediocre crap for large sums of money should be equated to trash.

Most of the discussions around modern art is around who sells for the most amount of money. It's a numbers game, gaming galleries which exist for no other reason than to peddle crap possibly for tax reasons, and con artists posing as real artists...
In theory it's possible to, if you're doing pool rides
Predictable Identities 26: Academic Identity
> What exactly degrades about HTML in twenty years? I can read pages from the 90s just fine: the main thing off is the font size due to the change in screen resolutions, but—surprise!—plain HTML scales and reflows beautifully on big and small screens. (Which is the complete opposite of ‘HTML has the same problems’.) I hope you're not lamenting the loss of the ‘blink’ tag.

I am indeed, and of other tags that are no longer supported. Old sites are often impossible to render with the correct layout. Resources refuse to load because of mixed-content policy or because they're simply gone - which is a problem with the format because the format is not built for providing the whole page as a single artifact. And while the oldest generation of sites embraced the reflowing of HTML, the CSS2-era sites did not, so it's not at all clear that they will be usable on different-resolution screens in the future.

> Markdown translates to HTML one-to-one, it's in the basic features of Markdown. For some reason I have to repeat time and again: use a subset of HTML for papers, not ‘glamor magazine’ formatting. The use of HTML doesn't oblige you to go wild with its features.

This is one of those things that sounds easy but is impossible in practice. Unless you can clearly define the line between which features should be used and which should not, you'll end up with all of the features of HTML being used, and all of the problems that result.
Your example handyman can negotiate on rates, serve the same client in the future (with the possibility of a re-negotiated rate), and set their own terms and conditions for providing the service.

None of that applies to drivers who can either choose to take what they're given or quit.

I can't find a reason why that the court's criteria isn't sound. Can you find one?
What Is a Brand?
I don't think you are applying the principle of charity when reading his words.
Emerald City Comic Con 2020 is still on, though they've changed their policy to allow refunds.

https://twitter.com/emeraldcitycon/status/123529219042063156...
To appreciate the context one must consider the much higher standards for employment.

https://www.lawteacher.net/free-law-essays/employment-law/co...

> "...the French law regulates much more heavily all the aspects of employment conditions than the United States: Only a few forms of employment contracts exist in the French legal system, whereas the American law allows the two parties – the employer and the employee- to agree on almost every aspect of the contract freely, as soon as the contract is respecting the same principles and regulations set by the American law for contracts.

> The French legal system also regulates more strictly the aspects related to the execution of an employment contract, the work duration, the remuneration and the contract termination.

> The social tendency of the French legal system to protect the employees is in clear contrast here with the American employment, contracting and competing freedom principles."

Uber is seen as an attempt to escape the relatively fixed labor agreement.
The problem is that statistically the confirmed number of cases is only 1 in 2 million in the US at the moment. Your chance of getting hit by lightning in any one year is higher at 1 in 700k. So at this stage it is very hard to comprehend.

It's when you consider the prediction that 40-70% of the adult population are going to be infected if it's not halted that you have to take it seriously. Noah Feldman while interviewing Harvard epidemiology professor Marc Lipsitch who gave that figure admitted that it just didn't seem real that we are looking at 1 million+ deaths in the US if that level of infection occurs. Very sobering thought.
Generating revenue alone does not make it commercial use in the context of copyright
How to Create REST API in Node.js with TypeScript and Fortjs
Even in formal employment, you do the same for the above when you negotiate an employment contract
Ask HN: How do you scan through tons of comments to find out those quality ones
Usually under a hot topic there will be hundreds of comments. Although some got up voted, to trust the up vote is to trust the general wisdom of the community.

Is there any strategy that one can apply?
It's amazing how I'd consider myself as having a pretty good grasp of Bash programming, certainly more than average among my colleages, and still this code got me already in the second line :-) (never used typeset before)

Thanks for the gist
With how much money everyone is spending, wouldn't it just be cheaper to build a private cross-country interstate where only AI drivers are allowed. Let humans drive the trucks to this interstate then let the AI take over. It seems like almost all the edge cases would be solved if you just got rid of other human drivers and let the vehicles network with one another.
No, but as I said in my parallel comment, I don't understand how you can do any better than having an infinite amount of pre-shared information without actually communicating. If you can explain that, great (I really would be interested), but the important thing here is that without explaining it the article is kind of flawed.
I've used nvie-like gitflow strategies without significant issues.

One of the things that I like about the strategy is that it works well for code-like things and for things like handbooks/documentation sets built with e.g. Hugo+docdock. Authors branch, work, PR, PR gets vetted for accuracy/policital-correctness/whatever and then gets merged.

Anyone have any experience using feature flags with static web site generators?
When the medium matters: The mighty mantis shrimp pulls its punch in air
I'd start here:

https://www.manning.com/books/learn-windows-powershell-in-a-...
What is the shed made of? What color is it?
Death by Snu-Snu
This. I've had to spend time fixing history after a Jr engineer did a bad rebase. After a few episodes of that I decided I had to either stop hiring Jr engineers, have them always supervised by a Sr engineer, or stop rebasing.

I stopped rebasing.
> Fair use is an affirmative defense against copyright infringement.

This is a misnomer.

Fair use is an authorized use, and consequently is “distinct from affirmative defenses where a use infringes a copyright, but there is no liability due to a valid excuse, e.g., misuse of a copyright.” Id. Lenz, 815 F.3d at 1152
Also born and raised in US and have no clue what a fleets enema is.

edit: apparently it’s a brand of enema laxative. I wonder what proportion of people have had to use an enema. I may be in the minority due to young age and being male?
Only anecdotal. I have an Uber driver friend, and other drivers have told me the same. I live in a very suburban area that's basically shut down for the winter season. There is often only one driver even active within 10 miles. It's not a problem in a city.
me]$ cat .bash_history | grep git | awk '{print $1,$2}' | sort | uniq -c | sort -n

1 git clone
2 git cherry-pick
10 git reset
17 git merge
23 git fetch
34 git checkout
37 git rebase
66 git diff
75 git pull
79 git log
87 git branch
126 git commit
135 git add
141 git push
201 git status
205 git grep
Groups are unstable IME, two person islands are a much better social dynamic and it's much easier to master 1 persons mind.
You get to avoid the Valley of Despond when you, y'know, write the tool.
This sounds like an rss reader in a way - subscribe to topics, it fetches them at set whatever intervals, can fave / save..

Option to download a copy of the article the hn discsussion is about and create a thumbnail..
Yes, I think a bridge to NNTP would also be helpful. The ability to post through NNTP might be good too.

This would provide some of the listed features when using a suitable NNTP client; my own NNTP client called "bystand" supports SQL (it stores all data in a SQLite database; if you use the SQLite FTS extension then full text search is available), but other clients may have different features, so may be more suitable for your use possibly.

(I think that all web forums and mailing lists should be NNTP instead. It is OK to have a web interface too as long as the NNTP server and message ID can be read from the web interface (even if JavaScript and CSS is disabled), so that if you are given links to the web interface then you can access the NNTP if you want to do. It would also be possible to provide a email interface too if wanted.)
Except for some of us who come from the time you had to get permission to get an ID on the Arpanet. In that case, the WHO is not saying mathematically nice things about us. :-(
That doesn't sound right, I don't think there's any reason a proc macro couldn't cache the .proto file's generated code and use the cache between runs.
Correction: March 25. Microsoftie.
When I work together with people on projects, I make them to agree that nobody other than the author of commits is allowed to resolve merge conflicts, and conflicts must be resolved in the feature/pr branch that is going to be merged into the main branch(es)
Sounds like rail?
I think the parents question is whether the real world follows the finite vs infinite model.
This hypothetical, dare I say strawman, scenario doesn't work in creating an equivalence between builders and Uber drivers for the simple fact that it is in fact not how price negotiation works for construction projects. In the real world, for real independent contractors, the contractor sets the rate and it's up to the buyer to accept it or not (and of course possibly negotiate). A typical process involves soliciting bids from multiple contractors and seeing which one comes in the lowest, while attempting to take into account work quality. You see this in real IT consultants too; they have a given rate that they've set that they want, or they're not doing the job.

There's no method whatsoever in Uber for drivers to actually set their prices, which is a key difference.
How Did Software Get So Reliable Without Proof?
From the WHO and the CDC. The WHO released the figure 3.4% yesterday, and the CDC lists the flu this season as causing 18000 deaths in the US from 32 million infections = 0.05%.
"I think it might be too much work to parse queries, and the easiest thing to do is to just access a string as query and pass that to the database engine." -- You could also use SQLite virtual table; this allows combining it with other data in the same query; SQLite will then automatically convert your query into a list of constraints, ORDER BY clause, etc, and pass the stuff to your xBestIndex method, which can decide which things the server is capable of using and pass those to the back end, letting SQLite handle the rest of the query itself.
Right, but no cheetas in Greenland, Hawaii, the Andes, on the banks of the Zaire river, in Sahara, in the Ganges Delta, and so on and so forth.
MS employee here. There's been no direction not to publicize this, in fact, this guidance is published on our public blogs[0].

[0]: https://news.microsoft.com/2020/03/04/kurt-delbenes-march-4-...
I wonder if this is part of how competitive environments get whittled down to small numbers of limited choices. iPhone vs. Android, Boeing vs. Airbus, Windows vs. Mac, Intel vs. AMD, Republican vs. Democrat—is this the level of choice we’re actually capable of sustainably handling?
Google didn’t lose anything by settling with Viacom. The Oracle lawsuit put the whole Android ecosystem at risk. The trade offs weren’t similar at all
If you can't win against electric cars, make your logo look like an atom. The oily black is not so trendy currently as it was.
That link doesn't work. At https://www.paypal.com/us/webapps/mpp/merchant-fees, I see 2.9% + $0.30, for in-U.S. transactions done in dollars.
For two nodes you need neither ansible nor k8s.
What are you going to do about it? a) just use parenthesis like everyone else, or b) turn the time back to 50 years ago and change that?

Seriously, the article was just a rant. Yeah, people 50 years ago did something wrong. So what.
I might bring my work computer home then!
Fascinating! I would be curious to see a follow up testing some of the popular Linux EDR solutions.
Great idea, and is exactly what I was thinking about a few months ago actually.

I'm not too sure about the name of the company though "Release", kind of an un-searchable name. Nobody will be able to find you in Google without significant SEO against business/tech blogs. Try searching "release app" or "release company" it's just too generic.

Sorry to be critical of the name, but I think it's much more important than people realise. I genuinely like product though!
YOU created that word salad in 90 seconds.

What I'm asking of you is to be less cynical about what actual art and artists and be genuine in the search for meaning.

If you don't find it - no harm.

Also, the meaning in the author's own head is irrelevant. Death of the author. You can find your own. Maybe their guidance and perspective helps there, maybe not.
Pinboard Is Down
I'd like to be able to move a discussion thread to the bottom, or collapse a discussion thread. Perhaps sort by timestamp the comments option as well.

Sometimes the scroll gets real and I want to get past a discussion to see other angles of whatever subject - scrolling trying to find where thread 2 ends and a different subject comes up is challenging at times - so I often go to a new tab on a different story and don't come back.

Even click/tap to draw a line from comment 2 to all sub comments so I can find where comment 3 starts would be helpful.
We built an ML platform for developers–not just data scientists
Very cool. How does this compare to Snyk? https://snyk.io
Lots of taxi drivers are owner-operators, and many others lease medallions/vehicles but otherwise do their own thing.

As for taking the most efficient route, a driver purposely taking a longer route you didn't ask for to scam you out of your money is just that, a scam. So it's illegal on that basis alone.

They key difference with a lot of these taxi restrictions is they are set by the government to protect consumers. The government imposing uniform standards on taxi drivers through legislation is not at all the same thing as private companies doing so on drivers while weaseling out of employment requirements. The government can set lots of restrictions on how jobs are done without requiring employment contracts with those workers; private companies do not have those same powers. Hell, the government can execute people; there's no expected parity here whatsoever.
Is "approximately 3.5" the answer to "which number will come up when I roll this 6-sided die once?"?
This is all covered in the book I recommended! :)

For the button:

I would say abstracting it out into a function or using dependency injection, and having a centralized switch statement is the way to go. I don't see why you would need to break your interface for most refactors, and if you DO have to, that means your code had a major issue anyway.

Additionally, how is the "just using git for feature management" alternative better? With a feature flag you can enable and disable the feature easily without a deployment. With git, you have to do a revert/rollback/whatever to ship a fix.

I struggle to think of an effective way to reuse a button component over and over again without using a function or dependency injection. If you are speaking of react: Those are functions. That HTML you are using is actually just some syntactical sugar around functions.

You would not keep both versions of the button around permanently. You would merge the branch into your master branch, and enable the feature for the desired environments. When all environments are using the new refactor, and it has been verified to be working, you open a pull request to delete the old version of the refactor and purge the feature flag.

"Well, that is still complicated!" That is true, there is still process around managing features with feature flags. The benefit is that feature flags are easy to grok. It is an if statement. Your application state is no longer contained in an interminably long git log. Instead, it can be determined by checking your feature flag configuration.

> Compared to having a long running branch that I periodically merge the main branch into to keep up to date with the current development without impacting the code that is due to released in 2 days (as it is every 2 weeks)

This becomes laborious over time. If you have many people working on a codebase, the feature branch will constantly break and you will have to go back in fix it.

What if someone has to revert something on the main branch that you have merged with your feature branch? You are now in merge-hell and you have to spend a bunch of time figuring out how to make your branch and the fucked-up master branch have the proper code in them.

What if someone on your team does a hard-reset to the master branch? ( Well just don't do that! Oh, sorry, I didn't realize you were the tech lead for your place of business, and get to decide how everyone else solves their various problems. ) Now your branch is out of date and you have to revert commits and fuck around with your feature branch, and HOPE that you actually unfuck your version history properly.

Look at the alternative: You uncheck a box on a web GUI, the bug is contained, you go in and fix it, deploy it, and re-enable the feature.

Your "what if we just don't worry about it, and not solve the problem" suggestion here does exactly that: Ignores the problem we are all experiencing, and then does NOTHING to solve it.
The most salient points for me were actually made in the last paragraph. IMO would have improved the article to put this at the top rather than at the bottom.

> The crucial point I’m making is to is ask questions of your team: What problems will this branching model help us solve? What problems will it create? What sorts of development will this model encourage? Do we want to encourage that behavior? Any branching model you choose is ultimately meant to make humans work together more easily to produce software, and so the branching model needs to take into account the needs of the particular humans using it, not something someone wrote on the internet and claimed was ‘successful’.
No, I'm not comparing an open marketplace or a weak aggregator with the Uber app. The argument of the French court is pretty clear.

Uber pretends to find clients for contractors but treats them like employees due to three proven powers they hold over drivers: the power to give instructions, the power to control the execution, the power to sanction non-compliance with the instructions given.
I don’t think the solution to “sometimes computers get malware” are laws requiring prior restraint on creative expression.

Not the smallest hurdle there would be that it’s unconstitutional in the United States.
There is definitely opaqueness and one needs to know how to read the data. For example China does not report people who test positive but do not develop pneumonia. The criteria for classification is clearly listed in the national guideline but is easy to escape notice because the daily report is terse and does not reference the definitions. It may not be a big deal in terms of assessing mortality (WHO explained the percentage of asympotamaic cases that test positive is small), but it can make a significant difference when assessing risk for a particular region. If a region reports zero case but there is actually a postive test, the risk outlook is quite different even though the report is technically correct.

But it would be unfortunate to then disregard all Chinese data. That would be like throwing out the baby with bath water. If we don't study their experience we will be bound to repeat their mistakes. Fortunately this does not appear to be the case with medical professionals and scientists, judging from the volume of peer reviewed publications coming out of China.
Now that's a hard problem to solve. AI generated text is usually more readable. I don't know of an algorithm that can dumb it down similar to your example.
So much raw concrete. You'd think architects would have figured out by now that this is not a material that ages gracefully.