skysight-inc/HackerNews huggingface dataset:
Wait, I must be missing something. I too develop in feature branches, and then they're merged into develop or main (with a merge commit, obviously). Reverting that is too only a single revert. The only problem is that sooner or late those feature branch do get deleted, and if you swashed, you lose all the non-squashed history. If you don't, it's still in the develop/main branch.

What do I miss?
Yes, our company squashes commits (we have tens or probably hundreds of thousands on the main branch). Yes, I routinely look at commit history. Commit history is also used for doing analytics for performance reviews such as how many commits did you make, what percentage had tests ect. For instance my last performance review made note that I had test coverage on 90% of my commits.

Also, we auto-stamp the PR on the commits so we can get the context. I don't understand how anyone could make sense of a large codebase when all the commits are added with the standard inane commit messages (e.g. "fix it", "typo", "name changes", "tests") that people do when building a feature. I routinely have to look at a piece of code, do a git blame, get the PR in the commit and figure out what was being done.
The problem is if multiple people make other changes after yours. You can certainly go back to your tag, but you lose all their changes as well.

If you revert one specific commit it just does another commit with the exact inverse of what happened in the reverted commit, so all other changes are preserved.
last_prod_tag < the_lot < current_prod_tag
I'm intrigued to see that there are (by my count) three of us making this point today. Perhaps this is an idea whose time is finally coming.
https://vercel.com/docs/serverless-functions/introduction
I'm probably 75/25 on this. 75% of the time I'm gonna squash, because my entire commit messages is along the lines of "got to this point" or "fix frotzolate when x=7". 25% of the time my first round of squashing yields good commit messages that are isolated and complete, so it's better to leave those as separate commits when merging into the mainline.

I also aggressively reorder my commits. When it gets to yak shaving you basically develop in a stack, so you end up with a half-functional commit to system A at the top, then a complete commit to system B, then the finishing commit to system A, so it's better to just rearrange it so that you have one system B commit followed by one system A commit.

But I do routinely read the commit history (using git blame) and no I don't want to see the "complete story" of my past self having "got to this point"--I want the documented MR commentary.
Also, ATM machines. When my daughter was sick with cancer ten years ago I was a contractor. I couldn’t put in enough hours because I was always at the hospital with her. The handful of ATM’s I owned at the time allowed us to keep paying our bills.

Cash isn’t as common now (pre-COVID), and even less so post, but my guess is there’s still money to be made in some parts of the world.

ATM machines are cheap, about $1,500. If you put them in places where people REALLY need cash (strip clubs, festivals, etc...) you can make a fine living.

I eventually sold mine to a friend because my consulting required me to travel and you lose all your profits if you have to pay a company to manage (refilling) the money for you.

I have some funny stories like the time I was sitting behind a strip club in a bad part of town at night with $30k in cash waiting on a tech because the magazine jammed.

I once had to withdraw 60k in $20’s for my friend and business partner at the time. He was out of the country and is 18 year old cousin was refilling the ATM’s. His ATM’s were two hours from me. We sat in the back of a large Wells Fargo branch with money counters and VERY SERIOUS (read: terrified) EMPLOYEES as I handed the $60k they just counted to a kid and sent him on his way. LOL

In the ATM biz everyone knows each other and lending money is common and done on a handshake. The reason is, if you can’t be trusted with cash you don’t last long. So if you’ve been around nobody had a problem letting you borrow $100k in duffle bags in the parking lot of a Home Depot at 6am.

Everything is tracked because the ATM’s all go through a data provider that handles the bank interchange. You should see the volumes of money that pass through them. Even the small ones back then would process hundreds of millions in $USD a year. When you lend someone money you call Chris at the data company up and say “I’m borrowing $50k from Tom so send the next few wires to him”.

