We probably don’t have enough user traffic to give people the specific help they need. Certainly not compared to something like StackOverflow, which is already what you’re describing.

The issues with generalised user-to-user programming help (esp re: StackOverflow) is that an increasing number of communities are doing this in closed-off areas like Slack and Discord, where their support is not indexed or searchable. Users running into the same problems are struggling to find each others’ answers. Creating yet another community that’s separated from the internet at large exacerbates this problem.

Man, I used to really like browsing the stuff at ThinkGeek. Even bought a few things. Now that it’s owned by… I wanna say GameStop?.. it’s ceased to be interesting to me. I liked things like the laundry basket that looked like a radioactive barrel, the shower gel that looks like a blood bag… that kind of light-hearted novelty stuff. But the new owner just gutted all the interesting content, and it’s just all IP collectables now.

It’s been long enough I forgot bout ThinkGeek. Damn. Wish something like it were still around.

• “progress on [1], fixed linting [2]”
• “[1] completed, setup for [2]”
• “[3] and [4] completed”
• “fixed formatting”
• “refactoring [1] and [2]”
• “fix variable typos”
• “update logic in [2]”
• “revert package.json and regenerate package-lock”

All my commits have comments. I generally commit after completing a ‘block’ objective, a describe what that was but in very simple terms mostly in regards to the file/section with the most significant logic changes. I don’t always specify the file if I did tiny typos/linting/annotation across a bunch of them, because the logic is unaffected I know that the differences will be visible in the commit history.

My weakness is that I don’t do it often enough. If I’m working on [2] for several hours, I’ll only commit when I consider it minimally-viable (completed 2), or when moving between machines ([further] progress on 2). And I have a bad habit of not pushing every time I commit, just at the end of the day or when moving between machines (though a messy rebase hopefully made that lesson stick), or if somebody else on the team wants to review an issue I’m having.

AI can code assist; it’s quite helpful for that. Predictive text, learning a less familiar language, converting pseudo, etc.

But it couldn’t possibly replace senior developers long-term. It just looks new and exciting, especially to people who don’t truly understand how it works. We still need to have human developers capable of writing their own new code.

1. AI is entirely derivative, it’s just copying the human devs of yester-year. If AI does the majority of coding then it becomes incapable of learning, thus necessitating human coders anyway. It also is only going to generate solutions to broad-strokes problems that it already has in its dataset, or convert pseudocode into functional code (which still requires a dev know enough to write pseudo).

2. It also currently has no way of validating what it writes. It’s trying to replicate what our writing looks like contextually, it doesn’t comprehend it. If it ever starts training on itself as it ages, it will stagnate and require human review, which means needing humans that understand code. And that’s not including the poor practices it will already have because so many devs are inconsistent about things like writing comments, documentation, or unit testing. AI doesn’t have its own bias but it inevitably learns to imitate ours.

3. And what about bug-testing? When the AI writes something that breaks, who do you ask for help? The AI doesn’t comprehend the context of the code its reading if you paste it back, it doesn’t remember writing it. You need people who understand how the code works to be able to recognise why it might be breaking.

AI devs are the fast food of coding. It will never be as good quality as something from an experienced professional. But if you’re an awful cook, it still makes it fast and easy to get a sad, flat cheeseburger.

I’ve worked with devs who are the equivalent of line cooks and are also producing sad, flat cheeseburgers: code of poor quality that still sees production because the client doesn’t know any better. IMO, those are the only devs that need to be concerned, because those are the ones that are easy to replace.

If AI coding causes any problems within the job market for devs, it will be that it replaces graduate/junior developers so well that fewer devs get the mentoring or experience to become seniors, and the demand for seniors will rack up significantly. It seems more likely that developers will split into two separate specialisations, not that our single track will be replaced.

These are essentially my thoughts. They’re helpful for indicating context (tone/expression/sentiment). The goal of language is communication; words alone can struggle with that. Well-placed emojis help improve communication. Numerous emojis breaking up sentences makes them harder to read; imo it impairs communication.

I also don’t like the idea of policing others’ use of a harmless sub-dialect of online communication just because one decides not to use it themselves. I personally don’t use or enjoy the ‘emojis’ that are just ‘fun graphics we like’ (most Discord custom emotes are this). Nor do I like that filter where 1-3 emojis are inserted after basically every single word. But that’s because it’s not my online dialect; it doesn’t mean people who use emojis that way are ‘wrong’.

Different platforms have different ‘accents’, and emojis are only one example of that. I find the numerous dialects of online English to be a fascinating topic that isn’t often considered.

Sometimes I’d feel sad that a trait of say, Tumblr’s dialect didn’t have a Reddit equivalent: Tumblr uses punctuation, capitalisation, and even typos as a tone indicator. A Redditor doesn’t know the different tones implied amongst these, even though most Tumblr users do:

• no. stop
• no stop
• noo staaaaahp
• noolkjaflakud STOP
• No. Stop.
• NO STOP

I can tell which of these are vaguely upset, genuinely upset, or pretending to be upset in a few different ways. Reddit doesn’t have that, because it expects everybody to write with formal grammar all the time, including not ‘allowing’ emojis as tone indicators. I suspect that formal writing style probably contributes to why so many comments are read in bad faith as smug/adversarial. 😢