Or a way to take money from green investment funds: you're never finished, but you're always only two years away. Both directly from governments and from mandates on the oil companies to do green investments.
> Vice Adm. Jan Christian Kaack, the inspector of the German navy, said at a press conference on Tuesday that the damage involved "more than one unit."
> The Emden is one of the five new K130 corvettes that Germany ordered for delivery in 2025 to fulfill its NATO requirements.
Ugh. Could that be five damaged units? Finds metal shavings in new engine. Touts it as sabotage without explaining further. Spends the rest of the article on fear mongering. If this was an internal investigation, that would have been great. Doing a press conference about it? Sounds more like "before we investigate where it came from, should we take the opportunity to do some propaganda?"
(With all the recent subsea cable issues, yeah, something is going on in these waters, but this is not a good press release.)
> Finds metal shavings in new engine. Touts it as sabotage without explaining further.
You sound very disingenuous. If you one day find a dump of metal shavings in a freshly assembled and validated engine, and the only possible and conceivable way those could be found in there is if someone goes way out of their way to purposely dump them in there, how would you have describe that?
The comment section is funny. The first 3-4 comments complain about the screenshot showing a column break, failing to notice it's from the suspected 1959 origin paper.
I can't tell what the publishing time was, but the first two comments are within eight minutes of each other. The third is an hour later. Sensible comments didn't start to trickle in until six hours later.
How many of those comments are from bots, and maybe human trolls?
US taxpayers feel very sick from learning about all these taxpayer funded cushy jobs for DC lawyers and clerks and aides who just push paper and get fat paycheck without any accountability, while the private industry deals with layoffs, performance improvements, at-will employment, and general uncertainty
It might be referring to job role rather than "age." A Staff Engineer is supposed to be inspiring (both up and down,) so doing quick tests fits the bill, and that's something LLMs are great at supporting. Mid-level is mostly about delivering reliably.
The question is if LLMs/tools could drag mid-level earlier into senior level, or if it's a phase one has to go through. Ultimately, the tangible promise of LLMs is to push the entire timeline up, so that junior tasks are automated and you go in and control the LLMs. Expectations on what it means to be a software engineer are sure to change, at some point. (I like the software craft as-is, but fact is most of our lumber is straighter now that we have automatic saws. And I've never heard a carpenter pleading to split a log manually.)
> I've never heard a carpenter pleading to split a log manually
Log splitting is a lumber mills job which has been around for nearly 2000 years. Maybe a better analogy is a nail gun? Which is actually insteresting because some of the old timers I met are actually as fast or faster with a hammer and nail as a nail gun. And hammers are still used everywhere daily by woodworkers and carpenters.
But the challenges of a carpenter are more about problem solving than brute force. How you join and the order you join can make your life a pita if you don’t have the experience. So a junior carpenter might be implementing repetive tasks or follow directions but you need experience to know how to implement a unique solution correctly on the first try and not waste hundreds of dollars of material or the clients time. Afterall “measure twice cut once” has to be learned.
Why isn't it better to redefine insertBefore of an already inserted element to being state-preserving? If I want to kill state, I can do a remove first.
I reject that claim as-is. In what situations would it break? Standards evolve. Changes to cookies, iframes, newly required HTTP headers all "broke" the web. Not to mention Flash deprecation. But somehow we survived.
Sure, this would theoretically be a backwards incompatible change. But if no one is using insertBefore without really meaning moveBefore, it's not a concern in practice.
Part of DEI at Google is to engage with universities to understand why some prefer not to study STEM/PR/whatnot. Shutting it down at Google will also affect the education pipeline.
Agreed on PR (or avoidance of negative publicity) being the main driver for Pichai to engage in the discussion, but there are many people at Google who care.
Dr Pippa Malmgren (political advisor) also pushes the idea that WW3 is on-going, and it will look nothing like WW2. She appears on podcasts once in a while and has a blog. Not sure if I care for calling it a war if it doesn't look like a war, but there sure are human conflicts all over the little ball of life now.
I'm in the business of data collection, to some extent: building a support system for residential solar panel installations. There's a bunch of data needed for simulations, purchase estimations, legal and tax reasons. Not insane amounts, but enough that filling out a form feels tedious. LLMs are great in that they can be given a task to gather a number of pieces, and can explain to the user what "kWh" means, at many level of technical depth.
We play around with LLMs to build a chat experience. My first attempt made Claude spew out five questions at a time, which didn't solve the "guiding" problem. So I started asking it to limit the number of unanswered questions. It worked, but felt really clunky and "cheap."
I drew two conclusions: We need UI builders for this to feel nice, and professionals will want to use forms.
First, LLMs would be great at driving step-by-step guides, but it must be given building blocks to generate a UI. When asking about location, show a map. When deciding to ask about TIN or roof size, if the user is technically inclined, perhaps start with asking about the roof. When asking about the roof size, let the user draw the shape and assign lengths. Or display aerial photos. The result on screen shouldn't be a log of me-you text messages, but a live-updated summary of where we are, and what's remaining.
Second, professionals have incentive to build mental model for navigating complex data structures. People who have no reason to invest time into the data model (e.g. a consumer buying a single solar panel installation in ther lifetime,) will benefit from rich LLM-driven UIs. Chat UIs might create room for a new type of computer user who doesn't use visual clues to build this mental model, but everyone else will want to stay on graphics. If you're an executive wondering how many sick days there were last month, that's a situation where a BI LLM RAG would be great. But if you're not sure what your question is, because you're hired to make up your own questions, then pointing, clicking and massaging might make more sense.
