skysight-inc/HackerNews huggingface dataset:
So a straight razor is the old fashioned, flip out single blade, need to sharpen kind. Not sure if you're intending to refer to that or not. Whereas safety razors are the two-sided head cheap disposable blade kind.

I can't talk too much about straight razors, I think they're a bit dangerous without a good amount of practice.

Safety razors are fine for below jawline shaving, though you will probably nick yourself a bit until used to it. I use a Merkur 25C and have a beard and I think it's excellent. Rarely nick myself. Could never use electrics or modern disposables effectively, they tended to load up and clog badly.
You're under no obligation to show your vote to anyone. Voting by mail only keeps records that you voted - not who you voted for - and that information is certainly not shared with your boss.

All voting booths I've seen had a curtain for privacy.
If the underwriter has every incentive to lowball the price, why on earth was Morgan Stanly selling its clients ways to short the Lyft IPO?

https://techcrunch.com/2019/04/05/morgan-stanley-which-is-un...
From the article:

Lisa Gallaudet, the landlords' attorney, said the smart lock was on a single door and that tenants were able to enter a numeric code to get in and didn't need an app. They'd also been offered codes they could enter without a phone
The specs look great except for a maximum of 16GB of RAM. Unfortunately higher-RAM options have been going away, particularly as manufacturers have moved to soldered RAM. The same has been happening with Thinkpads. I have a T460s with 20GB of RAM (4 soldered and 16 added). I could easily get a 32GB DIMM and have 36GB (it's been confirmed to work) and maybe 68GB in the future if 64GB DIMMS show up and work. And yet a few generations later the higher end X1 Carbon is limited to 16GB. I've seen the argument that soldered RAM can be lower-power so maybe that's where the market went. It's a pity because now that CPUs aren't getting faster at a high pace a RAM and SSD upgrade is a great way to keep older laptops working great.
Basic economics have failed when a company that has existed for over a decade without any ability to turn a profit IPOs. And indeed, I am all for using laws against abusive corporate entities.

I am also for using data protection laws (and not minimum wage regulations) to break the ability of social media companies to survive (or at the very least, rein them in). Have to use the right tool for a job.
This is not on by default.
Just by feel. I will miss a spot now and again but can sort it out by using a mirror.
Pragmatic? Well, we don't have mom-and-pop toymakers anymore due to regulation.
For me, it's less about waiting times and more about the omnipresent risk of the airline absolutely destroying my luggage (https://www.youtube.com/watch?v=5YGc4zOqozo).
You are correct if your goal is to maximize the amount of money you have.
If that knob is red-hot you are either dead or you don't want to go to the other side. It takes time for a knob to heat to scalding temperature. If you haven't opened it until that time you are already dead.
Rendering on Mac OS seems pretty irrelevant for embedded devices.
> This article reinforces my suspicion that the British, even the ones who supported the Remain vote in the referendum, simply have no idea what the EU is about.

Erhm, no. Some might consider those who supported Brexit "idiots" but most of them have a pretty good idea what the EU is about. (Which, by the way, is Elitarian empire building -- like for instance the United States)

> The British can just not comprehend the need for a united Europe in the modern world, where European countries are beset on all sides by many times more powerful rivals
> (Russia, China and now even the US is turning against us).

"Big bad US" and "big bad Russia" is what Brussels and the media wants you to think. People living in constant fear are much easier to control.

Putin needs the rest of the world a lot more than the rest of the world needs Putin. Without the sale of oil and gas Russia is pretty much done. Also the EU can be glad that the US is still more or less an ally because our armies are FUBAR. If China, whom by the way is indeed one of the biggest threats of the West right now but seriously overlooked by Brussels, would go offensive we have pretty much nothing to defend us with. This also makes the point of having a EU at all null and void, by the way.

> To think that the little nation-states of Europe can survive and prosper on their own like they did back in the days of Napoleon and Queen Victoria ignores reality for the warm fuzzy feeling of epic fantasy.

There were no "little nation states" in the time of Napoleon. He conquered pretty much the whole continent of Europe, tried to invade Russia (big mistake) and finally met his Waterloo at Waterloo. Seems you don't know a lot about European history to begin with...

> The EU's goal is to promote peace an the well-being of its people (Treaty of the European Union, article 3, par. 1).

I'm getting a vibe you never read Orwell or never really understood what he was trying to say.

> Therefore, the public conversation about the EU revolves either around irrelevancies

Yeah, let's never mention the irrelevant facts that the EU is lead by a public drunk, and as such even a bigger disgrace than Trump, and most of the officials signing in to get the money that comes with it and then return home (There's video evidence of this, and yes it pissed officials off to no end that they got caught on tape doing this).

