electromech

I had that experience this week, but with $X as a job title instead of a technology.

Hiring manager: "I see your resume doesn't list 'Frontend Developer'."

Me: "I haven't had that exact title, but I have years of experience building front-end applications using the tools you listed."

Hiring manager: "Hm, it seems like you might not have enough experience as a 'Frontend Developer' for what we need."

> why pay for 2 juniors, when you can get a senior for 1.5 price

That's how it used to be. Now it's more like, "pull the job posting altogether and make your existing seniors work harder because they know they don't have options."

I've had multiple positions that I applied/interviewed for get pulled, and at least two of my friends said the same is happening at their employers -- in one case a team of 5 is now a team of 2, running a critical service for an airline. :yikes:

So, I agree that it sucks for new grads, and it's maybe worse than you think.

My (SWE) job search this year has been exceptionally slow compared to past years. It's discouraging when the statistics don't reflect that, and pundits talk about correcting high salaries for devs — for those of us without jobs, we're having a hard time getting an interview at all, forget about salary negotiation.

I'm not sure how aggregate job posting statistics are collected, but the difference compared to a couple years ago is pretty stark. There are fewer job postings, for one, and more agency postings — meaning, 10 agencies posting for the same job. Except I can't get them to call me back either.

Many positions I apply for just disappear without the usual automated "thanks, maybe next time" email.

The one promising lead I had (with multiple interviews) went poof — they didn't fill the position; just stopped interviewing for it.

I sincerely hope that in the halls of power, discussions are being had about suspending IMO 2020, even temporarily.

> The New York Times leak does include sensitive information - I was able to identify a database of ~1k users (email, name and surname, hashed passwords)

https://x.com/stackdiary/status/1799180195892535441

From the linked article:

> those attempting to download the data via torrent are reportedly stuck at 85% and unable to complete the download... A few hours later, the person responsible for the leak provided another torrent link, which separated the files as opposed to making them a single archive. This new torrent has three folders called nytimes, nytm, and TheAthletic. The two files inside the TheAthelic folder are iOS.tar and android.tar; we verified that they reflect the source code of The Athletics mobile apps.

Thanks. I just had lunch with an old coworker this week. It sounds like the market is tough right now -- lots of "open positions" but few are actually hiring.

"having the recruiter route you to the best fit" is kinda what I want, honestly. I guess I have to apply for enough positions to get to that stage.

Thanks for sharing. I didn't make it past page one (https://app.mentra.com/signup) for similar reasons, and based on your experience it sounds like I'm not missing much.

Apparently they figured out the "why" of their mission but the "how" (how they intend to accomplish the mission) is lacking to say the least. The site feels no different to me from other job search boards -- AFAICT, they're just using different words.

Maybe "understandable" was the wrong word. I don't mean to make a value judgement one way or another. It's a counter-example to claims like this one from the article:

"non-heteronormativity, non-cis identity, non-traditional gender roles, and non-Judeo-Christian books are targeted"

In the BOOKS tab, there are 1,634 unique titles, which gets closer to their number. If that's where the number comes from, they are counting "Banned Pending Investigation" as banned books.

The meaning of "banned" can be misleading. When I looked into previous "banned books" data sets I found that some of the books were moved up an age level (e.g., from elementary school to high school) which is not what people think of when they hear the word "ban." Others were books that sounded religious in nature (e.g., I recall a book from the Christian publisher, "Zondervan") which is understandable for U.S. public schools.

The data set lists the book as "Banned Pending Investigation," and I don't see more info as to why or what that means.

Where does the "1,626" number come from?

In their data set they have 2,551 books in four categories:

Banned in Libraries and Classrooms, Banned in Libraries, Banned In Classrooms, Banned Pending Investigation,

If I filter out the "Banned Pending Legislation" entries, I get 1,164 books.

It sounds like it might not work as well for bash. https://github.com/ellie/atuin/issues/909

Right! Other commenters here seem to have interpreted the article backwards. How I read it: caring and working hard can get you punished; taking the safe and easy path can get you rewarded. Sadly, that lines up with my experience.

Although I still love the work (the real work) I hate The Game® more and more every year.

A slightly less "new" report from a 1931 issue of the American Political Science Review:

Recent crime surveys have shown that the majority of contested felony cases are never tried in open court, being settled instead by the striking of a “bargain” between the defendant and the prosecuting officer. Administrative discretion has thus largely supplanted judge and jury alike. The practice has been severely criticized by Professor Moley, who characterizes it as “ psychologically more akin to a game of poker than to a process of justice,” being “an attempt to get as much as possible from an unwilling giver” rather than “a search for truth.” In view of the technicalities and delay that were permitted to develop in connection with jury trials, the utilization of some such avenue of escape would seem to have been inevitable. The practice may be expected to develop still further unless judicial procedure is improved to a point where a trial becomes an efficient means of disposing of contested criminal cases.