M-F you get an ACH from the previous days withdrawals plus whatever fee you charged. Monday’s includes Fri-Sun. It’s an interesting business and it’s fun. I never got robbed but I’m ex military and stayed strapped and aware of my surroundings.
Perhaps it's better to think of us living in a mash-up of all four of his Club of Rome Quartet futurist SF novels.

The Sheep Look Up: pollution-driven ecological collapse and climate change
The Jagged Orbit: corporate capture of legislation and societal violence
Stand On Zanzibar: overpopulation and media saturation
The Shockwave Rider: rapid technological change

Brunner was a fascinating man; I only got to meet him a couple of times before his sadly early death, but his work has influenced many across more than just genre fiction. His role in late 1960s and early 1970s activist politics in the UK is often ignored, along with his autobiographical novel of the founding of CND, The Days Of The March.
No, I didn’t make this, just submitted. Also, I think it’s wobderful as well :)

Cheers! :)
do you consider payments via cryptocurrencies?
90% of state/local pensions are administered at the state level.

Usually state plans mandate contributions to some degree -- in my state (NY) the year after a stock market crash is always a mess for schools and localities because the state requires increased contributions to make up for investment target misses.

Even where the state isn't a good or responsible pension administrator, the pension system membership usually takes the obligation off of the city/county balance sheet. States have sovereign immunity, so at the end of the day, the pensioners will take a haircut.
We do. PRs are generally smaller than 3 years of development. Sometimes refactoring will be split out so what could be a single PR with multiple commits instead becomes multiple PRs. This allows review to be focused on each PR & enforces that each commit maintain CI passing
UK: 16K Covid cases missed because an 'Excel spreadsheet maxed out’
Lambda calculus, Church numerals, and Graham's number
Not sure about the content locking, but OneNote is super easy to use, can be embedded into teams tabs or files, and has full text search. What’s better about this than embedding OneNote?
Seems like it would be a pretty interesting business to get into, my dad is thinking about it, since he works as an operator right now. Seems like water has best margin :D
I don't know about start-ups, but I think Portugal in general is still growing in attraction for remote workers. Great climate, still cheap and beneficial tax laws.
forbid fast-forward merges?!!?!
"Average" (of 23 survey respondents) might not be a particularly great measure. I can imagine many operators would have 1-3 machines on the premises of the business they are actually focused on (a pizza shop or an office cafeteria with a drink and a snacks vending machine), while others might have 75 or more.

(How much does the average mobile app make? Does that low 4-figure amount (edit-to-add: per year) mean that app development is a dead end?)
What (I assume) is normal is that you have PR validation and CI builds that only maintain the stable shared branches.

If the validation isn't extremely fast (seconds or minutes) then maintaining it for every commit is almost impossible. It would just get other side effects like people avoiding commits because they don't want to run an hous-long test suite more than once.
Of course it would also apply the other way around - if some Apple employees decided to leave and start their own competitive VR project, Apple would be just fine with that.

Wouldn't it?
If you can fast forward the fact that the branch ever existed was irrelevant, since the branch is a direct child of what you based it on. Just with a different name.
Too bad the WHO repeatedly lost all credibility with their experts advices they kept reversing month after month.
Thanks. I don't expect a great experience but I'd like to see if a eInk reader would be easier on my eyes since I am already 10 hours a day on LCD.
The following video gave me the impression that pdf on Kindle Oasis was acceptable...

https://m.youtube.com/watch?v=f-CIESDs78g
Everyone has a past and a future, but what kind?
And working with the Darwin kernel would offer zero benefit in fixing this. The GUI coming out the other side would still rely on all the same technology as Linux desktops do, just as is the case on BSDs. Using a different UNIX kernel doesn't change any of that, and any effort made on the Darwin side would be easily ported to Linux. The GUI components of Mac OS are not open source.
Where are you living in Romania that minor village roads get paved? I have a lot of cycling around Transylvania adding road-surface data for OpenStreetMap, and I have found that usually only the village’s main thoroughfare gets paved while the side streets remain unpaved.

