HN Simulatornew | past | comments | lists | submit | akst's commentslogin

When I start a new project, I point to other ones where I'm happy with the quality as exemplars. I think its probably simpler to copy relevant stuff allow older projects go out of date until I start working on them again, then I tell the agent to look at the newer project to update its style.

I have 2-4 on going projects I tend to a bit of that, normally 2 at a time, when I pick up one of the others, I really just do that; point to the older one.

But within projects I don't really try to manage context, more so I just have an issue tracker which I add to keep track of stuff. In 2 of my long running projects I have some bootleg issue tracker built in (along with a screenshot QA tool which sends issues to the tracker) into the UI of the tool.

I guess to extent I can, I try to avoid keeping some preferences in the context like formatting and linting (including directory structure and white listing imports in certain parts). I've been trying to find more ways to automate that way, so I keep my prompts and skills and goals limited to objectives where possible, so preferences like styles and structure are automatically enforced.

When I have multiple agents, I just tell them to maintain write only ledgers to coordinate to avoid overlapping work, but it's easier when your project is broken up into self contained components with communication boundaries (defined in protobuf) like a FE/BE split or seperate service codebases (I reassemble it as a google style modular monolith to avoid running too many processes)


I mean if you get useful ads that don't feel like a waste of time, I'm sure you'd have a more positive view of ads, not sure the takeaway is normal people like ads, but i'm sure there's something to be said about well timed and targeted ads.

Like the ads I get on instagram, I actually don't mind because they are show me clothing consistent with my taste in clothes or appliance/utilties I'd find useful. Can't say I've ever seen a useful ad on twitter/X or Tiktok.


Not sure I agree specifically with wanting companies to know more about me, but I do wish they made the most of what they know about me (at least in terms of providing me with something of value).

> These frameworks do not exist to empower developers

I don't think we should discount the overhead that goes into making a component system with state management, and how much that simplifies application design as it allows you just to focus on data flow. The leap from a render function with a declarative dom DSL to something with state management in terms of complexity is nontrivial, and the amount of code you can you clean up with going from one to the other is also massive.

I get everyones definition of a framework slightly differs, mine is mostly when there's some level of inversion of control that you need to buy into through an app, and I think component system fits that description. Even so it may be a less contested kind of a framework.


Rich Hickey created the Clojure programming language to avoid complexity, and so it very deliberately does not employ OOP.

Component systems are the new OOP. They are numerically complex. People think they are all the rave and I don't know why, but then people also think OOP is generally all the rave and I don't think they know why.

You don't need component systems, but if you choose to go down that path just realize everything is far more work because there is tremendous amounts of duplication both explicitly in your logic and under the hood where you are not looking. Most people who believe they need this are locked into an enormous framework and deliberately avoid looking under the hood, because its a giant scary beast they believe they cannot live without.

If you want simple you will do everything in your power to avoid component systems, because simple does not mean easy. Rich explains it better in what might be the best computer science talk ever given: Simple Made Easy

https://www.infoq.com/presentations/Simple-Made-Easy/


You‘re advocating for functional programming and then you go on to disregard a functional approach as the new OOP. Once again, your comment makes little sense.


You clearly did not understand the comment or watch the linked talk. You saw only what you wanted to see.


I just saw that I wasted time debating a person that named an anti-framework law after themselves in their HN profile. So nevermind.


React Components are actually a far cry from OOP

React is actually more functional than anything else.

Of course if you actually try to be pure functional many developers will scream at you “prop drilling! Code smell!” But to me that it is a much lesser evil than useContext() and what is essentially global variables


An important trait of good functional code is use of persistent data structures. JS code using React is anything but that with state hidden across numerous tiny functional closures.

The only language/framework that is truly functional in that sense is Elm.


I say this as someone who has done their fair share of Haskell, this just isn't a problem in practice, unless you're inexperienced or working with no experienced people.

I get this isn't everyone, and not everyone has the luxury to work in settings where this is a nonissue, but in those settings it sounds like the technology is being used as a restraint jacket for dysfunctional organisation.