> Their message was simple and to the point: "us versus them"

Bullshit. Their message was simply: "We want our fucking country and our own destiny back"

> so, it's all identity, bendy bananas and travel privileges.

And the God given right to choose your own destiny as a free people.

QED.
> low-overhead in-production profiling/monitoring/management

This is a joke, right? The management overhead for the JVM in production environments is huge. It's really hard to get it right.
i really really really like swift. it's by far the best language i've ever used but i wish it weren't so "monoculture" (ios dev). i guess this is good for that but i really wish the open source port of foundation were the focus of the community.
Well in either case, I'll just repeat: force push should always be avoided. Regular push without forcing can handle both of those scenarios, publishing commits to your team, and also backing up data to a safe location.

That said, making backup data in a safe location isn't what git was really made for. If you really don't want history to be there, you can use cp or rsync, or you can git clone -depth 0 from the backup machine, or just use backup software. There's "bup" which is a backup tool based on git...
It's the natural consequence of people clamoring to turn a simple hypertext engine into a full on application VM. Feature upon feature was piled on, producing a gigantic ludicrously complicated garbage fire the likes of which simply cannot be replicated by mortals, and to ensure this whoever is on top will keep adding to the garbage fire so no one can ever catch up.

Web devs and evangelists of the world, you brought this on yourselves.
> Why should I invest for the long term in these companies?

The pitch for Uber is that operating at a loss and aggressively capturing the market for point to point transit eventually puts their competition (mostly Lyft, often regional startups since the real opportunity cost to make an Uber competitor is so low) out of business that lets them jack up their prices.

Basically, aggressively monopolize markets and then drive prices up until competition resurfaces, run in the red until competition dies first from less cash on hand, then resume exploitation.

Its also hedging that self driving tech is far out enough to keep reaping profits from this cycle for some time. In the same way people go to Amazon first to buy something in many cases, Uber predicts with enough domination of the market for long enough people will just always go to Uber first for transport regardless of if actual better options exist at some point.
Thinking about myself when I was that age, the biggest problem is that they don't know what they don't know. (myself included)
And I'm still there, there's a ton I still don't know but looking back, it was egregious.

There is _no_ substitute for experience. That said, it's important to have employees of all ages. I just hope people can find a place to work that emphasizes building good teams instead of cost minimization because it's good to have a balance.
If I reuse blades more than once I get warts on my face. My DE Merkur does in fact cut me, and I have a thick beard and olive skin. I’m “swarthy” as they used to say in the old Hardy Boys books.

I admit I don’t use shaving cream or gel either. An earlier post mentioned that DE razors turn a 10 minute job into a 20 minute job. I have to admit I spend maybe 3 minutes shaving with a DE razor, and about 1 minute with a Gillette.
There are many examples where American brands gained or dominated in market share in China. GM sells more cars in China than in US for example.
Do you have evidence that my comment stems from years of developing a poor world view or entrenched bad coding habits?
Interesting.. I've never heard of licensezero. Will check it out this weekend. Thanks for the tip!
I feel like discoveries like this maybe are more of "we don't see a lot of sites that would take this much work" and less so shock at the amount of effort put forth but the wording gets spun around?

