skysight-inc/HackerNews huggingface dataset:
Your time and mental effort are limited.
And your own research is not that effective in areas you have little working experience.

In my experience a lot of older people (40+) increasingly rely on advice/influencers to drive their product decisions.
> This is the second part of a series on the weaponisation of finance

I've been thinking about this right from the start.

6 August 1945 changed the world forever. After Hiroshima global
politics, national identities and the arms industry changed. Are we
actually dealing with a new weapon? After 2022 will we still be in the
same world where coordinated trade and financial information systems
are weaponised against countries, or perhaps companies or individuals?
What are the civilian casualties? (Think of Iraq-I sanctions did to
millions of Iraqis). What will be the blowback? What happens if this
proliferates into a sort of world trade war? Aren't banks in some
sense supposed to be neutral? If not, won't banks themselves become
targets, and what happens when retaliation takes out HSBC, Chase or
Lloyds?
> People are adults.

No, not really. Not all, at least.

I vividly recall from the start of the very first lockdown, when the only people expected to be outside were those attending pressing matters like restocking provisions on supermarket, the local police caught a middle age man who was avoiding the lockdown by strolling around repeatedly with the same days-old loaf of bread under his arm. He didn't even bothered to actually spend a few cents on his scheme, and reused the same loaf of bread every single day to go for a stroll.

And let's not get started on refusals to adhere to simple basic personal higiene measures such as washing hands and wear a face mask, let alone vaccination rates.

People might have the age of an adult, but too many people do not have the personal responsibility expected from adults.
Thats a wonderful thing but I think you know its quite rare.

Influencing is nothing new though the medium change has allowed for a preponderance of people to become influencers to smaller and smaller networks, we've always relied on proxy information if only on where to start research.

It applied to the clothes we choose, the movies of which we might consume the trailers and then reject, the research we do. The universe of awesomeness and crap which we create as a species is multitudes larger than any person could just navigate via pure first order research.

We all need signposts. While I abhor marketing and think hard about how to avoid or reduce its impact on me, its just not fully avoidable.
Similarly, I focused on companies that were based abroad but hiring in the US. Can't be forced to commute from Seattle to Mexico City.

And if anyone is interested in for real remote work, we're hiring SDE & Sr SDE frontend (React) and backend (Python). See my profile for contact info if interested.
>It never ceases to amaze me how many people/businesses have no idea what performance advertising is.

Yikes, that's incredibly unfair and arrogant.

It's amazing to you that, because most people don't have to actually employ performance advertising, they don't know what it is? That someone whose passion is cooking, and decides to open a restaurant, might not have that advertising knowledge? That someone - in the case of the OP - whose focus is writing software that helps research an automotive vehicle's life history, might not know everything you do about advertising?

C'mon now.
Got it, this makes sense, and continues to make more sense the more I think about it.

I appreciate you taking the time to break this down for me.
That's because you have the antibodies. The people who closely follow influencers and who do not realize what the influencers are doing to them, lack those antibodies. This is a sad time to be a person who browses the internet without any jadedness or paranoia.
I'm often contacted by recruiters that have no formal connection with the company that is hiring. They simply find wanted ads, go look for people that sort of match the requirements. When they find some, they'll take them to the company.

There are firms that only do this kind of pirate recruiting, and they even do it for roles where the company explicitly says "no recruiters".
> quite little drive space

> 625 GB

When did I get so old?
I have clicked on more banner ads (though few) about products I didn't know about, than I would ever be swayed by an "influencer", which is the new term for celebrity shill.

Pop ups, however, have made me NOT buy products I would have otherwise be interested in, lol. But I'm a spiteful person.

EDIT: I take some of that back, maybe. I do look at car experts on YouTube, and listen to their opinion. I guess they might be considered "Influencers". I was wrong.
VCs stop wasting money when the company is beyond salvation.
We are in fact the meat.
>I have never trusted anyone and anything. When it comes to spend MY MONEY I do my own research, period.

