@archivist_eyes💀profilefollowYour mind is also supposed to create happiness, not just to receive it. You're supposed to find solutions, to invent, to imagine, to remember, to love. This much we always forget.wrote:
Turn the car on. Shift in Neutral. Gas to the bottom.
This is how my head feels most of the time.
@miq☕profilefollowEternal disciple of impostor syndrome ∙ Perth, WA.wrote:
Trying to gently work my way back to the target intensity needed for the Norwegian 4x4 to get my weekly dose of suck and feel accomplished after. Chronic left leg pain unfortunately likes reminding me it's there though.
Switching from Claude Max to Team, cc was trivial, just another login, but Claude Desktop and on iOS holds sessions in the cloud so need to move them somehow.
Routines in Claude Desktop create Claude Code sessions, so hourly routine litters in iPhone' Claude.app Code tab. Screw it, built my local version of AWS StepFunctions - Stepper - and run skills as state machines there.
I finished Rejection by Tony Tulathimutte and now I'm struggling to take any other book seriously. I need a pallet cleanser or something before I can move on
Frustrated with my phone usage again tonight, I uninstalled several pointless and time-consuming apps. It’s a cycle I repeat every few months.
During this cycle, I wasted a lot of time on one of those puzzle-matching games.
I'm considering switching to Ubuntu Touch at this point
Writing.
I want to do it, very badly.
I just don't want to be bad at it.
You have to be bad at it in order to get good at it. But...
Catch 22 isn't it?
I think reading helps quite a bit, especially writing about what you’ve read, even to yourself, just so you can go through the process of having to explain something that you’re only recently familiar with. There’s something about that process that seems to be helpful, at least to me.
Same.
The way I consume information influences how I think. Short form content makes my thinking fragmented without a clear structure. I feel that fragmented thinking won't lead to convincing writing. And I'm trying to regain some of that lost control.
Very interesting! I think something along those lines might be happening for me too.
Another aspect, always cooking in the back of my mind, "if you can't explain it well, don't explain it at all."
The fear of being bad at it is the only thing holding you back. I experienced something like that with playing music with others. Perhaps you could learn to lay down your critical brain during the creation process and that good/bad isn't a useful distinction until later when you're editing your work.
When I was 10, I thought I'd be a scientist
I wanted to tinker in a lab, doing something with beakers and bunsen burners
Making a difference.
As an adult, I sit in meetings and discuss who to fire next
I tinker with spreadsheets, doing something with LLMs and JIRA
Be enthusiastic
#poemnotesfollow#aifearnotesfollow
As young kid I dreamed of working with reel-to-reel machines
Cutting/splicing tape, happy accidents
As a teen I couldn't afford reel-to-reel but got decent with multi-track cassettes
Everyone was telling me digital was The Way (tm)
In my 30s, I finally learned how to use a DAW properly
In my 40s, I'm back to playing around with multi-tracks cassettes
There is no money in it, but I'm enthusiastic as I can be
(this is not so much as direct response as simply a response)
#musicnotesfollow#aifearnotesfollow
I assume this is not original at all at this point - but (extreme) DRY is not a good practice. My experience is that a bit of copying yourself and your colleagues in the code base often make maintenance of the code base easier.
@honey_ohs🥷profilefollowSoftware engineer. [Reluctant] Salesforce dev. Salesforce’s biggest hater.
stephenlf.devstephenlf.devImportant Thingsreplied to@asmund🥷profilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.:
Many have adopted the term WET (write everything twice)
Uncompromising adherence to DRY.
First copy-paste? Fine by me. Second? I'll still let it slide. Third? OK, now let's think about finding a suitable refactor.
Getters and setters for everything. Certainly, if you want an object to be doing more than just getting and setting a value right now, get them in there!
Planning to add functionality later without breaking code? Stop it! That should break code! If I'm consuming a library and have been using this setter method for 2 years, I don't want it to suddenly introduce brand new validation, caching, or logging behavior!
Are getters and setters on everything even considered a good practice? To me it screams junior developer who hasn’t yet fully understood encapsulation and abstraction — if you’re just exposing getters and setters as the interface then what is the class/module/etc providing beyond what a standard variable does…?
@fastidious🙈profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to@kateprofilefollow:
It was only yesterday that I clicked on a Translate button to read a Japanese post. Today I see a Chinese post with English translation right below. Beautiful stuff.