skysight-inc/HackerNews huggingface dataset:
The market is though, but you should be getting at least phone screens. I suspect that maybe there's something that could be improved in your market positioning.

I have a similar amount of experience as you, and generally, ageism hasn't been a problem.

Start with the basics, have someone review your resume, no need for a professional, you probably can find a few people amongst your friend able to take a look and give a few suggestions. Ex-manager, ex-colleagues, even a former recruiter that was particularly cool and you really liked.

Recruiters sometimes get confused with resumes from people who can work in multiple languages and frameworks because they are not programmers. They won't understand that someone who worked with node will have an easier time understanding asyncio in python, that the way packages work in Go kind of remember the way you can write partial classes in different files in C#. They scan your resume trying to fill up a map where the keys are technologies and the values are years of experience, so, either you tailor your resume for each kind of opportunity or (better) send a cover letter expanding on your experience with the tech stack from the requirements.

Also, remember that now it is a buyer's market. You need to pro-actively apply for positions to keep your pipeline full. Long are the times where you just went to sleep, to wake up in the next morning and having 6 or 7 contact requests from recruiters in your linked-in.
Cattle are often interchangeable. You cull any that catch a disease (in some cases the USDA will cull the entire herd if just one catches something - bio security is a big deal) In the case of drought you pick a bunch to get rid of - based on market prices (If everyone else is you will try to keep yours because the market is collapsing - but this means managing feed and thus may mean culling more of the herd latter.)

Some cattle we can measure. Milk cows are carefully managed as to output - the farmer knows how much the milk each one is worth and so they can cull the low producers. However milk is so much more valuable than meat that they never cull based on drought - milk can always outbid meat for feed. If milk demand goes down the farmer might cull come - but often the farmer is under contract for X amount of milk and so they cannot manage prices.
It's not like C++ devs have much choice but to deal with this stuff since Asio was effectively kicked out of standardisation.

Asio also has its flaws, but the async story in C++ has quite the cognitive overload.
Thank you for the recommendation! Started reading yesterday and I'm loving it.
> If you designed […]

University department IT is not designed, it grows over decades.

At some point some benefactor may pay for a new building and the department will move, so that could be a chance to actually design. But modern architecture and architects don't really go well with hosting lots of servers in what is ostensibly office space.

I've been involved in the build-out of buildings/office space on three occasions in my career, and trying to get a decent IT space pencilled has always been like pulling teeth.
I struggle to use multiple monitors for this reason. I see my colleagues on multiple monitors constantly swiveling their neck, isn't that uncomfortable? Instead, I use a 4k monitor and tiling window managers like i3 or swaywm that lets me have unlimited desktops that I can instantly switch between with a keystroke.
> you can branch and merge the changes you make

I don't think this a fundamental exclusive benefit of "code" (ie text). I am skeptical how textual merging, especially default automated, can be applied in this domain except in trivial ways. This is a usually easy sell for software because you can structure your system to localize effects (even if there it isn't perfect). The big guns have very sophisticated workflow and tooling for this.

https://www.altium.com/documentation/altium-designer/collabo...

https://www.altium.com/documentation/altium-designer/using-v...

> code makes it easier for them because more information is captured in the code

I sincerely don't understand. Perhaps it is informative to consider that SPICE has been around for 50 years. The idea of using textual description for circuit design is not new at all, and they are used when appropriate. One must ask why the basic workflow is the way it is when the alternatives have always been possible.

> Currently the schematic forces you to have both the documentation and the implementation baked into the same document

Not entirely onboard with this forcing assertion, but is this necessarily a bad thing?
https://en.wikipedia.org/wiki/Literate_programming
Ranchers do eat their pets. They generally do love the cattle, but they also know at the end of a few years they get replaced - it is the cycle of life.
I often go down rabbit holes like this, trying to collapse and simplify the application stack.

But inevitably, as an application grows in complexity, you start to realize _why_ there's a stack, rather than just a single technology to rule them all. Trying to cram everything into Postgres (or lambdas, or S3, or firebase, or whatever other tech you're trying to consolidate on) starts to get really uncomfortable.

That said, sometimes stretching your existing tech is better than adding another layer to the stack. E.g. using postgres as a message queue has worked very well for me, and is much easier to maintain than having a totally separate message queue.

I think the main takeaway here is that postgres is wildly extensible as databases go, which makes it a really fun technology to build on.
The US has followed this as a guiding principle over the last hundred years and largely succeeded, however the end-state seems to be a built environment where car ownership is not simply a widely enjoyed privilege so much as a de facto requirement to go about the activities of daily living, which feels, at least to me, somehow less free.
Pets make sense sometimes. I also think there are still plenty of companies, large ones, with important services and data, that just don't operate in a way that allows the data center teams to do this either. I have some experience with both health insurance and life insurance companies for example where "this critical thing #8 that we would go out of business without" stillnloves solely on "this server right here". In university settings you have systems that are owned by a wide array of teams. These organizations aren't ready or even looking to implement a platform model where the underlying hardware can be generic.
can you elaborate a bit more how did you achieve this. also source code will be amazing if you have it open sourced of course.
Tracking servers is one thing, but tracking the dependency relationships among them is likely at least as important.
Absolutely not. For a country most labor doesn't compound in value.

