skysight-inc/HackerNews huggingface dataset:
Creator of Bun here.

Regarding the SQLite claim:

The "view source" link for SQLite is out of date (fixing shortly), but the numbers are correct. I forgot to change the label on the landing page from "x/sqlite" to "x/sqlite3" and I forgot to update the source link.

You can see I updated in this git commit:

https://github.com/oven-sh/bun/commit/4b5c9acc72908ba22e3f70...

Here is what it shows for me, but I encourage you to run it on your own computer to see for yourself:

deno run --unstable -A deno.js
cpu: Apple M1 Max
runtime: deno 1.26.1 (aarch64-apple-darwin)

benchmark time (avg) (min … max) p75 p99 p995
------------------------------------------------------------------- -----------------------------
SELECT \* FROM "Order" 26.3 ms/iter (25.06 ms … 29.23 ms) 26.74 ms 29.23 ms 29.23 ms
SELECT \* FROM "Product" 53.91 µs/iter (52.17 µs … 317.75 µs) 54 µs 65.63 µs 76.75 µs
SELECT \* FROM "OrderDetail" 269.41 ms/iter (240.72 ms … 308.82 ms) 279.05 ms 308.82 ms 308.82 ms

bun bun.js
[0.26ms] ".env"
cpu: Apple M1 Max
runtime: bun 0.2.0 (arm64-darwin)

benchmark time (avg) (min … max) p75 p99 p995
------------------------------------------------------------------- -----------------------------
SELECT \* FROM "Order" 14.44 ms/iter (13.71 ms … 17.82 ms) 14.56 ms 17.82 ms 17.82 ms
SELECT \* FROM "Product" 34.39 µs/iter (30.46 µs … 4.55 ms) 32.88 µs 48.5 µs 60.13 µs
SELECT \* FROM "OrderDetail" 148.17 ms/iter (144.8 ms … 154.92 ms) 149.85 ms 154.92 ms 154.92 ms

Regarding the FFI benchmark, you can see the commit from today here:

https://github.com/oven-sh/bun/commit/40506e33e73018103bcf08...

It threw an error until I googled "Deno pointer ffi", which mentioned this function https://doc.deno.land/deno/unstable/~/Deno.UnsafePointer and that worked. I assumed that `Deno.UnsafePointer.of` is the expected way to get a pointer to a buffer, but it seems that changing the type to "buffer" is a faster way for this case. Will update the page shortly.
"taking the easy way out"
Please don't ever. I have suffered from similar thoughts but largely have managed to get over them. Can you possibly take some contracting gigs ? It doesn't seem like you hate C++ but just hated the low paying job. If so, then there are quite a few consulting gigs you can grab just based on your C++ skills, especially in the financial world. Please try reaching out to some recruiters in the financial space. Is this something that would interest you ?

One other option is this company called crossover, it's a real shitty company and they monitor your every move and shit like that but they pay reasonably well, 100K+ and you can get in if you are reasonably good with code. I wouldn't recommend this, but since you are under a lot of debt, the money can be a lifesaver.

Another option is with database companies that are still on C and C++. ScyllaDB, Aerospike are a few options. They are hiring and if you need a referral at Aerospike, feel free to email me, email in profile. I worked there.

Lastly, weeks is not really that long to get a job. Some of the interview loops even at FAANG companies last for 4-6 weeks. So don't lose heart.
This may not be what you want to hear pal, but consider getting 'just any job' for now, to make ends meet. It's not going to feel good, and you're probably going to hate it, but at least you won't be unemployed... which will feel better than being unemployed.

I may not be a programmer, but I have been in your shoes. It sucks. The abyss looks friendly sometimes when society is not.
I am not an expert in "depression" although been there many times. What helped in my case were the short walks I made near town or in the park. This was the "pill" taken every day that turned the things around. Of course, if you really fill on the edge and "taking it the easy way out" you should definitely speak with someone! But try to take joy of the small things you have. Take it easy and slow and it will get better! Job rejections are always tough, I personally also am taking them way too serious, while in reality the companies really don't care. What they care is to reduce costs, and increase gains. What I did when I was in the same situation, I just reworked my application docs several times, until reaching a satisfactory quality to hook the recruiting guys up, and reduced my salary expectation.

