Comic Strips

16840 readers

2295 users here now

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

The rules are simple:

The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
The comic must be a complete story.
If it is an external link, it must be to a specific story, not to the root of the site.
You may post comics from others or your own.
If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
Politeness.
Adult content is not allowed. This community aims to be fun for people of all ages.

Web of links

!linuxmemes@lemmy.world: "I use Arch btw"
!memes@lemmy.world: memes (you don't say!)

founded 2 years ago

MODERATORS

lawrence@lemmy.world

355

Are IDEs really like this ? (programming.dev)

submitted 3 days ago by Docker@programming.dev to c/comicstrips@lemmy.world

59 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] GreenKnight23@lemmy.world 2 points 2 days ago

I'd say that's true for most devs.

personally though, all that is noise to me and is difficult to maintain focus when it's got all these popups and autofills.

I'm currently maintaining a codebase that's got something like 900 methods/functions across multiple classes, modules, and other objects. It follows a pattern and is pretty easy to maintain though.

another project I'm inheriting is doesn't have any logical flow or pattern and is a shitstorm of JS Christmas trees. I'll likely need to used something that will trace through the callbacks just to see what the fuck is going on.

my point though, is if you depend on the tools that make it easy to write sloppy code, you will write sloppy code because the key feature of the tool allows you to do it without repercussions.

building something without effort rarely ends with a result you can be proud of. this is true for development and in life, IMO.