skysight-inc/HackerNews huggingface dataset:
This is also why I think and hope electric vehicle is not the global solution to the too much ICE cars problem, nor is archieving self driving on those cars. A popular solution doesn't make it the best one, it is just the best solution under certain circumstances. Yes I'm talking about tesla.
YouTube, Facebook, & TikTok Won't Discuss Bad Takedowns? Sorry, They're Busy
I think it's so specific to a given codebase that it's hard to give advice that generalizes well.

I have the same feelings as you here, I often feel a little lost trying to decide how much duplication is appropriate in a given case.

I try to not overthink it in the difficult cases. There are many other places in code where it's more obvious, because you can see the history of how people worked with the code, what was the frequency of changes and edge cases added to it etc.

Often it's also just about the readability of the code, I tend to go by the "how confusing it will be for the next person if I defuplicate this code in a smart way" metric.
I work as DE in a local medium business and since there's no giant all-in-one ERP my role is essentialy build solutions to improve (or create) analytics to act upon. It's working and even if i'm not at spaceX, i feel like i'm inventing something. But, since the size of it all..i also fix things (software and hardware).

Now, the problem is to convince other business that they might need my services.
Instead of the gaslighting people that report chatgpt getting lazier and worse over the past month, looks like gemini actually forced them to ack this issue. I've seen alot of people post on twitter recently that gemini was returning all the code without //add your logic here comments and looks like this forced chatgpt to post a response.

With fb + ibm adding another big player in this space, we might even get some ungated models (within reason) soon as that companies "competitive edge" to get people to sign up. I don't see gated models being a nash equilibrium without government's mandating it.
This is why I've grown to like discovering patterns based on changes - new features and bugs being fixed.

I wouldn't worry too much about somewhat duplicated, but easily understood code, like the original example.

I would however worry if I have to fix the same issue in 3 places, or add code for a new feature in 3 places. That's when I start wondering if I can push the code I need to change or add into a common place somehow.
Yup this is the worst part of Clean Code. I've seen real-life bugs caused by this kind of refactoring.

The best part is that the same commit added unit tests so our coverage grew over the magic 80% bar, but of course unit tests don't usually test for race conditions.
After tough years for corporate profits due to covid, is it too simple that this inflation is the corporates trying to claw back additional profit that was lost during those years?

It certainly seems likely
The distance to the second closest supermarket is what matters. I dread living in a city (again) that has only one supermarket.
I live in an American city, population ~250,000 in the city center; 2.5 million if you include the suburbs. Nearest grocery store to me is ~2 miles away.
Not by stamping the steel which is what they’re doing
The thing to do instead is to keep the code simple and concrete, even if it is duplicated a bit.

I think maybe what you mean is it doesn't give you any guidance on when to do that, other than "sometimes".

That's just a matter of taste and experience. It depends on the specific code and circumstances.
> As long as it works, before and after, nobody will berate you for it.

This is not the reality in most places. People care about aesthetics, and about practical issues like how maintainable the code is, even if the code is thoroughly tested.
I'm taking extra good care of the USB-C cable that came with my phone, because I know that USB-C standard is a mess and I don't trust the standard to be able to find a replacement that allows the extra fast charging. I've had it for 4.5 years now.

Apple cables are notoriously fragile, though.
Just use progressive enhancement instead, so the site works in all browsers.

https://en.wikipedia.org/wiki/Progressive_enhancement
You didn't catch the end where they explicitly say

> Secondly, nothing is free. My code traded the ability to change requirements for reduced duplication, and it was not a good trade. For example, we later needed many special cases and behaviors for different handles on different shapes. My abstraction would have to become several times more convoluted to afford that, whereas with the original “messy” version such changes stayed easy as cake.

Clean code is easy to understand and to change. Ideally, any given file or method only deals with one concept.

Messy code usually results from someone merging concepts to avoid duplication. After that happens, differences in the concepts cause the code to become much harder to reason about.

I've seen this particular problem happen a million times. The worst code I ever stepped into was completely DRY. When, where, and why something happened wasn't something the original authors could answer. That's because everytime they found code duplication, they'd abstract. And everytime that didn't work, that ended up adding little "if (this instanceof Foo) special case;" to get over the most recent bug.
Even if they can it doesn't mean they should. People managers should manage people and let engineers engineer. Even if they are former engineers themselves
Interesting, I recall there being a Nickelodeon product called Gak that was ooblek-like. Maybe this is brand genericization?
Wow. Without a < 3 yo phone, it's not possible to switch between 2 apps without one of them being killed?

When I think about my atari 1040ST and what it could do with a single core running at a few Mhz and a few hundred kilobytes of RAM, it makes me realise how wrong we've gone with smartphones.

