skysight-inc/HackerNews huggingface dataset:
> manager says, "quanticle, I really need this to be done by Tuesday," and I know I'm going to be staying late until it's done.

At some point you have to grow a pair and create the workplace you want. (Or, y'know, unionize). Tell them to fuck off.

> But with Fibonacci numbers, it's like, I estimate a 3, manager nods and agrees that this task is a 3, and then it turns out that when I said 3, I meant that it'd take until Wednesday, but manager thought that a 3 point task would be done by Tuesday, and now manager is mad at me

They're explicitly not allowed to do that. If they're claiming to follow Scrum then that's a promise not to do that. At some point all I can suggest is "don't work for a liar". Of course that may be easier said than done.

> The old way sucked, but at least it sucked in an up-front and transparent way.

I agree that pretending to follow good practices while following bad practices can be worse than honestly folowing bad practices. But that doesn't mean that good practices are worse than bad practices!
> Eg. need to trim $x million of cost.

Let's start with that: the "need" to reduce costs. In another comment I used Google as an example so I'll do so here too. Google is specatacularly profitable on an overall basis and a per-employee basis.

Layoffs as a cost-cutting measure are largely virtue signaling than true cuts in costs, for several reasons:

1. Once you factor in severeance costs, it takes a long time to realize any of those savings;

2. Those layoffs assume those laid off were providing no value. It's hard to believe that 10K+ employees were providing no value. Whatever value they were providing is also lost, further defraying any supposed cost savings;

3. Mass layoffs tend to be hugely destructive to culture and have a long-lasting impact on those who remain; and

4. By the time any benefits are realized you're probably hiring again anyway.

The point of layoffs is to virtue signal to the market that they're "serious" about cutting costs and to depress compensation. These companies won't be getting inflation pay raises. They'll probably be getting minimal bonuses and 0-2% pay raises, if that. Refresh grants will be less.

But the real kicker comes from doing more work for the same pay. Whatever the laid off people were doing will become the additional responsibility of those who remain. Sundar Pichai has come out and said he's aiming for 20% increase in "productivity" (ie 20% more labor for no increase in compensation). Zuckerberg has said similar about Meta.

You see with inflation that there is fairly rampant profiteering: raising prices because prices are rising while reaping record profits. These mass layoffs are largely the other side of that coin. Wages are being suppressed due to some largely invented (to this point at least) "recession".

Now there are some other commpanies who truly do have to cut costs. They don't have a profitable business model and because of rising interest rates, the cheap VC money well is drying up. But all the FAANG companies are doing just fine but have seen (or arguably created) an opportunity to attack labor costs.
And those ex-McKinsey executives are not only primed to hire their former colleagues, but assuming they've been doing a good job, they're McKinsey advertisements at their current job.

Now that's a good deal for McKinsey.
> Tomato is a fruit, always was.

Are you genuinely incapable of understanding the concept of context?

> Sex is way more important in social context.

I sincerely hope that the vast majority of your social relationships are not based upon the promise of reproducing with them.
They were also already renting their GPUs on EC2 before.
No, they went East ... and kept on going until they were over China.
So you think it’s reasonable to have no idea what it will cost, or when it will be done, when building software? You think it’s possible to run a successful business that way?
Gah; markdown seems to have ruined my calculations; should read 4x7 and 2x14
There’s a thing in the wedding photography gig called a wedding hangover. Basically most of us are absolutely dead the next day after “just” an 8-12 hour wedding.

It seems stupid to a lot of people, but that many hours being hyper vigilant and stressed wrecks you. I did landscaping work as a teen on very hot days and that’s nothing compared to a wedding.
By definition it is 225% of what it was before.

Otherwise “increased 1%” means “massive drop”
Agreed. MIME came after SMTP, for example, and HTTP is used for all sorts of not-HTML-or-hyper-anything stuff. That statement smacks me of "wow, HTTP is a pretty good RPC, but too bad it's only/mainly for transporting HTML, shucks!". The name of the protocol is not very representative anymore either of how it's used or how anyone should use it. If HTTP fits the bill, then use it and move on.
>Then you haven't broken the problem into small enough pieces. You're not trying to deliver a finished product, only something that can allow vested interests to gain a better picture of what is being built, enabling them to provide feedback early.

This is called roadmap. Client provide feedback to roadmap. There can be few iterations. Interests of multiple clients are taken into consideration. Based on roadmap products are build.

I worked in companies that made telecom software. The kind that manages both business processes and operational aspects. There are no "smaller pieces" that can be delivered to show process. There are also no people who will care about it on side of telecoms, because they know what will be delivered. Those systems are upgraded once, maybe twice a year after very long verification processes. They influence how things are working for hundreds of millions of people. Sometimes stuff that life can depend on, like 911 calls for example.

I also worked in multiple companies that made telecom network hardware and various network security appliances. It's same story. Clients know roadmap. Roadmap implemented. If this is new product, maybe a few key clients will get some alpha/beta hardware to start working on integration into their systems. Besides this, people on client side are busy with their day to day work and don't have time or interest to provide continuous feedback, because they know scope of product to be delivered.
Good point. Makes a lot of sense.
That and their "sex sells" approach to marketing in the past has put me off using them.
When I was an undergrad, one of my professors was exploring “approximate” computation (forget what it was technically called). The gist was that you build mathematical circuitry that approximates an answer instead of giving you a concrete answer (kinda like floating point but also applied to Boolean algebra, integer math etc). The reasoning was that the approximation could let you reduce the power. I wonder where that line of research has gone.
I think your logic is flawed. Banner ads are explicitly permitted by the web site operator (they get paid for them after all). Plugins aren't permitted by the web site operator, however they are permitted by the user, who has to explicitly approve installation of the plugin. Same with malware browsers: the users chose those. Of course, the users were ignorant and clicked on something they shouldn't have, but still it's ultimately their own fault: they opted in.

It's different with Microsoft: MS never asked for users' permission to change content, nor did users ever expect it.
US Air Force AI Pilot Flies Real F-16 in Simulated Dogfights
what neck of the woods is that, as "i want to go to there". just one summer, i'd love to run around outdoors and not worry about mosquitos
It's not really what I meant by distributed. I meant more in terms of governance, though the underlying implementation should mirror than distributed governance.

Living close to Russia, then close to China for many years, I realised how western-centric my view of the internet was.

Internet was built on originally distributed technologies (DNS, BGP, etc) but the scale of this distribution did not expand with adoption. "Distributed" back then meant "a bunch of universities interconnected".

For instance, most root DNS servers and major TLDs are controlled by western orgs or governments. How could you convince non-western entities to rely on DNS to address their content, when e.g. the US can unilaterally order the disappearance of a domain?

Maybe the good question to ask ourselves is "would I use Outlook if it was made by a Russian company?" or "would I trust SSL if 90% of the websites I visit have a certificate from a Chinese CA?".

I think most of us would say no, and that scares me, because the way I see it, internet is more and more becoming just a bunch of separated "islands", with fewer and fewer bridges in between. I would not be surprised if in 10 years time, each superpower will have reinvented and deployed their own version of internet, incompatible with each other, with vastly different content and technologies, and each user will live in the illusion that they are accessing a worldwide network.

I would love to see a new internet emerging. Something that would be secure, opt-in anonymous, reliable, and unrestrictable by design. And I think for this to succeed, we will need to accept that we cannot have the same performance, immediacy and simplicity as we have now.
Even better: it has an optional source generator now! So, at compile time, C# can be generated. This can be at two levels: (1) just generate metadata so runtime reflection is not needed, or (2) also generate code that does the serialisation or deserialization itself.

Pretty cool!
then add additional specifications to clarify ambiguity when observed

That's such a clean, almost clinical way to describe, "After the software has caused several billion dollars in trading losses, bankrupting the entire company." (https://en.wikipedia.org/wiki/Knight_Capital_Group#2012_stoc...)
I believe that's super easy to answer: VC money.

Salaries in the US are a multiple of what they are inside China. And for the top 0.1% on the skill scale, the factor is probably 10x to 100x. Now not everyone reaches that level and many fail and burn (or suffer through un-payable student loans for many years), but still the few people that make it into OpenAI are probably paid 100x of what they could earn in their hometown in Asia.
Yup - this is the correct answer
What if all the text in your comment was approximately the correct set of letters in each word?
They were confused because the argument was made by Eric Schnapper, a very elderly law professor who has not argued before the court for a long time. He was very clumsy and disorganized in his speech. Listening to the oral argument made me confused too.
Except it does, quite intentionally: It was specifically created to prevent what happened to Nixon from ever happening again. He was forced to resign from the Presidency, or he was going to be impeached (by both Republican and Democratic Representatives) and convicted (by both Republican and Democratic Senators) for the crimes he commit and ordered while in office.

And it worked, by ensuring the Republican base and politicians were in lockstep with each other as well as the policies supported by their major donors (such as Fox’s owners), so when another President commit extremely serious crimes in office the vote was almost entirely party-line.
Bot spam on Tumblr is rampant even if you don't have many followers or post much.
yep. that's 100% a strategy.
> There's no intrinsic value in having 50% of the system working at 40% of the deadline.

In practice that's usually more valuable than having 100% of the system working at 100% of the deadline. Almost all deadlines are fake, and most requirements are too.
> I want the bare minimum that will run normal websites. I know that will break some pages, I'll accept that

If you are willing to accept quite a few pages breaking, Lynx is probably the smallest and fastest browser:

https://lynx.invisible-island.net/
Well, for one, UDP brings the U. It's called the User Datagram Protocol because (at least on UNIX-like systems) unprivileged programs can almost always send and receive UDP datagrams, but in general cannot send and receive raw IP datagrams.
BTW, Bellman actually coined the term curse of dimensionality [1]; got that confused with combinatorial explosion since it is a synonyms in the contexts I typically encounter it [2].

[1]: https://en.wikipedia.org/wiki/Curse_of_dimensionality

[2]: https://en.wikipedia.org/wiki/Combinatorial_explosion

OpenAI has a pretty good introduction to the Bellman equations in their Spinning Up in RL lessons [3]. Sutton's work in Reinforcement Learning also talks about Bellman's work quite a bit. Though Bellman was actually studying what he called dynamic programming problems his work is now considered foundational in reinforcement learning.

[3]: https://spinningup.openai.com/en/latest/

Uh, and for the dual mode observations the person that brought that to my attention was Noam Brown, not Bellman or Norvig. If you haven't already checked out his work, I recommend it above both Norvig and Bellman. He has some great talks on Youtube and I consider it a shame they aren't more widely viewed [4].

[4]: https://www.youtube.com/watch?v=cn8Sld4xQjg
Purchasing power for the middle and lower have been declining for 50+ years.

Total wealth is being wildly redistributed to just a handful of people.

I don't see how the average US citizen can afford to raise a family.

I've seen janitors sleeping in their cars because they can't afford rent.
1.25 cost is reasonable, and is solvable by adding a buffer. Taking 2x the time is ridiculous, and a professional should be able to do better.
it's absolutely the other way. the dense rot resistant wood from older forests was basically mined away by companies, like wyerehauser and others, over the previous 3 centuries.
Su is just talking up AMD’s strengths, many of which come care of TSMC and for which the original R&D was largely funded by Apple. She is not wrong, and AMD has certainly made large gains in HPC recently, but AMD does not monopolize all possible paths to success here.
We have know this for a long time. This is one of the benefits of ARM64 CPUs as they require much less energy. What's new about his point?
It's not confusing or ambiguous, it's just incorrect. 125% increase means 2.25x multiple. There is no ambiguity whatsoever. It never means 1.25x.

The fact that the article seems to use it to mean a 25% increase just highlights that TechCrunch has bad writers and no editors.
after a good nights sleep, I think I mixed up pali / sanskrit and the monk I am referring to surely considers himself "Suttayana" :-)

