skysight-inc/HackerNews huggingface dataset:
This is true.

I have had java professors never explain subtype relationship or interfaces properly.

Without understanding basic concepts that underlie programming languages, mechanically teaching syntax (with language specific OOP buzz words), is ensured to only confuse students when learning new languages.

Rather teach them how polymorphism works, what's a virtual function and a function pointer, any student worth their salt will understand why things are the way they are.
yale could afford to make tuition free for everyone in perpetuity using just their endowment.
You don’t exactly need to run a cluster per service ;-) Instead you can choose to collocate services who belong together and form a „domain“. But don‘t go the route and build the almighty one Kubernetes cluster where all your domains run in one single place.
All code should be public always. Easiest solution to this.
Large segment? Could I get some source on that statement?
Cliff, Thanks for being in this world. I still own my hardback copy of "The Cuckoo's Egg" from 30 some odd years ago. I also talk about the events that unfolded in that book to my students! It's a great story!
Why?

Because if you live in a great place, all those things are available to you without discontinuity regardless of WHO you work for. The reason that there's such a disconnect between 20-somethings and everyone else on this issue is because everyone else has been through it already. Sure, there's a possibility that you will remain friends with people at your former place of work after you leave. There's also a VERY strong possibility that the people who are at that workplace are socializing with the people AT that workplace. The longer you stay away, the more people you DON'T know, and the less you fit into their social crowd.
The main problem is that doing a good estimate is essentially "doing the design", but everyone considers the design as part of the work of the task.
In my ethics if you don't give a fuck about all the injustices that happen to black people when they aren't protesting then your morals are evil.
Hey thats me. I quit my office job to go remote. Don't regret it at all

Office work is weird and too political. It was like game of thrones every day. The boring bits with pointless drama to determine who sits on an uncomfortable chair.

Key question I have now when I have a face to face meeting: why exactly am I sharing oxygen in close proximity with this person? Especially after this silly commute just to do so.

BTW I now make more money than my boss's boss. Why would I want to go back? There's that pragmatism as well.
That’s not the same thing as remote. I’m fully aware of their proposed hybrid work setup. But the main reasons people want remote is to
1. Freedom to choose where to live
2. Reduce/eliminate commute time
3. Avoid in person interactions due to being extremely introverted, or certain medical conditions, or just because.

The hybrid in the office 3 days a week does not fix any of those three things. You’re still forced to live near your office, you’re still forced to commute, and you’re still forced to interact in person.
Decreases utilization but also decreases coordination between teams (no man-bear-pigs). Also weight the long-term costs of poorly maintained platflorms and infrastructure in desaster cases, security issues or when migrating to other providers.

High overhead can be automated away, google ORBOS.
I feel that the Internet as an archive isn't really feasible. At best, it can augment existing archival efforts such as public libraries. The fact people keep pushing off to webhosting what should be put into a library is a grave misunderstanding of the use cases for the Internet.
This is in addition to $65 in October, for misleading customers:

https://www.reuters.com/business/finance/robinhood-pay-65-ml...
Amazon Demands FTC Chair Recuse Herself from Investigating Amazon
How did the M1 supply increase $12+ trillion? That's surprising to me, especially when it doesn't include bank reserves, and anyway it's much more than even the total amount of quantitative easing from what I can tell.
If you read to yourself, do you hear the words read by an "internal voice"? Which you know is different from real, "external" sounds, but you're still processing as audio internally?

If so, you're imaging the sense of sound. Visualization is just doing the same thing with sight. You can still tell that "internal sight" is different from real "external" sight.

Also I believe visualization is a skill that can be improved with practice. It's just a form of 2D working memory and it's known that working memory can be improved with practice.
I have a portfolio site and had several interviews recently. Zero page views
I remember going to a conference in the 1980s (MacHack), and attending a "Software Project Estimation" workshop.

The guy basically listed excuses for padding the estimate.

Steve McConnell wrote a book about it, using a much more rigorous scientific methodology[0]. He has also written some other stuff about it[1].

This one is really the big one:

"9. Both estimation and control are needed to achieve predictability. "

In my experience, we can accurately estimate software projects that have iron-fisted control. No deviation from the plan. If we use quality-first techniques, like TDD, we can do a fairly good job of hitting targets.

Also in my experience, this results in software that no one wants to use. It doesn't crash, ticks off the punchlist, and basically sucks.

I avoid estimates like the plague (a rare luxury, but I can do it). I like to "wander down the garden path, and see what sights there are," so to speak. I call it "paving the bare spots."[2]

It results in software that comes very close to the user/stakeholder "sweet spot," with great quality. It also tends to come together fairly quickly, and allows for excellent early project visibility.

But that won't work, beyond a fairly humble scope.

[0] https://www.amazon.com/Software-Estimation-Demystifying-Deve...

