[ my public key: https://keybase.io/zaphar; my proof: https://keybase.io/zaphar/sigs/EBb9qSOchK8pT3zTsPnikv8z0ot6Af5Av8l-xffn6Bk ]
- I agree, the point of making usage monitored early on is so that you can train your child in what to do when they encounter stuff online. As that training has occured then you can begin to loosen the restriction and give them more freedom. This is the job of parenting. You are teaching your child how to safely and productively engage with the world and the younger they are the more of your time and attention this requires. If you don't teach them someone else might and that lesson may haunt them for the rest of their life.
- A five year old is not prepared to engage online with privacy. They have not had the necessary training yet. They will not get that training unless you are there to show them how to negotiate that world. They will not magically learn how to protect themselves if you just leave them to figure it out themselves.
- I don't know if this works for anyone other than our family but when we were raising our kids we solved this by the simple of expedient that gaming and computer use was done with us as parents present. Full stop.
It was not a solo activity for our kids. We could directly view everything they were doing online the entire time.
- Sure, if you don't model the error domain correctly you will leak stuff that maybe you shouldn't leak. But I'm not sure that this is worse than just not exposing the types of errors that you are handling.
Your example is interesting actually because there are real differences in those types of errors. IO errors are different from the globset errors. It is reasonable to assume that you would want to handle them differently. If your function can actually have both errors as a consumer I would want to know that so I can make the correct decisions in context. If you don't have a way to signal to my code that both happen you've deprived me of the tools to do my own proper error modeling and handling.
I agree that this is what happens in practice for most code that I read and have to interact with. I think where I differ from you is that I don't think this is good and do not advise people to do this for their own code. I think it's a pervasive but bad practice in our line of work.what you're describing about errors bubbling up to the top layer, is what happens with the overwhelming majority of errors in my experience.- This is an interesting perspective. I usually don't try to imagine how someone should handle the error. Instead I try to indicate the different types of errors that could occur and what type of information needs to be included to be useful to the caller. I can leave the question of what to do with that information to the caller since it's highly situational and the context necessary to make that decision lives outside of the code where I am modeling the error.
- If your error domain has only one useful category why not just create an error type with a useful message and be done with it. Why use anyhow at all? You are essentially saying the error domain is small so the work is tiny anyway.
anyhow seems useful in the very top layers where you basically just want bubble the useful errors modeled elsewhere to a top layer that can appropriately handle them. I don't think a crate should abdicate from modeling the error domain any more than they should abdicate from modeling the other types.
- My personal anecdotal experience is considerably different. I've worked multiple places where I had to learn the stack on the job. Up to and including the language at least once.
I've never found it too difficult to get hired even when the requirements don't list something I've done already.
- Those boundaries are pretty fuzzy. The complexity of the logic with conditionals and loops in a module means that you have pretty much stopped describing what it should like and instead described how to make it look the way you want it.
I have read terraform modules where I had to execute the logic to know what got produced which moves it from your imperative description to the declarative description as far as I'm concerned.
- You "call" a module with arguments. You can call them multiple times. In every way that matters they are just like a function call.
I don't understand why there is a distinction between for each in a standard language vs for_each in HCL2. They are both do something by iterating over something else at runtime. The syntax isn't what matters here.
I think maybe you are mistaken in your own distinction between declarative and imperative.
- I do think that holds more water than just "It's old".
However for pretty much any dev I would hire for a job they can get to grips with a technology that's older pretty quickly. Where it does get dicey is when good dev just refuses to work with it. For those devs, I think, when they hold that opinion it typically means one of those other reasons is behind their refusal.
- I think I'm mostly of the opinion these days that there is no such thing as an "outdated technology". There are technologies that are no longer fit for purpose but that is almost never because of their age. It nearly always because of one of as examples: Needing to run in an environment it can't support, Having bugs that are not getting fixed/no longer maintained, Missing features necessary to solve new problems or add new features, Hitting scale limits.
Outdated may sometimes be a euphemism for one of the above but usually when I see it in a discussion it just means "old" or "out of fashion" instead.
- Nearly every time we try to fix this problem with money it fails. The problem is not money. All else being equal there is little to no correlation between spend and outcome. Money get's touted by schools and politicatians as a way of pretending to care but not actually do any of the work to improve outcomes.
What does tend to correlate with money and also correlates with outcomes is parental involvement. Solving that problem requires societal and economic change in a district though not giving the school more money.
- I can not conceive of a worse way to teach a kid how to behave in Adult social settings than to throw them into a group of other kids who have just as little experience as they do and then expect the group to "figure it out". This is not to say that there aren't some homeschooling parents who practice a form of extreme isolation which produces what I would regard as an equally bad outcome as public school. But by the numbers from people who have studied this the evidence indicates homeschooling produces the best outcomes for social adjustment in Adulthood.
Probably because well run homeschooling groups tend to have high parental involvement which means the child learns how to socialize not from other children but from watching how the adults they are around handle interactions.
[Edited for clarity in some sentences]
- Where did you get the $311B number? Because I get a net profit of $59.25B which is only 40k per employee. This assumes that the company doesn't need to keep any profit for future usage which may or may not be case depending on how big their war chest is. Not to say that 40k couldn't be life changing for many of the Amazon employee but the 311B number seems to be pulled out of thin air.
- As a purely anecdotal datapoint, Perplexity was my first stop search engine for a while. It stopped being my first stop when they starting prompting me constantly to try their browser. Getting in the way of me being able to immediately ask my question drove over to gemini instead. It turned out that Gemini was good enough now so I didn't go back.
- That makes no sense. Just because they aren't a security vendor doesn't mean they don't have useful information to share. Nor does it mean they shouldn't share it. They aren't pretending to be a security researcher, vendor, or anything else than AI researchers. They reported on findings on how their product is getting used.
Anyone acting like they are trying to be anything else is saying more about themselves than they are about Anthropic.
1. Ask your school to change their policies. Coordinate with other parents. Make it clear to the school that if they don't start to enforce these policies then you will hold the school directly responsible for any harm that comes to your child in the environment they create.
2. Pick different schools. (Home School, Private school) if you can afford it. Charter schools may be an option.
Both of these require sacrifice on your part and neither are easy. But no one should ever think parenting is easy.