skysight-inc/HackerNews huggingface dataset:
This is great! The takeaway for me is that with squash merge you get one commit with all the changes which (optimally) has the full context in the commit message.

My typical workflow is basically the same, but with putting all that context in the merge commit. This allows you to find it with a bit of work (blame to find the commit line, then figure out where that was merged in, then find the merge commit). Squash merge puts all that context in one commit, and keeps a linear history. I had assumed squash merge squashes the commits, then creates a merge commit still, which would mean you'd probably do something like combining messages for each commit in the squash commit message, then capturing the overview in merge commit.

The article says you can still find the individual commits via PR, which is a minor disadvantage as it means you can only do exploration of these via github. If you've deleted the topic branch on github are they still accessible? If it's been garbage collected by git (or never existed locally if you're looking at someone else's changes), is there a way to check them out?
The Hot-Person Vaccine
I don't think there's anything wrong with pointing out that there's 5 companies whose combined revenue is 1/3rd of the federal governments annual revenue while we have staggering poverty in large part due to the pandemic.

It may not be the FAULT of the tech companies mentioned here, but it's time we take a look at how spectacularly these companies have benefitted from the situation of the last year and tax them accordingly to help alleviate the impacts of the pandemic.
I believe SF will thrive in the next wave. SF has decades of progressive exploration to continue, from the 1960's music scene, through hippies and psychonauts and LGBTQ+ culture, to the rise of open source and software, SF keeps thriving on new kinds of ideas. Then mix in the California outdoors, the ongoing health and wellness movements, and top research labs at Berkeley and Stanford.

My hope is we'll start seeing the next wave soon-- I'm seeing a lot of potential SFBA groundwork relating to CRISPR and genetics, neural links with AR+AI, and biopharma coupled with human potential advancements.
I take it back. That sounds worth it.

May I ask what the country is? I am guessing that is somewhere in Northern Europe.
In this case, it's technically "They're turning off X"
Internet and Google. Seriously.
I've been consulting full-time since my early 20s - it's been an adventure!

You could talk to your current employer about switching to a part-time contract - it seems like in the last couple of years, more companies (especially startups) are comfortable with this + remote. If you can get them at 20/wk, that will give you some good security while you work to fill the other 20 (sounds like you may already have a jump on that).

Have a lot of meetings with friends and past coworkers, and let them know you're striking out on your own with a particular skillset. All of my best projects have come from connections, and my worst ones have been anonymous inbounds/etc. If you're in-demand, you should be able to line something up before reducing your FTE hours or quitting your job. It might take some time to find a good set of clients + rhythm, and you want to avoid "burning savings" during that period as much as possible.

Do good work. It's good for your clients, good for referrals, and good for your soul. You're a craftsman, and your name is attached to your work in a new way as a consultant.

I charge a reasonably high hourly rate for my work, and my clients are usually around 15-20 hours a week. I've found two clients to be the right number for me. For them, it's a way to get senior experience on the team for the yearly price of a more junior dev, and for me it's a way to make a good salary, while getting to work with startups and enjoying some freedom and flexibility to do the things I love (traveling and learning to fly!).

I try to keep a bit of "slush time" (like 5 hrs/wk or so) to work on interesting one-off client projects that come along. They're fun and stimulating, and they keep me sharp at selling my skills to completely fresh clients. I normally work on the frontend/backend, so getting to work with things like Swift or ARKit is great. These projects are also really low-pressure, because my main stream of income comes from steady long-term engagements. This is my "blogging".

I jumped in feet-first, but I was a broke college student (and self-taught developer) when I started so my burn rate was ridiculously low. It took me a long time to find a good pace and to build a good network, and I started a few companies along the way. I'd only recommend doing it this way if you're young and resilient - in retrospect, I could have been doing many of the things I needed to do (getting experience, finding clients, making friends) with a more stable salary. I don't know if I would have, though - so the pressure was helpful in some ways. I was also lucky to be in a stage of life where stability was less important than adventure.

