No, it's bipartisan and even fucking international. I think there is a very obvious conspiracy to get this done, but maybe it's a big coincidence that governments and politicians everywhere suck now.
I was talking about the party. This shit is and always has been pushed from both parties. Even democrat states like California and Colorado are on board. See also, the OS age verification legislation.
TBH California one doesn't require age verification (while many other states do). It only requires the OS to provide a mechanism for the user to indicate their age group and apps should use the information (instead of asking for PII themselves). It's a fake one, but somehow drew most attention.
If that is true about the California case, it is basically a fluke. Lobbyists don't have total control of the legislation after all. It sounds almost benign when posed that way, but it is the wrong solution either way. The better solution is to tell people to install filtering software to block content that they don't want. Then you don't have to worry about compliance of individual sites, personal information, or any of it. This filtering strategy also makes sense for privacy and handling the subjective nature of what is age-appropriate or offensive.
Hardly, after attacking all their friends in the region, which would leave them even more isolated after the war, I would not attribute careful strategic planning either
> This wouldn't be another 9/11, it would be merely be retaliation
The Japanese and Al Qaeda framed their attacks defensively. An attack on the homeland is an attack on the homeland. I wouldn’t put it past Iran. But you’d rapidly see political consensus to ensure the regime is destroyed at all costs, including and up to leaving a power vacuum and humanitarian crisis.
the war is wildly unpopular in the US (rightfully so) - attacking US would rally the country (rightfully so) and regime would fall within a week (with significant casulties on our side)
It’s pretty fucking stupid. Convening the top brass above ground, failing to scatter the navy, bombing Azerbaijan and Qatar and Oman. I’m not saying the individual actors are dumb. But the result of the competing centers of power between the IRGC, military proper, clerical establishment and god knows who else produces a stupid strategy.
Broadly, taking American and Israeli threats seriously. And not overestimating how easily their neighbors would capitulate if bombed.
Tactically, this would mean not concentrating senior leadership above ground. Scattering their navies out of port. Targeting U.S. military bases and not the civilian infrastructure around them.
Their regime is made up of hardline Shia Twelvers that believe that if they kill enough people the Twelfth Imam will appear and lead them to global victory.
Only problem is the Twelfth Imam has been dead for a thousand years.
They may not be stupid, but they consistently act based on counterfactual beliefs.
I disagree heavily with them too but that doesn't mean we should eradicate them. We can't expect the whole world population to be aligned.
But once we start shooting they will obviously shoot back and we're many steps further away from the desired "agree to disagree and live together anyway" outcome that is the only way to peace.
I mean the US tried this too with Afghanistan. Many lives lost, trillions of dollars wasted and everything was back to 'normal' in two weeks.
Change has to come from within and the thing is this was actually happening in Iran. Now with military law and the regime uniting people against a common enemy this is much further away.
first, what does it matter whether they are Muslims or not? second, what is the structure of reality?! you may have some notion you know what “reality” is given what your media allows you to think - the actual reality is vastly different than you think it is - that is a certainty
they brought laptops to cafeteria? outside? the core issue is usage of phones outside of the class, no? if he used it during the class, cool (we all gad boring teachers). if he was able to use it after the bell rang that is not having a ban
I think having kids connects you to humanity in a deeply personal way and connection to humanity is at the higher level than anecdotal example of various human experiences we’ll never experience first hand.
I think there are many ways to connect deeply to humanity and you are being dismissive of those other experiences. Yours is just another anecdote amongst the ones I presented. Would you dismiss your kids experiences if they decide not to have kids? I would not.
> Once the tooling became too complicated and ever changing they couldn't keep up as front-end dilettante. It required to commit as professionals.
The best professionals did not fall for insanity of the modern front-end dilettante and continued hacking shit without that insanitity.
> You will not learn Grunt, Bower, and a large array of historic tech. You'll go straight for what's relevant today.
which will be outdated "tomorrow" just like grunt/bower... are looked at today
> A lot of the early stuff seems like an utter waste of time in retrospect.
This cannot be further from the truth, if you learned Javascript early, like really learned it, that mastery gets you far today. The best front-end devs I know are basically Javascript developers, everything else is "tech du jour" that comes and goes and the less of it you invest in the better off you'll be in the long-run.
> If you knew nothing about LLMs by the end of this year, you could find a course that teaches you all the latest relevant tricks in 5 to 10 hours for 10 bucks.
Hard disagree with this unless you are doing simple CRUD-like stuff
> The best professionals did not fall for insanity of the modern front-end dilettante and continued hacking shit without that insanitity.
"Front-end professional" and "no tooling" have been exclusive propositions since the early 2010s. You either learned to use tools or you were out of the loop.
> which will be outdated "tomorrow" just like grunt/bower... are looked at today
Not really. Historically, the main problem with front-end development has not been change, but the pace of it. That's how it ties in with the current discussion regarding the (now) ever-changing terrain of LLM-assisted coding. Front-end development is still changing today, but it's coalescing and congealing more than it's revolving. The chasms between transitions are narrowing. If you observe how long Webpack lasted and familiarity with it carried over to using Vite, it's somewhat safe to expect that the latter will last even longer and that its replacement will be a near copy. Someone putting time to learn front-end skills today might reap the benefits of that investment longer.
> if you learned Javascript early, like really learned it, that mastery gets you far today.
I did. I got a copy of the Rhino book 4th ed. and read it cover to cover. I would not advise to learn JS today with historical references. JS was not designed like most other languages. It was hastily put together to get things done and it had a lot of "interesting", but ultimately undesirable, artifacts. It only slowly turned into a more sensible standard after-the-fact. Yes, there are some parts that are still in its core identity, but a lot in the implementation has changed. Efforts like "Javascript: The Good Parts", further standardization, and TS helped to slowly turn it into what we know today. You don't need to travel back in time for that mastery. Get a modern copy of the Rhino book and you'll be as good as the best of them.
Yeah, I still get use out of XMLHttpRequest to this day good thing I got in early and variable hoisting isn't gonna get me! /s
A lot of snark aside there's a bit of a false dichotomy (I think) here at work. Whenever or wherever your jumping in point is into $something it will always pay dividends to learn the fundamentals of that $something well and unless you interact with older iterations on that $something then you'll never have to bother learning the equivalent of Grunt, Gulp, Stylus, Nunjuncks and so on for that $something.
With that being said it's also good to put aside time once a year to check out a good recommended (and usually paid) course from an established professional aimed at busy professionals.
As for LLMs I feel it's slowly becoming a thing big enough where people will have to consider where to focus their energy starting with 2027. Kinda like some people branched from web development into backend, frontend and UI/UX a good while back. Do you want to get good at using Claude Code or do you want to integrate gen AI features at work for coworkers to use or customers/users? It's still early days just like when NodeJS started gaining a lot of traction and people were making fun of leftpad.
this always starts out right but over the years the code changes and its documentation seldom does, even on the best of teams. the amount of code documentation that I have seen that is just plain wrong (it was right at some point) far outnumbers the amount of code documentation that was actually in-sync with the code. 30 years in the industry so
large sample size. now I prefer no code documentation in general
The good thing about having documentation in the (version-controlled) code is that it allows you to retrace when it was correct (using git blame or equivalent), and that gives you background about why certain things are the way they are. I 100% prefer outdated documentation in the code to no documentation.
If the documentation and code could be in-sync, then the documentation would just be code, like type hints. But good documentation that the parent is talking about cannot be in-sync.
Programming languages can't understand semantics, and that's why we program in the first place. I can't tell a computer "I would like a program to achieve this goal", instead I have to instruct it how to achieve the goal. Then, I would need to document elsewhere what the goal is and why I'm doing it.
LLMs change that, we can now legitimately ask the model "I would like a program for this goal". But the documentation is lost in the code if we don't save comments or save the prompt.
Git commits are also a good source of documentation. They shouldn't describe what we're doing, because I can just read the code. But often, I come across code and I'm thinking "why are we doing this? Can I change this? If I change it, what are the side effects?" If I'm lucky, the git blame will answer those questions for me.
It's not a massively complex AI monstrosity (it's from 2018 after all) or a perfect solution, but it's a good jumping off point.
With a slight sprinkling of LLM this could be improved quite a bit. Not by having the agent write the documentation necessarily, but for checking the parity and flagging it for users.
For example a CI job that checks that relevant documentation has been created / updated when new functionality is added or old one is changed.
interesting that they don’t mention doctest which has been a python built-in for quite a while.
It allows you to write simple unit tests directly in your doc strings, by essentially copying the repl output so it doubles as an example.
combined with something like sphinx that is almost exactly what you’re looking for.
doctest kind of sucks for anything where you need to set up state, but if you’re writing functional code it is often a quick and easy way to document and test your code/documentation at the same time.
right but docstrings are documentation, so if your doctest is working, then at least that part of the documentation is correct.
Even without doctest, generating your documentation from docstrings is much easier to keep updated than writing your documentation somewhere else, because it is right there as you are making changes.
I am not saying it doesn't matter because it does, but how much does it matter now since we can get documentation on the fly?
I started working on something today I hadn't touched in a couple years. I asked for a summary of code structure, choices I made, why I made them, required inputs and expected outputs. Of course it wasn't perfect, but it was a very fast way to get back up to speed. Faster than picking through my old code to re-familiarize myself for sure.
We cannot get full documentation on the fly, though. We can get "what this does" level of documentation for the system that AI is looking at. And if all you are doing is writing some code, maybe that is enough. But AI cannot offer the bigger picture of where it fits in the overall infrastructure, nor the business strategy. It cannot tell you why technical debt was chosen on some feature 5-10 years ago. And those types of documentation are far more important these days, as people write less of the code by hand.
This is the same discussion that goes round ad nauseum about comments. Nobody needs comments to tell us what the code does. We need comments to explain why choices were made.
Keeping the documentation in the repo (Markdown files) and using an AI coding agent to update the code seems to work quite well for keeping documentation up to date (especially if you have an AGENTS.md/CLAUDE.md in the repo telling it to always make sure the documentation is up to date).
Code can only ever document "what" by definition, never "why". If it could document "why", then no computer programmers would exist. So, we have to supplement the "why" using natural language. There's a 100% loss conversion there when we convert it to code.
yea, when it rains the world
stops and we all sit home and wait for the Sun to make an appearance. coolest part is that some places in the US get like 200+ rainy days and you get to stay home cause you have no choice, schools closed etc :)
> There isn't some kind of god riven right to transportation, it is always conditions permitting.
If the condition is a little fog and little rain and little snow/sleet I hate to break it to you but those are very permitting. In most of the continental US the number of days where driving conditions for an (below)average human and such that it is wiser not to get on the road is very small. If the "robo"taxi technology you posses cannot match that of a (below)average human you got nothing but vaporware you've been pitching as "done deal" for more than a decade.
> Well, even robotaxi's can't beat the laws of physics. There isn't some kind of god riven right to transportation, it is always conditions permitting.
reply