Mofpofjis

10 ms·

1.
by Mofpofjis 1y ago
A commit that was "co-authored-by" 6+ people and has three thousand lines of code: this is a total wreck of a development workflow. This feature should have been implemented with a series of about 20 patches. Awful.
2.
by Mofpofjis 1y ago
quick, the address of a burn clinic
3.
by Mofpofjis 1y ago
next level: use AI agents in their dating apps on both sides to decide if they want to hook up
4.
by Mofpofjis 1y ago
> I make a wall with bricks, even if it will be covered with coating i will do my best to have regular joints and pacing. Absolutely. This is at the core of it.
5.
by Mofpofjis 1y ago
> Why would anyone rather read and fix someone else code rather than writing the code themselves? Because their own review standards are low (so they find reviewing "easy"), and/or because they can't appreciate the em
6.
by Mofpofjis 1y ago
Strongly agreed. And, your wording is excellent.
7.
by Mofpofjis 1y ago
For me, the electric bike analogy works differently: it enables people to ride, regularly, who would not be able to do that with traditional bikes. That's totally fine. But electric bikes don't threaten to take away our normal bik
8.
by Mofpofjis 1y ago
There are things that "modulate" this. Violating copyright is never right, of course, some questions are however scale, and purpose. Taking others' creative output, unlicensed, for large-scale commercial gain, is about the wo
9.
by Mofpofjis 1y ago
Agreed. Smartphones are portable, mobile computers that suck at every single aspect of being, and working as, a computer, except for mobility. They are not powerful, they are not general purpose, they are not ergonimic, they do not respect
10.
by Mofpofjis 1y ago
> I got into programming because I like programming, not because I like asking others to write code on my behalf and review what they come up with oh finally someone else who didn't enter programming because, as 7-10 year old child,
11.
by Mofpofjis 1y ago
OMG I didn't notice. Way to burn down a huge amount of respect stemming from past cryptography work in just one blog post.
12.
by Mofpofjis 1y ago
> I am finding the most destructive aspect of LLM assistance to be the loss of flow state. Finally someone else mentions Flow!
13.
by Mofpofjis 1y ago
Wrong. I do pay my general contractor for the unseen quality that goes into the structure of my home. Programs should be built the same way.
14.
by Mofpofjis 1y ago
"regular" code review is indeed a total theater, a travesty, a farce. Real , meticulous code review takes absolutely forever.
15.
by Mofpofjis 1y ago
then you are a terribly sloppy reviewer
16.
by Mofpofjis 1y ago
well said!
17.
by Mofpofjis 1y ago
This is actually a good reason for exiting the industry before one's job goes away. Steering AI to barf up the right-looking pool of vomit is not the Flow-generating experience that many people have started to program for.
18.
by Mofpofjis 1y ago
> Understanding code takes more effort than writing it yes! > somehow not difficult to explain. Coding is a creative activity where you work top-down; you decompose the abstract/high-level into the detailed/low-level. You
19.
by Mofpofjis 1y ago
> why the hell did I do this? struggling to remember - git blame - always write good commit messages
20.
by Mofpofjis 1y ago
This is it. Reading AI slop does not form synapses in your brain like writing the code yourself does.
21.
by Mofpofjis 1y ago
> A heartfelt provocation okay then (profanity begets profanity) > Reading other people’s code is part of the job. If you can’t metabolize the boring, repetitive code an LLM generates: skills issue! Do you /intend/ to spend
22.
by Mofpofjis 1y ago
Evidence to the contrary (anecdotal, admittedly): - https://github.com/EbookFoundation/free-programming-books/is... -- "The most recent freely available draft of C17/C18 used to be c17_updated_proposed_f
23.
by Mofpofjis 1y ago
I agree with you about the seriousness and heft of POSIX (and I definitely know your name from comp.lang.c[.moderated], so I respect your opinion); however, there is no arbitrary gate-keeping around POSIX. If anyone is willing to put in t
24.
by Mofpofjis 1y ago
> Now try to contribute to OpenGroup. Funnily enough, I had ended up contributing to POSIX without trying to. I just participated in mailing list discussions and in the public bug tracker (reporting issues, commenting on tickets etc),
25.
by Mofpofjis 1y ago
> they could find a home at ECMA where Javascript lives or they could go build their own SDO for purpose One option is https://www.oasis-open.org/
26.
by Mofpofjis 1y ago
> "Maybe you haven’t really trusted anyone with your wins yet" At the end of one of her interviews on youtbue, Kelly McGonigal explains that -- paraphrased -- being praised to the face creates an intimate context around the pra
27.
by Mofpofjis 1y ago
> The public money is inevitably passed through [...] public sector bureaucrats I'd phrase it a bit differently -- local (country) regulations, taxes and fees stifle startups in the crib.
28.
by Mofpofjis 1y ago
> I think it's cultural. Oh yes. Being a failed entrepreneur is a stigma. Being a very successful entrepreneur is a stigma too. Only being a struggling or moderately successful entrepreneur is acceptable.
29.
by Mofpofjis 1y ago
The complaints about ISO Prolog, and about ISO standards generally not being available publicly / at no cost, resonate a lot with me. If you compare eg. the POSIX and the ISO C development workflows, and their respective end results, t