...so you're "influenced" by whatever sources you research, which means, having reached any conclusion at all, you trust at least some of them.
We haven't done a cloud migration, but I know from zero-downtime DATABASE migrations that if you do this:

- don't use any cloud service that isn't a packaged version of an installable/usable OSS project

- architect your services to be able to double-write and switchover the read source with A/B deployments

If you can migrate your database without downtime this way, then you are much more flexible than if not.
I think that's probably true, but I do think it's useful to continue testing that conclusion. For example, if we looked somewhere and didn't find microplastics, we could then start trying to figure out why.
It's hard to know what happened here without knowing the company and the internals - I know for Google, for the hiring committees I'm aware of (I'm a PM hiring committee member), we cant' even easily see where the candidate is based vs. where the role is based, and it's not something we take into account. We don't care, we just want to say whether the candidate passed the bar to work at Google, and from there it's between them and whatever team they're joining.

Now, there are other places where problems can arise. For example most (all?) hires go to a VP-level review, which is mostly a rubber stamp for more junior levels, but I have seen a few cases where a VP steps in with concerns about a candidate, and potentially that's what happened here - the hiring manager didn't have buy-in up the chain for the role location, and it got flagged at some point.

I'll also throw out there that maybe the recruiter was not wholly truthful, from the perspective that perhaps there was some other problem, either concerns around passing the hiring committee or negative internal references, and the recruiter told you that the remote was the issue instead. I haven't seen a recruiter be directly untruthful, but I have seen situations where the recruiter represented things slightly differently in order to try to keep the candidate's morale up.

As an example, I once got asked to do an interview redo for a candidate - this happens from time to time, either because an interview had to get cut short, or the candidate did really poorly and they want to give them another chance, or the interviewer left the company, but they don't tell you the situation when they ask you to re-interview so as not to bias you. When I spoke to the candidate, they said they'd been told something about the interviewer leaving bad notes and transferring orgs, so they had to redo it - I redid the interview, filed my feedback, and later found out that actually the candidate had bombed the previous interview, so much so that the hiring committee felt like it was an outlier and requested a re-interview.

Again, this is just from my narrow window on one company, but I wanted to share some of the dynamics at at least one company in the FAANG space.
The USD is at or near a multi-decade top in my view.
https://afterbrexit.tech/eu-domains/
What I want (and don’t want) to see on your software engineering resume
But, we now how to convert most of those process to electric. The engineering challenges have been solved.

It is just not cost effective at the moment because you would have to update manufacturing process for all the things you want to change and that takes money. But with cheap electricity, oil/gas becoming more expensive and political incentives...
It is, but it's worth giving companies the benefit of the doubt here. A lot of companies are actively changing their policies. At my day job we're transitioning from full remote to hybrid, and the rules on hybrid are themselves in flux. It'd be real easy for a candidate to get mixed messages if they entered the hiring funnel now. Yes, the company should be up front about the circumstances, but I could see how it would happen.

And yes, other companies are just malicious.
But tips aren't charity. They're even classified as income in tax codes.

Let alone - tips are very often not "optional"

Tips are literally a variable price co-pay for a service.
>They are at most as bad as any other key-value storage.

No, a lot of other key value storage systems allow you to update individual rows and get notifications when individual rows changed, kind of like you know, an actual database and not just an ini file.

>You can update X resources without reprocessing "the whole thing"

No, this is very wrong. What your example actually does is:

- Read the entire global database from the X server, by fetching a property on the root window, which is just a string containing the entire database

- Recreate the database in the client's memory

- Merge in the one resource into the client's copy

- Write the entire global database back to the X server again, by writing the root window property

I encourage you to look at the source code to xrdb to verify this. I don't think I need to explain why this has problems and is actually bad, as is any other mechanisms in X that require clients to write to properties on the root window.

>X resources are not locked to a single toolkit, they are locked to X11, but any application using any toolkit could use them.

Sure. The problem here is that other toolkits will naturally disagree on resource names and will support resources that other toolkits don't, or that even conflict with resources defined by other toolkits. I think we know by now you can't just dump every setting from every app and toolkit into a key-value store of strings and expect it to work.

>which was about applications using their own (or their toolkit's) INI parser instead of using what is provided by Windows.

No not really. Even Microsoft suggests you don't use that function and instead use the registry because, despite all it faults, at least it correctly functions as a storage database. That function is also just bad because it requires reparsing the whole file if you want to read multiple keys.
The company I'm working for is struggling with this. They firmly believe in no remote. They won't entertain it for juniors, and generally to get approval you need to be pretty vital. But at the same time they've also opened up multiple offices (that are all in different geos, timezones). What the end result is that in my section of the company I'm effectively remote working from the off as my team has a remote contractor, and the other teams in my area are all dispersed between home and the new other offices. It's frustrating being told to go into work and getting no benefit from it besides a change of scenery. I'm not sure I'm cut out for full remote at least in my current housing situation/skill level.

I suspect other companies are in a similar situation, and it's part of the growing pains of getting larger. But fuck is it hard to be happy with it.
The alternative is your quite cheap wholesale and retail electricity prices would have gone through the roof.

Nuclear is fucking expensive.
The naive Julia code made a few pretty fundamental mistakes (Complex vs Complex{Float64}, and row vs column major). The following is non-optimized Julia code that is roughly 6x faster (and much simpler) than the "optimized" code in the blogpost. Some further optimizations would give another 2-4x over this (like using StaticArrays), but I'll leave that as an exercise for the reader.

apply_filter(x, y) = vec(y)' \* vec(x)

function cma!(wxy, E, mu, R, os, ntaps)
L, pols = size(E)
N = (L ÷ os ÷ ntaps - 1) \* ntaps # ÷ or div are integer division
err = similar(E) # allocate array without initializing its values
@inbounds for k in axes(E, 2) # avoid assuming 1-based arrays. Just need a single inbounds macro call
@views for i in 1:N # everything in this block is a view
X = E[i*os-1:i*os+ntaps-2, :]
Xest = apply_filter(X, wxy[:,:, k])
err[i,k] = (R - abs2(Xest)) \* Xest # abs2 avoids needless extra work
wxy[:,:,k] .+= (mu \* conj(err[i,k])) .\* X # remember the dots!
end
end
return wxy, err # note order of returns, seems more idiomatic
end
I agree. Here's my screed on the topic:

https://littlegreenviper.com/miscellany/testing-harness-vs-u...
Been there, done that. Can confirm it works swimmingly.

It is much more fun though: don't be clever. Just cache-bust on change.
> Nevada was filling up with Cali expats years before the pandemic

I like Nevada but it gets a lot of CA expats because it was "close enough" for many purposes.

"close enough" is starting to encompass longer distances.
I think leetcode interview is useful to assess the candidate reasoning in front of a problem. If you don't produce a code that runs correctly in 30 mins, this should not matter as long as you have explained your approach and reasoned about options and complexity.
Of course, not all company reason like this. I guess in FAANG interview they want you to nail the exercises during the interview. I think for them this is a signal of exceptional capabilities and a proof that you real worked hard to try to get a job with them.
I agree the impact of and response to accidents is often exaggerated out of proportion. Except for Chernobyl. That one was a monster.

However if you take the long term impact and costs of those accidents and add them to the cost of nuclear power overall, it's not a pretty picture. I would not have supported significantly more nuclear 40 years ago, some but not massive. I do support it now though. We've learned a lot.
Yes, this happened to me with my last position.

Overall, they weren't one of the worst third party recruiters I've dealt with (though I shouldn't have dealt with them at all), but they told me in the first few calls that the position was "fully remote". This was only half-true. It turned out that the employer wanted me to come in 1 to 2 times a week. That was during late-pandemic, so who knows whether that would have been changed to not being remote.

Maybe it was miscommunication, but there's no way I can know that. An honest or competent recruiter would have sorted out those facts.

IMO, do whatever you can to bypass recruiters. Networking, doing presentations, and even just finding the emails of those who are really in charge of hiring, have a much greater payoff with modest effort than dealing with recruiters, particularly of the third-party kind. I believe this is particularly true for junior developers. If you are junior developers, expect most recruiters who reach out to you to be scum of the earth who will drop you like a hot potato if a single employer doesn't end up hiring you. They will tell you that you have "all the skills" and are "perfect" for a position and then they'll ghost you just as fast. Don't take it personally. Those people suck.
There's obviously a cost here. We do this with Auth0 and it makes our SPA a lot slower in some places.

It's an enterprise tool with desktop users, so it's not a big deal, but it's still a cost that we pay.
Prediction: offices are going to become a status symbol for an enterprise to prove it's substantial enough to afford one. It will be mostly style, negligible substance. Perhaps a receptionist/office manager, a couple of private offices in the back for those who desire them, and a conference room. That's all that'll be needed.
It's mostly line of business software and yeah, it took me a year before I got to know the ins and outs of the system so you can absolutely imagine the clusterfuck it is when user acceptance and deployments start coming in
MediaPipe: APIs for Machine Learning Apps
> Imagine the following scenario

"Imagination" is the core of the problem here. Plenty of people are imagining various scenarios, whereas people with successful advertising campaigns are just raking in the money -- no need for imagination.

I've turned off plenty of ads when they stopped working. I didn't need to turn them off to discover they stopped working.

Sure, you can imagine a dozen scenarios where an ad campaign doesn't work. Fortunately, I've managed to learn how to focus on the reality of the situation -- and have reaped the rewards in the process.

> you won't have accurate organic search traffic stats anymore either, because it's already cannibalized.

That' not true for us -- as I said before, a successful campaign for us brings in new sources of traffic from new marketing channels. One of the early lessons I learned was to not cannibalize what's already working. For example, we grew our Facebook Page (and email list) from scratch, when we had no Facebook traffic, by using Facebook advertising.

Operating under different brands -- even just for testing purposes, is a one another of the way we deal with this. Of course you can continue to imagine scenarios where we might be making mistakes. I do that as well -- it's called planning. Though, none of that really matters until money is spent (and made or lost).
Team I'm on obsesses with 100% unit test coverage which means that it takes 3-5x as long to ship a feature while engineers write tests that are:

1) Almost always better to be part of integration test

2) Offer no real ROI because the framework usually handles most of these issues gracefully to begin with, so its just a few hundred lines of cute code trying to mock out shit (or better yet getting multiple people in a zoom and wasting their time trying to test 4 lines of code - WHICH THE FKIN LIBRARY/FRAMEWORK ALREADY HANDLES)

3) Complete garbage. They write the code first and then add tests. That's fine if these were integration tests, but they run their little commands to print out a report that says 92% test coverage. Oh no No nO nO NO No meme-1.gif.jpeg. We have incidents regularly compared to my previous team, which was granted all Senior/Staff engineers and we didn't spend our time chasing dumbass metrics. If you want 100% unit test coverage, just do TDD and not this half-ass yolo cowboy approach. Or just write simple, single responsibility code so it can be tested easily. But nah, you know how it is.

