kentm
Sure, but how are you measuring this?
I hope to god no one is actually using the timestamp portion to replace an “updated at” timestamp but I suspect I’ll be disappointed.
Until then it’s all talk.
This is why people go scorched earth with adblockers. There’s a lot of discussion about “good” ad networks being allowlisted, but they are all just one missed earnings report away from implementing dark patterns. None of them are trustworthy.
Its incredibly frustrating to talk to people that take the position of "Well eventually they gave up after pressure from the courts and legislature, so no harm no foul." There's a difference between doing things that have a reasonable legal basis that the courts disagree with and what much of this administration was doing -- sometimes fragrantly ignoring court orders until D politicians got involved to pressure compliance.
Using the 2020 coup attempt as an example, yes, the courts shot down his attempts. The issue is that *he even tried* -- the attempt was transparently not good-faith concern about election integrity.
I think that this really needs to be internalized by a lot of people. I really appreciated when my boss sat our team down and said "Yeah this is the new normal, and I know its not what you signed up for. Its fine to feel sad that your job is changing in such a dramatic way." No, it didn't help anyone actually adjust, but sometimes you just need someone to empathize and tell you its OK to feel bad about this when everyone around you is excited.
> If you read this far thanks. And if anyone has any advice for me, how to go from "thinking through problems by coding your way through them" to "doing the thinking upfront" then really, I'm all ears.
I'm trying to replace it with "thinking through with AI" to limited success. A lot of people recommend having the AI "plan" the thing and review the plan, which is OK. I've also had it do a prototype and poked around a bit, summarized the learnings, and then did it again in an iterative manner without rough edges I've found. Whether you are given the space to do that is up to your org -- its hard sell to "do it again" but I've found that the second attempt leads to better results since I can prompt my way around the problems. Sometimes this also leads to a "Not even wrong" moment where I found out that I framed the problem wrong and the AI dutifully carried out doing the wrong thing.
While interests have a wide variety of norms, communication has a much smaller space of shared norms, and "strange" implies a negative value judgement in most of them. I'm comfortable with my comment.
I feel that the fact that people feel the need to pile on people who enjoy writing code is a problematic trend on HN, whereas telling them to maybe consider other peoples' priorities and preferences is not. The paradox of tolerance is apt here.
People enjoy different things. Its not strange. Treating it as strange is kinda insulting, so I'd recommend that you rethink how you phrase this.
Edit: And thats not a R vs D thing. The requirements have been this way under multiple administrations, and newspapers have not been a primary way of sourcing candidates for two decades.
I really wish this was quantifiable in some way -- I have no way to tell if this statement is accurate.
I've worked with some very skilled H1B that definitely deserved to be here. If companies like Infosys or Cognizant are taking "slots" that could be filled by people like those H1Bs, then I'd consider that a big problem. Companies like these are not doing "highly skilled" work.
Edit: I kinda wonder if the "highly skilled" value judgement is a holdover from the era where people thought you were a genius if you touched a computer.
They are wildly out of date compared to how jobs are actually filled. Regardless of any other enforcement actions, this needs to be fixed.
I don't think it even needs congressional approval to change these. The DoL could do it.
In my mind the issue isn't that it was crafted by AI, but that it wasn't crafted with the intention of getting the point across in a way that respects the reader's time or energy. The result is often needlessly wordy with information buried in a sea of flourish. This might be forgivable if the author had a certain entertaining style, but LLMs are aggressively mediocre by their nature, making wading through it painful.
Its certainly possible to get an LLM to write concise prose but thats not how most people are using them. We can talk all day on HN about the ideal LLM user that is conscientious, reviews the output, puts time and effort into stylistic concerns, etc. But none of that actually matters because thats not what people are doing; the entire reason they're using an LLM in the first place is so that they don't have to do that.
This is an unsubstantiated assertion. I'd want to see evidence that things like this actually move the needle on rent vs things like available housing stock, zoning, etc which seem much more likely to actually impact affordability.
In my professional experience, management tends to treat this as a dichotomy rather than a range. And its lead to situations where we're choosing to route every decision through a small number of 'experts' and expecting that to scale, or have people make very bad decisions about things like indices, data layout, etc.
I align with you on this. If you are using some sort of system, there is a sort-of minimum bar of expertise one should acquire. When using analytical platforms, having a basic understanding of how data is stored and the levers it gives you to optimize data processing should be standard.
Some examples:
MySQL - I would expect developers to be able to come up with a list of columns to index and why, understand why UUIDv4 is a bad choice for primary keys, know how to write performant SQL by hand and understand when their ORM is going to do the wrong thing, etc.
Redshift - Understand dist and sort keys and have some mental models on how data shuffles and is pruned based on each choice.
Iceberg + Spark/Trino - Understand that data tends to be stored/loaded as batch files. Understand how deletes work. Understand partitions and sort as options. Understand generally how bloom filters work and when you should decide to place a bloom filter. Understand why UUIDv7 is better than UUIDv4 when its part of a partition key.