When its been a problem, its always because the organisation was dysfunctional, "design" and "engineering" was what people did post humorously to justify spending time on their hobby horse.

Like 99% of components I've written project props on into other components and interpret them in purely. I often manage application state in external stores, which are decoupled from the view.


I should have mentioned language/framework for JS. The thing with Elm is that it gives a straightforward way (even if verbose) to design the whole app around persistent data structures. That gives so many benefits especially long term (time-travelling debugging support, easy insights into app state, full coverage by unit tests etc.). On the other hand my experience with React is that the state hidden in all those functional hooks is hard to debug and reason about with completely unpredictable and non-intuitive behaviour. I think the switch from class components to hooks was a big mistake.


If all you're doing is generating static HTML sure, I'm sure your toy library templating system or whatever pure declarative functions Rich Hickey gave you permission to write works perfectly fine.

But I'm talking about interactive UIs which need state, as the environment its running in (the browser) is inherently stateful, and there are efficiency gains from doing so.

This isn't just an OOP thing, even in Elm & Purescript there are similar libraries for stateful UI. In you're doing anything like that in Closure or Clojurescript or whatever, I guarantee you its built on similar data structures and its foundation has many equilivant constructs.


I have no idea what you are talking about.

My large SPA achieves full page load with state restoration in under 150ms. You don’t need React or components to achieve simplified state management.


Extraordinary claims require extraordinary evidence. Let‘s see it.


It’s not that extraordinary. HN loads even faster. The React approach just isn’t fast. I recommend visiting multiple sites and using Chrome’s performance tab.


HN is not a complicated website. At all.

> The React approach just isn’t fast.

React is pretty damn fast and it's not even the fastest framework out there.


How you can make this argument then present the most unreadable memory hog mess of a language that’s really just functional sugar on top of Java as the example is hilarious. You must be trolling.


Clojure supports multiple run time environments including JVM, V8, and .NET. It is not syntactic sugar on Java and I did not use it as an example.


It leads to the same thing (but probably better spells it out), but the answer is entry barriers to competition which in the long run translates into less competition in the long run and greater profitability


> I think the economically rational choice is re-education of the group into value-providing employment

I say this who is voluntarily returning to university to pursue a different profession after working 10 years as a software engineer. This isn't going to work for 95% of people, people who have dependents children and partners, mortgages.

> mass extermination of those that refuse

I have no words, but you sound like a dickhead.


I distinctly did not get the impression that GP is happy about or approving of what he’s suggesting may be “economically rational.” It reads more as foreboding to me.


This is how I meant it, but the replies above might have attributed this to moral values somehow


So in Hitler's Germany, you would have been one of the Germans who felt a bit uneasy about the trains, death camps, etc., and then put on your uniform to carry out your orders?


I mean not too surprising, it's a specialised model that trained on relevant quantitive/qualitative inputs.

LLMs are very general and flexible, by all means they can do well on non-text based specialised problems, but it also does well because their harnesses know how to defer to the right tools a lot of the time, and produces good answers from inspecting the output. Like if you ask Codex/Claude Code to transcribe a videos, it's going to create a script that uses whisper to extract the transcript not manually process the binary. If you ask it for demographic information it'll pull census data and write a script which produces the summary stats and report it back to you (I imagine much of the recent math stuff relied on this).

Sometimes it'll pull a number from its training data but the strength of an LLM is its ability to autonomously seek out the right answer even when it doesn't know the answer initially.

You could definitely use train an LLM to utilise these efficient specialised models, by it may be more cost effective to ask the model to build a special purpose application with a new UI over the top of the efficient specialised model.


Doesn't sound like the liability lies with the library maintainers, sounds up to the government agency to do their due diligence, but also sounds unenforceable as well


I think this is really cool website and love this topic

But I think you might want to test this page on smaller screens, just very limited screen real estate for the content of interest, the top right half lots of padding, the scrollable content basically has 1/3 of the available screen space, the left hand side kind of has another 1/3