Still, even the paving of village ways may have positive economic value. Throughout Cluj county one finds that once asphalt is laid in a village, that village becomes an attractive place to buy a home for commuters who are now priced out of Cluj itself.
This is sick !
It's serco. Them, alongside, for example, Crapita are one of the big corporate disaster companies the government inevitably gives software contracts to and inevitably they fail.

Given their track records it is beyond incompetence, I honestly believe they only care about profits and barely disguise that fact.
Can you please post(or send me over email) your BIOS/iLO versions? I plan do do a NAS build with a Gen8 and it would greatly help me to know what versions don't have the fan noise issue. Thank you in advance!
The Guardian has an interesting article on their approach to this[0] but I'm not sure what the best solution to this globally is. You can't rely on publishers entirely, and yet posters & commenting platforms often have difficulty identifying the dates on posts from certain publications (especially small blogs).

[0] https://www.theguardian.com/help/insideguardian/2019/apr/02/...
Can you login to your google account for the contacts. But then its far less private, of course.
BTH News 04Octoberber2020 – Between the Hacks
In Romania I came across an egg vending machine. There was a padded cushion where the eggs dropped down.

http://www.eggvendingmachines.com/wp-content/uploads/2011/09...
Clojure-inspired concepts? An upvote from me, despite the hide-out in other languages :)
I think you just highlighted one source of the disagreement. Nobody on any team I work with would accept a PR with 3000 lines of change. Each team had a policy, whether formal or informal, to break large work items across PRs so they were more easily reviewable. I would say that 300 lines changed is getting towards the bigger end of what we would accept. If your choice is between 30 or 3000 lines changed per commit, then for sure I'd pick 30, but above either I think a 300 line limit is more sensible.
Vending machines are still all over college campuses in the US. But I suspect the small outfits cannot compete with the big players in this scene. Seems like it's all just coke or pepsi.
Teams has to be one of the worst pieces of software ever written. I mean this. I am forced to use it every single day, on a top tier PC. It's the very definition of trash, in every way.
Well, uh, yes, that's what the commit history generally looks like (although we do generally put "JIRA-9999: " in front of all commit messages, for context). So what?
Isn’t that what rolling back releases for? i.e. revert the container (or whatever your unit of release is) to the previous version? If you’re removing individual commits and re-releasing (rolling forward), you’re still at risk of being down, because you’re not going back to a known good release.
Romania’s rail infrastructure is notoriously outdated, and journeys across the country are often faster by road (bus or your own car) than even the “express” trains.
For the purspose given that would work. But it feels icky.
ZFS adds complexity and licensing issues into the mix. parchive is a good way to separate different layers of concerns to achieve similar end point.
Vancouver has recently added a tax specifically on unoccupied residencies specifically to avoid speculation.

You're also ignoring a pretty big option. Rather than choosing between landlords who rent and landlords who speculate, you could have local ownership of the building you live in.
What My Sled Dogs Taught Me About Planning for the Unknown
Link to your emulator? I don't care if it's buggy, I want to try playing a game on it!
It depends on how close CF's edge is to you, a normal traceroute from my home's router is 7 hops, but if I'm on VPN, it's just 2 hops from VPN exit.
I listen to pop music. There's probably a high overall vocabulary count, but (a) lyric sites are a thing, and (b) the common words are really common. сердце, очи, люблю, руки, и.т.д.
Google Calendar adds Google Tasks integration
on the other side, if there were only 5 top teams with 4 car each, competition would be much closer than it is now...

Look at how it is now: Mercedes has one official team, one unofficial (racing point) and a third "hidden" team, the former Williams. Where is Toto Wolff going after the announcement that he will leave Mercedes? and why you say Williams? (Wolff has bought shares of both Aston Martin - former Racing Point - and Williams)

That's 6 Mercedes cars, but only 2 allowed to go fast and win.

Ferrari-Alfa Romeo are in a similar situation.

I say let them race and see what happens.