[1] https://stevemcconnell.com/17-theses-software-estimation/

[2] https://littlegreenviper.com/miscellany/the-road-most-travel...
Indeed yes, however much we may dislike it, change is the only constant. Of course that doesn't mean we shouldn't bother archiving, but there is no need to fret over saving every byte out there on the web.

Entropy is king. Eventually all information loses its coherency.
Globally Distributed Postgres
I think the argument has merit. Unfortunately it won't be decided on technical merit, but likely in the manner expressed in this excellent response I saw on Twitter:

"Can't wait to see a case for this go in front of an 80 year old judge who rules something arbitrary and justifies it with an inaccurate comparison to something nontechnical."
I'm assuming GP's preexisting condition requires frequent doctor visits and medications or other medical devices—or even occasional surgeries—that would be prohibitively expensive if you're uninsured.

This means:

- If you lose your job, all your coverage goes away at the end of the month. COBRA is completely unaffordable for most workers. You have to ask yourself: "if I end up with a three-month period of unemployment, will I be able to afford the meds I need to stay alive?"

- Just because you have coverage doesn't mean you have afforable coverage. You could be stuck with a sky-high deductible, your insurance could pay for such a low percentage of your medical costs, or your company could only pay for a tiny percentage of your premiums, and any of those mean you end up having to choose between medicine and rent.

- Just because you have coverage on paper doesn't mean your stuff is actually covered in practice. Getting medications and surgeries approved is often a colossal pain. It's not uncommon for someone to switch insurance carriers because they got a new job and immediately get told their new insurance won't cover the meds they've been on for years unless they try three other medications first and their doctor determines those other medications all don't work. This is especially dangerous because if the other meds don't work, you could die. Also, a lot of supposedly qualified doctors have no idea how to work with a large number of chronic conditions. People with autoimmune disorders often go without a diagnosis for decades because most doctors don't know what to look for. Imagine if the only doctor in your metro area that knows how to handle your chronic condition is out of your carrier's network (and remember you don't choose your carrier, your employer does). Now you're having premiums deducted from your paycheck and you have to pay out the nose to see the only doctor in town who can treat you. The best-case scenario is that the out-of-network rate is still high enough to take the edge off, but that's still going to be expensive. Worse is if you're on an HMO or EPO where out-of-network doctors aren't covered at all. Then you might as well not even have insurance! And it can get worse: many doctors only let patients self-pay if they don't have insurance at all, which means being on the wrong carrier (which, again, your company decides for you) means you're completely blocked from accessing care.
The full game was never released, only two/three demos. The first demo was distributed as Nintendo DS homebrew and contained a fetch quest, some dialogue and the first minigame. The second demo was released for the PC and included demo 1, some more roaming around & dialogue, two additional minigames, and an unskippable cutscene at the end where "bob" laughs for over two minutes.

The third demo was also released for the PC, originally playable in an embedded Java applet in the browser, and doesn't contain much of the RPG - it's mostly just bob's game (the puzzle game inside "bob's game")

So it's a bit hard to tell how the actual gameplay of the whole thing could have been, you don't get to explore the world much in these demos.
If I read a lot of GPL code, absorb naming conventions, structures, patterns, tricks and later when it comes down to writing a P2P Chat server, I happen to recall similar patterns, naming structures, conventions and many of the utility methods are pretty much how they are in the GPL code bases out there.

Now is my produced code is also GPL derivative because I certainly did read through the code base to be able to write larger programs?
Not neutral: Black and White readers associate yellow emoji with White ethnicity
Job: CEO, Advanced Research and Invention Agency (ARIA)
Me. I try to be objective and honest about everything, including myself.
And they are being flexible :) 2 days of remote work per week is way more than the 0 that used to exist.

I think people need to remember this is going to take time to slide into, and that WFH being a default option (because many people won't change from the default, due to inertia) isn't actually great either.

This is going to take time. You can force that for yourself, by quitting, but forcing it on every company is a battle you aren't going to win. That is going to take time and concerted effort to show that WFH isn't a detriment long-term. This is especially true since the pandemic has left a lot of managers and employees basically hating WFH, because this is what they think it means.

I say this, incidentally, while having direct reports of both kinds; some who loved WFH, and some who can't wait to get back into the office. They are all incredible, and I'd like to keep them. :) Our company is luckily being flexible, and allowing folks to pick, but the default is 3 days in the office. Anything else has to be manager-approved, but shouldn't be difficult (1-2 days, vs 5 days; the latter gets you a perma-desk, the former is hoteling).

And management is terrified of this arrangement; it's going to take time.
We can still edit their memory palace and have fun like that. Put kerosene on the porch and set fire to it. Make the Donald the doorman wearing a mankini etc
Relativity to open new headquarters and factory in Long Beach
Like where?
Plans are nothing, planning is everything.