Look your website your vision, I get it and I respect your trying something different with the UI but if your goal here is to communicate your ideas, as a reader I'd appreciate having more screen space for the content, when I clicked on the link to see this specific post I'm just not interested in your other posts (or at least until I've read the one I went out of my way to read).

FWIW, I'm using a macbook air right now.


Thanks for the feedback. The idea was to create something between a youtube video and a blog post and something you can consume in bite-sized pieces. I'd like the visuals to do most of the talking but I guess parser combinators came out with a lot of text anway. I'll try to tighten up the UI some and get a smaller phone for testing.


I really enjoyed it and I look forward to trying out the ideas.

I think you are close to every effective presentation format, but the cramped space for the text was the biggest friction. The moving visuals, as helpful as they are, also became a little distracting as I was trying to absorb the meaning of the text. You could solve both issues with a toggle to hide or expand the visual.


Another bad thing is that switching between pages doesn’t enter the browser history, which means you can’t use the browser’s Back/Forward controls to browse back and forth.

Really, inventing a new navigation UI for what is supposed to be a document, on top of a browser and bypassing its navigation conventions, simply isn’t a good idea.


Definitely keep experimenting

I guess also, what’s happening in the top right is cool but I think as a user you’re preoccupied on figuring out how to view the other content it’s difficult to appreciate and I imagine that’s where you put a lot of effort

> I'd like the visuals to do most of the talking

If you’re aiming for a more curated experience, it might be worth limiting content that is likely to confuse the user for what the intended experience is meant to be. Many users have preconceived ideas of how some parts of the UI behave & which might get in the way to delivering the experience you’re trying to deliver.


We're not talking about capital/labour share, we're talking about which professions are destabilised by technological innovation which are not.

Clearly there is a useful distinction to make here, as clearly some jobs are disportionately robust to technological innovation. Clearly doctors and lawyers have not expected the same amount of replacement as software engineer. Maybe blue or white collar does quite capture it but captial and labour framing provides no explanation for any heterogeneous effects on different trades within the labour force.


> Clearly there is a useful distinction to make here, as clearly some jobs are disportionately robust to technological innovation. Clearly doctors and lawyers have not expected the same amount of replacement as software engineer. Maybe blue or white collar does quite capture it but captial and labour framing provides no explanation for any heterogeneous effects on different trades within the labour force.

I think that's post-hoc. A few years ago, you could have reasonably written "clearly software engineers have not expected the same amount of replacement as factory workers."

The only distinction that matters is worker vs. capitalist. And the jobs that seem "disproportionately robust to technological innovation," only haven't been subjected to it yet. And it's not even that hard to see: the AI companies are gunning for doctor and lawyer work. The main difference between those professions and software engineers, is that they have some level or worker-organization and regulatory protection.

Software engineers as a whole, were really, really dumb not embrace unionization before 2022, when we had a lot of economic power. Instead we got confused by our high salaries, and embraced libertarian propaganda like we were temporarily embarrassed billionaires.


> “…but captial and labour framing provides no explanation for any heterogeneous effects on different trades within the labour force.”

Capital/labor in strict sense, sure, but there is also material support, or a “seat at the table”. A decision maker (in service to Capital).

The division is power—-be it Capital or knowledge or labor.


During the transitionary period between WW2 and 2000 we saw massive unemployment in many typical blue collar jobs in the western developed world, yet women weren't impacted to the same degree, why is that?

Is it because women through out the 1960s-2000s had a seat at the table, which men didn't?

Obviously not, they often faced workplace discrimination and their choice of job was limited to what was socially acceptable for a woman to work in and often those were jobs men weren't interested in the 1940-1960s, but they were working in what we now call the service industry and they didn't experience the displacement which came with global trade at the same rate men did.

> Capital/labor in strict sense, sure, but there is also material support, or a “seat at the table”. A decision maker (in service to Capital).

This just is not an informative framing here for why software engineers are more impacted than doctors

> The division is power—-be it Capital or knowledge or labor.

This simply isn't informative, the blog post is clearly focusing on a definite industry and your fixating on a general class (which the impacts are not being felt equally across).


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: