dbalatero

Sorry, did you have a real rebuttal here to OP or did you just want to say the tired phrase "copium" and drive off?

You're not wrong, but GitHub can only control what they can control. They cannot hold everyone at gun point and make them stop vibe coding. They also cannot shutdown Anthropic/OpenAI - you'll have to wait for their A/OAI's debts to come due for that one.

I read it as: "once the dust settles, the capital/debt explodes, and whatever else, we will be left with something there that endures"

Sure, but why?

Consumer Reports has generally rated them as highest in privacy and security, whether or not they've had any issues in the past.

Have a look yourself: https://github.com/search?q=repo%3Apingdotgg%2Fts-rust+unsaf...

Doesn't look like any on skim, also looks like an explicit goal was to avoid unsafe code: https://github.com/pingdotgg/ts-rust/blob/ad8f2746ea85a6354b...

I'm running my 9070XT on NixOS and it's working great. I have Steam + Blizzard games running.

You're presenting this as an exclusive choice, which I doubt describes most engineers. I value both those things.

I'm surprised by the negative response towards this professor. The syllabus was extremely clear up front, and students did not respect it and decided to see what they could get away with instead. Yeah there's some weird rules to follow, but the homework seems fairly scoped to smaller problems and it's just one class out of a few dozen.

Now GP comes off as knee jerk.

I picked a hell of a day to stop impulse shopping.

If they are used, sure.

(as usual)

> I had to bisect over around a million commits to the monorepo to find the culprit.

Thank god bisect is O(log n) at least...

Do it, it's a beautiful work of art.

To me, the ee-oo sound feels more like a Y in my mouth. However if I really draw out the word slowly it feels like ee-oo. But in practice it feels like Y.

I feel like dozens of sites constantly nag me about this. The best ones at least save a cookie to note I'm not interested, such as GitHub.

Sorry to say, DHH invites it.

When one person does it, the FBI is called. When an AI lab does it, it's cute?

Making these kinds of AI projects with fancy READMEs give you a veneer of authority, but the lack of earned wisdom tends to stick out once a few people glance at it.

If LWN isn't your exact thing, consider donating to a project you get outsized value from. For me it's neovim, for you it might be something else!

When it comes to UX, perceived latency is king.

While I have a CS degree from a good university, I think I see things differently than the author here. I think CS degrees are great overviews of the field and give you 4 years to practice programming basics without needing to worry about your job. You also might meet some smart classmates and learn from them too.

However, I think the core issue that individuals run into is that the industry does not stop to train engineers in any kind of formal way. If you do not address this, then your skills will never adequately develop over time. This goes for CS degree holders too, they just might have some more confidence initially from the 4 years of marinating in the material.

There are so many ways to develop your skills:

- cs degree, sure

- pair programming with people that have the skills you want

- helping others with their problems

- building personal tools

- reading blogs, watching videos, and generally soaking up external opinions

- taking projects slightly outside of your skill level

- self-reflection and writing down the problems you have, then actively seeking help with each specific problem

- learning to read error messages so you don't sit there slackjawed when red text shows up

- learning to read documentation and scan for useful APIs

- reading books, if that's a method that works for you

- doing retreats like Recurse Center that push you

- SRS practice with tools like Execute Program

- paid courses with work edu budgets

No one will really make you do these things though, so it is very sink or swim. You don't have to do all of these things, but you likely need to be on some kind of upward trajectory, particularly for the first solid chunk of your career. For me, this is mostly work I would do as part of the job, during 9-5 work hours.

Where are you getting a steak and potato for 2 for less than a bag of Doritos? Is it a 50 lb bag of Doritos?

I mean kinda yeah

Yeah, there's no mandate for government agencies to use login.gov AFAIK, so they can either go with login.gov or buy the private id.me solution. In general it's not a slamdunk to get agencies to cooperate and use their services, it seems.

I've built a few boxes:

https://www.printables.com/model/355924-clickable-touch-id-b...

https://gist.github.com/KhaosT/1406a6b6bea38f59e059c2afcb39d...

You have to carefully tear down and extract the touch id sensor, and then remount it in a box. I went the battery route so it could stay wireless. The tradeoff is the box is bigger.

Reading it is good, but working with it more directly seems to help retention.

You seem to be massively exaggerating here for effect.

I think the main point is, if you're building frontend web apps, you should probably know how HTML, CSS, and JavaScript interact to some decently high level. Can you look stuff up on the margins via AI, or StackOverflow, or whatever? Sure.

If you're building <something else>, you should probably know the core tools and concepts at the appropriate level to build them.

No we do not need to know every aspect of CPU branch prediction and whatnot to make a webpage.

> Of course both are useful, but I’d rather have familiarity with the codebase than a deep general understanding of software systems.

In my experience, getting that familiarity with a particular codebase in a way that isn't surface-level has always been a hands-on process. E.g. just because I know many general things about software, I need to know the particulars of the current codebase I'm in to know what is reasonable to actually apply to it.

This is a chicken and egg problem I find hard to resolve with LLMs. If we're pushed to delegate most work to them, how do you build that expertise? Sure you can ask questions about the codebase, but IMHO that falls under surface-level information, and the devil is often in the deeper details. Hmm.