(before someone mentions it, I know that my atari didn't have wifi, couldn't play full HD videos, etc, and that it was harder to develop software for it, but still, something's off IMHO)
> your problem space doesn’t need an LLM to solve it

Hmmm… kinda opinion right?

I’m saying; in specific situations, you can validate the output and aggregate solutions based on deterministic criteria to mitigate hallucinations.

You can use statistical methods (eg. There’s a project out there that generates tests and uses “on average tests pass” as a validation criteria) to reduce the chance of an output hallucination to probability threshold that you’re prepared to accept… for certain types of problems.

That the problem space is trivial or not … that’s your opinion, right?

It has no bearing on the correctness of what I said.

There’s no specific reason to expect that just like you can validate output against a grammar to require output that is structurally correct, you can’t validate output against some logical criteria (eg. unit tests) to require output that is logically correct against the specified criteria.

It’s not particularly controversial.

Maybe the output isn’t perfectly correct if you don’t have good verification steps for your task, maybe the effort required to build those validators is high, I’m just saying: it is possible.

I expect we’ll see more of this; for example, this article about decision trees —> https://www.understandingai.org/p/how-to-think-about-the-ope..., requires no specific change in the architecture.

It’s just using validators or search the solution space.
The map was cs_filistin (Palestine in Turkish). Note that I wasn't even 18 at that time and had no idea about politics. There was an official CS map named cs_iraq which looked unique to me and I just wanted to create something similar.

I put all the maps I worked on to my web site with some screenshots, comments from me and my friend (in Turkish) and download links.

You can find cs_filistin here:

http://www.canol.info/maps/counter_strike/cs_filistin/ (I need to install an SSL certificate, I haven't updated the web site in years)

You can find my other maps here:

http://www.canol.info/maps/counter_strike/
> “It's the same in most large cities. Of course this is paid for at the till...”

I think it can actually save you money.

I’ve lived in London flats where there were multiple large supermarket brands (Sainsbury’s, Waitrose, ASDA) all within easy walking distance. And smaller corner convenience stores like Tesco Express and Co-op and even Amazon’s one. And also some of the discounters (Iceland, Aldi) only slightly further afield.

If you want to save money you just go to whatever supermarket(s) have the best offers on whatever you want to buy. Waitrose, for example, would often have good deals on olive oil and coffee beans but tended to be expensive for fruit & veg. So I’d buy my olive oil and coffee there but go elsewhere for my apples and tomatoes etc… easy to do when all the shops are close together and you’re walking by them anyway!

Besides, you’d be mad to drive to a supermarket in London anyway, waste of time even if you’re buying more than you can carry: just order online, free delivery is usually available (with a minimum order value).
In the Netherlands this still exists, but mostly in the form of shops "from foreign people". So you have some Turkish stores, a Bengal store, a Polish store, an Afro-Carribean store. They are often run by one person or a family. The customers know where to find these stores without advertising.

Recently, in my town at least, there are a few larger Turkish supermarkets. I don't see the smaller shops take a hit yet, not sure if things will change.
I mean, you can use anything if you just want a dumb pipe to put an ad-hoc data stream over.

My point is that SSE is already a standard to do exactly the thing you're asking for: publish a one-way event stream, with a built-in mechanism for reconnecting and telling the remote end the last event you received (so you can catch up on anything missed during the disconnected period).
The problem is that the source material (the Clean Code book in this case) has almost no caveats. And it rarely acknowledge other styles or points of views. For example, when the book discusses possible objections to having "lots of small functions", it simply doubles-down, suggesting also having tons of small classes, and rationalizes it. Experienced developers know that reality is a bit more nuanced than that.

This is actually a big reason for the popularity of the book, showing a "one true way".

And this carried on to followers of the style. Some linters even enforce the style without much regard for the practicality of it.
Have you heard of Wikipedia? It’s actually rather good.
I had no idea that the numbers were that huge!

In retrospect I could have guessed it. Just read this article [1], that FOIA requests are badly dealt with. It is the same problem. It is just to easy to make the request. There is no economic upside to dealing with them, i.e., dealing with them doesn't generate the resources needed to deal with them.

So my solution to both problem (takedown request and FOIA request). You can still do them, but you pay $100 for the privilege. Nothing major, just to put a damper on it. An appeal is also possible but costs $1000.

[1]: https://www.vice.com/en/article/5d9qna/i-filed-136-public-re...
That's a bit pedantic, no? You use acceleration to get speed.
Small ICEs should just be banned. Leaf-blowers, chainsaws, mopeds, motorcycles. All of them can be replaced by electric motors.
> This is what confuses me though, people don't write things like: What is the most relevant sentence in this book?

I think it's because this is confusing even researchers. The current explanation for why these models are robust (and accurate even) to data not found in its dataset is that various regularizations are applied to the data during training. There is a 10% random token dropout. The optimizers also apply regularization of sorts via weight decay and othere math tricks I'm not privy to. This consistent regularization means the model will try to overfit but randomly fail. Since the token is occasionally missing, the model instead learns a robust strategy of sorts to handle tropes/cliches/common patterns.

Basically, the idea is that since hte model has seen enough "most relevant sentence..." examples, it actually does indeed begin to grok/model-internally the sort of intent and meaning of those words across a variety of contexts which it has also learned (but it's never seen the combination as in e.g. "relevant sentence in this book"). Modeling this internally may be a waste of parameter space at first, but quickly becomes the most efficient way of storing the information - rather than memorizing every instance used in the dataset, you just call the subset of weights which "understand" how those words are intended to be used.

Since this happens recursively as the generated output gets longer (feeding back into itself), there other such strategies that have been developed are also called upon and the whole thing becomes difficult or impossible to interpret in a meaningful way.

I'm not sure of a whole lot of proof of this, but I see these ideas thrown around a lot. This is also found a lot in biology where cells and multicellular life will experience lots of damage to structure, even down to the DNA, throughout a lifespan or series of lifespans. To account for this, instead of memorizing exactly how to walk with n-numbers-of-limbs dependant on how many you happen to lose; life may instead develop a system which can learn on-the-fly how to walk (or in humans' case, wheelchair) around.

As for your last point about the attention vector - I don't know if it could accurately print its own attention vector. But I do think that it could use those values as a sort of temporary solution for "ranking" perhaps. I don't htink that's what happens in the natural language case of "ranking subjectively the `best` sentence in the article" and still think that is mostly the case of modeling language well and in _many_ domains and modes.
if you didn't have frames you weren't shit
Sure, they use the 48v mild hybrid system to act like the ICE when the ice is not running to power some things that would be on the serpentine belt and need to keep spinning when the ICE is off. It's a slightly more fancy engine start/stop system.

> the tech exists within car companies

Of course. Elon said very clearly in the sandy munroe interview the move to 48v everything is nothing revolutionary, its just bringing vehicle wiring into the 21st century. Anyone could have done it, they just have not been able to pull it off before now.

> They have a 12v only model that shares parts and they apparently didn’t want to move everything to 48.

They couldn't move everything to 48v because their suppliers dictate what they can do, and that prevented them.
sure everyone should be able to change the code, but somebody is immediately refactoring new code to align with their own opinions and making it worse in the process is not ok. i would immediately revert the commit if somebody did that to me (and then tell them why of course)
Maybe we all shouldn’t be greedy. Maybe profit as the objective is not the best objective. I’d like to see other metrics in the boardroom drive companies - social good, environment, data privacy, customer service (ha!) and so on… Not just “let’s screw out customers for an extra billion this year”.
Hunting of elephants was widespread among Neanderthals 125,000 years ago
Your logo demo is very satisfying to look and play at. Very cool. Just want to let you know
I like having wireless as a temporary alternative if the usb-c port breaks
Personalized ads are the problem ... not the solution.
Given the choice almost any EE would probably pick the higher voltage system for cost saving reasons, but I imagine they were mostly constrained by legacy compatibility requirements here.

It’a “smart”, but there are probably reasons it hasn’t already changed everywhere else.
“A General Theory of Love” by T. Lewis et al.
Remember how there was a hosting company called "50 Megs" because that was a huge amount of storage back in the day.
True for so much of compsci stuff. You won't understand regular languages, automata, grammars etc until you have done a fair bit of pattern grokking yourself.
DRY might be the bane of my existence as an engineer. The vast majority of developers I meet that are self proclaimed as "senior" are extremely dogmatic. They've had roles where it's been drilled into them {{engineeringPractice}} is god tier engineering and it should be applied indiscriminately to everything you write.

Being a great engineer is about being able to be pragmatic, learn the rules, then learn where you can break the rules.

DRY is like the entry level dogmatic practice everyone adopts, and it leads to some god awful abstractions and it's really hard to explain why having un-DRY code is ok, it's really unintuitive to the "initiated".
Please notice that they do not say which year. :)
At least not with vanilla settings.
Imagine if math books told you that you should ALWAYS solve for X and if somebody tells you to solve for Y they are a bad mathematician :)