When a farmer produces wheat the value created is equal to the value of the wheat. When a barber cuts somebodies hair the value created is again more or less equal to the price charged. A barber shop doesn't make anything that accumulates in value. This is true for most the economy. It trades at about 1x revenue.

Tech is different. Write software once, sell it many times. Design a chip once, sell millions of copies. Tech companies are the outliers. The rest of the world doesn't work like this.
fwiw you're likely replying to someone's GPT bot
But in a plane the background isn't moving... it's the inside of the plane, which is always stationary at least with regards to the passenger. I'm not saying you're wrong, I'm just saying you shouldn't need that even on planes.
Sadly, this might well be the case.
Tesla owners told not to wear Apple virtual reality headsets while driving
> I guess rather than regulating cookies, they meant to regulate tracking. Or maybe even regulate targeting, rather than tracking.

When I see statements like this, I wonder: have people ever read anything besides what the industry feeds them? Or the echo chambers of HN and twitter?

Here's GDPR's text: https://gdpr.eu/tag/gdpr/ Please show me where exactly it talks about browsers. Or cookies. You could start with Subject Matter and Objectives: https://gdpr.eu/article-1-subject-matter-and-objectives-over...

> But the giants definitely had something to gain by suggesting they "were forced" to harass visitors.

Indeed. They redirected the ire from themselves to the law and the EU. Spreading FUD works.
TIL that I need to now shred my secret documents before throwing them into the burn barrel. Also, possibly, mix the resulting ashes into a slurry and dump into the sea.
Thank you for your comment. We're working hard to add support for other languages. I agree that exposing a Go library as a C shared object is non-trivial and rough around the edges. We are committed to polishing these edges.
That’s true. You never know when someone’s tire’s gonna blow out. And I think the added disorientation from having to hastily remove an unanticipated blindfold would contribute negatively, as well. I could even see myself pausing for a beat thinking it would come back.
Tech recruiter here with 8 years of experience running a recruitment agency and I have seen 1000s of people negotiating salary (in Switzerland).

I wouldn't never recommend doing what the author suggests, namely: "I’d prefer to discuss the details of the offer over e-mail."

The phone is always better. Busy business people such as recruiters prefer it. Especially, because nowadays everyone hides behind text. Only the phone or an in person meeting gives you the chance to really hear what is possible compensation-wise and then really get what you want.

Btw I wrote this guide years ago: https://iwangulenko.gumroad.com/l/5-salary-negtiation-hacks?...
I don't understand, isn't your team coming up with your OKRs yourself? If you have a manager who is assigning you OKRs, that's a management problem.

In all the teams I been in we have whiteboard sessions where come up with ideas. Then we slowly move ideas into the ones we want to work on, our Objectives.

Then for those Objectives, we set a qualifier to determine if that thing was done, the Result. Next we rank these Objective/Results by priority and we remove ones that will probably not get done, boom OKRs. Not difficult.
Yeah, Cybertruck is shipping without some of its major features enabled. They also have diff lockers that can't be engaged. :facepalm
I don't think this has any consequences for science.

The question is whether the language / metaphor was too extreme as to be defamation.
Some people at Boeing criticize Mulally though. 777 program involved already a lot of outsourcing. There's a nice documentary about the program on youtube, "21st Century Jet": https://www.youtube.com/results?search_query=21st+century+je...
The point of OKRs is that doing the right thing is the most important thing for the business. But how do you know if you're doing the right thing if you don't set and measure goals? You can then reflect and learn from your success/failure. The whole point is to learn whether our assumptions were correct. Otherwise it's just gut feeling and wishful thinking.
I don't know about that. Music is as much mathematics as playing basketball is physics. Musicians I have met, just do it completely intuitively, they can just feel it. Yes you can describe all notes, their relationships and their resonances with mathematics, but you can do that with anything and everything. That is the very point of mathematics - to describe things.

I think it is odd to say that something is mathematical, when all things can looked at through the lenses of mathematics.

Also for tasks that have clear indications of varying degrees of success. Like throwing a ball in a basket. Yes absolutely computers and AI will in time do them better than humans ever will.

But for music once you make a song that is perceived as "good" or "not bad", there is no such thing as better or worse, it becomes entirely subjective. So I do not know if it is possible for anything to be better than something else. For composers and music makers we often assign celebrity status and perceive some greater than others, but really the music some create is not better than the rest.

Maybe AI will be able to demonstrate technical prowess beyond human ability like be able to instantly write down all 15 sounding notes in a given beat in a song. But it does not make sense for it to better at creating music than humans in general.
Relax. “Professionalism” of this sort is almost as nebulous a concept as it is overrated.
> How would you know if a crime has been committed or not unless you actually find out the truth about the event/situation?

How would the police get involved unless a crime has been reported?
Seems like it's less than a week ago that someone (rightly) posted that it isn't [1]. Postgres is a relational database, and it does this really well. It's not a convection oven.

[1] https://news.ycombinator.com/item?id=39243655
hyperfine is such a great tool that it's one of the first I reach for when doing any sort of benchmarking.

I encourage anyone who's tried hyperfine and enjoyed it to also look at sharkdp's other utilities, they're all amazing in their own right with fd[1] being the one that perhaps get the most daily use for me and has totally replaced my use of find(1).

[1]: https://github.com/sharkdp/fd
Art done right is a tax dodge by the wealthy.

Rich person buys a painting, by an artist, for $50 million and puts it in their collection.

Another person buys another painting by the same artist for $75 million.

The rich person gets their painting reappraised by an art expert. It is now “estimated” to be worth $75 million.

The rich person donates the work to a museum, a non-profit. The donation gives them a $75 million tax write off.

The rich person just saved $25 million that would have otherwise been taxed.
Autopilot is a standard Tesla feature which is different than full self driving or FSD.
The U.S. effectively subsidizes drug development for the world by paying higher prices. As an American it does seem unfair, but if you drastically cut prices paid in the U.S., you would get many fewer new drugs, so the cure might be worse than the disease. Similarly, the U.S. has been subsidizing the defense of Western Europe and Asia (Japan, South Korea, Taiwan etc.) since World War II. This is not fair either, but I'd be wary of drastically cutting U.S. military spending. You could say there are "hysteresis" effects -- drastically different drug prices and levels of military spending would not make sense if starting from scratch.
Yes, it's crazy.

One company pays you 50€/h and think you're expensive, another pays you 150€/h and thinks it's a bargain.
* providing context for why work is done and what the outcome should be

* projects with fixed time and variable scope, look at Shape Up by Basecamp for one example, or MoSCoW method for a simpler model

* giving team the ownership and autonomy
NASA APIs
LineageOS and ChromeOS Flex are 2 heroes of extending the useful life of older hardware.
There have already been accidents where some people have had exactly this opinion - that "autopilot" can brake/steer enough to avoid an accident - and crashed or died as a result.
These make analogies make no sense. The author is a self-described expert in fraud and security. It's totally reasonable to ask why he didn't use base-standard advice like, "Don't accept incoming calls," and "Don't give an incoming caller information about your card." This is basic security stuff we tell our parents and grandparents.

The analogy is more like, "Why would a car mechanic put a part in his car that he didn't choose himself?" or "Why would a doctor take pills some rando on the street gave him?" Most people would look at that car mechanic or doctor and think, "How good a mechanic or doctor are you?"

Yes, the expert was "manipulated", but only in the sense that when his "CU" called him, he didn't heed the initial advice experts give everyone -- hang up and call the number of the CU directly.

That said, I'm not piling on him. His article provides a great lesson about how easy it is to ignore one's own advice and knowledge and what the consequences can be. In this case, he /knew/ the right thing to do, but he also knew so much about how the systems worked that he ignored the base knowledge because he thought he "knew" what was happening. In a way, he manipulated himself.
Its a matter of informing people how to use the scales - we have temperature and wind chill but people still need to know that -40° will hit the Midwest much differently than -40° would hit Texas.
The devops meme referenced, "cattle not pets", probably popularized by a book called "The Phoenix Project".

The real point is that pets are job security for the Unix herder. If you end up with one neckbeard running the joint that's even worse as a single point of failure.
It's enough until you start working with json and how painful it is to manipulate data.
Love postgres and use it extensively. However, there's always an issue when I start doing the more advanced stuff: how do I combine that with all my years of experience with version control, code reviews, types, tests, static analysis and all the niceties of coding in general?

Migrations?
I've worked with people that say the same thing, and they are usually very smart and high functioning.

These type of people really need to work on their own startup where they can dictate the quality of work vs selling the product. It's the only way they will understand how to make the compromise between high standards and other long term product decision consequences.
Don't know if it helps anyone but darkreader in "light" mode absolutely destroys the linked page for some reason, works fine in DR dark mode tho
I think everyone is collectively ignoring that I'm specifically talking about accelerating the craft from earth, not using an ion drive or similar form of propulsion on-board. As that's what is implied by the comment that I responded to: "If you could shoot it out at close to speed of light"
Tesla and Apple have teamed up for a new commercial, impressive!
The same argument of UNIX design patterns (Single responsibility, well defined interfaces and communication protocals) vs Monolithic design patterns comes up a lot. I think that its mainly because both are effective at producing products, its just that they both have downsides.
Don't entirely disagree but the investigation of misgendering tweets most likely doesn't need anyone to actually leave a desk so a "thorough investigation" sounds like the police are doing a lot but really it's a bit of clicking and scrolling. To claim the same level of effort for an unexplained death would take a LOT more effort and expertise - but if (I don't know) they are weighted the same in crime statistics the police are going to go for these easy wins all day long.
Sure but I'm specifically talking about two examples that've done an incredibly good job of vertical integration.