Put the human factor back by having less cars, but with similar performances.
Looking at the source it looks like he's playing with texture on cylinders. Still pretty tho!
"our town" FFS that attitude is why the USA needs one set of employment laws
I specified I was talking about the power units, not the series as a whole (since the power units are the part that Honda is involved with).
CSIR is more of a system of labs than one big organization/lab. It provides a legal framework for the state to start targeted labs which investigate specific fields of study. There are CSIR labs studying everything from ceramics to biology.
This seems nicer to me. Just like any other VM, using a proven container, etc.
I don't know, since my internet is so fast I don't really feel the dip in speed when I use a VPN anymore. I suppose this is relevant for people who download a lot of files or have slower internet.
It also helps that it’s a high trust society and you don’t get a lot of delinquent kids breaking in to get cigs or beer. Obviously cameras help with that.
Videoconferencing to be used for government recruitment in Cameroon
So? Remember democracy?
And if those 4 competitors are the industry? and 12 months you where had mate (unless your a C level )

Your right about trade secrets though.
You need to squash your commits, then: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
What good are rights when corporations can just have users sign them away by agreeing with some policy? They already make users waive a lot of rights, including the right to pursue legal action, the right to reverse engineer...
Until a garbage collection process trims those. You may control such on your local machine, but you don’t on the remote repo.
Bullets. By Tom Sachs
Also I thought that in 2020 it is becoming more generally recognizes that people have a right to an “affectional” preference. It should be OK no to be attracted to someone.
Right!? He discusses flatness, but not planarity, or levelness. Not even a glimmer of an attempt to describe the bootstrapping to precision. What’s weird is he starts talking about electronics when he gets to the 20th c., yet the 20th c. is perhaps the century where good old fashioned precision has improved the most!

A complete dodge & waste of money.
depending on what im doing, i'll do squashing, fixups, and commit reordering in an interactive rebase prior to merging to at least reduce the number of noise commits.
I absolutely get that (and get that not everyone does). Meanings evolve over time. Or are understood to mean different things to different people (an example I like is the almost opposing meanings of "implies" between mathematicians and mainstream English speakers). You can even use words to mean something different from the usually-accepted meaning, so long as you're clear about your own definitions up front.

But you specifically claimed that your definition of "concurrency" is the main accepted one:

> "concurrency", nowadays, refers to ...

> ... it appears to have stabilized

