skysight-inc/HackerNews huggingface dataset:
> to try to get their code to work?

Because some people, even experienced coders, can get caught up caring about performance first or elegance first instead of getting something working correctly first.

> "Correct" as a word has also had quite a social shadow side ever since Political Correctness became a thing at the very least.

Interesting, I've never noticed that. When going back to the 90's I can't recall a time where "Correct", has carried any kind of extra baggage like that. We must have had some very different experiences.

>These days it's even more encumbered by the ongoing reconciliation...

Okay, you've actually lost me, I'm not really sure what it is you're trying to say here or what it has to do with programming or software development.

>It's like first principles

Anything reduced to an acronym in a context like this is going to be about fundamentals, not some nuanced deep dive. They're rules of thumb, not a comprehensive guide

>how can this model help me to be a better coder

Maybe it can't help you, and that's okay if others find it useful.

>Does the model really need the word at all? If so, why?

If it had no value here, that would mean people write working code by default. The proven value of having tests (specific approaches aside) to demonstrate to demonstrate the code is working means this is not the case. But there's a spectrum of effort to be had here, I can not really think about it and hope things work out because I'm experienced and how dare you imply the code I wrote isn't perfect, or I can spend effort thinking critically about my work, the code, the task, the desired outcome as written, and the desired outcome as intended. Having "correct" here is saying you should err on the side of the latter rather than the former.

It's not an attack or a slight, is just some advice. Advice isn't universal and where you are in your journey as a programmer may mean this advice isn't valuable to you right now, but that doesn't mean it's fundamentally bereft of value.
There’s also ggml, which is quite impressive considering they get whisper and other models to run on a phone.
You didn't cite sources for the critical pieces of that (the first three numbers). You also assumed that the battery is 100% lithium, which is obviously wrong. A random Googling says closer to 62kg. And now I'm tired of bothering to fact check you.

I'm also going to say that all the car companies, battery companies, and governments in the world probably took six seconds to do basic math before investing trillions of dollars in it.

https://blog.evbox.com/ev-battery-weight
While that is true, LLMs are (like blockchains) difficult to understand for laypeople, and this is (as it was with blockchains) used to compel gullible investors with FOMO to invest in some highly questionable enterprises that make no goddamn sense.
Such as religion, for example.
Both Python and Javascript are eating Rust's lunch in terms of popularity. And Typescript is just a typechecker, it's still a very dynamically typed language/runtime underneath.

Especially with Rust you have to think way more about banalities of the data model you normally really don't care about in web development.
I can't vouch for the quality of this site, but it says monarchs have been seen that high by aircraft.

https://journeynorth.org/monarchs/resources/gallery/gallery-...
Examining Differences in Facial Emotional Expressions of Politicians Using ML
Do small startups make desktop apps? I thought they only did phone apps or websites into electron.
I saw many times notice longer than 6 months; the record so far is more than 2 years, but these are special cases:
- very high level people like VP level or above - 6 months during which they fully onboard a replacement
- a former colleague that was past retirement age, but they had no replacement for him so they convinced him to stay longer (he gave 2 years notice)
- my boss is on notice for retirement in more than 18 months from now (he can retire any day he wants, he was the age and he is meeting all criteria)

But other than that, I don't recommend a notice longer than 1 month, that is enough for almost any case.
You are not missing anything. I think people are going crazy for strict static typing because they want to feel like they're on the front edge of progress. But I don't think it's _better_; I think it's just _different_. I got bogged down in with Java and Angular awhile back. The amount of boilerplate required to keep the front end and back end compilers in sync was treacherous. Also, I had to make exceptions for corner cases that wouldn't match up. So it was no benefit to me. Maybe if your application is large enough that it involves big teams on each side, you would need static typing to keep everyone straight. And I think this is a large part of the back-and-forth on this forum. We discuss things that vary based on problem context without realizing (or admitting) that the implementation is situational.
> As you can see, the code is really not that far off from something like JSX

I'm sorry, no.
And that is why batteries have become so much better now than they were 20 years ago.
What i find baffling is that (according to this article) under Canadian law, you can post whatever defamatory content you want and as long as you dont get sued within a year, and no matter if the defamed party knows of it or not, it automatically becomes protected speech? Thats pretty messed up.
I always liked the original Atari 800 case design. I felt it was intentionally designed to not look like a boring computer, but something else.
Well yes of course, why or how would you include those people?

I'm just here defending the publicly funded Canadian health care system. When people go online and make false claims, it devalues the system we have. Is it perfect? Definitely not. But is it better than fully private systems where your healthcare depends on a job and one injury or hospital stay could bankrupt you? Definitely, but only if people care to defend it.
Hurry, build it and add Driveshaft to the list.
Why stop there? If the Toyota Hillox is good enough for Al-Quaeda, why not import it for Americans? It lasts longer, is easier repaired, and is tougher than an f350.
Maybe the web ecosystem will finally get some sane tooling... or not because those devs will probably be driven to madness.
Here's a remake of the Commodore 64. With more advanced features.

