I can be an idiot every once and a blue moon. Thank you to anyone who put literally everything a manual just in case someone is braindead and isn’t afraid to rtfm.
To be honest it’s just after I’ve spent 10 hours on something fairly complicated and new to me. I suddenly can’t think for myself anymore. It literally becomes a chore to do the simplest shit sometimes.
To be honest, I kinda wish some projects came with API manuals. I understand it’s not a priority in an open source project with limited resources.
It would be nice to use a python based ml tool without passing commands through it via shell. People do it, I just don’t have the time or experience to analyze a complex project like ML voice synthesis.
The last thing I messed around with choked on some wide characters that weren't in the current locale, so I guess picture the top half of the burger bun, about two thirds of the top part of the patty, a small pile of raw ingredients off to the side and some inexplicable six-inch nails through the raw meat, maybe.
Most of the rest of the stuff I do could be compared to those nouvelle cuisine jokes that have been running since the 1980s. Large plate, inexplicably small serving of something allegedly gourmet but is probably a cube of the cheapest pâté from the closest supermarket that was flash frozen and then stylishly drizzled in jus de menthe or something.
We had a consultation last year to better structure our code base to look more like the first picture. Then it slowly evolved back into the second picture.
Apparently, this is a dogfood burger. No idea why that exists, but I’ll take it, because I’m definitely dogfooding.
I’m building a build system. And I’ve got three previous/ongoing projects where I’m directly integrating it.
And yeah, I’ve noticed that I’m kind of jumping between features, always just building them as far as I need them.
And in particular, I’m not really planning ahead. For exanple, I noticed after the fact that I could easily pull out a whole feature into a separate library, and that would already be useful on its own.
But on the plus side, it’s much easier to figure out actual requirements this way.
I usually keep todo-lists, where I’ve kind of noted down the next few steps for each feature. And well, those then usually also contain infos for the step I’m currently working on or for previously completed steps.
I rarely actually stick to my planned next steps, but it does help when switching between contexts, if that’s why you’re asking.
Please edit your image so some of those sliders contain a tenth of an ounce of meat and some of the other ones have a full beef wellington half wedged into a bun.
I would take an already-made burger, then inspect it and rip out elements of it, replace several others, add a bunch of layers of new things. It would take a few months and I would have no idea what I’m doing the whole time, but I would persist. The end result would be a delicious burger that occasionally has a missing item. Still working on why/where/how that happens. People would enjoy it, but most would not know that they can customize their burger, or the extent of the options.
(I used to code as a hobby in VB, C#, and Java over a decade ago, almost two; this burger example is me not knowing a damn bit of Lua, as I fork and modify a game mod to have a lot more features, less confusing variables, and lots of broken commented code as I have ideas but still don’t fully grasp what I’m doing. Weeeee!)
programmer_humor
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.