Regarding the Cpp, man I don't know in which country you are, but at least in Switzerland, my country, I stumble upon thousands of job openings for Embedded development engineers every day. Don't know your background, but try thinking a bit more broader.

Bottom line, take it easy, and try doing something you love every day consistently at least once. Tweak your Resume. There some good templates/suggestions in the net these days. Reduce expectations. DON'T read news!
Looks great, but Jira was never getting picked by the users this is marketed to; it's picked by their bosses. It'll be much tougher to sell those people on an alternative.
Did you ask more details?

try to find out what is lacking in your experience from their POV

Finding a job can take time even during good times, you already quit so only thing you can do is be persistent now and flexible to whatever comes up

In the meantime, Github is always a good option: contribute to OSS projects, show activity and your experience.

Maybe some of the companies regularly contributing to OSS would consider hiring you (RedHat etc?)
The Empire of the Ants – HG Wells
They seem to be particularly against it (https://forum.obsidian.md/t/open-sourcing-of-obsidian/1515/1...) which has always been my own worry about using this product. A knowledge base is something that takes a long time to start producing results and the idea of being locked into using a closed-source piece of software that I can't depend on being functional 5+ years from now is very scary. At least with open-source, a community project is likely to form a fork if the original maintainers disappear.

I realize they are just markdown files, but they use a proprietary "Obsidian" markup that will require painful conversion if I ever need move to another app. I've been through this before and it has always been a massive headache.
There's this meme that you get laid off on Friday, you send some emails on Monday, and you have a job by the end of the week. Not broadly true and certainly not at the moment.

But, yes, review resume and reach out. But also be prepared for this to be a multi-month process.
What sort of positions out of curiosity?
Having raised a (preish) seed round on Europe, I'd like to add that it's even quite common in Europe that they expect you to be able to raise some first money (lead investor) in your home country first. Raising remotely (country wise) is definitely a much bigger challenge, at least in early phases.
It's interesting that the author puts "downloading the code" in the exhaustive section.

Is it really that much work to run git checkout? I routinely checkout code in PRs if I'm not familiar with that part of the codebase. I can navigate the codebase much quicker in my editor than in GitHub. Although GitHub is actually getting there with the semantic analysis of code and finding references and stuff, sometimes I just need to open 5 files in different splits to figure out what is going on.
Not to forget that OP could do the home schooling and the spouse keeps working.
Wiki page: https://en.wikipedia.org/wiki/2021_Facebook_outage

Their report: https://www.facebook.com/business/news/update-about-the-octo...
Reddit does this, annoyingly after typing Ctrl-F. I have to wait a short while until the browser's search bar pops up at the bottom, otherwise my instinct to immediately start typing the search phrase causes all sorts of actions, like following some people, hiding a thread, who knows what random stuff happens on each key press.
When people crib about how the modern web stack is hodgepodge of buzzwords with little-to-no value, you can show them this. Nearly every page loads within milliseconds, and it's perfectly usable even if you disable JS. The product itself is a great example of how you can deliver a blazingly fast and near-native experience with web technologies.

I have been programming web for nearly 15 years. I, too, have issues with needless complexity, but I also dislike how (many) senior folks want to pretend that simple HTML/CSS is all it takes to build anything and all the coders using modern stack are stupid enough to ignore that.
That's one form that ticketing can take, but I think it's way off to suggest that's all ticketing is. I've known even solo devs who got a lot of benefit out of a (simple) ticketing system.
Actually, I think your post highlights a couple important things:

1. The reason everyone hates Jira is because, over time, it has essentially become all things to all people, yet it doesn't solve the needs of any individual group perfectly. It actually has a huge, ginormous feature set, and part of the difficulty is figuring which settings or set of features are right for your team.

2. The reason Jira has become so difficult to replace is because nearly every team of moderate complexity uses some subset of features that aren't replicated in any other tool.

So, to the point, I hope that Linear doesn't implement your requested features (not exactly, but I just hope they are extremely judicious in which features they add). Or, rather, I'd just point out that Jira got to be the way it is because they basically implemented all the features. I think a good competitor will necessarily have to hit that sweet spot where they have 98% of the most critical features (especially startups/new companies), but will ruthlessly not add features that will lead to bloat and complexity.
> Microsoft thinks the exact workings of the partitioning is something that should work so well you don't need to know it in detail. But, if your usecase is slightly off you end up really needing to know. I know at least one team who routinely copy all their data from one Cosmos instance to another and switch over traffic to the copy just to get a partitioning reset; it is one thing to have to do it; another to discover in production yourself it has to be done with no prior warning..

AWS DynamoDB used to do that. When I was working for a team in AWS we ended up discovering an unexpected bad hash choice, had a hot partition and ended up with a crazy number of partitions and a need to have really high r/w allocation on it. The only option at the time was to roll over to a new table (which we could do and fix our hash choice, thankfully, without too much hassle).

They fixed that stuff a few years ago now so most (all?) of my "here be dragons" concerns about DynamoDB have been addressed.
I think I disagree with the emphasis on asking questions. Not because questions shouldn't be asked, but because they should be asked much earlier in the process than the PR stage. Every feature should at a minimum have a brief doc for the requirements and high level design. If you haven't read that and are reviewing the PR for anything other than style, you need to take a step back and go read that doc first.

In my opinion, the levels are:

1. Barely-existent review: The PR author is the SME, I'm only reviewing and LGTMing this because peer review is needed to submit the change. I might notice a typo or something along those lines, and will call out if they're being lazy and skipping tests.

2. Functionality-focused change: Does the code meet the objective and do the tests adequately cover the change?

3. In-depth review: Does the code address the problem in an efficient way that is not likely to cause the team future pain?
There is no easy way out for your family.

Sack up, work a restaurant job until you're back on your feet. Once you build your stacks back up at the restaurant job use that confidence to hit the job market and take what's yours. You got this, I believe in you.
Ditto. Java is like C++‘s popular cousin who lives nextdoor, talks too much and doesn’t like to take his trash out. It won’t take you long to get familiar with it.
Yeah that was me, and I am talking iPhone. Don't try to overanalyze the "15". There's nothing scientific about it I just made it up and put the tilde in front. Didn't realize it would be the focus of such debate. It could be 10 or 20. Most people I know were early adopters and have replaced every 1-2 years and have also probably broken a couple along the way requiring early replacement. I'm also not claiming my observation is representative of anything other than that, I'm sure it wouldn't match some larger dataset. It's biased by a ton of factors. I was trying to point out 2 things;

1) we've used iphone's since the beginning and are pretty loyal, would likely never consider non iPhone