These people are annoying as hell to work with, and unfortunately I work at a bigger company so this kind of BS is normal as people try to chase promotions instead of actually shipping quality products. I personally wouldn't hire people like this, nor keep them around this long.
These posts are always useless without relevant information. Convince me that you know *how* to advertise and then tell me that it "didn't work" and we can have an actual conversation about it. Author didn't even show the actual ads! Targeting, timing, copy, creative, landing pages, retargeting, follow-up... Give us something to work with here.
Oh, hmm, sure, I didn't really look far. But I figure anyone who can cast whole "cartridges" in silver, with such precision and detail, and so pretty, can probably cast just bullets in silver too. If no one does, I bet it's because reloaders don't care to load cartridges with silver bullets -- it's just too expensive!
I don't see how lying can ever be recommended. It purposely misinforms. It distorts the worldview of those who are lied to. You can be honest in a kind way. You don't have to always say everything. But don't lie!

Don't lie, it is not helpful and just misleads those who you lie to. It is cowardly. It's much better to be honest and kind.
A site billing itself "World's Premier Independent Aviation News..." might assume that their target audience is more familiar with those things than the average HN reader is?
Skipping directly just makes you a clown.
Can confirmed the others that pointed out ex-Amazonians aren't pleasure to work with/for.

Will avoid 10/10.

