some people who make programming easier
(who am I missing?)
@b0rk oh what good stuff there's also a lot of non-programming-specific answers to this, things like people who make sure everyone gets a chance to talk, or people who make it clear that the community does not stand for hateful bullshit @b0rk i think it'd be funny if they were just a rubber duck on a desk but it might be less helpful as an inclusion than something else @MrsPiglet @b0rk oh yeah, rubber duck debugging is a Thing, but it might not be the most helpful way to finish this image in particular The Breaker of All Things. They go where no fuzzer can and show your program is not correct HERE. Pedantic investigator ("let me see what this thing actually does and what edge cases it has") is related but am not sure if identical. @b0rk the forum moderator, who manages the space where you can find all these people (and pushes back on the "people who make programming harder" folks)? @b0rk the code reviewer, who reviews every new pr thoroughly and quickly. @b0rk the "loud old-timer" figure labeled "old": "X never works!" figure labeled "new": thinks "maybe I should change jobs" @b0rk maybe “the willing pair”? @b0rk Oh bugger, do you think you should replace X with, idk, XYZ because X means something now?? You forgot to draw yourself in the last frame ;) But srsly, someone who inspires with a positive attitude. Programming discourse can be full of negativity. Like, The Coding Train videos made me happy and inspired me to try new stuff. newbie "what's this thing" @b0rk The translator "My people don't speak English, I'm going to translate/explain it to/in Spanish", "Now I learn it, I will write how to do this with R if you come from Python" @b0rk The rage refactor guy/gal. Somebody has a problem so this person spends the next 24 hours fixing the problem for good. @b0rk not sure what to call them. But always appreciated the presence of people who question (usually in a design review) the why of things and every little assumption being made in the design (assuming other people know x or other assumptions). They can be tiring, but in a good way. @b0rk The quiz writers: https://hachyderm.io/@shafik/110968979182957281 and cursed code posters: https://hachyderm.io/@shafik/110770752177238000 🧐 @b0rk @neurothing The UAT guy who runs through all of the weird edge cases to make sure your code works properly! @b0rk people who write well detailed bug reports, with exact steps to reproduce the problem, attach all relevant logs, and keep the report up to date as new versions of the software get relased (yes, most of the hard tasks in code I touch is fixing bugs, not writing new code) @b0rk the artist, who draws comic stripes to explain complex programming concepts 😄 @b0rk also "the good Samaritan": that senior that is busier than anybody, but ALWAYS has time to listen to dumb questions and help even the newest intern @b0rk I am Tab Gurl for sure, and learn so much from my beloved loud newbies when we say "let's figure it out together" (probably how all those tabs got opened) so I'd add the partner in crime or interlocutor or similar @b0rk "Let's double your estimate so you have time to research this" - Donations @b0rk "This refused to work, and here's 482 different classic problems I tried solving before finding this really obscure one." @b0rk The SCM Knower: "I think I broke my git/hg/p4..." @jalcine @slightlyoff literally the most recent conversation I saw in a friend slack was folks helping someone solve a git issue @b0rk the Enlightened Layabout “Oh you don’t need to do <complicated thing> we can just do <simple thing> instead” @b0rk people who add good logging so bugs are easier to track down as they happen. Thanks folks! @b0rk This feels like a solid counterpart to the Being Glue post that’s been going around @kissane ooh interesting! I hadn't thought of it in those terms. personally I don't really know how to code without doing a lot of these things -- I need to talk to people to figure out what the computer is doing @b0rk I love this. Also: the Deep Diver, whose eyes light up upon encountering a problem that most other people walk away from, who then dives deeply into it, and comes back enthusiastic and ready to infodump on it. @b0rk There's people who just make stuff look fun. Kind of like the people who demonstrations at science museums for kids. The Showcasers? @b0rk the wild ones that push things to their limit to make them do things outside their immediate use case and open your horizons (how to think outside the box). @b0rk at this point I'm pretty sure I'm a "tool builder" Hard to test before pushing to the cloud? i made a tool for that. Same tool also troubleshoots failed flows! internal only, oc (cause it wouldn't help anyone else much anyway) @b0rk the "glue engineer": "yes! you can totally convert a video signal from outer space into a 3D model for the pico8! you will need these 200 tools and this 700 line script, but it's totally doable!" @b0rk the Database administrator: "did you know that with this index here and this index there your code will run 100 times faster?" - "Wow I had no idea I was making inefficient database queries!!! Thanks!" @b0rk how about the teacher? I’ve learned so much from your comics and also videos by people like Corey Schafer. @preslavrachev @b0rk @deadprogram "The oldtimer who's open with what they don't know (yet)" @b0rk In terms of internal / external team members, there is the internal facilitator: X: "Argh, I need an account on Z to do that..." @b0rk the cardboard cutout. The person who's just here listening to you ranting about your code @b0rk The bug reporter who writes up an extremely clear description of the problem and provides a perfectly succinct reproduction case @b0rk the detective: "I know we still haven't found the cause of this mystery bug, but I think we're close! Here's a document that explains what we've tried so far." @b0rk And there is also the guide: X: "How can we implement feature Z in this system?" @b0rk Janitors for keeping the office a clean and healthy place to work. All the other service workers in your day to day life. The people who are just really nice, who makes other people feel better (like a capybara). @b0rk @KirstieJane @b0rk that's amazing! It gives me strong "WikiFauna" vibes, c.f. https://en.wikipedia.org/wiki/Wikipedia:WikiFauna for some inspiration of who might be missing! 😃 And I guess I'm moving across all of those archetypes over time and context 🙈 A WikiOgre is described as having traits of an editor who can sometimes be inactive for periods of anything from days, weeks, or months, but often engage in a rampage of activity, editing wildly. I LOVE THIS! Hulk smaaaaash! @KirstieJane @b0rk also accidentally proven your point of “read the whole internet” 🙈😂 @b0rk Sigh. I have been so distorted by negativity that I was afraid this was sarcasm. That aside, it is quite good. @b0rk the thesaurus: “Yeah you can use X, but Y and Z also exist and make these tradeoffs to solve the same problem differently” @b0rk yes, it does seem somewhat ironic that "the textbook author" is not in the bottom-right panel. But maybe "the zine maker" should be :) @b0rk The Clarifier @AlanSill love it, the whole reason I wrote this is to talk about how essential communities are :) @b0rk My favourite variant on the grumpy old-timer/read-entire-internet is the "Other Tool Fanatic" who says "Oh right! That part of X was COMPLETELY INSPIRED by Y, which had a cool model that..." @b0rk a spelunker / muck raker; someone who's prepared to keep going deeper and deeper into a bug to find out it's true cause. @b0rk the QA, I found a bug for you here is the list of steps to reproduce it and a stack trace of the crash. @b0rk maybe too similar to the tool builder, but i nominate The Librarian (who spends their time writing reusable code snippets or libraries that other people can reach for). @b0rk the theorist - "here's a list of papers you may need to familiarize yourself with to fully understand the set of concepts behind this seemingly simple procedure" |
@b0rk the railroad patcher. “Oh you should just do it like this, wanna stamp my PR?”