skysight-inc/HackerNews huggingface dataset:
> how do we address issues where there's implicit bias being applied to our work?

my experience is that most workplaces and social spaces I'm in are systemically liberal, "reality has a liberal bias" abounds
3bi USDC Print
I see your points, but I disagree. FWIW, I also adopted the squash-merge only strategy with no regrets.

> Squash merge has the major disadvantage of getting rid of valuable meaningful git history.

It's not lost, at all -- it's in the branch it was squash-merged from. The point is that the topic/fix/experimental branch will likely have lots of history, including discarded ideas and other 'meanderings'. Every commit in that branch is meaningful in that it was a discrete step in that path. But, eventually what is _finally_ in that branch is what is relevant when merging to master. All that extra history in master would create confusion (and has for many in projects I've worked on).

If the discipline is that every commit must be a meaningful, viable point _in master_, then a merge of the history would make sense -- but I've never seen that possible (or even desired) in practice.
I don't understand this at all; I didn't think the mico-op cache was visible to code written for the x86 ISA at all. Can anyone explain to an idiot (me) how something in micro-op cache can become visible to the outside world?
He also had an infamous Fiero with a "hot vapor engine" that was claimed 50+ mpg and 250hp (when the stock 4cyl made ~90hp, it was the 80s after all): https://www.legendarycollectorcars.com/featured-vehicles/oth...
I've lived on minimum wage before. Those numbers are not realistic.
>I think you vastly overestimate the number of phones that become waste due to using glue on parts.

Okay, this is your view, and we have a disagreement. We'll just have to agree to disagree :)

Also, its not just about glue vs nuts/bolts - Please consider the larger picture here about repair.

>It's also not hard or terribly expensive to get most broken phones fixed at plenty of repair shops.

That is not accurate, Apple for instance, chokes the supply chain by banning sale of components to repair shops. They prevent replaced parts from working by employing DRM. In any case, you're missing the general point. Right to repair isn't just about phones. We're talking about a common movement across multiple industries - Agriculture, Appliances, Automotive, Consumer Electronics, etc, etc. You can find more information here - https://www.repair.org

People don't make their decisions in a vacuum. They know they can repair their laptop, their PC, their car, etc. They know this based on their experience and experience around them. We need to promote the same mindset for other consumer electronics.

In any case, any added change will force the companies to innovate their assembly technique to reduce costs - just like every industry does when there is a new environmental regulation. The reality is we are seeing piles and piles of electronics fill up the landfills, and we need to do more to address re-use, repair and extending the lifetime of devices - This is the just one component of an overall plan to reduce e-waste.
In the original post you state

> For now, it seems like DEMOCRACY is the best thing to prevent wars.

I'm not interested in throwing punches, however I don't think your claim is coherent

Twice now you respond with a loosely related objection about the definitions of terms used to describe 20th century philosophy and geopolitics

You claim a certain locus of power is best able to prevent war- I point out that this same power has been at war across the globe, in some form or another, for almost a century- is this not a contradiction you see fit to address?
I've found this: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5610684/

Facebook use after acute social stress impair recovery of cortisol levels. I translate it as "Facebook use after social altercation makes stress longer".

Thanks for idea!
So what? That doesn’t prevent changing the batteries. I have done it myself, and Apple will do it too, as in fact do many third parties.
“Buying the dip” sounds brilliant in theory but it fundamentally requires holding on to cash outside of the market waiting for that dip to happen. An order of magnitude more gains have been lost waiting for dips that never come than have been made holding onto cash waiting for those dips.

I have a friend who sold it all in 2017 expecting the crash to come any day now. He’s still holding on to cash waiting for that dip. I’m sure in early 2020 he felt prescient and that this gamble would pay off. Only it didn’t, and he likely missed the one opportunity he had to minimize those lost gains. Not only does buying the dip require correctly guessing the bottom, but by definition you have to have the constitution to put it all in at the peak of bad market news.
Timing belts are toothed, and if installed correctly they will never slip. Modern kevlar timing belts are near-indestructible under normal use. The real problem is the pulleys—once those bearings wear out, they can seize, causing the belt to slip or even break.
What I learned after a few hours with LMMS on Linux
Unfortunately, I can’t think of anything. I grew up not-quite-orthodox (in a stream of Judaism that doesn’t really exist anymore) and that provided a, in retrospect, very interesting slightly outsider vantage point.
You're comparing mass to volume in that last paragraph there. Based on a quick google search, that 1 kilogram of hydrogen is going to take up 3.4 gallons as a cryogenic liquid—so even more as a compressed gas.

Source: http://www.uigi.com/h2_conv.html
From the article, this person has done over 4,000 interviews. Their primary job is to talk to people, find out as much reliable information as possible to allow them to decide whether they are the right fit for the role. When this is your job, you need some framework/toolchain to do it in a consistent manner.

The problem (as many people here would frame it at least) is that unlike engineering, the best practices are very soft and subjective to each person, since the perception of another person is through your own lens. So this author is trying to convey the importance of having multiple lenses to view people through, so you have a higher chance of seeing signal from that person, rather than reflected signal from yourself.

I found it very helpful (and I am prone to dismissing people that do this as scummy/manipulative when I encounter them), and made me a little more understanding.
Sure. But labour is only a third of costs. And given the relative bargaining power of landlords, owners, and labour, the flow through to retail price might be less than you think.
Sincerely: what is bad?
Do they know it's a warmup and how much time you expect them to spend on it? I can easily imagine doing the question methodically and talking through my approach, and spending 20 min to do so. And I can also see the value in a candidate that approaches it that way, vs one who fires off the answer without doing some planning, even if it's an easy question.

I dont have context to know how you're asking it, but if you're not already, be clear about what you're looking for in the answer and the amount of time / effort you think the candidate should spend.
Just talking about the RX-8 brings back great memories - what a strange, yet beautiful car!

The cat blower, and the subtle whining sound it made when you started up cold was one of the ways every RX-8 owner was hazed into the fold... after calling the dealer or posting on a forum and finding out it's entirely normal!

Other oddities included how it deliberately burned oil (scaring new owners into thinking they had a serious engine problem), and how you were required to drive it hard to clear out its engine ports (multiple Mazda mechanics confirmed this factoid) - driving it like a normal car would literally clog up the exhaust ports and cause a loss of power (something to do with the lack of moving valves). If memory serves right, it had only 3 (!!!) moving parts in the engine, and was perfectly content to hang out at 9,000 RPM all day - that's incredible.

But, it seems the issues Mazda had maintaining it's emission certifications, and warranty issues with those apex seals (mine had 3 engine replacements over it's lifetime) eventually caused it to be retired. I was sad back then, and still sad we don't have a new improved version - there's really nothing else quite like it out there, not even the RX-7. It really was/is an enthusiast's car.