In most jurisdictions, the only alternative to such a compromise agreement has been a jury trial. Trial by a judge alone, the right to a jury being waived, has been regarded as of doubtful constitutionality. Recent decisions of the federal Supreme Court and of the supreme court of Illinois, sustaining such non-jury trials even in the absence of statutory authorization, have gone far toward dispelling this doubt, and warrant an examination of the practical working of the waiver plan in those jurisdictions where it has been given a trial.

https://www.cambridge.org/core/journals/american-political-s...

> Despite my socket wrench not solving all problems

If only, amirite?!

The big brain move is to ask yourself why you haven't enabled strict null checking yet.

Then again, NULL was a $1B mistake anyway, so why not...

reWriTE It iN RUST, bABy!

Right, and "root cause" only has meaning in the context of some goal being achieved. If you're a detective investigating the scene of the accident to determine culpability, your goal is very different than if you're a civil engineer investigating the accident for ways to improve traffic management. It'd be really strange for either of them to conclude their report with a recommendation to increase World Health Organization's budget for alcohol abuse treatment.

--

Therefore, Your Honor, my client is innocent. Why has this tragic accident occurred? I shall tell you to look no further than the root cause...

The Big Bang.

> the fatal flaw

> dramatic oversimplification

> single answer

If someone pitched it to you that way, I agree that's a dramatic oversimplification -- not of causality, but of what's meant by the "Five Why's."

"Five Why's" is a tool, a reminder to separate the symptoms from <waving hands> whatever complex system dynamics that caused them. Nothing about that analysis has to be linear nor yield a single answer.

The key lesson is to never solve a problem on the same level it was created -- i.e., the symptoms. Take the time to think through the causality. If you can go five levels up/away from the symptoms and still find an actionable mitigation for a whole class of problems, great! More likely, you go up one level and at least you won't experience the exact same symptom twice.

My approach to avoiding downtime from slow upstream repos: I run an apt-cacher-ng service in my k8s cluster and have the containers in the cluster build with apt.mydomain instead of the upstream sources. Even under normal circumstances, this makes apt operations blazing fast.

At a local Burger King drive-through, there's an attendant who looks off to the side while handing me stuff through the window. It was a learning moment for me: "so that's what other people see when I'm talking to them!"

Rock on. Hack on, my friend!

As others have noted, you have what appear to be credentials in your repo. If any of those are real, change those passwords immediately. Removing them from your git history only after you've invalidated the credentials.

---

Like, right now.

---

I also use a personal monorepo for all my projects, including an "experimental" directory for one-off things. However, I am (and you should be) much more careful about what gets committed.

One of my rules is that credentials never belong in the same directory tree as the repository. Entries in .gitignore are not sufficient to prevent accidentally committing sensitive info to the repo. Occasionally this rule takes a little effort -- e.g., some project templates default to using ".env" files for secrets, and to uphold my rule, I need to understand the tool well enough to configure a secure alternative.

Another thing that I find helpful for managing a large number of throwaway projects: a global .gitignore with defaults like "node_modules/", "target/" etc.

Interesting read! I don't see the benchmarks discussed at the end. IDK if I'm blind or my phone is blocking images or what. Anyone know where the benchmarks live?

It helps that Signal uses an HTTPS apt repo and includes "signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg" in the apt list entry. If their download server were compromised, (and assuming the hacker didn't also get the private gpg key) the attacker would have to provide malicious archives selectively to avoid detection. Anyone who installed the old key (e.g., me) would notice the key validation errors.

Respectfully, I don't think that's correct, or possibly I am misreading your comment. IIUC, placing a key in /usr/share/keyrings does not allow those keys to sign any package, only the packages designated with "signed-by" in the apt list.

Sadly, plenty of applications still take the old "apt-key" approach of adding the keys globally (e.g., installing keys to /etc/apt/trusted.gpg.d), but I think Signal's installation process is the correct/recommended approach for distributing apt packages securely.

> For now the only target that works is "aarch64" (for a raspi3b machine running in simulation on qemu).

Bummer! I recently purchased an STM32 development board specifically to try out Rust-based embedded projects like this.

Depending on the type of product, maybe a discord/slack community?

Aside from that, unless I'm super invested in a product, the feedback mechanism needs to be ultra low friction.

This example is probably outdated now, but I remember I used to use Visual Studio's smiley/frowny feedback that was (IIRC) in the title bar: click the frown, type my complaint, click submit.

Sometimes multiple choice works too, BUT: the button should be something like "Submit Feedback Now" not "Next"! If it's a "Next" I assume that means 10-100 more questions, including and my SSN and home address.

^^ just some rando's opinions. Take em or leave em.

PSA: it doesn't work on Ubuntu 22.04. I wanted to use it a few months ago, and it's not yet fixed.

I created an account at gitea.com and when I try to edit a file, it says, "You must fork this repository to make or propose changes to this repository."

(Tried on https://gitea.com/gitea/tea/src/branch/main/README.md)

Edit: IIUC, Gitea doesn't support this yet. https://github.com/go-gitea/gitea/issues/13508

(Side note: it's odd to me that Gitea hosts its source code on GitHub.)