I never really looked into Tibetan buddhism tbh.
I think you're right that he's "right", but the writing is shooting itself in the foot here. I agree that there's a mostly-unexplored middle between TCP & UDP, but you need to not utter things like "HTTP is bundled with HTML". I also think RPC is a poor label for "request/response" protocol (HTTP is request/response, and many of the problems here apply to HTTP too … but it isn't RPC).

I'd like more discussion of the contenders in the space: why do they not work? QUIC is barely mentioned beyond "we tried it and nope". SCTP isn't mentioned on the OP at all, but if you click through the Homa stuff a bit, it's written off as "a WAN protocol" — whatever that is? I get that his focus is datacenters, but "WAN protocol" is what I feel most of us are interested in, and I don't immediately see why WAN vs. DC matters¹.

What I'm also not getting from the Homa page is … what is the protocol, what are it's packet structures? Is there no documentation? (I've not hit all the third-degree links because I'm not a spider, but nothing seemed relevant or it seemed a little relevant but didn't hold the answers.) The old adage about data structures over algorithms seems to apply:

> "Show me your flowchart and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowchart; it'll be obvious." -- Fred Brooks, The Mythical Man Month (1975)

¹I'd also want to know why a good "WAN" protocol that solves the stated problems wouldn't equally apply to the datacenter, modulo needing some adjustments around assumptions made about the network's latency and maybe reliability: a DC network, I'd hope, is going to have much lower latency. But like Raft timers, it seems like a by-use-case adjustable constant.
Depends on the company.

When I worked for a larger company with a pretty mature product, this was true - deadlines were internal and arbitrary. It also helped that the product was more of a “nice to have” for our customers than “absolutely crucial” - they didn’t truly NEED anything it did (it was software to make social media marketing more efficient).

But I’m now at a smaller Enterprise SaaS startup, where the product is absolutely crucial to the customer’s work (core operational software for public transportation agencies). The reality is that the product isn’t yet mature enough to close big sales without making sales commits. I dislike sales commits, but we’d legitimately lose every big RFP unless we commit to adding the ~2-5 features they really, truly need that we don’t yet have. And sales commits come with real, external due dates, that you need to be able to meet if you don’t want to piss off your customers. You need to be able to say “yeah, we can build X by date Y”, and then actually deliver on that.
Put another way: if AMD (and especially Intel) don't do something about this they're going to get completely eaten alive by ARM.

The amount of processing power available in a modern smartphone is truly mind-boggling. I'd love to see a chart showing the chip cost and energy cost of the power on an M1 chip in each previou syear. I would guess that 30+ years ago you'd be in the millions of dollars and watts of power but that's just a guess.

As we see from the modern M1/M2 Macbooks, these lower TDP SoCs are more than capable of running a computer for most people for most things. The need for an Intel or AMD CPU is shrinking. It's still there and very real but the waters are rising.
Hang in there, big guy.
Normal DNS will switch to TCP for any large request and has done for quite some time.
A lot of young people want the experience of working abroad, they just want into live in and experience another culture. Not really economic refugees (yet). I did this in china for 9 years and it was a great life experience, although my compensation lagged a bit compared what I could make in the states (now working for google to catch up).
He gave a well-known talk with that name -

Hammock Driven Development, Rich Hickey, Closure Conj 2010

https://www.youtube.com/watch?v=f84n5oFoZBc
I've seen it argued that it failed a lot more quickly and cheaply than most comparable projects at comparable companies.
Weird how emulating TPS never includes lifetime employment. Agile is a talent attraction / retention device more than anything else these days.
Firing full-time employees in Japan is quite hard. If the company is taken to court, the burden of proof is quite high.

Disclaimer: I'm not a lawyer, so all that I say here is my personal understanding, from working in Japan, but also from talking to lawyers about this.

Firing an employee due to lack of competence or bad performance is permitted by law, but practically unheard of in practice - the bar for proving this is quite high.

Firing an employee due to misconduct is possible, but the bar is quite high. Embezzlement, getting kickbacks or getting into trouble with the law (outside your job) are common causes for termination, but I've even heard of cases of embezzlement and kickbacks where the employee in question was demoted instead of being fired.

Firing an employee due to the company's financial situation is often referred to as Risutora (corporate restructuring). That's perfectly doable, but the bar again is high. If the company is taken to court, they will have to prove the economic necessity for reducing their workforce and that they tried anything they can before they resorted to firing people. This includes:

- Offering a voluntary resignation plan. This means the employee reigns and get some monetary compensation.
- Cutting other unnecessary costs besides salaries (otherwise they cannot prove economic necessity)
- Selecting the employees that will be fired based an objective and fair criteria, no random culling of 10% of your workforce.

Since the bar for all of these is quite high, employers in Japan will more often try to negotiate voluntary resignation plans or (unfortunately quite often) bully their employees into resignation. The bullying tactic involves demotion, changing the job's content or trying to harass the employee in various ways until they decide to quit. This can also be challenged in court, but this tactic apparently shifts more of the burden of proof to employees.

The most common tactic big companies use in Japan to avoid all this hassle is to just not hire all of their employees as full-time employees. A great chunk of the workforce in Japan nowadays are fixed term contract employees, part-time shift employees or outsourced employees of various types.

Edit: I also have to add that from my personal observation, IT salaries in Japan experienced major growth over the last 10 years. YMMV depending on the type of company and the industrial sector, but if we focus on Japanese tech-focused companies (Yahoo, Rakuten, LINE, Mercari etc.) the average yearly salary grew by a 30% or so, and on the high-end you can see international companies and some Japanese tech companies offering senior positions at 20-30 million JPY / year. That's significantly lower than US salary at tech hotspots, but seems quite in line with salaries in Europe.

https://japan-dev.com/blog/software-developer-salaries-in-ja...
> I don't understand why people are so confused about permissions.

Ask the not-tech-savvy.
Webhooks with message brokers and Convoy
- State management: not necessarily in my opinion. This is not React. Don't use tools you don't need, don't apply principles of completely different libraries. Work with cascading parameter and contexts instead.

- Runtime extensibility: you can do whatever you want in C# so you do you. In addition there is also DynamicComponent now, which is what I believe you are looking for.
I thought this was already known? What did this study add?

> The team found that tabanid horseflies are attracted to large dark objects in their environment but less to dark broken patterns. All-gray coats were associated with by far the most landings, followed by coats with large black triangles placed in different positions, then small checkerboard patterns in no particular order. In another experiment, they found contrasting stripes attracted few flies whereas more homogeneous stripes were more attractive.

The paragraph before this quoted paragraph seems to imply this study addresses the why, but for the life of me, I can't understand how this paragraph answers why.
Privacy is bundled under Trust & Security. I don't have precise numbers or estimates, but basically every Google product area has a team of Technical Privacy Engineers, TPMs, TPgMs, and VPs. They are the arbiters who can block a production release if privacy and security issues are discovered and not remedied.

No other company I can think of has invested in such a rigorous Privacy review and support structure in an attempt to reduce risk. Other BigCorps do take it seriously, but get by with much less investment. Despite this, FB et. al. are keen to poach Google Privacy employees, because there are very few Privacy Engineer in existence and Big-G pioneered modern day corporate privacy efforts. Google is a huge target for hacking and public criticism or even loss of human life due to product decisions, especially because the products are so ubiquitous and widespread (browser, mobile OS, search engine, Gmail, ad network, etc). See subjects such as Differential Privacy.

Source: I have a few friends who've worked in the G-Privacy org.