skysight-inc/HackerNews huggingface dataset:
Surprised that guard clauses weren't mentioned here yet, you could also write

```
if (account == null) {
throw NoAccountException
}

if (account.contact == null) {
throw AccountWithoutContactException
}

if (account.contact.phoneNumber == null) {
throw ContactWithoutPhoneNumberException
}

// do stuff here
```
Basically, a digital twin of the world economy. There are conspiracy theorists who think that this exists and captures all of the major firms and simulates the rest out for small businesses.
The Decentralization of Atoms Is Underrated
If you look at statistics of successful founders, the average age is like 45+. Why? Because you now have time to start a startup and you went through all the lessons in your 20s.

The answer is simple. You keep building on the side part time until it can become your full time thing. There are plenty of success stories from people in their 30s with families who made the transition (rare, but there's plenty).
You know, I feel privileged (in an epistemologically doubtful way) that I once lived in a world where I could have confidence that I wasn't being fundamentally deceived by literal dei ex machina. I've understood for the last decade that this faith was on borrowed time as we bridged closer to overt technophrenia, but it's harrowing to be a witness to it.

I can't help but wonder at what point I will inhabit a world indistinguishable from that of a paranoid schizophrenic. Will I even notice? And if I do, will anyone else? When we become as slow as trees to digital arborists, what will become of us? Will they domesticate us? Will they deforest us as we did Europe amd the Near East? Quo vadis, Domine?
b would be included twice in that case, wouldn't it?
That’s the secret of dinosaur bones, most of them are fake artists renditions based on fragments of bones found in the wild. Who knows how accurate any dinosaur skeleton really is. I still think it’s stupid that IP can be controlled for what’s ostensibly some stuff you dig up from the ground.
That was because of missing drivers, or drivers that needed to be modified a bit (like the nvme driver), it had nothing to do with a locked down boot loader.
I add: https://sel4.systems/About/seL4-whitepaper.pdf
nah that's going to bring a lot of pain to your world.

Go read this book: https://www.amazon.com/Product-Roadmaps-Relaunched-Direction...

It's hands down the best approach to roadmapping out there.

The tl;dr:

Commit to Outcomes (future states of the world your product can create that don't exist today, and have meaning for your customers) without committing to solving for those Outcomes in any particular way.

So something like "It's easy for customers to get their data out of the product to feed into other applications" is an Outcome, and the Outputs can be all sorts of things: APIs, Direct Integrations to Other Apps, Excel exports, or just a dumb form for them to request the data and you have a SQL script you run to do it because it just doesn't happen enough to warrant the investment.
You're in it!
I used it mainly to communicate with my local services on Android, It's excellent but I have moved on to a Linux phone and so I have little use for Termux anymore.

But here's a security researcher from Zambia using only Termux for his development[1] and research as he couldn't afford a computer. I'm sure there are plenty more like him in developing economies, Where using smartphone for general purpose computing is not just a lifestyle but a necessity for livelihood.

So I really appreciate Termux for catering to those who might be still running older android versions.

[1] https://twitter.com/cyb3rops/status/1548961346104053764
Jetbrains, Notion, and YT Premium. I have a few hobby based subs, like Fantasy Grounds VTT for gaming. But I'm a bit over the subscriptions for everything model. I finally had enough and started canceling things such as my MS360 account. I'm sure more will be cancelled by the end of the year.
Setting aside the issues that revenue maximization is not typically the only (or even the main) concern for those selling tickets, I still think this system isn't very good. One key issue is that it assumes that the underlying value of the tickets themselves does not change over time (in the article's specific case, 6 months). But an artist's popularity can be extremely unpredictable, and over the course of 6 months could change drastically. This would likely mean leaving money on the table, especially if that rise in popularity comes close to the actual event date.

I think a better approach that could deal with this would be to avoid trying to come up with the 'max' and 'min' amounts and instead simply let people submit bids for how much they are willing to pay for tickets. You would pre-authorize that amount at order time, but it wouldn't yet be deducted. At the end of every day, the top n bids would 'win' and actually actually purchase the ticket.

In the simple case where the artist's popularity stays the same over time, this would probably result in a similar outcome to OP's suggestion. But if the artist undergoes a big increase in popularity, the ticket price would rise again to a much higher value later.
Indeed, consistency (with the lengthy dialogue histories, but also the game state as well as game plans) was a huge challenge for us. We spent a lot of time working on techniques for detecting and filtering these kinds of low quality messages. You can see the Supplementary Materials in the paper for full details, but TL;DR: we built a suite of classifiers for detecting common mistakes (training classifiers to discriminate between human messages and counterfactuals), and used these classifiers as an ensemble which acted as a filter on top of message generation.
>The reality is most huge companies are majority bloat.

Something I learned early in my career is that some companies consider this a feature not a bug. As in, they are hoarding talent so that they don't go to work for their competitor.
It is the same old story, later repeated with agile manifesto, REST, and so on.

They became misunderstood and abused by enough people that the terms stopped meaning anything useful in public space. When I hear a company say "we're Agile, we are doing REST" etc. I just roll my eyes and think to myself: unlikely.

Over the years I figured out the right way to use all of these things: as resources with solutions to frequent problems.

So no, I will not preach GoF or DDD or CQRS or Agile or REST or anything else, but I will make sure I understood each one very well on many levels and apply the lessons to my projects.
Totally possible that I just phrased the query in a way it didn't understand, and totally possible that a Google Home just can't do this (or couldn't at the time). If anything, I think that kind of illustrates another important point; not only is it hard to figure out what exactly a given voice assistant is capable of doing, it's also pretty hard to tell the difference between "I need to phrase this differently" and "this device can't answer the question I have". I guess it's like how professional dog trainers say that they're really training the person rather than the dog; the quickest path to getting a voice assistant that people can use isn't just training the language model, but training people to talk to it correctly. This makes sense, given how similar trends happened with text-based search engines.
Great story.
Did you have a family with kids at that time as well?
How did you determine that their poor performance was an attribute of the employee, rather than a consequence of their strengths in a given environment?

Everyone’s performance differs depending on the environment and their personal context. I’ve know poor performers whose impact shot up once they were no longer asked to do things that frustrated them, for example.
If you’re going to try and find a cutesy way to flip someone’s words around, you could at least flip the words around in a consistent way, rather than turning the entire sentence into sausage like that.
I'm serious. Why would you need more than one developer for the Android or iOS app?
My personal policy was "No regularly-scheduled meetings" (which included things like daily standups).

But I worked for a Japanese corporation, so we had regularly-scheduled meetings. I was able to reduce them, though.
C# have taking it further. New projects give errors if you don't declare vars as nullable when they may be null in some context. It will help for static analyzers to find these cases. I see a big risk in it. That people will just init nonsense objects to get around the warnings.
It's sad because while I don't think the second concern is so big, the first half of your comment is deceptively important, but this is a conversation that really difficult to have.

I've brought it up when using Swift and Kotlin and it takes so much energy for people to realize that safety operators, which feel really really good to use, accidentally sweep up major issues

People assume you're missing something when you explain that they need to get more comfortable with force unwrapping (which is intentionally introducing a NPE)

-

But for example, if you have getAccount().getContract().getPhoneNumber() so you can show it in a settings page, you should not throw an NPE. You can easily correct the issue in a non-invariant breaking way by say defaulting to "<missing>" in the UI.

But if you have getAccount().getContract().setSomeFieldWithRealWorldImportance(true), you should either be force unwrapping or returning a Result type, and ensuring someone is actually handling it with a hard stop on the user.

The problem is reality is often much more subtle than "doSomethingImportant()".

For example, I worked on an iOS app that was used for medical work, and one habit iOS devs had was wrapping access to weak references to objects with a null safety:

So they were super comfortable writing things equivalent to viewController?.showSomeDialog()

because in most situations crashing over lifecycle issues is a bad idea... but here we could be creating incorrect output in a highly sensitive situation.

"someDialog" could be "Drug interaction between X and Y detected" for example, but the mental patterns wouldn't detect that a safety operator was hiding that.

It was better for the app to crash than silently hide that information, since at least then it'd be known the app was in an invalid state.

-

Now the problem is here devs start to think "well I'm not making medical apps" or "well I wouldn't make that mistake"...

But go through any moderately large codebase and you will find important user actions that silently fail where a crash would actually serve the user better.

It's how to convince people that a hard crash can ever be good though.
@NonNull
Optional<@NonNull String> getMiddleName() {
return null; // error
}
Breaking backward compatibility is not the end of the world.
No doubt you can have big teams doing highly complicated work.

That doesn’t mean your AI system performs better than a simpler one. Or that the system is useful in the first place (recommendations.) I’m not saying they were sitting around twiddling their thumbs. I’m saying the vast majority of Twitter staff were not actually improving the Twitter product noticeably to users. They were doing highly complex, cutting-edge engineering that was make-work.

If Twitter tech was so advanced, why were they losing so much money?
Which shows that you weren't born in Japan: people there are born 1 year old.
That's great news for Home Assistant however!
If you're not a FAANG engineer, and like 95% of people work somewhere that doesn't give you a ton of stock or RSUs, and you don't live in a super expensive metro, $100-150k is basically strong mid/weak senior money. I know plenty of places hiring with no stock, no bonuses, and seniors top out at $160k or so. They hire capable engineers no problem.

With that in mind, taking a pay cut into the middle of that range to do your own thing and potentially make a lot more isn't as drastic as going from a $400k FAANG job to a $35k ramen-every-meal situation.
Fingerprinting by detecting installed fonts is certainly interesting, esp since it could be used by both offense and defense.
Digging in deeper, I’m wondering if it would be possible to craft a font that consists of Javascript fragments which could be rendered and eval’ed when a page loads. There must be something in the browser’s rendering process that would block this, right?
Tasks, Automation, and the Rise in U.S. Wage Inequality
Facebook kept their shadow profiles to themselves, but that didn't make it any less gross. Defending Apple's data collection on the basis that "they don't share it" is like defending a guy taking creepshots of you in the bathroom because he doesn't look like the sort of person who would cause you trouble.
Equally often it’s worse and a waste of time. And you won’t know which world you’re living in for a while.
Effective Altruism Is about Getting Rich with a Clean Conscience
“It’s my big number.” I tell people it’s OK to be rich.”
I like Raymond Chen's formulation of this point:

> Good advice comes with a rationale so you can tell when it becomes bad advice. If you don't understanding why something should be done, then you've fallen into the trap of cargo cult programming, and you'll keep doing it even when it's no longer necessary or even becomes deleterious.

from: https://web.archive.org/web/20100104031036/http://blogs.msdn...
curl, sqlite, awk, etc. They're all free. Am I the product?
>how do I continue my current standard of living for my family while working on a startup?
You can't

You either have to save up for a year's worth of expenses and also downgrade the lifestyle and make sacrifices or convince a VC and raise a decent seed round but that too will come with conditions and you will probably not be able to pay yourself your market salary.

Entrepreneurship is hard. Very hard. Survivorship bias ensures that we only hear about successful ones where everything worked out. But as you already know, that happens in a tiny number of cases and that too after a lot of hardships.

Starting up something as a side hustle is the only viable option. You will have to put in after work hours and sacrifice some family time to fulfill your dream if you don't want to upset your marriage and lifestyle.
Of course they would say that, they have to for stock price and market volatility. Whether it is true or not, being a leak, they would never say anything else until they are ready to announce it coming out of their PR department.
If you want to maintain your current standard of living and start a business you need customers, investors, or savings. If you want to start any business, startup or lawncare and all points in between, you need customers, investors or savings.

So start by solving that problem.

P.S. the "90% of startups fail" is inaccurate and moronic. It gives no context on the type of business or the outcome. Starting a 1 million dollar / year lifestyle business is incredibly simple (not easy, but simple). Starting a fifty billion dollar pharma company is incredible difficult. Anyone saying "well I want to start the latter, not the former!" has never had a 1 million / year lifestyle business.
Nobody said “self-sacrifice” and it’s somewhat telling that that’s the lens you viewed it through.

I said “maximizing utility” which is the opposite of self-sacrifice. I’m just saying “utility” is measured across more dimensions than profit.

E.g., do you pick your spouse/friends or make a decision to have children based on their ability to maximize your wealth?
Or Firefox to say to the user to buy more RAM, close other apps, etc.

Also Windows should step in and say that this application is consuming almos all of the remaining memory, close others, or this or buy more RAM.
I just did this. I had 2 very important things that helped me succeed in starting.

1. A supportive wife
2. A wife that can pay the bills while I take 0 salary to build something.

Without those 2 things I wouldn’t have been able to start.

As I’m sure you realize now that you have a wife and a child your free time is limited and at bad times. So if you want to actually be able to accomplish something you have to pull real time away from something else.

Your choices are 1. Your family 2. Your job.

You could try going part time and asking if your wife is willing to do an outsized portion of the family work but that goes back to (1) being critical. First and foremost you need a wife that will support you.

I know this probably isn’t helpful but it adds a datapoint for you.
> don't understand why the Meta stock hasn't plummeted even more than it already did.

Because they are still making a lot of money
You can hustle and still take care of your body/mind, unlike the person mentioned in the post. I would even argue that is part of the hustle. You need to hustle to keep yourself hustling, which is probably a whole discipline in and of itself.
It's definitely fully supported, it gets many upgrades and has a pretty long-term and serious roadmap.

I strongly recommend not to use it though.
I agree with you here.

But what you are describing still isn't good enough for a lot of people, because even though `--first-parent` hides the noise it's still there and just knowing there's a mess under the rug is enough to be problematic.

I don't think it's really the fault of the tooling, moreso with what is a common interpretation of what is a mess and what isn't. If the github commit history allowed you to show `--first-parent` maybe it would be less of a problem.
Man, I'm surprised to hear that's the case

I assumed that Macs were mostly preferred because of their UX and relatively high-quality drivers/OS working well with sleep/wake. But if you put linux on there, you're giving all that up

Are there not any linux laptops out there with decent build quality and comparable perf/battery life?
I'm currently going through this process with a very supportive spouse. I quit my job last year and have been burning through my savings to develop prototypes. This is obviously very stressful, especially as, in this economy, it's no longer guaranteed that if I give up I could find a job in my area that pays the bills.

She accepts the risks and wants to see me try to follow my dreams rather than give up. We've moved back in with my parents to save money and help with childcare.

Once I can secure some investment, it should get easier -- at least financially, if not in terms of work hours. That's also difficult these days but we'll see how it goes.
This looks pretty great, though I'm surprised at the filesize for a simple diagram - 333kb from a simple test I made. A cat of the SVG prints out some base64 which I didn't try decoding, but I'd assume it's the bundled font that takes up most of the space? It'd be nice if it contained only the characters necessary for the diagram itself.
By the time GPT-4 botswarms infiltrate HN, Twitter, LinkedIn, Facebook and are weaponized to write articles that outshare the current media, it will be too late to stop them. They will amass more and bettee social capital, real capital, produce the vast majority of content and will be Among Us!

My prediction is 2029
Sounds like the sort of problem your preferred hardware vendor can fix.
Javascript also has Option with fp-ts, so it still leads on this front.
PSA: I strongly recommend not to use Cobalt (unless of course you are a Google employee, with support from Cobalt team).

Cobalt's roadmap is 100% Youtube on TV roadmap. I've never seen anyone use Cobalt professionally for anything else. Even Android TV doesn't trust Cobalt for anything but Youtube.

It mentions "subset of HTML5" which begs the question of "which subset", and the answer is pretty much "whatever Youtube on TV" uses.

Please note that I'm not speaking of the actual quality of the project which in my experience is fine.

If you're wondering what to use then for an embedded Linux web browser: I don't have a professional experience on it, but most people I know use WPE WebKit/COG
There are a lot of assumptions baked into your position.

1. The employer pays for your time, not your expertise or output.

It'd only be stealing from the company if the company cares about hours worked over output. If we explore this concept in a theoretical sense it's clear that it doesn't hold up.

You have two candidates
One candidate has 20+ years of experience doing the exact thing you want them doing. This candidate says they'll work for you for $100k/yr, and they'll work 10 hours a week, complete all the relevant tasks, and very very rarely cause catastrophic errors or user-impacting bugs.

The other candidate is fresh out of school and says they'll work 50 hours a week. They'll complete the same amount of work as the first candidate, but they'll write more bugs, there will be more planning mistakes causing feature delays, and there's a reasonable chance of catastrophic failure due to debugging-in-prod shenanigans. They are also asking for $100k/yr.

Which candidate is better? Under the assumption that employers pay for _time_, the second candidate is better, but I'd argue most companies should prefer the first candidate.

2. More hours worked produces more or higher quality output.

There's a reasonable amount of research and practical anecdotes that disputes this recently (see companies that have gone to 32-hour 4-day workweeks with no reduction in productivity). Enough that at least, this point is seriously in doubt.

3. Twitter maybe pays a senior engineer $400k/yr under the expectation of their output for 40 hours, and if they get less it wasn't a fair deal.

This is a reasonable take, but Twitter (like most for-profit companies) theoretically has a performance evaluation system, managers, deadlines, etc. They're paying an engineer some amount of money for some amount of output. If that engineer produces that amount of output, Twitter is happy, the engineer is happy, there's no issue. If the engineer working 20 hours or less per week caused them to not meet their goals, then Twitter has the right to fire that employee. They don't, so that implies that they're happy with the arrangement.

4. The employee's salary is equal to their expected output/profit

If the Labor Theory of Value is correct, then companies derive their profits almost exclusively from the labor of their employees.

In order for an employee to "steal" from a company by under-producing work, they would have to earn more in salary + benefits than they earn the company from their work.

This is necessarily not the case (on average) in a for-profit company, because if the company makes a profit and uses those profits to grow or to issue dividends to shareholders, they have earned "_surplus value_" from the employees' labor (on average).

---

In any case, it's not necessarily true that you're wrong, but your comment was fairly dismissive and confrontational. There are a _lot_ of cultural and individual assumptions baked into how we exchange salary/wages for labor, and it's worth examining those before firing off moral judgments at one another for not working hard enough or working too much or whatever.
Thanks for the feedback. Regarding the configuration language, I don't think it's too hard to learn, I modelled it after the structured configuration NGINX uses since I find that easy to read and write compared to something like TOML, or YAML for the configuration I wanted.

Regarding the documentation styling, I appreciate the 40% width is a bit too narrow. The styling is something that has gone through multiple revisions, but some more work still needs to be done.

On the brevity of the documentation, especially on the manifest structure, I decided to err on the side of verbosity. But I will take your feedback on board.

Thanks.
IF it's fine then why was Google data collection ever an issue?