Mastodawn

Engineers, artist, craftspeople, and really everyone else doing anything productive:

Please take pride in your work.

Do not settle for "good enough, move on", if you have the choice.

Feel comfortable signing your work, and take full responsibility for whatever you produced.

Even more so if you could easily hide awful, fragile messes without people dying immediately. Looking specifically at you, fellow software engineers. :)
We can do better than ~gesticulates wildly~ all of this. You have it in you, don't lose the spark.

I know this is easier preached than done.

Don't feel bad doing what you have to do to survive, but do know you're not alone in wanting something different, and you're certainly not in the wrong for doing so.

Nobody's worth is determined by their paycheck.

Gyroplast 23h ago

tante 1d ago

Anthropic's Claude Code's full source code leaked. Claude is seen by many to be the best coding LLM on the market with Anthropic proudly stating that Claude Code itself is mostly written by the LLM.

Now this sounds good as long as nobody can see the code which is quite the trash fire. Detecting "code sentiment" via regular expressions, variable and functions names containing prompt parts trying to influence the bot, a completely intransparent mess of a control flow that makes actual maintenance and debugging functionally impossible and the prompts ... of the prompts. All the begging and pleading to the chatbot not to do this or not to do that or please to do this.

It is fascinating but it is as far away from actual engineering as drunkenly pissing your name in the snow. Dunno what you call the people prompting software at Anthropic but "engineer" is not it.

Now it is fun to look at the currently hyped product striped bare and showing its pathetic quality but that is the future of software if we let those companies continue to undermine every good practice software engineering has tried establishing.

The software we have to use will be bad, insecure, unmaintainable, expensive with nobody having the skills or resources to build something better. As I wrote a few months ago: LLM based software production is equivalent to saying that fast fashion should be the only way to produce clothing. A tragic degeneration of the quality of the artefacts we rely on build for maximum profit on the backs of people in countries from the global majority.

Gyroplast Mar 17

Solawi Köln 🌱💚Mar 15

Gerüstet mit Gummistiefeln und Regenzeug wagten sich gestern einige tapfere Solawistas aufs Feld, um Dicke Bohnen zu säen. So viel Einsatz wird hoffentlich mit einer reichen Ernte belohnt! 🫛

#Solawi #Köln

Gyroplast Mar 17

Nath Jan 25, 2022

Somewhere, someone finally made this and I think it's beautiful: https://www.thingiverse.com/thing:4687836

Ethernet | RJ45 clip to secure/repair/fix broken tab by guss67

This clip was design to fix/repair/secure the broken or loose tab of a RJ45 Ethernet connector and avoid crimping. Designed to prevent from moving, wiggling, falling from the connector and easy to install.UPDATE v.4.9 | 28/01/2021Added the 3 following files which have slightly wider body (0.25mm) than 4.7 version and small upgrade on the tip.1. "4.9.nf.supported" (extension) comes "with supports" for the ones are not very familiar with. But I still prefer S3D's supports.2. "4.9.nf" (extension) with "no fillet", to make it easier printing with supports.3. "4.9" (extension) with fillet, for "smooth edges". On FDM printers isn't that much noticeable.UPDATE v.4.7 | 01/01/2021Added another version with "no fillet" (".nf" extension), actually it has sharp edges to make it easier printing with supports.PrintingSuggested printing orientation is the one as the files are stored, why?Printing the tab from the base to the tip in X-Y axis makes it stronger and more flexible since its printed in one continued string.If you change the orientation with the tip on top then tab's base will start from the bottom and builds up while the Z axis is sticking the rest of it till the tip. With this orientation the tab has more possibilities to brake since Z layers don't bond the same as the method I suggested.*If you have another solution let me know.Supports Supports needed and you need to be experienced with good slicer settings. Also attention needed when removing them from the actual print.Or you can print the file with "4.9.nf.supported" (extension) which comes with supports. But I still prefer S3D's supports.Installation note:1.Before install the "printed clip" check the left overs of the broken tab. If it is too long the tip of the "printed clip" might not click underneath the left-over. So, I suggest to leave a length of the broken tab about "0,5-1,0mm". If the broken tad left-over is to small or cuted flash then the printed one might not click and hopefully that would work well, haven't tested that scenario.2.Follow the sketches to install the "printed clip", also while sliding in if you find it a bit hard some wiggling might help.*You may call it the "ScorpioNet" or "Devil's Network Tail"! Designed in InventorIf you enjoy and want to support my work you can donate me on the link below,Thank you!

Thingiverse - Digital Designs for Physical Objects

Gyroplast Mar 13

502 Bad Gateway — No Cookies!

Gyroplast Mar 10

Well, if anyone else wonders why their AKAI MPK249 MIDI controller isn't recognized at all via USB, despite everything lighting up just fine and even with an external power supply— try a USB 2.0 port.

For some reason, it seems to hate the USB3 controller in my laptop, an Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) to be exact.

Same behavior in Windows, on the same Laptop, this is not a software/driver issue. Maybe the crappy cable I use doesn't fly with USB3, but either way: if you're not on an M1/M2 Mac (you might need the FW upgrade to 1.02 for that) and cannot establish an USB connection to your MPK2, try a direct connection to an USB 2.0 port, or loop in a cheap USB hub to enforce USB2 that way.

Gyroplast Mar 8

ελΥ.𐤍 Mar 6

And that's how I ended up on mastodon

Pete Prodoehl 🍕Feb 28

I read a README file I wrote a few weeks ago and decided it didn't have enough information, so it's now twice as long with a lot more detail.

I'm the only one who will ever read or use the file, but I have learned I cannot rely on my own memory a few months or years from now when I need to revisit the project or do something similar.

Make notes! Make more notes. It's a text file, it won't take up much space but it might save you a bunch of time in the future.