My work is basically just guessing all the time. Sure I am incredibly lucky, seeing my coworkers the Oracle and the Necromancer do their work does not instill a feeling that we know much. For some reason the powers just flow the right way when we say the right incantations.
We bullshit a lot, we try not to but the more unfamiliar the territory the more unsupported claims. This is not deceit though.
The problem with LLMs is that they need to feel success. When we can not judge our own success, when it is impossible to feel the energy where everything aligns, this is the time when we have the most failures. We take a lot for granted and just work off that but most of the time I need some kind of confirmation that what I know is correct. That is when our work is the best when we leave the unknown.
Any project written in a language with big user base java, C#, C++, perl, rust even fortran has this problem. The only thing that helps is experience with the language. I very seldom see code that survives ten years, even no deps things fail because your compiler interpreter changes.
It is just part of the job. Sure I am not a big fan of C# or PowerShell but a big part is just that I have no experience.
That’s not generally true for .Net, though the use of third party libraries could create an issue in some cases.
.Net was designed deliberately so that multiple versions could be installed side by side and an executable would pick the version most likely to work based on target version and compatibility. In most cases .Net is also forward
compatible so e.g. a .Net 3 app continues to work on a PC where only .Net 4.8 is installed. In addition, libraries could be part of the application installation and in modern .Net, the framework can be part of the application installation.
In most cases, everything will just work, and when it doesn’t, one can just install the older .Net version needed and nothing will be broken.
What I mean with "no experience" is that I have never fixed issues with them myself. The amount of hours we were billed internally for fixing a broken .Net app tells me it was not that easy though.
My point is that if you do not know your platform things get complicated, either for yourself or for people that take over after you. For me personally python does not mark it self as extra hard to handle.
I have never been a Python fan, but I wrote my first python application in Zope 26 years ago it still runs. Since then I have touched other things that are much worse not all of them on the list above. My point is that while python may break, other stuff breaks as well.
There are a lot of prototype integration projects in Python though and that is incredibly hard to get running. I know nothing about C# but as Linus Torvalds said the binary compatibility layer for Linux is Win32 because of Steam, so MS has worked on the problem before. Though I would like to point out that when you are talking about prototype integration projects Windows is as bad as Python, I have rebuilt test environment in Windows that had been left to rot for ten years.
So in my work life experience all programming languages suck at this, python might suck less or more but it is more of a skill issues than anything.
I have a hard time saying that in a way that does not make vocational schools worth less. I appreciate people having done theoretical things, spending time are university is well spent time.
There are mechanics who did not do any theoretical work at all that later in life really need some university. My point is that some people really should go back to university because their work gets better after.
Doing a PhD later in life is a cool thing to do too.
One of those empty words one needs to be careful with it does not mean anything, and everything. Politics is not about suppressing ideas of other people, somethings parties can agree on others not so much.
I wonder if it is easier/lighter to make a parachute that can handle different speeds, e.g. for atmospheric reentry, reusing the same structure for the drogue chute and the main chutes.
Loading the VST in Reaper makes it fantastically easy to turn just about any Android or iOS device into a monitor. Great for checking the final mixdown for YouTube videos and EQing my podcasts in real time. It is also handy for bringing a guest onto a show since I can wire things up to use the mix minus in the studio without relying on AEC.
Looks seamless when you use it like that. As a "normal user" of a desktop OS, network audio always seems so custom, I guess how the OS and applications handle audio is always going to be the bottle neck. I have no need for a DAW but I often want to stream audio from something to something else e.g. as you say monitor audio on some other device.
You need to work out what the nearest routable adress is. This works wonderfully with taxis here.
FWIW cul de sacs are an evil invention, and what you describe is a common routing problem. The rescue services here solved it by mandating addresses with geolocation and the nearest streets for every house around here. That failed me because everyone uses that official data that is convenient for fire truck rescue.
The issue was resolved by complaining to the Uber Maps team for 9 months until they removed their fake road block.
The work around in the interim was a combination of:
1. Writing a long description of how to access our property.
2. Trying to limit the distance an uber driver had to travel. <1km made it more likely for them to review the map and comment before driving. Dont ask me why.
3. Oscillating the drop off marker on the map to make it more likely that the driver was sent to our street at all, where we could wave at them to get them to drive beyond the psychological roadblock.
4. Attrition lead some drivers to remember my name, and just come straight to the property ignoring the map.
Any other mapping service delivered people to our property fine. Its just that Uber randomly blocked the end of our street. Meaning our street had no entrance.
Problem was that, uber has an exclusive relationship for delivery with one of our local supermarkets, and my wife doesnt drive and was stuck at home with an angry baby for the duration.
Due to this issue we did push the maximum amount of our orders through other delivery apps, probably taking significant income away from uber. But they have deliberately structured their support channels to be impossible to deal with.
As a Openstreetmap contributor I know it is a rather common mistake, it is very seldom support actually can edit the map like you can on http://osm.org sadly these mistakes are not always trivial. I have similar support tickets oldest one is from 2007.
I have replaced thousands of flash chips on a running server farm, the guy who did the soldering had a 100% success rate in the end. My part was not perfect, so I agree it was hard but perfectly doable.
My work is basically just guessing all the time. Sure I am incredibly lucky, seeing my coworkers the Oracle and the Necromancer do their work does not instill a feeling that we know much. For some reason the powers just flow the right way when we say the right incantations.
We bullshit a lot, we try not to but the more unfamiliar the territory the more unsupported claims. This is not deceit though.
The problem with LLMs is that they need to feel success. When we can not judge our own success, when it is impossible to feel the energy where everything aligns, this is the time when we have the most failures. We take a lot for granted and just work off that but most of the time I need some kind of confirmation that what I know is correct. That is when our work is the best when we leave the unknown.
reply