2) we don't tend to switch apps for "inclusivity" as the original comment parent stated. We blatantly exclude people that are not on the Apple product ecosystem by being rather inflexible to even try the universe of platform agnostic options (WhatsApp, etc).

This is my experience in the US. Basically, we're acting like the teenagers except in a not so mean and judgemental way.
The media isn't made by aliens, it's just a bunch of people just like their viewers, so maybe such desire to manipulate is intrinsic by humans.

But anyway this kind of thinking is just the lazy way out by holding prejudices instead of evaluating each news article by its own merits, like when a woman says "all men are the same" (or a man says the equivalent thing)
The Mike Acton & co C++ gamedev targeted data oriented design campaign is good and deserves credit but data representation/layout emphasis was old hat in other domains perf work before that. And since the "memory wall" has been talked about a lot much earlier, the fact that memory/cache is the bottleneck was inevitable. Thus the need to start programming around that absent hardware inventions to solve it.

Game programmers hit this on consoles due to facing platforms with relatively slow/tricky memory a bit earlier than PC devs (Cell processor[1]). But HPC programmers had by then been worryign and programming around the problem for longer, since the extinction of SSI vector supercomputers and transition to message passing clusters. (Also the data oriented design movement is only partly about this, and much about other C++ / programming / measurement etc ideas)