Good luck on your project - sounds like a fun one!
You'd need to add "no spurious HR complaints against people who disagree with you" apparently.
I don't really care what people do as long as they understand one thing: the entire point of keeping history is to be able to track regressions. Seriously, give me one other reason to not squash master down into a single commit every time I commit anything. If you understand the purpose of history then you'll understand it's important to keep it in order and then you can make a decision about how you keep it in order. Personally, I think squashing branches down leads to unnecessarily large commits. Smaller commits are better.

> Commits are essentially immutable.

Commits are immutable in the strictest possible sense. As is any other object in git. Not only that, you can't delete objects either. Every git repo in the universe together represents one giant, immutable, append-only object store.
I said that it would reduce demand, not that it would eliminate it.
Isn’t it back to being unacceptable to be transgender and in the military because of the previous administration right now?
If you are a cook, spending a ton of money on a knife that cuts well, is balanced and — most importantly — you like to use is totally common and normal. A cheap kitchen knife from ikea probably would also work for them — but this is what they interact with, so spending money there is totally reasonable.

People on this site probably interact with computers much more than the average person, and many type stuff into their machines for the majority of their days. I don't see why it wouldn't make sense to get yourself something decent that feels good to interact with there.

Tiny annoyances multiplied by a hundred times a day, 365 days a year add up. And even if it is only that slightly mushy Ctrl key or that spacebar where the right stabilizer is weird because the thing fell off the desk once.

For me a mechanical keyboard must be sturdy, heavy, with no flex of any kind. Preferable with black linear/silent switches, something that you can punch in hard or type completely silent if needed. Not a piece of plastic that moves around on the desk.

Maybe the fact that I am playing musical instruments (and work in audio) plays a role here. Tactile feedback is very important to me. I don't need a click, just very predictable and reliable responses that don't distract me when I am in the flow. I need a keyboard that can be silent if I need it to be silent.

That alone (for me) justifies spending more money than usual people would spend on a keyboard. It is not hobby to me, it is a tool. But a tool I enjoy using and that works for my use case. Sure I could use any other keyboard. But I don't have to, so why would I?
Especially because apple has a lot riding on their use of crowdsourcing even though they have a privacy stance.

Personally I think privacy and crowdsourcing cannot go together, no matter how much algebra and privacy boilerplate is thrown in.
I don't find those talking points convincing.

For one, even with your statistics, half of folks employed are school-age. Also, poverty is measured by household. Confusing the math isn't a good way to make a quantitative argument.

But mostly your argument is a semantic trick around the word "poverty" to rationalize weighted terminology.