I believe they were molded to survive the Amazon culture, unfortunately.
Netflix is hosted on AWS to name just one such instance. I have heard that internally the customer names are obfuscated, including other Amazon services. Indeed it would be a death sentence to prioritize themselves.
I make my employers put it in the contract before I sign. But I’m not unsympathetic to people being abused by big companies and recruiters. This is some bullshit.
And asset duplication on older console generations. The consoles only had HDDs, and so to ensure a level's assets would stream from disk quick enough they packaged copies of all those assets together. So the exact same game can be smaller on PS5 than PS4 as the SSD makes fragmentation irrelevant.

Often the developers also forget to remove unused files and cut content, but I don't think this has a large effect on the game size.
Ask the people you're talking to where the teammates are, the expectations of return to office. Ask them in the very first call. Either they'll be offended because they probably have nefarious plans (dodged a huge time waste), or they'll happily explain how their team is spread across 4 timezones and could never return to the office since there isn't one.

Sadly "remote" is just a buzzword to a lot of people. But on the flip side a lot of companies are truly serious about it.
Git as a system has no objection to having more than one 'initial commit'. It will happily take that branching history and merge it together. With a bit of branch renaming you can add extra remotes to your repo so both 'masters' are present. Commit to both to make the resulting directory structure not overlap, and then just merge. You'll end up with full history of both.

