plif
Another degree of capability, yes. But we have been trending here for a long time.
I may now have proven why. If you start your prompt input with many compiled JS binaries, it will force the LLM to take an abstract logical reasoning path that we have not seen before. I have run this thousands times against Llama-4-Maverick-17B-128E-Instruct-FP8 and Gemini-3-Flash with consistently working results.
For example, when I uploaded all Facebook binaries (i.e., FB-Static folder when loading facebook.com) at the start of my prompt, then provided my code and abstract brief, Llama-4-Maverick-17B-128E-Instruct-FP8 was able to render a fully contextual working view, considering client attributes, at a cost of of 1200 compute tokens (given 380,000 prompt input tokens).
The punchline: LLMs that we know as "math" models, significantly outperformed LLMs that we know as "abstract reasoning" models, at a small fraction of compute cost. And this may only be the beginning of the punchline.
Seeing is believing. All detailed on the link, including examples you can click and try for yourself: https://terminalvalue.net/
JavaScript Bundles Are Why LLMs Can Think
Show HN: A pipeline to render and serve web components dynamically via LLM
https://github.com/pilifs/Terminal-Value
OP here. I built this repository to demonstrate a specific concept, which is that LLMs are a probabilistic tool that can be harnessed within a deterministic architecture to do much more than "vibe code". Think probabilistic core, deterministic shell.The linked project, Terminal Value, is a sandbox with working e2e examples that demonstrate this. It takes in user context from a mock e-commerce...
I also noticed a significant improvement running it on WiFi after I upgraded to a mesh network. I've only tried over cloud a few times, can appreciate connection requirements may very high, but even being able to load it up wirelessly in different parts of the house or backyard is a big plus for me.
I can see Midjourney already replacing the low end. The question is how good can it get, and then as the bar is raised what can be done to differentiate. Answer to the latter ironically may be going back to old school human interfaces.
Maybe not the most lucrative revenue stream, but not nothing.
I can't game on PC anymore because of RSI when using mouse. Even for cross platform games, the console version usually has far superior controller support.
How wrong they ended up being...
Not saying their QA is useful, but it's not tough to imagine their QA being many layers removed from decision making. ie: Program Manager -> Product Owner -> Project Manager -> Business Analyst -> QA -- not even mentioning reporting lines.
That person in QA at the end of the chain is likely following a script written & approved by the layers above them to a T. It's highly unlikely that they are empowered to go off script or raise tangential issues. Doing so may even cost them their job.
I'd also be careful with the term "programming hours". I'm not sure how the news article got that or who said that initially, but it seems like a misrepresentation of the type of work needed. That estimate almost certainly includes everything involved in getting the code to production. You can imagine that means a lot of QA, red tape and holding the code's hand through environments.
I agree with your sentiment, just unsure what your point of reference is and how much impact the fancy AI actually has. My car (2017 model) has the features I mentioned from the factory and is great on long trips too.
Based on my experience, this statement scares me :)
Not to pass any judgment on your impact or abilities, however the types of devs that have been the most challenging for me to work with are those with this attitude that aren't quite as good as they think they are. It can be incredibly toxic to the rest of the dev team and generally bad for business.
You need to have a very strong handle of both the business side an tech side to do this type of work effectively. Meaning: no matter how much technical debt there may be, some stuff cannot afford to be broken. Judging risk there is quite challenging as you need a holistic view. I would strongly caution people from diving in and making sweeping changes if they don't have this.
The other internal flag that went off is refactors that improve parts of the codebase in isolation while leaving a less cohesive / congruent codebase a whole. This is often worse in the long run than just patching it and actually can make changes harder.
Disclaimer: I am in mostly a management role now so you can take the above with an appropriately sized grain of salt.
We've used Tock a few times in the way you described (recreate resto exp at home) and it's been awesome.
The pay scale is going to be tough. Looking quickly through the top bounties, none of them are really student level. Issues that are truly good for beginners or someone unfamiliar with the codebase in any moderately popular open source project usually get scooped up immediately for resume building.
I can see this as being useful for abandoned projects, or as a way to promote something new. It's a much better signal that the ticket is actually meaningful and impactful than a GitHub tag.
Whether that is enough to get past psychological barriers behind transactions, I don't know. I do like the "buy the author a coffee or two" mentality of support, which I think does remove some of the transaction aspect of it. Not sure if this is what Rysolv was going for -- it feels a bit more formal.
However, tone is an extremely important part of cross-cultural training, and the tone of this article takes its premise from: _you may have a conflict of interest with group B_ to something between _group B is out to get you_ and _group B is evil_. I personally wouldn't recommend it to anyone because of this.
> As a footnote, quotation marks suggest you're quoting someone. Your claimed quote doesn't exist in the source article. Your point would be stronger if you commented on what the author wrote than your (somewhat inaccurate) read-between-the-lines.
The original post has always had the exact paragraph that I derived my subtext from in it. Emphatic quotes are a bad habit of mine, so I removed those, but c'mon -- this is a pretty common grammar mistake and the sentence preceding it pretty clearly "implies" (emphatic quotes) that it's only my interpretation :)
> That's another place cultures differ a lot: how things are implied and subtexts. People misread subtexts, which I think you did here.
Can you please explain how you would otherwise interpret the exact paragraph that I quoted? I'm usually pretty good at seeing the other side, but I genuinely can't see this one. Maybe it's because I've been in management too long (or maybe I'm too Canadian). Either way, I'm genuinely curious.
I'll quote the paragraph again directly from the article for you:
> Expert gaslighters, they are. What really makes me wonder is how the people keep doing these jobs. Many of them are in the very classes that get abused by other people regularly. How can you honestly keep doing that job when you are just enabling the abusers?
The only other interpretation I can think of is the author was referring to the people in the previous example. However, she switches from singular ("person A" / "person B") tense in the example to plural ("gaslighters" / "abusers") tense in this paragraph, so it's either an uncharacteristic grammar mistake or a generalization applied to a broader group.
The generalization is that HR people are "gaslighters" and managers are "abusers".
With that in mind, how would you interpret this sentence? "What really makes me wonder is how the people keep doing these jobs."
I can only see: _how can these people live with themselves_. How is that subtext not correct here?
This is a very cynical take that applies wildly general negative sentiment and statements to a huge group of people. It's not just about workplace dynamics. I couldn't keep reading after the ~5th paragraph where the (not so subtle) point is: how can _these people_ live with themselves?
I'll copy the relevant paragraph below:
> Expert gaslighters, they are. What really makes me wonder is how the people keep doing these jobs. Many of them are in the very classes that get abused by other people regularly. How can you honestly keep doing that job when you are just enabling the abusers?
Sorry, but this is insane. You're generalizing millions of people here. Imagine this type of statement made towards a cultural subgroup rather than a profession. What would we call it?
edit: removed quotes in the first paragraph to reduce confusion around attribution, as per post below. I don't have time to reply in-depth right now but I appreciate the rebuttal and I'll give it a shot later.
Just as important to build (some...) trust and preserve culture among remaining employees.
Imagine this from the lens of remaining employees: A) The new big boss wrote an algorithm to fire our friends B) The new big boss had to make a tough decision to fire our friends but went out of his way to do right by them
Which one sounds better? I think the algorithm was a good idea to explore possibilities, but I'm not sure about the subsequent blog post.
There are recent examples of these layoffs among tech companies who had to make a pivot due to Covid and took approach B. Ritual is the one that immediately comes to mind for me.
I agree that it's a no brainer in a professional context, however I can see there being a ton of value in having a simple / cross-platform / cross-medium personal signing mechanism as well. It's something that we could have used yesterday.