Hope some of that is useful, and best of luck striking out on your own!
Nah, this all started with normal retail channels. They introduced the concept of the middle man and the markup that entity would demand for their services.

App stores just brought this into the digital space, overwhelmingly large profit margins and all.

Folks here frequently laud Epic for their attack against Apple, but even their (comparatively low) margins are kinda ridiculous for the bare minimum service they provide.
This is quite useful. Would love to see it extended to different providers (not just the latency internal to each provider but between them).

For example, I'd like to find a set of 3 locations across 3 providers that have the lowest latencies between them.
I can’t wait for 802.11ax in 2030ish.
Yes but the only ones not on long since obsolete nodes are the Intel fabs in Ireland, I think.
The older I get the more I find these discussion as counterproductive as figuring out where to put the bike shed.

I worked in teams that did squash merge and in teams that didn't. And in teams where some did and some didn't, on the same repo. In the grand scheme of things it didn't matter, except for hardliners who had nothing better to talk about.
Yes there’s a bigger chance of a black swan event. You have to answer for yourself if the extra point or two of cagr is worth it.
I don't know how they are accounting for the various different data centers within a region (IE. Availability zones). It could explain self latency if a packet is leaving a DC
LinkedIn removed a post criticising Indian Government's COVID handling
> If every startup started compensating like FAANG, they’d have no trouble finding talent.

That can't work. Current talent is a zero-sum game. You offer more, you get someone to switch over to you, somebody else offers more still and takes that person from you.

You might attract more future talent to the industry by offering more, but since software developers already make 2-10 times the average, I doubt that people think "you just can't make money in software, I'm going to do something else".
Most comments here are about right. What they do not discuss at length is that you'll need to be searching for clients in the middle of projects and possibly scheduling them in or adjusting your staff appropriately as needed. Smaller consultancies may need to search for clients and schedule them in months later, or adjust staff on-demand to account for onboarded clients.

Yes, finding work is important, doing the work is important, and getting paid is important, but the latter two are not as important if you know what you're doing and you work with people who will pay you. Those parts are not hard. Sales is "hard," in so much as it takes time.

The risk factor involved in my previous statement is that they shop around and rescind the work agreement because their timetable has immediate needs. Not a lot of clients are patient.

It's sort of a basic thing that goes without saying, but once you get into this line of work, you'll learn a lot about HR, compensation packages for your contractors/employees and corporate tools.
This was really educational! I love the design of the webpage, and I especially like how you can rotate the 3d diagrams and see each component from every angle.
Website Workflow – Deploying Hugo on AWS
Some platforms (at least MacOS) hide the scrollbars by default if you’re using a trackpad.
I love the "Great Wave" and it reminds me of fractals:
https://en.wikipedia.org/wiki/Fractal

I think the painting has great similarities to fractals, before fractals were "discovered".

Another one of his works (Not save for work!)
https://en.wikipedia.org/wiki/The_Dream_of_the_Fisherman%27s...
Serverless email forwarding using AWS Lambda and SES
Hi, I am Romaric, co-founder of Qovery. We do support Digital Ocean (https://docs.qovery.com/docs/using-qovery/configuration/busi...) as well as AWS (https://docs.qovery.com/guides/tutorial/how-to-deploy-your-a...). We plan to support Scaleway and GCP in Q3 and Q4 2021. Here is the roadmap https://roadmap.qovery.com
> The only step up from this is to have an interactive, radically simplified version of the product embedded in the landing page

Just having a live demo link would be great.
This is a bad analogy. The stock market is not a lottery. It’s a place to buy and sell shares of a company. Most people treat it like a lottery and that can serve you rather than hurt you if you know what you’re doing.
But it's quite possible that the Roku devices won't be capable of supporting those higher resolutions using the older codecs.

Not saying that is the case - I don't know, but I don't think you do either.
In the end, it was Bruce Baumgart, winner of the 1972 "Intergalactic Spacewar Olympics" described in the Stewart Brand article "Spacewar — Fanatic Life and Symbolic Death Among the Computer Bums"? Probably the only person bearing the title "best Spacewar player in the world" with some legitimacy… ;-)
Yeah, but people could work at Intel in Ireland for a long time, ditto for Google in Ireland/Switzerland etc. Knowledge transfer happens but the people it goes to stay with the US firms. Or they leave but aren't interested in competing with their old haunts and go to do something else.
Absolutely this - most ransomware attacks are pretty unsophisticated. You don't need privilege escalation, or an exploit. You can carry out the attack using just basic user permissions. You are exploiting a basic "problem" of most modern OSs (that apps run "as" the user executing them) - the user/group permission model ceases to work in 2021 with non-expert users. Portal-based access to individual files via secure OS-provided portals (i.e. like on Android/iOS/flatpak) help to prevent apps needing access to every file on the filesystem, but until those are widely adopted, it will be increasingly difficult for "normal" organisations to prevent ransomware attacks.

You can prevent ransomware fairly simply by following best practice, and taking some steps that most companies will feel are excessive (but effective), such as whitelisting binaries, preventing running of any binaries not on that whitelist, and keeping that whitelist up to date on a regular real-time basis. Nobody wants to spend the time doing this, so they leave it a "free-for-all".

Exploiting user-level access is just the natural escalation now that getting good exploits is more costly and difficult. Now attackers will "make do" wiht what they have. IT can win the battle, but with inconvenience, friction, and increased costs in IT.

There's important businesses that are "critical infrastructure" still using Windows 7 on their corporate day-to-day let-me-check-my-emails-and-browse-the-web laptops, without extended support. Organisational inertia and a lack of recognition that they need to pay for the technology that enablers their business leads them to this position.
> and then the guy started running around the arcade (Sega Center) yelling "This guy is the best Space War player!" over and over again while pointing at me. I was pretty embarrassed for him.

He sounds refreshingly honest and self aware to me. He went around loudly letting everyone know he was the best player, when proven wrong he just as loudly informed everyone of the correction. Everyone should be more like the second best Space War player in the world.
Having seen many of his videos, I agree with you. Not that I'm against it, but under tantacrul, Audacity will likely become nearly unrecognizable. Many of us have a huge investment in the present, imperfect system. We should admit upfront this is a fork, and a separate maintenance effort for Audacity classic will be a separate project.
That's not the issue. Google wants other companies to adapt to their software, not the other way around. Is the MS playbook all over again.
Strange how Spotify managed to create and distribute their app entirely without Apple's "help" on macOS, but would somehow be incapable of doing the same on iOS.
> Developers should be required to submit _clean_ PRs, that is, PR's whose git history has been organized and refactored in such a way that it removed "clean up commits", "typo fix", etc.

A complete and utter waste of time. You spend more time messing about with rebase than solving problems.

When you're digging through VCS history due to a bug you often ignore the commit message anyway - if the code did what it seemed to do you wouldn't be there.
Thanks for the insight. I have often wondered if there is a space between the companies operating very large data centers and those running small businesses. In distributed systems, my own experience is:

- the very large organizations will engineer whatever they must to meet their availability/performance targets
- the mid-size orgs will use whatever they can from the big orgs to work in their area of competence
- the small orgs are happy with the basics

There may well be a middle ground that I should explore more.

Thanks for the servethehome.com reference. I'll try to learn from his approach.
Exchanges are good at blacklisting BTC ,so this means it will be hard for hackers to cash out. Just converting BTC into XMR is not a trivial process, as it needs to go through an exchange. Trustless cross chain transactions are still in infancy .
I know someone who uses tones as an easy way of knowing if there's a market move on some cryptocurrencies. Basically, there's different tones for a trade that traded higher than previous and for a trade that traded lower than the previous. Possibly pitch or volume or something was used to indicate the volume of the trade, I don't quite remember. Either way, he could quickly hear if there was a major market move or something just by the amount and tone of the beeps. He used this as a way to know then he should look at the chart or whatever.
They are hidden by default on certain platforms, and you need to scroll to see your position.
My thoughts on the points raised in the article:

* Differences in keystroke logging - this has nothing to do with the switch and everything to do with the design of the traces on the board, the controller, and the interface to the computer. There are plenty of what you would consider to be mechanical keyboards by your definition that are 3KRO/6KRO. A beginner reading this article may wrongly assume that if it has a discrete switch it must be NKRO.

* Typing feel - this too is a problematic claim because many very good keyboards (Topre, IBM Model M) employ a membrane.

* Lifespan - I struggle with this claim as I've seen many very old membrane keyboards and I've had mechanical keyboards fail early. I think there are too many factors and components that go into a keyboard to claim they will have long life solely because the switches may be tested at millions/billions of actuations.

* Travel Distance - while this is mostly accurate there are a few "speed" variants that have been popularized by gaming brands. They may offer a superior gaming experience but some people may find typing on these keyboards to be cumbersome.

In my opinion there is really no optimal keyboard for everyone. What works for someone may feel terrible for others. It's really about what your personal preference is be it "mechanical", membrane, or heck even apple butterfly.

I am currently using a Tex Shinobi https://tex.com.tw/products/shinobi?variant=16969883648090 with 78G Zelio V2 switches.
Also compatibility with future hardware, aka bitrot.
> When going out, you could easily meet people working for those

It's not just that, you actually can't avoid them. If you write software and are walking someplace in a commercial part of San Francisco, basically every conversation you overhear is one you could immediately join in on.

Breaking up the clump is probably healthy for everyone involved.
maybe its not 100% one way or the other?

I love squash for somethings, but not others

today I brought in one big merge, 20+ commits , so don't squash it.

but I also have 20 "little fix" branches, with 1,2 commits each which I merge all together and squash in as one merge to main.
This video does a well explanation of how time and money consuming the hobby of having custom mechanical keyboards is
https://www.youtube.com/watch?v=xzWm40Tq4F4
I entered having a Keychron K2 with brown switches and I thought that was it, that was going to stop there and never invest in another one. But I started watching videos about how switches work, how people assemble their own open hardware keebs, how to lub switches, how to lub stabs, and then 1 year later I ended having 7 keyboards, plenty of switches sets, bough my soldering station to continue soldering diodes and leds to open hardware pcbs to make custom split rare keyboards...
man... save yourself if you're still out of this addiction.
Save your time and your money and go and hang out with people. Save your soul.
Assuming the snark, this is correct I think.
You should look at what people actually write 'smart contracts' in. It is so bad it seems like a parody of what you would actually want to do.
Many developers naively sell `git squash` using a clarity argument. By squashing you lose historical information: there are times when the content of a merge requires a paper trail, times when individual commits can aid to separate the portions of a merge you would like to keep versus those you would like to rollback. Perhaps in a 10 times a day release regimen you decide never to look for such history. One size does not fit all, however.

I prefer a "have your cake and eat it too" approach. Keep the commit history. Use readily available tools to squash when performing analysis should you choose:

`git log -p --first-parent` (git 2.31+ ability available in early versions of git with different syntax)
It's honestly about the same, cost wise. $100 for Apple, I've seen as low as $170 for Windows. If anything, Apple is worse because I require an Apple device to sign, though you can work around that with hosted CI.

Apple actually arbitrarily adjusts the price for non-US regions. For some reason they want twice as much from me here.
Ransomware wouldn't be a problem if the software industry took quality assurance seriously (or was regulated to do so), like every other engineering industry. There's little difference to me between an insecure program that allows hackers to hold your data for ransom, and a defective home appliance that occasionally starts electric fires.
> A big reason that stuff isn't replaceable anymore is because consumers wants some of the benefits that come w/ non-replaceable parts.

