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

Education data and analytics are mostly selection bias. The product at many private school is "I pay 75k to not have disruptive and problematic kids around my kids" and the academic benefits flow from this. When comparing Alpha vs other private schools, I think the thing to look at is the admissions process and associated selection bias. Of course a school that only lets in smart kids outperforms others. If Alpha are gating on non intellectual or academic items (which they claim is the case), then you will have below avergae and non-disruptive kids in the peer set and some won't hit the goals.

My takeaway here is that the Alpha approach helps high achievers, and doesn't gate keep access to only high achievers.


This isn’t what justice is. It’s also not holding people (or orgs) to account. It’s complaints against an entity that people often don’t understand or like.


I think all of your points are very valid, but it doesn’t remove the point that the government is trying to make it free and easy for application builders to do a little bit better than they are today. This is commendable on its own, even if it’s not perfect.


I find it interesting that the co-author of the OP violated long-standing security practices and copied a social security database into an insecure AWS instance without proper oversight.

Is it still commendable if in order to develop this, the taxpayer-funded developer themselves published our PII to a consumer, privately controlled third-party server without following federal data security protocols? Seems like an attempt to make up for the damage they caused.

Standing up your own AWS-equivalent internally is not much work, yet the PII data leaked to publicly available services due to this developer's personal choices and lack of oversight to prevent sensitive government data from being published externally.

Notably, this resulting work has not been published as public domain (CC0).


what i understood from the above comment is that the government should first do the basic policy making (set some non-negotiables for the ai companies etc) before jumping into solution building. let the market figure out the tech solutions.


Letting the market handle things is how you get all the problems America has today. Markets are a good way to distribute goods and services but they don't really work for public services with no money to be made. Things like roads, hospitals and open source software.

The purpose of a government is to serve its people, not make sure every business gets the same conditions at all costs. Picking winners and losers is fine if the losers still have a chance to beat the winners when they're really better.

If someone makes a free PII detector better than Rampart I bet the US government will either switch to it or make Rampart v2. For now it's enough. Perfect is the enemy of good.


If you can do x and a pro can do x better who do you think can do it better using AI?


so basically pro cooks are better at ordering pizza?

"pro"-ness does not transfer. I can be both good at reading english, and have AI hallucinate non-existing details from the documents it processes.


Ohh I'm gonna steal that one.

Although I don't fully agree. With AI the focus now shifts a lot from 'being able to implement the thing' to 'being able to know/figure out exactly what you want the thing to look like', also against the siren song of the LLMs constantly having ideas of what you could _also_ build.

So, I agree that it's not a direct translation from 'pro pizza cook' is 'pro pizza orderer', but I'm quite sure the pro pizza cooks would generally have the better pizzas in the end, if there were infinite variations of pizza on the menu and the ordering agent was constantly trying to upsell you on slathering on another layer of sauce and cheese.

Which is not to say there aren't exceptions in both directions, because as a pro pizza connoisseur you could even be better positioned to 'know exactly what you want', without ever having made a pizza; and as a pro cook you might still be overwhelmed by the ordering process.

Though all of this still assumes of course that we are in the 'complexity region' where we can expect the LLM/the pizza agent to deliver _exactly_ what we wanted, without issue. As soon as we leave that region (though it expands every week, it feels like), the skills of the cook are still very much necessary to make sure things are as they should be, and fix them if not.


there are two completely different activities both called "writing software using AI".

At work, for important stuff, I go through every change, mine or LLM's, edit it, clean it up, rewrite, until I am satisfied with the code.

At home and for one-off unimportant stuff I go "computer make me sandwich".

The second is nothing like the first. No amount of design and pro I have can make sure stuff coming out of LLM actually implements it, as opposed to me be tricked into thinking it does. After all, that is exactly the training criteria – convince the "eval" that task is accomplished, isn't it?

And the second kind of activity takes skill that no amount of "I am pro dev" can compensate.


I’m the author of one of the most popular mermaid renderers in Confluence. People spent huge sums of money on this. Feel free to message me if you have questions about the space.


Thanks, very kind offer. When people paid real money for this, were they paying to make diagrams look good, or for convenient source-editing and rendering in the page? Line9 is built around the first and doesn't have an ideal solution for the second yet.


I think the main thing people paid for was avoidance of change. Devs already use mermaid (by preference or policy) and therefore they wanted to keep using it. When I first build the Markdown Macro in 2012/2013 my thesis was that people would want to keep using Markdown in place of WYSIWIG, and that there was value to having a file in git be a source of truth and updating it there would keep Confluence automatically updated thereby reducing work to keep docs accurate. The first half proved true for devs, the second half did not, the stats showed that almost everyone would paste the markdown source into the in Confluence editor. When we added Mermaid, we saw more of the same. I am not sure how much I can say without violating NDAs, but I would encourage anyone working in this space to work to understand the ratio between how often content is authored vs consumed and by whom in each category. The idea that 1% of people author the content for 99% of consumers that we see on the internet does not translate to corporate environments and this has important product implications.


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

Search: