skysight-inc/HackerNews huggingface dataset:
When I graduated with a CS degree and an EE minor in 2004 it wasn't clear my degree would pay for itself. When the dot com bubble burst, a ton of people got laid off and software engineering jobs became very competitive. A significant percentage of the people in the CS program at my school changed majors. When I graduated in 2004 near the top of my class from a respectable university and had prior work experience, the best offer I got in the Greater Boston area was for $45K. That seemed to be the ceiling for those in my peer group, too. Those with Master's degrees were getting $55K ($10K premium for a Master's seemed standard).

I was pretty deflated. I ended up applying for a research assistant position and fortunately got it, so I went back to grad school. Along the way I opted to start a company since I at least had guaranteed health insurance as a student. I graduated and ran the company for 4.5 years. The job market recovered some during that time.

Software engineering salaries now are monumentally different than what they 18 years ago. For a long time I questioned whether I had made the correct career choice. Of course, nowadays we can't get enough engineers and new grads are being offered salaries that I still have trouble believing (and that took me years to work up to). I don't have a problem with that, either. It's just the last time I saw something like that, the industry collapsed.

I feel reasonably comfortable with job security now. But, that's a semi-recent thing. I worked my ass off trying to stand out in case another dot com situation was forthcoming. And for maybe the first decade of my career I operated under the assumption my salary could be cut in half if the other shoe dropped.

Anyway, my point I suppose is that society sometimes changes rather quickly and it can be hard to predict what's going to work. As the first person in my family to attend college, I had to navigate uncertain waters. But, when the price of entry to most jobs is having a degree, you go and get a degree and hope you can work the rest out later. Of course, nowadays we understand that the US doesn't put any value in the humanities so getting a degree in it is probably a bad deal. It just wasn't always that way and the current trend hopefully won't last either.

-- It's far easier to get an engineering job without a degree now, at least in the US. Even if you could get one in 2004, you almost certainly were going to get paid less and be relegated to back office scripting.
This hypothetical glosses over an essential missing element. The site owner is in control of gating who enters into a transactional relationship with their site or service.

Offering a false dichotomy between "be forced to allow those malicious actors an[d, sic] account" and "take actions to protect myself and my other paying customers" that have adverse impacts (many times with severe monetary damages) is externalizing the cost of poor gating control in the first place in the pursuit of pumping up subscriber numbers chasing the next funding round or quarterly call to brag upon. This is similar to financial services institutions flailing around "identity theft" to cover for gating control of their transactions implemented in pursuit of transaction liquidity over security.

Both take the externalized costs out of customer hides as both uncompensated time and monies spent to make good on unwinding transactions, and in making the aggregate customers pay for the direct costs of fixing the problematic transactions on the way, way back end. Both are a result of implementing poor security practices.

Both also will not scale to the coming era of hyper-converged global financial services. First mover advantage accrues to the one who fixes this challenge at the front end where they gate the transactions, cutting out the majority of the costs of fixing this on the back end after the transaction has been compiled and deployed into production so to speak, not coincidentally speeding up settlement, increasing liquidity, and grab the significant network effects that come with establishing such an infrastructure.
> If anything deviated from the plan, including me getting lost somewhere along the way, it all fell apart.

I hate to say it, but this is exactly why most people are tourists and not travelers: getting lost is the best part of traveling, it's only when you randomly find yourself in the most remote part of say Kyushu that you find the quaint ramen shop that you have the best bowl of Tonkotsu and meet a lot of people that were never mentioned in your AAA travel brochure when you realize what it really is all about.

Nothing about what you said was how I traveled all over Europe back in 2012 and I probably did more in 2 weeks than you did in a year as a result. (I lived there for 3.5 years, and I speak over 5 languages now for those reasons.)

Technology is fine, it's the person who makes it a replacement for Life that is my issue.

With that said, I just traveled half way around the World with 5 phones, none of which had any data (and sim cards weren't recognized in some networks) and I got home fine.
Yes, most definitely. My main work these days is on supporting high performance drawing of such large data sets on GPU. It's not entirely wrong to say that my continued explorations into UI architecture are motivated by wanting to drive the renderer with really high-bandwidth input.
Indeed, they even called the Buddha “the great doctor” because they saw his teachings as the medicine to suffering
So, it seems that you know better than Blackstone https://en.wikipedia.org/wiki/Blackstone%27s_ratio even though, as others have commented in response, the current American system does not follow the principle.
Who, where, and when? Not doubting just curious about the practice.
My experience is that almost any startup needs to write some complex SQL and has to deal with slow query performance, so at least one or two engineers tend to be good at SQL/databases/query plans/indexing/etc. They may not be as knowledgeable or useful as a full dedicated Database Engineer/DBA, but at least you have indices/someone who enjoys writing SQL/someone who thinks about query performance.
I also observe this bias, I imagine it is an artifact of > versus >= on the pixel boundary.
Imagine instead of left-wing politics it was right-wing politics. How would you feel then?

Statistics and Accounting use math to solve problems as does Computer Science. Just don't be that guy who buys 100 Apples and eats 32 of them, what has he left?
You make the weird assumption that any law requires a big monopoly that meddles in everything. Not true. Anti-slavery law covers the ability to discharge with bankruptcy.
Not really. I would never begin an ebay account with selling. I would start with buying, get some positive feedback and completed transactions before moving on to selling small items initially.

As a buyer, I would never buy anything worth hundreds of dollars like a GPU from someone with zero feedback who just joined ebay.
I think the secret to caffeine is tolerance breaks. If you tbreak on the weekends and increasingly up the dose during the weekdays
I used to play Melee doubles with 2 mirrored TVs at smashfests. It was always a huge hit.
Yes. Lots of companies employ them. They tend to be less flashy companies than the kind you see talked about on here. Think banks, insurance companies, manufacturing companies, etc. Not startups / pure tech companies - while they may have them, you're more likely to encounter them mashed together with other roles (data engineer, devops, etc...) in the tech companies that tend to chase the latest dev tool fads.

Personally, I'd take a proper DBA over modern data engineers any day - there's a ton of value in knowing how to set up, maintain and use an effective SQL database. It's just not a place you find shiny new tech, so people regard it as boring and old. I'm biased though - the beginning of my career I was a DBA in a boring industry, but it taught me A TON that still has an impact on my skill set 30 years later even though I'm now working in totally different areas.
Looks like blockchain/crypto related.
What you say also marks some direction: there are new and useful DB technologies to be learned.

Anyway, software world is built on DBs, whether they are administered by someone in the cloud or not.
If you use multiple screens and your mouse gets stuck in the corners, I recommend https://github.com/MouseUnSnag/MouseUnSnag
I don't think you make it sufficiently clear that you've essentially plagiarized this from the Instagramer you link to: https://www.instagram.com/loewhaley

There is no "special thanks". You've copied it word-for-word. I think the only reason you've posted this here is to crowd source more content, rather than do the work yourself.
I mentioned it because Yale specifically is one I passed on due to the loans I'd need to take.

That said, a quick Google says that 12% of student debt per year is taken by students at elite schools, despite it representing a tiny portion of borrowers. Link below.

https://www.brookings.edu/opinions/biden-is-right-a-lot-of-s...
I remember taping printed instructions to motorcycle tank to drive from NC to OH. It rained. That was good times.
I'm located on the opposite side of the world with respect to Silicon Valley, and admin jobs are disappearing quickly here. This may surprise you but we have heard about this "cloud" thingy. ;-)
I'm not into word games, I was just asking. I'll just let it go.
Imagine you're at work, and you have tmux running with 15 sessions to various machines. You go home, connect to that tmux session and you can keep working without having to re-connect/SSH and log into 15 machines and just continue where you left off.

It's sort of like being able to RDP into the machine you were working on except it's text-based.
It is more or less a dead job.

It's important to understand why it existed in the first place. A long time ago, if you were building business software on a database at all, it was a very costly commercial database. Imagine 6 figures a year for the software licenses, the same amount again for a support contract, and a similar amount for the hardware to run it on. If a company is spending $1M+ a year on a critical piece of software infrastructure, that is very complicated in addition to being very expensive, they will usually be very open to spending more on top of that in salary to employ experts to look after it. Those experts are your DBAs.

A funny thing happened when MySQL and Postgres made databases "free": companies (irrationally, IMHO) stopped being willing to pay for experts to run their database software. That duty became a secondary responsibility of developers or operators or both, none of whom really wanted to do it or cared to learn how to do it well. There are counterexamples, sure. Some companies get big enough, and lean on their databases hard enough, that they cultivate true competence in them, but it's rare.

And then along comes AWS RDS (and similar), automating away the most tangible aspects of what DBAs did: HA, backup/restore, configuration, provisioning. There's still plenty left for DBAs to do, but it's stuff people don't understand the value of. As above, the residual DBA duties silently fall to developers and operators.

Also, being able to run databases for $0 in licensing on small-ish, commodity servers has led us to use more and more of them, rather than giant, central, shared databases. This amplifies all of the above effects. It also has important 2nd-order effects on the social organization of our software-building endeavors. When databases were shared by many apps, it made sense to think of them as their own services. When each database is built and run to service exactly one app, that makes less sense, plus it's also easier to push everything onto the devs (as above).

Make no mistake, all these companies still need DBAs. Their schema designs are awful, their query performance is worse, who knows if their backups work, etc etc etc. But we don't see it, because there are so few people working in software today that understand what a DBA is, or ever met (and worked with) a good one.

It's rewarding work if you can get it. I still love doing it. But outside of the Oracle and Microsoft ecosystems, it's not really a career.
That's because he copied it from a West Coaster: https://www.instagram.com/loewhaley/
That ungracious retort would work better if the ZX81 had 81kB.

Anyway, the Commodore 64 famously had a usable 39kB, because the rest of the addressable memory space was usually occupied by the BASIC interpreter / OS (much the same thing on that machine).

However, neither of those numbers is strictly true, as some developers paged in (kinda sorta) the 4kB RAM allowed to the I/O system -- effectively turning the machine into a 68kB box.

Fun times.
That's not optimal though, like the blog says. When doing the first egg, as you get up near the top you've already used up many drops, so the gaps need to get correspondingly smaller.
It's not even a Cochrane review, the newly-created, anonymous account appears to have been lying.
Good news, OpenAlex has launched already in API and snapshot form! Includes most Unpaywall data.

OpenAlex featured in an HN thread a few days ago: . https://news.ycombinator.com/item?id=31271477

Web UI in the works.

Heather
COI: cofounder and dev for Unpaywall and OpenAlex
Last.fm's recommendations were better even 15 years ago. I was spoiled by them, and that's the reason I don't pay for or use Spotify despite wanting to like it. The recommendations are bad compared to other options.
You're doing too much
What is the energy density of these batteries? Last time I checked, it was infeasible to replicate something like a powerwall in even 10x the volume. Which means it is a non-starter for EV.
DBAs do that second thing too, and always have.
Gahdam, they never put you on the yard?
This is supportive more than constructive but this is a really great article. Your code is clear and instructions are really nice to follow. Bravo!
I use Spotify everyday and think it's great but I ignore the garbage recommendation features. Useless.
“How silly”

How quickly we forget.

https://www.google.com/search?q=worst+overcapacity+covid+cri...
I’m not a fan of SF particularly, and there are some problems unique to it, but my experience has been that individuals treating the homeless as invisible non-persons is pretty universal. Have you observed this to be different elsewhere in some large city?
This [1] and this [2] might set some context here.

[1] https://ugapress.org/book/9780820355856/mark-twains-aquarium...

[2] http://www.twainquotes.com/angelfish/angelfish.html
the problem is it can happen to anyone for just about any reason, you've just gotten lucky. meanwhile people who don't even use the platform as much as you get banned much quicker.
It's about these electric trucks

https://voltatrucks.com/

Coming soon to USA
> don't even create indexes and just consider it to be a database problem

is this DBA stuff though? Sounds like creating indexes would be basic junior-level backend dev knowledge?
It is indeed :)
(COI: Unpaywall cofounder and dev)
I appreciate, as described, some of your needs may differ from the standard format (I'd probably still use them to make interoperability between other l languages/people/systems easier though and have my comments etc. in documentation). However, with all that in mind I may not have communicated well enough about CSV as a built in.

> Most of my scripts are small, and adding libraries makes them more difficult to move around. So, I shy away from CSV as a format as a result.

The CSV library I speak of is part[0] of the python standard library. Unless you're working with a restricted subset of the language or something it should have no impact on the size of your script or its portability between platforms/locations.

[0] https://docs.python.org/3/library/csv.html
> ... high-level staffers at Affirm and Afterpay ... emphasized the accessibility of these services, especially for younger consumers looking to bolster their credit and consumers working to restore their credit scores

Something about that feels pretty dystopian.
Thank you, fixed the typo.
Article's a bit of a mish-mash. Mostly points finger at Afterpay and the dark patterns it used both in the marketing campaigns and in app.

Unfortunately it also misses one major point aside from the lending regulation and reporting of debt/late repay to credit scoring agencies, which is how the hell didn't these people underwrite their users properly? In the end it's the company's money that is put upfront.
That's what the comments on /r/nvidia are thinking.

https://www.reddit.com/r/nvidia/comments/uke679/latest_niceh...

But apparently does not apply to the 3080 12gb and 3050 as they have a different LHR lock.
This is pretty extreme take on me suggesting limiting predatory rates on loans.
I've wanted something like this but for "screen" for a long time. Does anyone have such a solution?
Mercure: Real-Time Made Easy
> The right way to do this is giving everyone the same amount of cash and increasing marginal income tax rates.

And in your system, this counterbalances the natural advantage that children born to wealthy parents have how?
Indie Founders community on Twitter – join to grow together
The reason it's frowned upon is that it makes the code not thread safe. This is fine in application code, but if you are a library author, you generally want your code to be as flexible as possible, and able to be used in various situations. Making the code not thread safe brings upon some limitations how the code can be used by your users. This is why using internal mutation sparingly is the default.
Yes, Unpaywall is self-sustainable as a result of service-level agreements with companies who use the data in their products (specifically Web of Science, Scopus, many others). We also recently got a grant to help with additional development and integration into OpenAlex: https://blog.ourresearch.org/arcadia-2021-grant/
Bigger yes but as dense? And how can evolution be that fast?
My approach:

1. Model business processes that you expect to be generating data as well as those that will be asking for data. Both sides inform the design: how hard it is to put data in, and how well the representation supports the different ways you want to get it out again.

2. Design the schema. Pen and paper is a good start, as are some tools that let you do it graphically.

3. Start writing down queries you expect to be able to do. Again, pen and paper/whiteboard. These force you to think through the relations and see if they make sense when you're building queries. It isn't uncommon for a schema that makes sense for putting data into a database to not quite be flexible enough to support the kinds of queries you care about.

4. Prototype, test. This entails not just coding up the schema, but connecting it to some source that will populate the database. I often write synthetic data generators to shove a bunch of data in so I can evaluate queries. This can inform schema revisions to address performance issues.

SQLite is invaluable for prototyping. Last time I did this I used the SQLite manager plugin for Firefox to play with the database design as it was being designed in that 4th step above. Even if the plan is to move to a different database, SQLite is good for getting the rough picture right and playing with it with minimal work/friction.

I have a couple database textbooks around that I refer to that are good references for SQL and schema design. I'd have to go dig them out of a box to find the names though - it's been a couple years since the last time I went through this exercise.
Settle down Nietzsche its going to be okay.
That was a very fascinating read, I'm not sure what it adds here. The US slave trade was color based. The colonies slave trade was through color. And anybody that studies north American slavery without being censored by their state is very aware that north american slavery morphed into a color based one in the 1600s. Every example I gave was 200 years after your example, far after this institution was enshrined as color based ones and extremists were trying to enshrine the US as a land for the white european race where possible. This level of enlightnment is unfortunately a distraction and deflection for what this land deals with now: 400 years of color based disenfranchisement that leaves a class-based disenfranchisements with a seemingly 90% correlation to color.

If you're interested in this topic I would suggest continuing to study it.

Yes as your article mentions, the "Barbary" slave trade was briefly bigger than the transatlantic slave trade, so what happened? Why did the obsession with subsaharan Africans prevail?
Thought we were better than doing /s here.
Not the same extension, but Dendron actually has one:

https://marketplace.visualstudio.com/items?itemName=dendron....
If only cities in Canada and the US simply enforced traffic laws that are already on the books. But no, drivers are free to do as they please because the police does nothing. Actually, the police is part of the problem in a lot of places by double parking or stopping on bike lanes and sidewalks when they want a coffee or a donut. Cities are so human hostile in most of NA, it’s really disheartening.
You'd have to build a lot more wind turbines while you switch cars to electric, and/or invest in some grid scale storage.
i've done this with mosh in past which gets you part of the way there.

problem is that it then doesn't work for local sessions. so you run it locally, which gives you local sessions and window management, but then all remote connections have to be via mosh -or- you mosh into the datacenter which is good for accessing infra, but leaves you having to run a separate instance for local work.
Ask HN: In HN's algolia search settings, what is “your HN login” for?
BU has a couple of cost calculators online here [1] that let you enter data on you and your parent's income and assets and on how many other siblings you have and their ages and tells you how you would likely be expected to meet the costs.

[1] https://www.bu.edu/finaid/aid-basics/cost-of-attendance/net-...
People can and will bikeshed about any subject, this is about a core tenet -- the contradiction of which, would, at most charitable interpretation, be nominalistic.
The proper notation would be "サラリーマン", with a bar between リ and マ which indicates an elongated sound. In fact, writing it as "サラリマン" actually evokes images of a "caricatured western-POV stereotype of a Japanese stereotype salaryman" due to westerners frequently making this mistake.
For anyone interested, I am hiring Postgres DBA’s @Cloudflare.

Drop me a line: vignesh@ or reply here.