I was searching for older memory wall discussions and found at least this from 1994: https://www.eecs.ucf.edu/~lboloni/Teaching/EEL5708_2006/slid...

[1] in fact if you browse some of Mike Actons slides you can see his username on slideshare is "cellperformance" - eg https://www.slideshare.net/cellperformance/data-oriented-des...
Migrating from SAP to MS CRM for Microsoft would be more a billion project than just a few millions.
In one of the projects to port a game to Linux phone with 16MB I had to allocate all the memory upfront for performance reason to avoid memory allocation/deallocation overhead and fragmentation. Fun times ;)
> Badly formatted code should make the the push fail so the dev has to fix the problem before they can open a PR

I'd rather people check in their WIP than have it sitting on their machine. Let GH actions worry about whether the code is formatted correctly.
All of my Ikea products have lasted forever, and my bed is actually better after the last move because the mover replaced some of the parts for me.
There are also windows in Red Hook, New York City IKEA. It's nice at sunset.
In australia, the painpoint is very close. Few people take trains or drive between Melbourne and Sydney, its one of the worlds most heavily used routes. Lockdown meant nobody was able to drive or go by train. Remove aircraft, the burden on australian norms would be immense. In Europe, a case is being made somewhere between 4h and 2h is a place to say "you should not fly" -France had a small panel of ordinary citizens propose this, and its being dickered down by the government but the principle is there.

Mel-Syd is 1.5hr by plane btw. By car its 9 hours. even adding the 1hr either side of flight process costs, its faster than car.

We don't have HST. Its a 20+ year dream to build one.
They're making fun of the fact that during the data breach the CISO was someone with a music degree and no background in security.
You just can't give it a rest can you? You're in total denial of the reality that many people including experts and journalists use the GDP 2 quarters definition, entirely because you are blinded by politics. You didn't even understand how GDP was calculated and had to have the parent poster kindly and simply explain it to you, and instead of being grateful and learning something you've sunk to "it's dumb lol".
Sounds like that 80% could also be covered by talk therapy. I’m not discounting your approach, but identifying fears and their sources is pretty common.
I’m sure it has nothing to do with Ukraine embarrassing Elon by calling him out for a stupid ideas this week.
For anyone who missed it, he posted some stupid tweet about ending the war by capitulating to russia’s demands and they told him to fuck off.
Curious timing if you ask me.
> Why reduce your chances of success by chasing a market that takes more work than other markets

That is the same excuse which was - and in IoT-land still is - used to delay thinking about security because it could be bolted on later. The answer to this question is "because if your business ends up successful you will eventually have to implement this functionality so you have to make sure your architecture allows for it". If your "fast iterations" lead to personally identifiable information being scattered all over your system in such a way that removing this for any given user is an onerous task you made the same mistake as those developers of yore - and of now in IoT-land - who assumed everyone who had a 'net connection could be trusted. That was a costly mistake for which we're still paying off the debt.
Thank you for the comment. I'll update the gist with this.
You should put some contact details into your profile, so people can reach out directly.

Sounds like you have some specific interests, and interesting skills, I'd be down to chat. My contact details are on my profile, send an email!
Yes. The hardest part of a job search is learning not to take the rejection personal, because it is not.
This is confusing because Australian KMart and Target have nothing to do with American KMart and Target. Australian KMart is American Target, while American KMart traditionally looks like a bomb went off inside the store and nobody has bothered to clean it up yet.
I think that often it's not just coding style (yes, a linter should catch indentation errors), but coding conventions/requirements to enforce an idiomatic code structure in the code base. Linters can't catch that. E.g. how to organize files, where to put business logic, how tests are structured, which libraries to use, how to handle non-blocking or concurrent code, errors, code documentation etc.
What I’m missing, is bouncing issues back and forth. We rarely have clearly defined issues, our current system [0] has a "fixer" and a "tester", if I’m the fixer and I need clarification at some point, I set the issue to "missing information" which removes it from my "issues waiting on you" list, and adds it to the same list for the tester.

