this post was submitted on 24 Apr 2026
1251 points (99.3% liked)

Comic Strips

23453 readers
5271 users here now

Comic Strips is a community for those who love comic stories.

Rules
  1. πŸ˜‡ Be Nice!

    • Treat others with respect and dignity. Friendly banter is okay, as long as it is mutual; keyword: friendly.
  2. 🏘️ Community Standards

    • Comics should be a full story, from start to finish, in one post.
    • Posts should be safe and enjoyable by the majority of community members, both here on lemmy.world and other instances.
    • Any comic that would qualify as raunchy, lewd, or otherwise draw unwanted attention by nosy coworkers, spouses, or family members should be tagged as NSFW.
    • Moderators have final say on what and what does not qualify as appropriate. Use common sense, and if need be, err on the side of caution.
  3. 🧬 Keep it Real

    • Comics should be made and posted by real human beans, not by automated means like bots or AI. This is not the community for that sort of thing.
  4. πŸ“½οΈ Credit Where Credit is Due

    • Comics should include the original attribution to the artist(s) involved, and be unmodified. Bonus points if you include a link back to their website. When in doubt, use a reverse image search to try to find the original version. Repeat offenders will have their posts removed, be temporarily banned from posting, or if all else fails, be permanently banned from posting.
    • Attributions include, but are not limited to, watermarks, links, or other text or imagery that artists add to their comics to use for identification purposes. If you find a comic without any such markings, it would be a good idea to see if you can find an original version. If one cannot be found, say so and ask the community for help!
  5. πŸ“‹ Post Formatting

    • Post an image, gallery, or link to a specific comic hosted on another site; e.g., the author's website.
    • Meta posts about the community should be tagged with [Meta] either at the beginning or the end of the post title.
    • When linking to a comic hosted on another site, ensure the link is to the comic itself and not just to the website; e.g.,
      βœ… Correct: https://xkcd.com/386/
      ❌ Incorrect: https://xkcd.com/
  6. πŸ“¬ Post Frequency/SPAM

    • Each user (regardless of instance) may post up to five (5 πŸ–) comics a day. This can be any combination of personal comics you have written yourself, or other author's comics. Any comics exceeding five (5 πŸ–) will be removed.
  7. πŸ΄β€β˜ οΈ Internationalization (i18n)

    • Non-English posts are welcome. Please tag the post title with the original language, and include an English translation in the body of the post; e.g.,
      SΓ­, por favor [Spanish/EspaΓ±ol]
  8. 🍿 Moderation

    • We are human, just like most everybody else on Lemmy. If you feel a moderation decision was made in error, you are welcome to reach out to anybody on the moderation team for clarification. Keep in mind that moderation decisions may be final.
    • When reporting posts and/or comments, quote which rule is being broken, and why you feel it broke the rules.
Banned Artists

The following artists are banned from the community.

  1. Jago
  2. Stonetoss

It should be noted that when you make reports, it is your responsibility to provide rational reasoning why something should be removed. Saying it simply breaks community rules is not always good enough.

Web Accessibility

Note: This is not a rule, but a helpful suggestion.

When posting images, you should strive to add alt-text for screen readers to use to describe the image you're posting:

Another helpful thing to do is to provide a transcription of the text in your images, as well as brief descriptions of what's going on. (example)

Web of Links

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] ChickenLadyLovesLife@lemmy.world 4 points 21 hours ago (1 children)

It's funny, but there has long been a paradigm in programming called test-driven development or TDD. The idea is that you have a small number of experienced developers who write a suite of tests that an application has to pass, and then you let an army of newbies write whatever the hell they feel like writing and if their code passes the tests it goes into the application (somewhat snarky summary but not entirely). In my experience it does not produce solid applications but a large fraction of the programming world swears by it. I've always thought that the construction analog of TDD would be letting a bunch of inexperienced workers build houses and then the experienced contractors drive around in bulldozers knocking down anything that happens to not be built well enough.

[–] Baguette@lemmy.blahaj.zone 3 points 19 hours ago (1 children)

Test driven development is moreso

  1. You know what real life scenarios you're solving for. Basically, this is the problem statement of your design.
  2. You write out these tests to say your service must pass these tests in order for it to be considered working. In order to consider problem x solved, the service must do y.
  3. You make the first iteration of your service to just repeat exactly what the tests want it to output (basically to create a skeleton with a bunch of magic numbers)
  4. You make the second iteration. What magic numbers can you remove and actually implement for? What workaround can be fixed? Are they still passing the test? If they start failing the test, you should relook at what you wrote and debug from there (this assumes your tests are rightfully written).
  5. You keep continuing with that process until you have a service that fits your test cases and without mocks

The obvious flaw is that 1 is almost never truly accurate. Scope usually changes, and assumptions made probably invalidate your test. It is a valid way of thinking though, because it helps define your expectations, and reduces the likelihood of you making something that misses the target.

[–] trem@lemmy.blahaj.zone 4 points 18 hours ago

For what it's worth, when we say we do TDD in my team, we write a singular test case that fails, then we implement the production code until the test case works. Then maybe do a bit of refactoring to make it all work nicely together, and only then you start with the next test case.

Writing swathes of unit tests upfront sounds absolutely mad to me, for the reason you state. But also because you do need an API to test against. You can't write a unit test in complete isolation, pretty much by definition. You can often do so for integration tests, but you definitely don't want to put all test cases into integration tests, as that increases complexity massively...