That's Clean Code.
What about FB, IG, Reddit?

Hard to know the impact without comparisons.
The long answer is a bit complicated, but the short answer is you should duplicate code.

It is far less work to dedupe WET and abstract later once you truly understand the correct abstraction than it is to try to untangle the wrong abstraction later.

Or as Sandi Metz would say, "Duplication is far cheaper than the wrong abstraction."
Although I really appreciate Fairphone, I've got to admit my experience is similar. I had a Fairphone 2 until the screen went haywire. Not broken, but showed random noise. Replacing it was expensive. Meanwhile, I've replaced several broken iPhone screens. Even if iPhone's are harder to repair, they're still not all that hard to repair. It just takes time and patience. And instructions from ifixit of course.
In particular, a good approach to this is to abstract the common parts to all those into just some very simple functions. Abstract bottom to top, not top to bottom. There is no need to create a single point where everything happens and deals with the 2^n combinations.

You still reduce repetition, you can still change stuff in a single point, but you retain the ability to make custom changes if needed.
The E2E protocol is immaterial, it's about what the endpoint app does and which telemetry it reports.

Not saying they do it, again it's about trust in the context of:

- Meta (the company, not the employees) having a bad track record

- Meta's business model being what it is (building profiles and selling tooling around that), creating tension with privacy matters
The highly involved build process for my doctoral dissertation
Yes it's a shame.