Again, I have strong feelings that employers should be conscious of the lives and prospects of their employees. For instance, having policies that lead to irregular patterns of night and day shifts that have to be unhealthy long-term. But we can have rational discussion about these issues.
i think your website looks good. the subtle animated gradient on the rectangle at the bottom of the page is a nice touch. i like how straightforward the page is. nice work
Minor point, he's a Ruby/Rails programmer, or was last time I saw him.
Screenprinting multiple colours, and like additive, point registered techniques. Higher points for things you have to do in some sense "backwards"

Knitting, writing knitting patterns. Both iterative and recursive qualities inherent in knitting complex clothes (mathematicians might call them a manifold)

Most games of patience. Many games like "nine man morris" or "solitare" puzzles, Rubik's cube (group theory)

Rowing, cycling. Cyclical repeated path following.

Train, carriage, aircraft and bird spotting. Sets, set theory, groups, sequences. Yes, obsessive behaviour too..

Cooking. Generating complex recipes
Switzerland has had programs giving methadone and heroin to addicts for more than 20 years now. They've been a success; heroin use has plummeted since it's peak in the 90s.

One reason for the success is that giving out free product kills the local market; many users finance their use by selling to and actively recruiting new users.
Incentivises potential agitators to leave peacefully and on good terms. If you implement a no-politics policy in a politicized workplace without an easy to use escape hatch, you risk creating a fifth column in your company acting against your interests. It may seem expensive in the short term, but it saves a headache later on.

The alternative is the gory legal and political process of executing a targeted purge which may create controversy, sympathy, and miss more quiet actors.
I’m glad to hear that your forum is functioning well. That being said, your description of your policy on ad-hom./insults seems overly reductive to me.

If I said Trump (or some other political figure, I’m just following from your example) was a fascist, rather than a Nazi, then undoubtedly that would also be viewed as an insult by many. But it’s a position that I could try to defend by looking at the characteristics of fascist groups, and showing how they could also apply to Trump. Trump would undoubtedly never self-identify as a fascist, but if he fit all the conditions to be a fascist, then it seems naïve to say “Trump is a fascist” could not be a statement of fact just because he disagreed with the label.
You can already do this today with iPhones and iPads and the police won’t do anything
Well, that's kinda where 8051s get weird (not by a stretch the only way it's weird). 8051 performance is more '2 dimensional' in the sense it relies on clock speed as well as instructions-per-tick.

The 'classic' 8051 is (over simplifying) a 12-clock ticks per instruction processor. So you pretty quick had the second source providers introducing 6-clock and eventually 1-clock per instruction variants, with commiserate increases in speed. And then they jacked the clock speed.

So now you have '100 MIPS' 8051s, running at high clock speeds and 1-cycle per instruction.
I was a teenager working a minimum wage job. I also had to pay for housing, meals, healthcare, etc. Don't assume a teenager has a life less complex than yours.
[Edit: Didn't see that you started answering my last question before I wrote this, about the operational implications of trying to eliminate everything that could be considered inadvertent discrimination. Going to just leave this comment as is, as I do think the utilitarian/deontological thinking about product development processes is an interesting quandary in today's climate :) ]

Given this thinking about inadvertent discrimination, and that the word 'discrimination' is very much coded as a 'bad' thing, what should be done about it?

Should any website/product that launches without being perfectly operable for every single user be sanctioned in some way? If not, aren't we supporting inadvertent discrimination? Isn't any allowance of inadvertent discrimination a bad thing?

Should there be some sort of utilitarian calculation with it? Or is it strictly a deontological thing? There can be no discrimination, therefore, we must not allow or we should disincentivize product development processes which release versions before they are equally workable for everyone?
Lot of people bring up the Nikkei but averaging in money in was still better than holding cash over a long enough time period. I highly doubt anyone bought at the peak and then never bought again afterwards.
Yes. There are many ways to achieve the same thing with git.
You have apparently never had the benefit of a properly run git repository.

Our master has straight history. We always rebase to merge a PR and we have build scripts that check this as well. You will not be able to merge a PR that tries to get more than one commit onto master, if the commits touch more than one of the modules (we have a monorepo with lots of individual services). Until the PR has been approved we leave individual commits on the branch though as that can be helpful.

I have not had to "mess" with rebases ever. Most rebases apply cleanly and if they don't the conflict resolution is mostly very easy. The 'hardest' conflicts to solve were actually in the end the easiest to solve, because all you had to do was to `git rebase --skip` the appropriate commits. Of course some developers that didn't know better spent hours trying to do those conflict resolutions and complained loudly. Fortunately they were that loud, so we caught it and just did the skipping. Everything applied cleanly without any conflicts after that.

It's pretty awesome to have one commit per ticket on master and especially if something goes wrong. I can easily `git bisect` to find which ticket introduced a bug or a regression and I don't ever have to mess around. All commits have to have a ticket number in the commit message.