You have to try, even if you know it's going to be bad/inaccurate.
Robinhood is and has been manipulative and predatory for years.

Arguing that Robinhood did illegal things "for the benefit of their banking partners" or whatever other conspiracy theory you're suggesting is just that, a conspiracy theory.

Let Robinhood be punished for the terrible things they have actually done instead of pointing at provably-false boogeymen.
I didn't mean that TV personalities are inherently trustworthy. The people advising to get the vaccine on TV here are chief medial officer etc, not some Oprah equivalent.
NASA Spinoff Technology
Someone might have published a project I've contributed to, on GitHub. There's no permission.
> Purely ethical - is it right to take licensed code and condense it into a product, without having to take into account the wishes of the original creators? It might be treated as normal that other coders will read it, and pick up on it, but when these licenses were written no one saw products like this coming about. They never assumed that a single person could read all their code, memorise it, and quote it near-verbatim on command.

It's gonna be really interesting to see how this plays out.
> it gets spent all over the country/world. Instead of wealthy people gentrifying certain neighbourhoods as a group and pricing everyone else out, there can be more of a mix of incomes.

Will folks from SF really move to the middle of Oklahoma?
Yes and no. I have never implemented so much as a linked list never mind any more complicated data structures at $JOB. These things are provided by standard libraries.

But knowing what they are, and when to use them, is useful. As is the general background knowledge when it comes to understanding something new (since everything devolves to machine language eventually).
MLPerf Training v1.0 Results
That's interesting. Which one do you prefer for daily use?
Google and Microsoft agree to start suing each other again
Bill Cosby to Be Freed as Court Overturns His Sex Assault Conviction
Preach. It’s a metaphor that enforces harmful beliefs, like master/slave terminology.

Our language defines our world, so we should aim to shy away from language that amplifies a harmful message, even in radically different contexts.
Because you might get fired or laid off or burnt out and leave and only then discover that you have invested too much of yourself into this faceless entity that does not care a whit about you. This is one of those things where peoples' warnings to the young come from hard won experience, but where it doesn't sound right to people who have not themselves yet gained the experience. So we fail to impart the lessons and each generation is forced to relearn them on their own. It can be maddening to know something is correct but unable to convince someone who must experience it themselves in order to see. But it's just life and humanity, it just works that way.
I have to wonder whether they're available for more hours or actually putting in more work. Home distractions tend to extend the work day for people who have pride in their craft.
Do you also agree that your blue-collar friend shouldn't receive anything from society when their job is outsourced or made useless by technology? I disagree, but at least that would be consistent. If you believe everyone should fend for themselves, why do we even have a society instead of being lone hunter-gatherers?
This would not be (so much of) a problem if there was a statutory obligation on public officials to perform their duties and as part of that share certain information with the public. That would override any NDA seeking to circumvent it.

Oh wait... there is (at least in the UK - not so sure about the US but I imagine there are similar laws there). Hmm.
Resource utilization is the main reason I would run a cluster in the first place. Immutable infrastructure is also expensive to build and maintain.
The Premonition by Michael Lewis
And while the machines are distracted by all that, we can get back to writing code.
One strategy I've found useful when asked for an estimate is to ask back: "What do you need the estimate for?" Often, this leads to a useful discussion, and we can discover things like:

- They don't actually need to estimate, because the task can very obviously be completed by the previously window

- They're simply trying to prioritize two different features, so the estimate doesn't need to account for who will be working on the project, known vacations, meetings, etc.

- The business is trying to use the estimate for strategic planning, so high-confidence, or multiple estimates (optimistic/normal/conservative) are actually needed.

It's similar to when someone comes to engineering and asks "Please build this button for me" - it's always crucial to ask "Why?" and understand the problem they're trying to solve, since often what they've asked for is not what they need.
Why do they want protection in the first place? Isn't it meant to be open?
Reddit is having a nice discussion:

https://www.reddit.com/r/SPACs/comments/oai9fi/embarccom_spa...
I like the idea of "Building on Quicksand" as the analogy for Distributed Systems, but also maintaining your software dependencies. This article basically recommends trying to minimize your dependencies to keep reproducibility/portability high. I generally agree with this, but also carry an "all things within reason" mentality. But just as the article describes coworkers growing into their cluster, the complexity of what they run in their cluster will also grow over time and eventually they'll realize they've just built up their own "distribution". A few years ago, I've written a post asking people to think critically when they hear someone mention "Vanilla" Kubernetes[0].

The real problem they suffered is actually that Kubernetes isn't fundamentally designed for multi-tenancy. Instead, you're forced to make separate clusters to isolate different domains. Google themselves run multiple Borg clusters to isolate different domains, so it's natural that Kubernetes end up with a similar design.

[0]: https://jzelinskie.com/posts/youre-not-running-vanilla-kuber...

