Current #jjnotesfollow aliases:
# The canonical tug
tug = ["bookmark", "move", "--from", "closest_bookmark(@-)", "--to", "@-"]
# Show my current work-in-progress(es). To wip it, whip it good.
wips = ["log", "-r", "bookmarks() | description(exact:'')"]
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
It's not clear, based on personal experience, how long - if it all - the software development field will value devs who actually enjoy the work. Most people I know are producing mostly AI work and there's an obvious skill decline that's resulted from it. 1/?
But does it matter if your boss doesn't care? Or if their boss doesn't care? If the paychecks keep coming who cares? What's the point of choosing the mountain if the "joy" just means more hours on screen that could have been spent elsewhere? 2/?
I got into doing dev work, because I thought it was fun to learn and do and I genuinely enjoyed hanging out with others who felt the same. Now, more than ever, I realize how few people feel the same. And, now - more than ever, I realize that no on cares if I feel that way. 3/?
No, it obviously isn't that. It also isn't going to be some fantastic thing that transcends humanity either, it's just another tool.
@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.wrote:
I was contemplating pwc372, p2 and came up with โ- 1+&/-/'(&'(?x)=x)@0 -1โ (goal). Conceptually I like it, but maybe it can be simplified further? #thinkeringwithcodenotesfollow
(defun textlog-post (beg end)
"Publish the region between BEG and END to `textlog-url'.
Interactively, requires an active region. Returns the URL of the
new post when the server reports one."
You have #kakounenotesfollow, there is no need. I tried Emacs out a while ago to see whether it could replace Kakoune (I wanted to draw arbitrary stuff like images, 3D views, etc., in the editor) but honestly, Kakoune makes everything so easy to integrate that it was hard for it to compete.
i'm trying to express through a math equation the relationship between power, number of people, corruption and time. corruption = (time in a position of power * power)/number of people who have power
what do you think?
You look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress from work. He takes care of his family. Capitalism
Likewise... you look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress for lack of work, or food, or future. He wants to take care of his family. Communism.
We havenโt figured out yet. Maybe we never will.
Yea, aside from the money, sourcing is a big problem, one thing I noticed when trying to #vegannotesfollow at some point was that there are zero vegan snacks in ordinary neighbourhood stores, so that #experimentnotesfollow didnโt last very long.
Hello! I am a cynical optimist and recovering realist. It's been 3 days since my last sip of Hobbes. Today, I'm hopeful again. That's all I have for now. Thanks.
These days Ive been learning how to deal with guilt and feeling gulti about things I didn't cause. NGL is hard man, how do you start cntl-z your brains on that
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
I think you're right but executing on that idea requires a lot of care. It's similar to how functional programmers pathologically fear state; sometimes coupling/state are a necessary evil in order to keep the theory simple.
true! i might have been wiser to say: code quality is about managing coupling across the whole system. extracting a coupling sometimes requires you to introduce complexity beyond that which the extraction reduces.
@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.wrote:
Spending mornings scouring job boards and listings and applying.
Afternoons working on Cheltenham Open Data and iOS app development.
What about you?
@prophetorit๐งprofilefollowgrand and intoxicating innocence
always onlinereplied to@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.:
waiting for my friend so she can put my hair into a bun
ooh maybe I revive hallucinate.sitehallucinate.site and add this feature but instead of being able to modify everything it would be limited to adding features to the game/world. And itโs the perfect domain, a site thatโs been entirely mostly hallucinated.