It also enables firefighters to almost mechanically solve production issues. Prod is broken after the last production deploy? There's very very likely only one new commit since the last deploy before that (or maybe a few). In any case, just revert to the commit of the previous deploy, lock down the deployments and now you have time to properly solve the issue without time pressure. If there was more than one commit and you can pinpoint which of them caused the issue it would even be very easy to just revert that one commit and let deployments continue. No dealing with 27 commits that make up one ticket.

Know thy tools!
> But watch out for technology and automation...that is the part of the equation that has been "solving" the labor problem for some time now...

This claim in particular was examined in studies on minimum wage increases, and found that increases in the minimum wage had no impact on the adoption of automation[1].

[1] https://research.upjohn.org/up_workingpapers/260/
Rustical – calendar CLI written in rust
rutical its like a cal command line but minimal and uglier
> automation is expensive.

Especially without right to repair!
I have two separate mega huge employers and they both have similar approaches on this matter.

My bank employer’s approach is maximum inclusivity and mutual respect. That generally mean no politics just because it isn’t professional. Religion is a grey area. If religion is an excuse for social gatherings and celebrations then it’s fully allowed so long as everybody is allowed to participate. If a religious focused context is cause for distraction or disagreement then the conversation isn’t professional and the behavior, regardless of the religious content, can be punished.

My military employer is absolutely adamant that politics must be far away from the office. They also strongly nurture and require maximum inclusivity. Their view on religion is maximum support for any professed religion or faith as necessary to advance the religious Liberty of all employees. They have dedicated employees to ensure and guarantee religious support and exercise for any employee that requests support.
Because they're not equally important. Most engineers don't add billions of dollars of value. If a miscellaneous engineer resigns, it will have in most cases little impact on the prospects of the company. Most add only incremental value. The superstar seven figure ICs do get paid as such but they're rare, most people aren't that capable of that much value add as an IC.

The company made billions in profits. That could be due to a number of reasons. IP, relationships, network effects, scale economies, regulatory capture, brand equity, etc.
It sounds tricky, not because it's hard, but because of all the exceptions to date format.

If we simplify it to be fake dates by assuming all months have 30 days, and the input is MM/DD (i.e. 04/30), then it's trivial, multiplying MM*30 + DD.

That said, the solution for the real dates, would just be a bunch of maps ... month numbers mapped to how many days they have, { 1: 31, 2: 28 }, etc. Same for leap years, another map. And then it's the same formula as above but looking up the values first.

In other words, this may be hard for the wrong reasons I feel. Junior candidates would take longer, but it's bcause of the exceptions of date format. Perhaps you can think of a similar problem that uses something other than dates, and that has more regularity in its type.
What about all of the content on the DVR which is unwatched? Missing out on some channels? Worse features? There are costs but they may not be monetary. Some people would prefer plonk down a one-time $50 or whatever rather than give up recordings, channels, or other features.
People who choose to do business by selling a phone or opening a restaurant choose to do so within the context of the rules and regulations that society imposes on businesses of their sort. If they or society don't like the current rules they are free to lobby congress.

There isn't any inherently correct answer just a variety of possible answers with various outlooks for many parties.

I don't think anyone regards a restaurant as a market for silverware and plates where different vendors compete but Apple explicitly clearly runs a market for apps which is a notably different situation from selling burgers.

There is everyone reason to suppose that burgers ought to be regulated differently from software and regulators, lawmakers, and courts aren't robots required to interpret law like code. Reasonable results require both the literal text of the law and common sense.

A lawsuit attempting to force Burgerville to allow third party plate rental would run into the common sense conclusion that the Burgerville isn't presenting plates inc an opportunity to do business with customers they are simply offering them an opportunity to sell n plates to Burgerville for usage in their business.
I think at root this might be about authority. Today's SV culture seems to challenge authority and hierarchy (the boss, management) in favour of the team, flat organisations, and fair play.

When the boss makes a decision then, the boss often gets challenged and the challengers feel right doing so. Disruption, innovation.

All this is new but we think it's normal now!

Businesses used to have clear lines of authority, heirarchy and the boss was on top, made the decisions and was generally obeyed.

I wonder how management academics will write about this period of time in 20 years or so.
I am the WebCall developer. I can see a number of people are using the service right now. However, I can not see what is happening on the P2P links. If you run into issues, please let me know. Same if you think there is anything missing.
Wouldn't the ideal situation be firing someone for _acting_ as a homophobe (which a no-politics rule encourages), rather than _being_ a homophobe (or having any other undesirable trait)?
Well, that seems like a generous and reasonable solution to the problem.
Timing belts have teeth.

Occasionally chains are used instead; more expensive and heavier, but more durable. You do need to maintain the timing either way it it will destroy the valves.
Basecamp's political talk ban prompts mass exodus
That was the FAANG stocks doing the thinking