Disclosure: I worked as an engineer and product manager on CoreOS Tectonic, the (now defunct) Kubernetes used in the post.
Why delete the reply? It is an accurate angle, albeit inflamatory, after all that was the outcome of the Buffet bet vs HedgeFunds regarding the ROI of index funds

But yeah, not sure if id say that they make money through luck "alone", more like they make money through "the aggregate of luck" and very deep pockets which themselves are financed through suprasecular low interest rates, or in the same manner that a Casino will always win in the aggregate
Proper planning generally means those bathrooms are right next to each other, so the toilets use the same drain and vent pipes and water supply except for the last 2 feet. You ideally put the kitchen and laundry close as well. Of course you often cannot put everything close and that add cost, but it is attempted.
> A common counterexample to OO inheritance is the relationship between a square and a rectangle. Geometrically, a square is a specialisation of a rectangle: every square is a rectangle, not every rectangle is a square.

Well yes and no.

A square and a rectangle are two kind of objects that have some common properties.

In Math, for an object to belong to a set, it must have the properties described by the set.

- Squares is the set of polygons with 4 sides of the same length and 4 right angles.
- Rectangles is the set of polygons with 4 sides and 4 right angles.
- Diamonds is the set of polygons with 4 sides of the same length.

So yes, it's difficult to represent this relationship with inheritance. But no, in OOP, you should not consider those properties as data on a class, but more like a trait/interface.

Your functions should take as input shapes implementing the expected traits/interfaces.

Then what is a shape? It's a collection of points. But a point can be 2D, 3D, n-D. Here you would still not use inheritance but generics.

Usually, I only use inheritance to specialize configuration, for example:

class Foo {
constructor(options) { ... }
}

class Bar extends Foo {
constructor() {
super({ some: 'options' })
}
}
Confuse the issue more by flipflopping which party signals to their base to virtue signal giving a shit about the topic every....3-5 years.
Monopolies don't need to be as competitive.
I haven't heard of someone being a VP of Engineering after just 5 years of SE and 65k after taxes after 10 years sounds a little low.

I think the main problem is that a few companies have very challenging technical work and are happy to pay really high salaries (think OpenAI specialists, a few teams at Google / Netflix pushing the boundaries forward), the rest need relatively trivial solutions and they will pay higher than average (think most people working at FANGs on stuff they're overqualified for) or average / lower than average (think most startups, small companies).

After a while, you won't grow technically in most companies and you won't advance the state of technology.

Some people just keep contributing the same stuff over and over until they die (1), some people specialise in some technically obscure niches and charge a premium for that (2), some people decide to become people managers (3) and eventually become CTO.

It doesn't seem like you're happy with (1), you already did (3), I would say you have too much people experience to go back and do (2).

A master's degree in something you like won't be particularly useful at your level, it could be an expensive gift to yourself.

If I were you I would just start my own business: you are technical, you are a manager; the next skill to learn could be business.

Other options include looking for a CTO role in an early stage startup, or doing the interview-algorithm-memorisation-game to join a FANG.
Early stage startups and FANGs will likely not be very nice places to be in terms of politics though, so you may not be as happy as you're now.

Best of luck
That is an exaggeration. Most successful people in the software industry definitely have an engineering degree.
> c# and ruby fibres (altho i think ruby removed them, ultimately?

Ruby did not remove Fibers (in fact, they’ve been recently, in 3
0, enhanced to optionally be nonblocking—that is, automatically yielding on any operation that wpuld block.)

Ruby removed continuations from the core (moved them to stdlib) after adopting independent Fibers way back with 1.9; continuations were the previous mechanism for similar lightweight concurrency.
Not me. My career networks are online. Offices are full of people trying to give each other eating disorders through passive aggression, politics and generally pointless power games.

That's the perception we have in our groups. We meet up weekly face to face to share air when possible.
Oh thanks. I was actually looking for something more factual/academic. Without any sensationalism. But, I'll take a look at this one in any case!
True. There are ways to use a 2nd exhaust for the portable AC to increase efficiency but not sure if it's worth it. For ~3 weeks per year I wouldn't really care. Also, if ACs are sold with 2 hoses they fall under a different category of ACs and must be somewhat more efficient. That's why those are not sold usually.
I’d like to see a vegan alternative to the pets/cattle meme.
Well, the PNW just had record temps for three days straight (100+ F is unheard of with avg Seattle July highs of 77) and AC is an uncommon residential amenity that is usually offered at large offices.

Does the office run the AC a bit cold? Yes, but to be honest when you reach almost too hot to sweat that's a nice problem to have.
and commute. even a 'quick' commute (and attendant 'getting started for the day') is going to put you closer to 50h/week. Then another... ~50h/week for sleeping, as you say. The 'commute to an office' is closer to a 1/3rd of you week, and ~1/2 of your waking life for many folks.