Jon Sneyers (main JPEG XL designer) :

"According to my benchmarks, JPEG XL also outperforms AVIF at quality settings very much suitable for the web, especially if you compare them at same-cpu-effort encoder settings. If you have data that says something else, could you please share it?"

https://twitter.com/jonsneyers/status/1666062661585367042
Funny how it is claimed simultaneously that we enter labor shortage zone and there not being any meaningful jobs for people to do.
Indeed! I was in SF for a few months. Finding affordable food was insanely hard. Fast food was both really cheap and everywhere. Fresh produce and basics like bread were expensive or hard to find, a long bus / tube drive away. Of course it's much easier to fall into that trap of shitty and cheap food.

Where I live the balance is much easier. Vegetables, fruit, meat, ... it's all relatively cheap and easy to get, there's supermarkets and bakeries everywhere. Fast food is relatively expensive, so you get something to think about: (expensive+unhealthy but easy) || (cheap+healthy but you need to cook)
In the UK, the supermarkets, the Internet, and modern 'town planning' have largely caused the demise of the UK high street.

In the 70s towns were smaller, fewer people had cars, and there were hardly any supermarkets, so people walked into the town centres and did their grocery shopping there.

Then in 80s we started getting the first out-of-town supermarkets with free parking. You have always had to pay for parking in UK town centres since I can remember.

And the UK government relaxed Sunday trading laws. Many family owned stores stayed closed on a Sunday - having 1 day a week off.

Then supermarkets started offering more 'range', to the point now where many UK supermarkets are like mini-shopping malls. Clothes, music, opticians, locksmiths, pharmacy, and so on. And they started closing their town centre supermarkets and moving everything to the new out-of-town ones.

At the same time UK planning laws now favour developers building 1-2000 homes with a couple of small shops, no High St. or Main St., and as many houses as possible built on all the remaining space for profit. These developments are unsurprisingly nowhere near town centres, so people need to drive. And they don't want to go into a town centre where there's no supermarket, and you have to pay to park. I don't really understand what we're trying to build over here.

Towns that have prevented mainstream chains (Sainsbury, Tesco, Starbuck, MacDonalds) from setting up, have faired far better. Butchers, bakers and greengrocers, small convenience stores (mom+pop groceries) all still exist in those towns, unlike those towns with nearby supermarkets.

So in part, we're not as bad as the US, but we love our cars, and just blindly go to supermarkets now.
Exactly. most of the roads in Amsterdam will have people driving on them at or below that speed without any official limit.

I imagine bicycles may exceed the limit now.
I think you might have responded to the wrong thread :-)
It's a puzzle game so there's only so far you can go before you watching someone else play it.

In that vein, you can watch people play to see how to do it. I have to admit that in this case, it's not just knowing, you have to be able to execute it in a timely manner too.
> but there are probably reasons it hasn’t already changed everywhere else

Yes, the legacy OEMs are constrained by their suppliers, who dictate what they can (not) do.
"The future of the car is self-driving, but the future of transportation is not the car"
If you can save by going to Waitrose you know you're in a massively expensive area ;)
Does every post need to propose a new One True Way?

Letting go of the Old Way is just as valuable without having a preferred replacement.

It's similar to the bell curve meme about any niche/skill. A beginner only focuses on the fundamentals, a "mid-level" focuses on all the best tools & methodologies (to the point of overcomplicating things), and the master only focuses on the fundamentals.
Mating in captivity by Esther Perel. It touches on how comfort and safety in a relationship can pose a challenge on sexual desire and excitement as an increase in one can decrease the other. It provides realizations and examples that make you think and see your relationship in a different way. It also touches on how societal norms and views can conflict with sexual desires and limit us in expressing ourselves
And once they notice no one gives a sh* they’ll throw 100b at it, then more…..