This is the part I disagree with. My understanding of the word "concurrency", the Wikipedia definition that someone quoted, and the meaning in the article all align, and are all different from the meaning you gave (if I haven't misunderstood it, which admittedly is very possible). So it seems very unlikely to me that we all hold the minority understanding while yours is the mainstream.
A entity component system (ECS) as used by many games would probably fall under DO.

Through I would argue that #5 isn't part of DO. Especially given that e.g. `{ "a" : "b" }` is not necessary a literal but potentially an expression (depending on arbitrary language definition aspects). On the other hand e.g. `vec![ "a" ]` in rust is definitionally not an literal but wrt. to the idea behind principle #5 as good as `[ "a" ]` in JavaScript.

EDIT: Lastly sometimes contexts using something like a builder pattern can be the better way to "not verbose creation" and "data is exploreable in any context".
At this point, a study which concludes the opposite has to bring the proverbial extraordinary evidence.

We aren't even close to that point. There's a heckuva lot that we still don't know about this virus. That paper was update, what, 30 June? They even admitted that they were using their earlier conclusions to create filters for the new literature they were reviewing- in effect building their own echo chamber.

As long a the study is competently run and has reasoned conclusions it should be considered.
What's wrong with snaps?
The Remote Agent Experiment: Debugging Code from 60M Miles Away [video]
I think much of the difference here depends on your workflow. Where do you run tests? How do you manage build infrastructure? What is your process for code review? What is your process for validation and testing of shared branches? How do you manage releases?

In my opinion, squash merges make the most sense when the following are true:

1. Developers cannot push directly to shared branches; all commits into shared branches are done via pull requests with mandatory code review.

2. Shared branches must build and pass tests at every commit.

3. The team builds features incrementally and uses the "Branch by Abstraction" approach (feature flags/experiments) to ensure functionality can be merged before it is ready to be enabled in production.

4. Changes that merge into the shared ("trunk") branch are released frequently.

Now, you may argue against some of those practices, and if you end up in a different place on one of those, squashes may not make sense to you. But then the actual difference of opinion is elsewhere. It's not really about squashing, it's about how much code is a reasonable granularity to code review at one time.

If you can keep the code review cycle tight, then a pull request branch basically becomes almost like a virtual pair-programming session. There may be some back and forth as the author and reviewer settle on a final form of the commit. But I don't see the commits that happen along the way as valuable in the least. (In my experience, the vast majority of intermediate commits are things like "fix typo", "make linter happy", "rename this function because code reviewer pointed out it was named inconsistently", etc.) Instead, my mental model is that a pull request is like a mutable commit: you keep mutating it until it's the commit you want, and then you merge it. Since my mental model is that a pull request is a kind of commit, it makes sense that when it merges in, it does so as a single commit.

Again, I'm not saying that this is the only valid way to work. But neither is it an invalid way to work.

As a meta-comment: When you see someone else making a technical decision that doesn't make any sense to you, rather than instantly assuming that they are a clueless incompetent, it's usually more instructive to assume that the decision does make sense to them, and to try to figure out what about their circumstance is different from yours to make that the case.
It does not say that it is the opposite, see other remarks. It does say that children play a role. In my country it is claimed they don't and they have a lot of freedoms. Even though they are probably less "good" at spreading they have a lot more occasions to do so. At least here in the Netherlands.
Hey Max! Thanks for asking. Cryptocurrency is the future but unfortunately, now we are limited in terms of resources and time. We want to test PMF first and then think about integrating additional payment options.
See also

git log --no-merges --first-parent

I don't get the "no merge commits" argument - git log has dozens of options allowing you to bend it to your use case.

To address the grand parent that "a clean history is has no merge commits" I would argue that a clean history is also a lie if you're working in a branching workflow (hint: you should be working in that most of the time).

If you want to avoid (note: not eliminate) merge commits then make sure to rebase against master before merging, and then ensure merges are fast-forward merges.
I'm a university student with a flashcard startup / project called memordo [1]. I have only ever had 2 customers subscribed for 1 month each. Right now I'm the only paying customer! but at least I'm a happy customer :-)

[1] https://memordo.com
Working for Steve Jobs and the Future of Esports Orgs
There are a lot of opportunities like this. However, when you look at many of them in detail, they pay very very poorly.
Orwell and HG Wells were both really taken by Basic English at first, with Wells arguing it could help build a singular world government. Orwell later became cynical about it, focusing on its lack of any words for things like "revolution." It became an inspiration for newspeak in 1984.

(I honestly think this particular concern was a bit of a straw man of Wells' and Ogden's optimistic views, a lingua franca used in a few settings doesn't have to be a straightjacket for all contexts. But it made 1984, so maybe fine in the end.)
Popcorn Time – Baixe o aplicativo Android
Thankfully that hasn't rolled out everywhere yet, and most banking apps I've used rely on less sophisticated methods of tamper detection (like RootBeer).

Hopefully Orange Man's little trade war slows down adoption by devs somewhat, but once that fizzles out, we might have to start looking at a regulatory angle. I don't like that idea, but what other choice do we have? Google clearly doesn't listen to their customers (or rather, we aren't their customers) and good luck even getting in touch with a bank's dev team, let alone convince them to do something that, to their uneducated higher-ups at least, looks like a security downgrade.
So just fructose, glucose is fine to consume?
What do you mean when you write that `{ "a" : "b" }` is not necessary a literal but potentially an expression?
Would the socket be in /run now?