I can't think of a Swiss watch company that's operating it's own mines and metalworks, for example, or a British Saville Row tailor that also owns the herds and the looms to make the cloth it then turns into clothing. Both Hermes and Loro Piana on the other hand do this (LP is owned by LVMH).
> could have been outsourcing to China since 2000?

No need to guess. You can actually look at what was imported and exported and it’s nowhere close to making up that gap. 2.2 Billion tons / year isn’t difficult to track down.

> I would argue that it is not being actively addressed at all.

Coal is dying, oil and natural gas aren’t nearly as plentiful. Even if you assume we’re going to extract all the oil and natural gas that exists the worst case is net zero by 2100, with better options leaving more carbon in the ground. As 2 °C means ~620 ppm that’s seemingly already off the table which wasn’t guaranteed 20 years ago.
Do you happen to know if those low intelligence wealthy people are slowly losing their wealth? Or is there a structure (like a trust) that administers this so they can't lose too much of it by their own action.
Summary of macOS VM performance on Apple Silicon
Cognitive fun — Learn your mind. Play it too.
Aspiring to "use the right tool for the job" leads you into conflict with some of the ideas posted on the gist.

To give a concrete example on the first item in the gist: if i need periodic jobs - and all the operational headaches that go with (rerunning, ordering, dependencies, logging, yada yada...) - is postgres the right tool for the job?

It CAN be, but for most people in most circumstances, it's probably not.
> Nope. With actual market forces you end up with Texas-like situations.

The Texas situation was low costs leading to low prices.

But the reliability of renewables isn't to a high enough standard so it'll do odd things to the profits of the remaining suppliers. They probably won't drop by as much as a naive prediction would estimate.
Not "giving away", the lighter and pen certainly are captivating, but more like on a second view some things clearly stand out as CGI.

1. The window. The water behavior is straight impossible, I think. Too much water an the glass.

2. The lighting dynamics and lens distortion are slightly off in this uncanny valley way. Too algorithmic, too smooth.

3. Clearly the lighter and pen have gotten the most touch up. Everything else is a bit too generic. Additive and subtractive manufacturing leaves marks and uneven deposition.

In reality, sometimes things do look weird from a certain angle, and they never avoid the impression of CGI origin, ironically. It's really hard to perceive and recreate the world the way it is, because your brain only ever constructs it as mix of filtered and processed visual input and internal modelling. Very well illustrated with the involuntary multi-stable perception phenomenon [1] and illusory contours [2]. People are blind to the way things don't look like the things they are. I think, artistic mastery is overcoming the inherent limitations of perception and becoming fluent and expressive in the unspoken language of pre-cognitive expectations, symbolism and archetypes.

[1] https://en.wikipedia.org/wiki/Multistable_perception
[2] https://en.wikipedia.org/wiki/Illusory_contours
EU mum as solar industry time bomb ticks
> Of course these systems only get replaced every couple decades, if ever

This is despite the massive energy savings they could get if they replaced those older systems. Universities often are full of old buildings with terrible insulation heated/cooled by very old/inefficient systems. In 20 years they would be money ahead by tearing down most buildings on campus and rebuilding to modern standards - assuming energy costs don't go up which seems unlikely) But they consider all those old buildings historic and so won't.
That misses the point (again). The point is you need some threshold if you’re going to have a standard, or else it’s all subjective and there is no standard. So the standard is 1/8”, and you claim 15/128” is only “marginally” different so it should be allowed. There’s nothing to stop someone from claiming 7/64”, or 15/128” are also only “marginally” non-compliant. You either is or you ain’t compliant, there’s no “kinda pregnant”.

So if you think they should be safety standards, there has to be hard thresholds for compliance. And (again) the bigger issue isn’t this particular incident, it’s that it brings into question how they are managing all hard safety requirements if some apparently slip through the cracks.
On the [Simplify: move code into databases](https://sive.rs/pg), has anyone actually tried this?

My instinct is that the output won't be simpler at all, but a big twisty web of varying parts and competing use cases, all extremely hard to discover. To me, having two things that do something distinct is simpler, and ironically, Rich Hickey says this exact thing in Simplicity Matters, which is quoted in the article.
Turning off servers seems like the wrong call instead of transitioning servers into a lower powered state which can be exited once the power budget is available again.