This may be true, but we shouldn't confuse 'a decision made by a product manager' with 'the customers want this'.

Some design decisions succeed because of the other strengths of a product (and the competition cargo-cult copies them), not because they are good design decisions. Some design decisions are made because they are more convenient for the vendor, not better for the customer. Some design decisions are made because of inertia. Pointing to any particular design trade-off in a successful product, and saying that 'Well, this is obviously what the market wants' is not always a correct conclusion to draw.

USB is unarguably the most successful mechanism for two hardware devices to communicate with each-other in history, and yet you need to flip the cable over three times before you can plug it in. Should we conclude that customers want to play the cable fandango every time they plug one device into another?
Muy Buen Producto
a
https://en.wikipedia.org/wiki/AV1#Hardware
>We used to be allowed to record tv shows on VHS legally. Look how far we've slid down the path of non-ownership.

What's changed that prevents you from doing that today? I'm guessing the answer is: "But that's a crappy alternative to what people watching Netflix or even renting DVDs are doing." And I would agree with that. (Though in the case of music, owning versus renting is still very much a legitimate choice at least for me.)
When I watch 4K YouTube videos in Firefox or Chrome on Windows, YouTube uses VP9. I don't see why YouTube could use the same 4K VP9 streams for Roku, like you suggested. Perhaps they have different requirements from partners for DRM content on YouTube TV?
In the end I just jumped. For me, thinking about how to jump optimally was procrastination. "Jumping optimally" was a fine-grained optimization whereas the act of jumping, itself, was a huge huge coarse-grained optimization.

Do what's right for you, but I jumped and never looked back.
> "The hackers were the Ryuk ransomware gang and they demanded we pay them 45 Bitcoin, which was about half a million dollars.

Make no mistake: this ransomware surge is 100% enabled / facilitated by Bitcoin and possibly other cryptocurrencies.

This would not have been so bad if cryptocurrencies would actually provide anything of really significant value to our societies, but no.

Aside from a mixture of Ponzi scheme, Pyramid scheme, and MLM + the energy waste, this ransomware is yet another terrible effect on our world.

It is time we effectively ban cryptocurrencies. Let’s end this madness. Please.

I am dead serious. I think cryptocurrencies and blockchain technology is the asbestos of the software world.
“I’ve been served legal threats by What3Words”
There are a class of engineers who have very little Linux experience, but use AWS extensively. For them, "Setting up a server" is always going to be more complex and frustrating than using the platform that they are familiar with, even when the AWS setup they come up with to replace a single server is way more complex to an "outsider".

Personally, I don't think there is an excuse to not learn Linux. It's usually the right tool for the job, and you can use tooling like ansible and AWS instances to get your stack cloud based, stateless, automated, yada yada buzzword . But I can't really blame people for using the tools they are comfortable with.
Either way it's bull as Roku supports VP9 already[1], there isn't a codec barrier as far as I can tell.

1: https://developer.roku.com/en-gb/docs/specs/media/streaming-...
History is full of things that people did not want to mandate via their purchases, but we as a society decided was important... so we made it legally mandatory.
Where did you get plans to remove subscriptions?
If only there was a way to have our cake and eat it too.

I'm assuming there is because I'm assuming those squashed commits are floating somewhere in the reflog and somehow connected to the squashed commits in a way that should still let you bisect if only we had a tool to make it not suck.

Alas, maybe someone with greater git-fu can inform us.
Does Porter support having isolated environments per git branch like Quovery?

https://docs.qovery.com/docs/getting-started/what-is-qovery/...
I would argue that the percentage of bonds should be your age is not timing the market in any meaningful sense of that phrase. (I also think that's too conservative an asset-allocation, but in any case "make a periodic rebalancing trade according to this preset formula" is the opposite of "time the market".)