I agree with you, it doesn't seem unlikely that a community or multiple communities would put that much work into something.
I don't understand why uber's costs don't scale well. They make an app that drivers use. They're not having to buy cars or hire drivers to grow. They just need their app to function. What is all their money going towards?

Is all that money lost just subsidizing the cost of the ride? If they stop subsidizing the drive price, which they will have to at some point I imagine, will people just abandon the service?
I know little about EE (and I'm certainly not speaking for anyone but myself), but I believe Java EE has lost dominance not because of any corporate decision, but because it simply started losing ground to unstandardized open source projects [1], as opposed to EE's JCP. So people who liked EE wanted to ditch the slow-moving JCP in favor of a faster process, and one question was whether the new project will be able to change specifications of namespaces that are traditionally reserved to, and associated with, the JCP. In the end it was decided that no, they will not be able to change JCP namespaces (but can choose to maintain them until the end of time in addition to any innovation they do outside of JCP namespaces). The decision obviously disappointed some, but I don't think it's viewed as catastrophic (although some may think so). And I don’t think that the “negotiations have failed” so much as that either side wasn’t able to achieve what they believed was the best outcome for them, but an agreement has been made. You also need to realize that it wasn't a negotiation between Oracle and some grassroot project, but among multi-billion-dollar corporations, some of whom have fought Java standards for over a decade, so the process was both legally and politically complex. But now everyone can move on.

I, for one, am curious to see how Jakarta EE's current approach of what seems to be an internet-based, democratic semi-standard would work out, and if it can be better than both the JCP as well as more common centrally-controlled open-source projects.

Anyway, this is what Eclipse's director said on the matter:

https://twitter.com/mmilinkov/status/1125213654775889921

[1]: That post you linked to reminds me of those who blame Oracle for killing Solaris. Solaris is a terrific operating system, that was sadly killed by Linux long before Oracle acquired Sun. After a few years of trying, I guess Oracle decided they could no longer save it, and there was no point in continuing to throw good money after bad.
Let’s remember that “conflict with humans” means “will eat your children.”
Spring Boot with Webflux and any rx supporting libraries you can get your hands on
I'm not sure if it's a requirement or something they use algorithms to select certain new accounts for.
I'm just going to keep this simple and give you my perspective, which you can take or leave (feel free to ask more questions):

Spend as much time as you think you need to come up with an educated guess.

Build a proposal that quotes a fixed time for the project, but bill the project T&M. Include in your proposal a provision for overage, pro-rated at a daily rate.

Don't bill for scoping work. If it takes 2 weeks to scope your typical project, and those 2 weeks are dragging your practice down, what I'm hearing is that you should raise your rates on delivery, not that you should try to charge some secondary "discovery" rate for or (god forbid) try to bill at your delivery rate.
There are some interesting points there but many are inaccurate.

Difference 4 discusses the loss of antimicrobial colony walls. They coat man man hives, it’s there. There might be less but the amount depends on the age of the gear.

Difference 6 relates to hive entrances and how snow blocks them and they are the wrong design. This maybe true somewhere, but many places have no snow and good beekeepers adjust their entrances to suit the conditions and prevent robbing. This is superior to an uncontrolled entrance.

There is criticism of wax removal. Old wax spreads diseases and makes disease management harder. Yes, making wax consumes energy, but it improves hive health.

Point 18 discusses the human selection of larvae for queens, or culling of poor queen cells. Strangely, bees choose queen larvae poorly. If a colony is queenless they need a new one. The best queens are fed royal jelly early, but a queen is needed fast if a colony is queenless. The first queen to hatch is usually the winner so the older larvae fed jelly wins. These queens tend to be poor.

Human management of bees keeps them alive. Unmanaged they die, fast. Often bees are kept where they wouldn’t be naturally, so deaths may not all be bad, but humans go to a lot of effort to keep colonies alive by working with bees, not against them.
as the client, i would always split the project into 2 parts - a functional spec and a technical spec. my job was to interpret and write the func spec as a kind of pseudo-code version of what i thought could be built. then i would commission a fixed price job of interpreting the func spec and re-writing it as a technical spec ie, click a button and take the user to a summary of xyz turns into a bit of SQL. the tech spec must be written so that any programmer could use it to understand what needed to be done. then I'd ask for a fixed price quote to deliver on the assumption that i could get multiple quotes if needed.

the benefit is that my coder who wrote the tech spec should be very comfortable with what is needed and i get to sell a lower risk $$ to my managers.
A bit of reading online. A bit of trial and error. Only one error leading to a deep cut, and I think there was wine and jet lag involved.

With a hollow-ground razor, the most popular style, the blade is held flat against the strop or hone and the width of the spine holds the edge at the proper angle. This makes serious mis-sharpening less likely. It probably does help to have some knife sharpening experience though.

My method using a bench strop and diamond compound is not traditional, but I've found that as long as there's no actual damage to the edge, it always restores proper sharpness while more traditional methods with a hanging strop require sharpening on a stone every few months.
Not terribly big, but big enough: LibrePCB (https://librepcb.org/)
FWIW I was aware of the the reference and it wasn't lost on me. I was simply reflecting on current state of the shoe shining profession.
I'm not sure I can fully agree with the author's point. 'Don't feel bad that your company is running outdated and expensive technology with known vulnerabilities!' I'm not sure how else to read an article seeking to highlight folks running telnet and ColdFusion. Complacency here isn't serving your customer's best interests.

It's absolutely the case that HN / tech social media induces FOMO and Resume Driven Development, but it's very easy become complacent if you adopt such a viewpoint.
It's OK in the sense that it's not a security emergency, but, don't use HMAC-SHA1 (or HMAC-MD5, which is also in the same sense "ok").
We are a long way from diluting the IT labor pool to the point where it systematically depresses wages.

Assuming some sort of relationship between potential talent as a programmer and natural attraction to programming, then programming is already tilted toward the talented. Trying to recruit more programmers with early-education programming is going to add more mediocre/bad programmers than good ones.

And you need the good ones. Work that can be done by mediocre programmers will eventually be replaced by software doing what they used to do - software written by the more talented programmers. And the supply of good programmers is necessarily limited.
Amazon Centauri, its been renamed as part of a sponsorship deal
It's not outdated, it depends on context. Several modern languages, including Rust, Swift, Scala, Kotlin, and F# are built around having expressions as constructs (if, match, try, etc. are all expressions). Once you have that powerful feature it makes sense to write code in a certain way to make use of that, and it ends up being clearer a lot of the time.
Prosecuting people for doing that won't actually change anything, because very few people in emergency situations are actually thinking clearly enough to even consider laws in the first place.

Compare to airline seat belts: the reason they always have that demonstration at the start of the flight about them is because there have been cases where people literally forgot how the seatbelt worked in an emergency situation, didn't have the mental coherency available to figure it out again, and kept trying to push at the side of it where the latch release would be in a car.

A better legal approach would be to place limits on carry-on luggage in the first place, so that the physical possibility of delaying evacuations with it is removed.
I have noticed this phenomena a number of times. My theory is that the first article sparks people digging into the matter and related subjects further. This leads to them posting related articles. A bit of herd like mentality.
There were a few incidents where people were crushed to death by a panicked crowd trying to flee burning buildings. With that much force behind you, there’s no way to open an inward door. It’ll also generate a lot of friction between the bolt and strike plate, making a traditional doorknob hard to open.

The new-style emergency exit door is designed to act like a pressure release valve— if a person is pressed up against the inside with life threatening force, the door opens automatically and lets the fleeing crowd out.
It's not 'editing' the raw history files, but you're still presenting a false history to your coworkers. To me there are essentially two kinds of rebases:

- Summarizing history: squashing "implemented subfeature A.A" and "implemented subfeature A.B" into "implemented feature A"

- Rewriting history: moving commits around, changing the base commit, and so on

In my opinion summarizing history is acceptable, you're making a creative decision that certain information will not be useful in the review/when trying to understand the code in the future.

Rewriting, on the other hand, is essentially lying. You're creating repository states that never existed, and which you have never tested. In the worst case, consider the following history:

* F: (master) Merge branch 'component2'
|\
| * E: (component2) Fixed component 2's integration with 1
| * D: (component2) Merge branch 'master' into component2
| |\
| |/
|/|
* | C: (master) Refactored component 1's API
| * B: (component2) Implemented component 2 that depends on 1
|/
* A: (master) Base

Yes, it could probably be completely linearized, but that would be a horrible idea. Commit B will leave the repository in a completely nonsensical state. Sure, you could squash in E to mitigate it (since, luckily, nothing else happened in component 2 in the meantime), but then you're still stuck explaining what will likely look like a bunch of really weird design decisions compared to if you had designed against component 1's new API immediately.

Historical context matters. If in doubt, don't rebase. Never `git pull --rebase` blindly.
You are not alone. I really like KDE and enjoy using it mostly but it's full of bugs but every other day I'll attempt to use GNOME and I'm back in no time.

I'll share the display issues - something deep inside calls random() on monitor resolution and position - I'm sure!

I've switched to Arc Dark and Numix Circle Icons and it's not ugly anymore. I don't know why they still ship Breeze with that broken padding by default.

But it's really getting better every release.
See also: why are seats not facing backward?
I think it depends on the part of the community you speak to. Yes, they had a very unrealistic dig schedule, but they brought resource that most sites can't dream of to many locations that would otherwise not be investigated, and delivered full reports as well as proper Reithian television.

Source: archaeologist mother & sister, and appeared on Time Team myself... :)
> many companies that outsource to China have very strict QA

I do not doubt this for a second.

OTOH, recently we've even seen quality on Apple's Mac products deteriorate noticeably. Assuming Apple is extremely good at this strict QA, I wonder if some sort of China manufacturing sea-change has occurred.
Yep. MS has around 27MM shares out there for stabilization pot IPO. Once they blow through that, it's the market's game.
Chase payments constantly from the START. Make it the norm that you must get paid on time. People will often defer payment if you don't push them. If you can help it, try and get paid in advance - at my firm, clients must pay for the next 2 weeks of consulting, or their work stops. I know it sounds brutal, but my people need to get paid, and if clients can't handle that, then they're not worth having as clients!

Edit: clients who REALLY understand their business are better than those that don't. You want to work with people who know what they're doing, so that they can explain their requirements clearly to you. You'll be surprised at how many people can't do that, often resulting in them expecting one thing and getting another (and they'll blame you for it).
On the rare occasions I use shaving cream, it’s Barbasol, and I swear it feels like the most luxurious expensive concoction I could put on my face. Nothing feels better to me to matter how costly. I’ve literally spent about $30 on Barbasol in the last 25 years, and that’s largely because I have multiple houses.
Security cameras and barbed wire: Living amid fear and oppression in Xinjiang
On a similar note, I remember when Apple had a similar outage in the App Store [1], and a lot of my App Store bought software stopped working, claiming to be damaged. The workaround was to re-download the software again from the App Store, but because Apple doesn't let you download old versions, some of the apps had since updated to a newer macOS version than my machine could handle & I couldn't download them with the new certificates. Some of the smaller indie developers were gracious enough to send me non-signed non-App Store builds that I could keep using, but I did lose some software I'd bought. I haven't bought from the App Store ever since.

Considering Mozilla's certificate failure, Apple's cert failure, and the number of websites I encounter that have forgotten to renew their certificates, it seems like a broken system. Or a really effective form of DRM, I'm not sure which.

[1] https://discussions.apple.com/thread/7336980