my vocal synth models the vocal tract as a network of branching acoustic tubes, unlike vocaloid which stitches together and pitch-shifts phoneme recordings. still working on improving naturalness by tuning it against recordings of real singers, but I'm already impressed at how cool it sounds!
@alexanderrX_ You don't really select the attributes, more like you discard the embryos that don't have them.
Would likely take a few tries to get the exact combination one is after.
@RobSetters@GMFinX A friendlier reply than others: when supply and demand aren't tampered with, it causes a chain of value
If people didn't want luxuries then there wouldn't be jobs in high demand that pay well
The salaries are literally decided by consumers and available workers
We need to reconsider our priors on code readability.
Humans, compared to agents, are pretty slow at understanding large quantities of text. So in the old days, readability was important so the human could efficiently grok what was going on.
So readability now comes down to:
1. Can a human, if needed, jump in and understand the code
2. Does the code use the same domain language as the human describing the code?
1 helps with observability and the occasional spot checks you need to do on important PR's. 2 helps the agent translate the words you use into code changes.
In other words, readability is now a nicety, not a necessity.
The way agents 'read' code is different - good agents are all about gathering data about how the code works. They'll prod around with it, execute parts of it.
So 'readability' to agents really means 'verifiability'. How easy it is to mess about with that code to see it working.
Let's take this scenario:
- You have a huge module in your codebase that uses all sorts of complex performance tricks
- It has 100% test coverage
A talented human would need an hour or two to get comfortable working in that module.
An agent needs zero time. They verify it with the tests, poke about a bit, and they're good to go.
The takeaways:
- When judging a module (or a codebase), don't think about how easy the code is to read
- Instead, think about how easy it is to verify
- Design your codebase so modules can be tested and verified independently
- Feel free to sacrifice a bit of readability for performance
- Cyclomatic complexity and function size don't matter to agents
Long post worth the read. I have a close friend who flies private jets. He flew Lear 60 for over 15 years and now flies a Gulfstream. This is a copy and paste of his response to me asking him if I thought Ice was the issue.
“We always fly in ridiculous cold temperatures.”
“Usually you get the bad ice when the temperatures are like 0 to negative 20. Believe it or not, there's a point where it gets too cold for ice. At negative 40, you pretty much can't get ice. Besides that, the airplane is equipped with hot wings and hot tail.”
“I flew the Lear 60 for like 15 years. It's a no joke airplane and probably the most dangerous airplane I've ever flown. It has a super critical wing. The airflow has to be perfect. When it gets into rough air and turbulence, it will easily stall. It has stalled on me at 41,000 feet just because we got into some turbulence. (On the way to Palm Beach as a matter of fact. ) we recovered and got her flying again around 30,000 ft. Scary
But here's the problem. This airplane has a terrible coffin corner. (At high altitudes) what that means is, you fly in a really narrow window where if you lose 20 knots, it stalls. And if you gain 20 knots, it goes into overspeed. The air goes supersonic over the wing and it goes into a high speed stall, or worse, a Mach tuck.
So if you stall, the normal recovery is to push the yoke forward to lower the nose and gain air speed again. At low altitude, you can push really hard and recover quickly. But in the 60... if you push hard, it will gain air speed and go into a high speed stall, it doesn't take much. It's very sensitive. The 60 has super short wings that don't make much lift. So then you high speed stall, and the computer is yelling at you... OVERSPEED! So then you pull back and enter a low speed stall. And you go back and forth trying to keep it in the air speed window.
This whole thing is pretty scary. And you should recover basically by using your finger tips using super small corrections. You can't over do it. If you try to muscle the recovery, she gets mad and will become unrecoverable. If she enters a mach tuck. You're done.”
“I taught the Lear 60 to other pilots and mentored them. I told them... this airplane has a soul and it's trying to kill you. Do not ever try to top the weather. Don't go over a thunderstorm. Go around it. If it means a half hour longer, then do it. Going over the thunderstorm will go into turbulence that you might not recover from.
These pilots went right over a thunderstorm. I think it stalled which caused them to drop down into the thunderstorm and ended up in mach tuck. They picked up so much speed that it ripped off the horizontal stabilizer. At that point... chuck Yeager can't fix it.
These same pilots did something similar a couple months ago. ATC got mad at them. They poked the bear one too many times.
This is not a beginner airplane. The Gulfstream would never do this. It has HUGE margins of error and won't stall like that. But then again... it's got HUGE wings. It's a pussy cat.
The Gulfstream is like driving a 4 wheeler. The Lear 60 is like riding a uni cycle.”
I was flying back home. Over the city there was a great storm. The pilot informed us that we'll be circling around the airport waiting for the storm cell to pass.
It was a small ATR 60 and at some point fuel started to become a concern. "We'll have to go through it. It will be very bumpy" is what the pilot announced.
Thirty seconds later the plane started to shake. It felt like the plane was simply thrown around by the winds with nobody controlling it. Some overhead compartments opened and bagages fell down. Fortunately, nobody was injured by the falling trollers.
It took around 1 minute when we broke through the clouds. People were screaming the entire time. Some were praying. A gentlemen literally peed on himself.
That's how people react to heavy turbulance and the growing probability that we've all approaching our finish lines.
Now imagine a plane falling down the sky, nose down, at roughly the speed of sound. And a 20 year old first officer giving exact readings of the situation to ATC. Descend rate, bank angle, aircraft state.
In this situation most humans will simply pass out due to the enormous G force and a first row view of the ground approaching,
Yet the 20 years old first officel was still giving precise technical readings to ATC. There were short screams at times, but she continued to do her job while most of us would have been passed out.
I'm not sure what combination of circumstances caused the Learjet to crash in Palm Beach. Maybe there were some less optimal decisions by the captain. Maybe not.
But what I know is that I wish I had the same lucidity in critical situations that the 20 years old first officer had.
@JDRockwellJr Looking forward to the completely black and white takes that ignore either their physical development (sleep and discipline are actually important) or general well-being (if your children are miserable then what are you even doing)
@danpdc A lot of software out there is just a solution to managing specific types of work that's normally done by exchanging emails, and quite often the solution ends up being a very usecase-specific Jira clone
@PaffyPete@MR_T1OOO@JMcMurdockMP How are you not getting the fact that a tax break will make that more affordable for more people?
On lower salaries in particular if one partner's allowance was extended to the other that's an extra £12k for the other one and the huge nursery fees would go away