VoterFrog

What? I've already written the design documentation and done all the creative and architectural parts that I consider most rewarding. All that's left for coding is answering questions like "what exactly does the API I need to use look like?" and writing a bunch of error handling if statements. That's toil.

Definitely depends on the person. There are definitely people who are getting 90% of their coding done with AI. I'm one of them. I have over a decade of experience and I consider coding to be the easiest but most laborious part of my job so it's a welcome change.

One thing that's really changed the game recently is RAG and tools with very good access to our company's data. Good context makes a huge difference in the quality of the output. For my latest project, I've been using 3 internal tools. An LLM browser plugin which has access to our internal data and let's you pin pages (and docs) you're reading for extra focus. A coding assistant, which also has access to internal data and repos but is trained for coding. Unfortunately, it's not integrated into our IDE. The IDE agent has RAG where you can pin specific files but without broader access to our internal data, its output is a lot poorer.

So my workflow is something like this: My company is already pretty diligent about documenting things so the first step is to write design documentation. The LLM plugin helps with research of some high level questions and helps delve into some of the details. Once that's all reviewed and approved by everyone involved, we move into task breakdown and implementation.

First, I ask the LLM plugin to write a guide for how to implement a task, given the design documentation. I'm not interested in code, just a translation of design ideas and requirements into actionable steps (even if you don't have the same setup as me, give this a try. Asking an LLM to reason its way through a guide helps it handle a lot more complicated tasks). Then, I pass that to the coding assistant for code creation, including any relevant files as context. That code gets copied to the IDE. The whole process takes a couple minutes at most and that gets you like 90% there.

Next is to get things compiling. This is either manual or in iteration with the coding assistant. Then before I worry about correctness, I focus on the tests. Get a good test suite up and it'll catch any problems and let you reflector without causing regressions. Again, this may be partially manual and partially iteration with LLMs. Once the tests look good, then it's time to get them passing. And this is the point where I start really reading through the code and getting things from 90% to 100%.

All in all, I'm still applying a lot of professional judgement throughout the whole process. But I get to focus on the parts where that judgement is actually needed and not the more mundane and toilsome parts of coding.

As far as I understand as a layman, the measurement tool doesn't really matter. Any observer needs to interact with the photon in order to observe it and so even the best experiment will always cause this kind of behavior.

With no observer: the photon, acting as a wave, passes through both slits simultaneously and on the other side of the divider, starts to interfere with itself. Where the peaks or troughs of the wave combine is where the photon is most likely to hit the screen in the back. In order to actually see this interference pattern we need to send multiple photons through. Each photon essentially lands in a random location and the pattern only reveals itself as we repeat the experiment. This is important for the next part...

With an observer: the photon still passes through both slits. However, the interaction with the observer's wave function causes the part of the photon's wave in that slit to offset in phase. In other words, the peaks and troughs are no longer in the same place. So now the interference pattern that the photon wave forms with itself still exists but, critically, it looks completely different.

Now we repeat with more photons. BUT each time you send a photon through it comes out with a different phase offset. Why? Because the outcome of the interaction with the observer is governed by quantum randommess. So every photon winds up with a different interference pattern which means that there's no consistency in where they wind up on the screen. It just looks like random noise.

At least that's what I recall from an episode of PBS Space Time.

Unfortunately the horrible death would come long before you even reach the event horizon. The tidal forces would tear you apart and eventually, tear apart the molecules that used to make up you. Every depiction of crossing a black hole event horizon just pretends that doesn't happen for the sake of demonstration.

"Don't get got" great game, lots of fun. Played sort of in the background of whatever you're doing. You try to get other players to do or say something according to your secret objectives.

There's a pretty vague official rule that if the other person becomes suspicious of you trying to trick them, they can just call you out and you lose the objective. But with my group you can't sneeze without someone going "Is that for the game? Because I'm not saying bless you." So our house rule is that they have to guess at least somewhat in the neighborhood of what you're objective is for you to fail.

It does make you get a little more creative about how you might trick them so that even if they're suspicious, they at least can't tell what your goal is.

My favorite use is actually just to help me name stuff. Give it a short description of what the thing does and get a list of decent names. Refine if they're all missing something.

Also useful for finding things quickly in generated documentation, by attaching the documentation as context. And I use it when trying to remember some of the more obscure syntax stuff.

As for coding assistants, they can help quickly fill in boilerplate or maybe autocomplete a line or two. I don't use it for generating whole functions or anything larger.

So I get some nice marginal benefits out of it. I definitely like it. It's got a ways to go before it replaces the programming part of my job, though.

He became a rogue scholar, huh? A dark path that leads only to evil scientist.

I don't think it's working. LLMs don't have any trouble parsing it.

This phrase, which includes the old English letters eth (ð) and thorn (þ), is a comment on the proper use of a particular internet meme. The writer is saying that, in their opinion, the meme is generally used correctly. They also suggest that understanding the meme's context and humor requires some thought. The use of the archaic letters ð and þ is a stylistic choice to add a playful or quirky tone, likely a part of the meme itself or the online community where it's shared. Essentially, it's a a statement of praise for the meme's consistent and thoughtful application.

The problem with these long term journeys is that it's entirely possible that the probe could get half way there by time we develop the technology to make another probe that's twice as fast and cheaper. Or maybe we make other discoveries and find that we don't need the data the probe is equipped to gather. We're not really near the limits of propulsion and space engineering yet so it doesn't make a ton of sense to invest in something with such a distant payoff when it's somewhat likely to be outdone before then.

It's what OP's parents call the first day they saw him.