I did a quick google and these instructions seem about right (without the delete step):
https://gist.github.com/msrose/2feacb303035d11d2d05
The recruitment industry needs to be massively disrupted to stop this bullshit, but unfortunately there's too much money involved so it's unlikely to happen. Stack Overflow had a good effort, but have recently bowed out.
>One FAANG has a recruiting proc where you are hired once you pass the interviews, you can figure out your team later.

I suppose Google fits here, but Facebook is even stronger in that you generally have to accept the offer not knowing what you're going to work on and team match after boot camp.
Totally agree. But the thing is that costs money and the real desire is to tick the compliance check list at the lowest cost. So they throw out some software assurance tech, force staff through a click through phishing training program once a year and low ball ISO 27001 and SOC 2 certs.

Ass covered. Security and defence in depth? Hell no. They can employ the apologetics department dung beetles to roll that turd away quickly after the fact.
> "Failover requires manual intervention" is a feature, not a caveat.

I was scarred by the DDoS of Linode on Christmas Day 2015 (as a Linode customer at the time). I believe that was the only time my Christmas was ever interrupted by work. Of course, one might respond that being the one perpetually on-call sysadmin isn't ideal.
Same story here. I was interviewing through much of 2021 and got a _fantastic_ offer from a local startup but I ended up passing because I just didn't believe their remote work promises. Ended up taking a position at a fully remote company and I'm very happy with it.
Your friend probably has a claim against the company for breach of contract. When people leave a job to join a new one and incur expenses and then the new company lays them off or fires them for no fault then the judges usually side with the employee.
Laravel-Husk – A thin and light scaffolded Laravel Dusk environment