This is extremely convenient for us as our issues are often discussion threads. I’ve rarely seen this mirrored in other ticketing systems. But then with 1 IT person (Hi), we are not quite the normal customer of such systems.

[0] DoneDone V1, which has an atrocious search function and questionable email notifications, can’t remember what our issue was with their current version V2 https://www.donedone.com/
That's 130,000-150,000 annually if you clock 40 hours 5 days a week, not hourly.

I don't know in what universe you think $150 per hour is low, I've never seen anything near that rate. Maybe for highly specialized work but not any general purpose development.
> The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use child/parent hierarchies to sort these in a tree with this hierarchy: L1 high-level business requirement, L2 technical breakdown stories, L3 very specific requirement/bug/signal.

Support for this kind of overcomplex use case is what makes JIRA so horrible to use. I very much hope Linear never bloats itself by adding this kind of thing.
I have met people with fortunes in the hundreds of millions (which is basically the same as billionaires) and rock stars and actors.

They are all just dudes, and I didn’t expect anything more than that because although I loved to party back in college I made sure to be sober for the lecture on Powers law.

As the sample gets bigger a layman observer can be fooled into thinking that subject x or y is special , whereas in reality it’s just a combination of a big sample and powers law doing its thing
Style is much more than formatting. It's best practices around naming, when and how to add comments, and how to write clear and maintainable code.
You're desperate. That's good.

Desperation built this world. It's the number one motivator of life.

Desperation mixed with insecurity can seem like depression, but if you're really depressed, out of money and with limited prospects. It's time to go ask someone for help.

Alternative ideas: Can you make money on bug bounties? Can you apply to local universities for tutoring? Can you do some gig work just to chip away at the bills?

Most of our lives are spent spinning our wheels. What separates us from or former selves is how we prepare for take off.
So they're obligated to accept bribes if they're in shareholders' best interest?
Those people already left or are on their way out soon, and there is a fresh crop every year
There is a great framework for understanding this process in "The Act of Creation" by Arthur Koestler. His thesis is that creativity is essentially about finding previously undiscovered/underappreciated connections between "diassociative matrices" (which is his terminology for frames of reference or contexts essentially if I remember correctly). If that is true then it sort of stands to reason that people who have many and broad frames of reference because they have a diverse or unusual set of things in their background stand to have more of the raw material for creativity. Or to put it another way, foxes are more creative than hedgehogs.
Ticketing is a form of organization. If it's being used to control people, that's a problem with the org, not ticketing.

Simply having everyone do what they think is best and hoping they talk enough to sort that all out on their own is great until you have several people unsure what to work on, two people accidentally doing the same thing, and management upset because your features are taking twice or thrice as long as your guestimates.

Eventually you realize that for anything sufficiently complex you need to track what the steps are, who is doing what, and when each part is probably going to be done. You don't want to be a bottleneck, so you make it publicly available to the whole team. Then congrats, you've invented ticketing.
> I also dislike how (many) senior folks want to pretend that simple HTML/CSS is all it takes to build anything

Although simple HTML/CSS cannot build anything (not even close), simple HTML/CSS with a sprinkle of good JS can get you very far.
I don’t know. Do password managers absolve people of their responsibility of having personalized secure passwords for different identities?, or are they just an acknowledgment and reaction of the reality that humans just are not able to do so?
> It's much easier to read code that uses named data structures.

That's why a bunch of large Lisp software was written with named data structures in the 70s/80s. They were called class, flavor, structure, frame, ... One can find a lot about that in the literature. Common Lisp was literally the first officially standardized object-oriented language, providing named classes and generic functions as building blocks.