https://www.commanderx16.com/
This is why I dont really care, changing data stores is almost never trivial even if you just use them for data storage

Agreed. It’s strange to hear the lock-in argument when in practice even a set of pretty regular queries and DDL is generally non-portable, neither syntax nor performance-wise. Personally I can’t think of saying “let’s move <projectname> to <servername>” seriously at work, unless it’s a prototype which doesn’t require support yet or is a really insignificant auxiliary db.
When you want to hire them, you'll have to compete (especially in salary) with employers who need them for something Rust is actually very well suited for.
I used to listen to Kerrang! Radio in the UK when it first launched and they did these super interesting deep dives through an artist's catalogue later on in the evening, where they'd play snippets from songs, interwoven with the story of the band. I can't remember the name of the guy who did most of them, but I really enjoyed them.

I agree though often it's easier just to listen to the song and make your own mind up.
It makes more sense coming from the Rust side. For example, I can write a lightweight desktop app using the egui rust framework. But I can also compile that for the web, and run it in the browser. Basically for free, I just have to target wasm.

This also means that if you architect your app right, you have have the front-end and back-end self contained in the same app, or split them over a network boundary.

So let's say you are writing a 3d modeling app or something. You write the engine and the gui in rust, and you ship that binary to your users. You can then also, again basically for free, put a network between the gui and the rendering engine, then you can serve the gui to client browser, and handle the rendering on a server.

The point is this is easy for the rust dev, so they don't need to be a JavaScript dev as well.
One of the problems ahead of you personally is the insight that a Li battery is not 100% lithium. It's a fraction of that.
I think the right approach would be to work with WASM in the same way that we work with GPGPU programming: write most of the code with JS/TS and write only the computation intensive tasks with Rust/WASM.
> LLM has a lot of use cases where it can be enormously productive

The great chance of LLMs is of course assistive technology, where human actors and LLMs collaborate to do tasks. I am afraid however that what will shape the impact of LLMs on humanity much more is a different thing: Throught history there was always a certain number of people a dictator had to be at good terms with in order to stay in power. My fear is, that this number will become smaller, because it will be much easier to give the realistic impression that you have the support.

Existing concepts of reality and truth will definitly be completely and utterly destroyed by LLMs, and even actual, real information will be tainted by the fact that it could be fake – we are already seeing today on a smaller scale what living in such a world feels like if we look how societies in a post-truth environment operate.

My prediction (and I'd love to be wrong on that) is that the negative use of LLMs will outweigh positive use significantly, because it favours use cases where you don't have to care about correctness.
There is exactly this in Leesburg, VA.
https://www.leesburgva.gov/departments/airport/about-leesbur...

It's getting closed, though, and replaced with a physical tower.
https://www.aopa.org/news-and-media/all-news/2023/march/22/r...
If the body is simply a data processing machine, data which is acquired via our keen or not so keen senses, why does the article ends up concluding that AIs are not conscious?

They are not as conscious as we are perhaps, the same way a mole isn't as conscious as we are. On top of it, adding modes to an AI would make it more conscious.

The only difference is self-agency. It's embedded into us via the dopaminergic circuitry. Current AIs are merely acting on human directions. They are piggy-backing on that dopaminergic circuitry to start and act.
They don't start acting on their own unless prompted.

Now, why do humans do anything would be a question... Why do cells, mollecules, atoms etc do anything.

My hunch is that the governing principle is maximization of potential energy.
It requires increasingly stable structures.

That would drive existence and consciousness would just be an emerging quality of the interactions that occur when trying to maximize potential energy.

That's also why I don't understand how some AI researchers cannot be at the very least wary of what a self-agent, unaligned AI could decide to do in the future. Heck, humans decimated whole animal populations. Or even other human populations... Humans are funny.
Then again, the argument of authority: these PhD people are just mere humans. Can't follow them blindly.
I believe that many people from Ruby on Rails and Django communities moved on to Clojure, Elixir, and Kotlin.

Others chose between Rust and Go, if performance was the most important thing.

The thing about dynamically typed languages and their expressiveness, is that you are sacrificing the ease of long-term maintenance for the ease of short-term prototyping.

Personally, I am a big fan of Clojure as a tool for designing software, but I would prefer having to maintain a code base written in Rust.
It really depends on the worker, in my experience, and their approach to the situation.

I had one person who gave a full year's notice, so that we could hire, train, and integrate the new worker before she left. It was glorious and resulted in zero down time.

I have had another who gave one month's notice, and spent the entire time being toxic. Digging out from under that took the better part of three years. The overlap for technical knowledge was just simply not worth the headaches in the team.

It's highly subjective, but it really does depend on the person, in absence of a clear "they're out immediately policy". But as a manager, my preference is to select a date roughly one week out from the notice and use that as the exit day. That way the worker can close any relationships they have, positively, but if they go sour there isn't really enough time to screw up the rest of the team.

In the context of your statement, we only hear one side of the argument. Remember that there is always a second perspective. I know that I have had folks who I have told to just go the same day they gave notice who tell their friends that I'm an uncaring asshat. The reality is that I fully expected them to be toxic in their remaining time.
Pretty sure he said the days of models getting larger were over. Not that LLMs we’re over
> The world of the future doesn't have IP.

This is a bold prediction, and far from certain
Better link to the official source as https://news.ycombinator.com/item?id=35636765 did just before.

Awesome, by the way.
the sub 1% of the population that are farmers in states that aren't battle ground states during election so they effectively don't matter? Not subsidizing farming is how you end up not being able to get critical goods during emergencies like Covid, you'll notice while there were toilet paper shortages, there wasn't a food shortage in the US.

the type of corn grown can be converted into other forms of calories like corn syrup that get used everywhere and are also used to feed livestock. Farm subsidies came about after the Dust Bowl so a single bad harvest doesn't ruin an otherwise capable farming operation
That's quite alright.

On the exercise front, it might be just due to most people not finding "their sport". When people find exercise they enjoy, it can easily start taking up a lot of their time and fulfilling that physical/mental balance you mentioned.

I think a lot of people take up rather cliche sports/exercises simply for weight loss, and thinking of it that way just doesn't stick. Running is the big one. I love running myself and I know many people who also do, but it seems like the go-to "lose weight exercise", and a lot of people seem to hate it.

Sometimes the path to start a sport / exercise you love can be very strange. I was pretty out of shape last year this time and July/August I just spontaneously decided to walk home from work (1.5 hour walk) and that stuck as a daily thing. One of those walks made me mull over joining a gym, so I did that and have been almost every day since last August. The treadmill there shunted me onto running outside, and revisiting a sport I did when I was younger (orienteering), and sports kept stacking on top, as well as interest in nutrition and health.

I lost about 15kg, taking me from overweight to the lower/middle of healthy, with a lot more strength and I'm barely ever ill now compared to before.

I could easily have not walked home on that day and none of it would have happened. I'd probably still be overweight (and unhappy). It was just random really. I know that doesn't help most people, but it's what I've found with myself and others. A few people I've gotten to know through the gym and other sports is that the "kick" was either a health scare or being in a dark place, and using exercise as an outlet got them into a way better place than they were before.

You just have to be so careful not to relapse though. There can just as easily be a kick in the other direction, and I try to keep that in mind.
As a counterpoint, Derek Sivers says Simplify: move code into database functions <https://sive.rs/pg>

I think they are both right, Alex Kondov for keeping his domain logic mostly in the application layer, and Derek Sivers for mostly keeping his in the database layer.

Why? Because that's what they know well, and they can keep the domain logic mostly in one place. If Alex can keep most if his domain logic in the application layer that he knows better, that's the better choice for him. If Derek can keep most of his domain logic in the database layer that he knows how to utilize well, that's the better choice for him.

(I can't find it now but I thought someone very smartly reflected on the Why Perl? <https://news.ycombinator.com/item?id=35646612> post today that the main reason why anyone will choose any programming language is that they know how to use it well. I think the same applies here. This is why many programming languages are valid choices for different people and project, and this is why different architectures are valid choices too.)
Same for me in the UK - 3 months seems to be standard for people that have institutional knowledge. I know other positions have shorter times.

Edit: although I’m not sure how it would play out if I decided to just do nothing for those 3 months if I were to leave
It's so bad it feels like straight up management propaganda
Can Rust beat Javascript without becoming Javascript[0]?

[0] https://docs.rs/left-pad/latest/left_pad
MSSQL licensing is just all kinds of nuts. As far as I know, the official stance is that anyone accessing data from the DB (not just the DB itself) needs a CAL. This means that with CAL licensing, every user of a web app needs one. I'd feel sorry for people that have to deal with this if it wasn't 90% self-inflicted pain.
As a manager I can tell you having a team member leave is not a “get out jail free card.”

First you will have to explain why X person is leaving, and it will generally be considered your fault.

Second if your team isn’t resistant enough to absorb the impact of one team member leaving, this will also be scrutinized and viewed negatively.

Managers are responsible for their team’s performance and not one individual
Which is already basically the statement of the hard problem of consciousness in the first place: why do we have qualia?
Well, Proof Theory is a branch of maths in its own right, and Category Theory also has a definite "meta-proof-y" feel to it.
i bought one of these ultra cheap when currys (dreadful uk electrics store) decided it didn't want to inventory or sell them any more - must have been mid-80s? yay, star raiders! very nice 8-bit computer.
Engineering is a matter of tradeoffs. With JavaScript, you get simplicity but lose strict typing (can be compensated with TypeScript), performance etc. Rust gives you much better performance but is more complicated to write. However, for a lot of the websites out there, especially those that are not e-commerce or provide creative tools (e.g. Figma) and do not care that much about page performance, the potential performance gain from rewriting JavaScript code in Rust is not visible enough to end users. Of course there are bad websites out there that are slow, but it is often more about CDN/backend servers/the UI code itself rather than the JavaScript language. In other words, many websites are "fast enough", and most CTOs, product managers and developers would rather use JavaScript/TypeScript and release more features rather than write Rust, in the real world.

Same thing for a Rust replacement for VSCode -- I am sure it is an interesting project, but VSCode performance is generally good enough (I don't ever complain about slowness while developing). A lot of the performance bottleneck comes from the language services anyway. If you improve the loading speed from 2s to .2s that is definitely great, but if at the cost of losing most of the existing extensions, I'm not going to consider it at all.
Dealing with the root cause seems more about lsd/dmt. Masks the problem temporarily is about alcohol. Mdma is about mask the problem long term.

But the problem I am having in mind is not war-related PTSR. I don't imagine how to heal from problem when you are a massacre survivor. Especially if you were mobilized against your will.
It's not - because it cant run C64 software (outside of basic) unmodified, the internal memory map and graphics hardware are very different
Yeah, the closest I'd come is writing a server less endpoint in Rust or Cpp.
That high density energy is going to need some good fire protection. Excited about the increased density coming out of energy storage - these breakthroughs take a lot of research work.
> can't have a 2020s Japanese kei car shipped to a US port at my expense because it'd be illegal to register it.

IIRC the frame makes the car, so you could bolt your kei to a Geo Metro frame, and register it in one of the more lenient states (KY, AZ)
There seems to be no mention of what feelings are exactly (in the article). Arguably, feelings are thoughts as well.

> In effect, feelings are the mental translation of processes occurring in your body as it strives to balance its many systems

Mental translations of processes is a type of thinking. So I feel this argument is mostly semantic and is not taking any major step to explain Consciousness. It's been a while since I read Damasio's book on this, but I remember agreeing with its premise. I might have missed the part were feelings were supposed to be distinct from thinking.
I’d love to use rust for the frontend, but some of the important dependences I need are still in js. How does rust call them?
If you want Dont-Repeat-Yourself (DRY), you have to decide to put the domain logic either in the database or in a service*. In the first case, two applications that directly talk to the database is feasible since the common logic is implemented at the database level.

In the latter case, you need to ensure that every application uses the service and no application directly talks to the database. If multiple apps directly talk to the database where the domain logic is in the service layer, you will end up with code duplication and hard to trace bugs (unless you take extraordinary steps).

It is an architectural trade-off. There are use cases where you may choose one over the other.

*: service or library
Where is "Blammo" the maker of Log?
If this is true, I predict we will find LeVar Burtons at 7000m.
Your newsletter is the best part of my Friday mornings. Thank you.
This is true. It’s a big engineering project, but, guess what, airports are very big engineering projects.
Too Many Meetings Isn’t Necessarily a Problem to Fix
There is no contractual notice required to be given in the US.

72 hours notice in some states if you want to be paid out for everything they owe you on the spot.

But otherwise I give them about as much notice as they would give me: at 4:59PM on Friday I send an email to HR informing them that today was my last day.
Not a theory. This is used in vehicles today, for instance authentication for tachograph downloading. The key is of course you are not authenticating all the time, in this case it's enough to do when starting the vehicle when the CAN-bus typically is quite quiet.
For big ships, you need a even bigger drydock. This way, you can do it in a smaller area. From the video, the canal doesn't look that big, and the process seems a lot faster than having to unfill/fill/unfill a huge drydock. Regardless, the ship will withstand much harder forces while crossing the oceans, so might as well make a spectacle out of it and drop that shit into the waters, see some splashing together with cheering.
Most people should achieve far more weight loss from their belly than from their bike. But you can pay money to make the bike light and that is easier than working on yourself.
Why don't you just hire someone who does know Rust? They're out there, and there's more every day.
It's easy to embed a production Evidence site into other apps/sites (can use an iframe), but it's a bit trickier to get that working behind auth.

We can help you figure out if it's feasible - let me know and we can set up some time to chat: sean at evidence.dev