Elektrine lite

← Feed

@NichEherVielleicht@feddit.org

2026-01-29 22:07 UTC

Replies (23)

  • @kubica@fedia.io 2026-01-29 22:31

    That's why I let my code rest for 2 months before committing.

    Open ##178192

  • @tiredofsametab@fedia.io 2026-01-30 09:27

    I looked at code I wrote about a year ago today. Yeah, there are things I would've done differently now, but I had no trouble following it. Some of the choices I made were company standards at the time as well which, thankfully, have improved.

    Open ##182758

  • @BillyClark@piefed.social 2026-01-29 23:30

    This does happen a lot, but have you ever had the opposite happen? Where you go into some of your older code, and not only is it nice to read, but you had anticipated that you'd have to make this change later, and so the design makes the change easy? That's happened to me a few times and all I can say is that it takes days for my self-satisfaction to wane.

    Open ##1234691

  • @Sanctus@anarchist.nexus 2026-01-29 22:16

    Who the fuck wrote this!? ''Written by Sanctus Two/Months/Ago''

    Open ##1234692

  • Junior ass meme

    Open ##1234693

  • @SaharaMaleikuhm@feddit.org 2026-01-30 06:26

    I am usually quite pleased with my old code. It ain't perfect, but it's doing well for itself. Sometimes there is silly stuff I need to fix, but then I just laugh at myself.

    Open ##1234694

  • @hdsrob@lemmy.world 2026-01-29 23:37

    2 months. I've been writing the same software since 2003. Someone left some real crap in there.

    Open ##1234695

  • @Guttural@jlai.lu 2026-01-30 18:14

    As soon as I stopped trying to write textbook OOP stuff, this stopped occurring to me. That was years ago. I'm not saying I write perfect code, no. But when I read bad stuff I wrote, I can understand it and think of ideas about how to improve it if that becomes necessary. On top of writing more functional-style code, the way I achieved this was: - Absolutely no inheritance whatsoever. Composition + interfaces work wonders for what I do. - Minimal mutable state. This pays dividends when debugging. - Ditto for type-system-encoded nullability markers (ie. `?` in C#, `std::optional` in C++...) - I avoid writing code just-in-case something happens. If I haven't run it manually or via unit tests, it goes to the garbage bin (not an absolute, just a guiding principle). There's a chance that code isn't even correct to begin with and you'll have to throw it away should you ever need it. - Low indirection. I don't want to jump through 10 functions to see what something is doing, and nobody else does either.

    Open ##1234696

  • @zeezee@slrpnk.net 2026-01-30 09:18

    I like that this meme implies women and enbies write immaculate code and never regret what they've written before 😎

    Open ##1234697

  • @Otiz@sopuli.xyz 2026-01-29 22:11

    *his own two months old code

    Open ##1234698

  • @itsathursday@lemmy.world 2026-01-29 22:44

    Depending on the state of sleep deprivation and flow state, even waking up to the previous nights code is an out of body experience of shock and awe. Either I am surprised at the level of complexity and elegance with the rabbit hole that I went down or it’s a fragmented mess of FIXME placeholders that don’t communicate the brilliant ideas and plans from past me.

    Open ##1234699

  • @Kolanaki@pawb.social 2026-01-29 23:39

    Also the face almost everyone makes when they open up that tupperware that's been in the very back of the fridge for the same amount of time as your code.

    Open ##1234700

  • @diemartin@sh.itjust.works 2026-01-29 22:43

    TWO MONTHS!?!? I don't even know what I did last week!

    Open ##1234701

  • @rebelsimile@sh.itjust.works 2026-01-30 09:09

    Eh. I just jumped back into a project and felt kinda like a fish getting back into water.

    Open ##1234702

  • See, this is why vibe coding is awesome. You’ll never have to look at the code ever again!

    Open ##1234703

  • @Goldholz@lemmy.blahaj.zone 2026-01-30 07:57

    Its a great to see how much i've improved in 2 years :) Remembering the code i used to write and how i do it now

    Open ##1234704

  • @YerbaYerba@lemmy.zip 2026-01-30 02:13

    When I git blame after finding the production issue and see the committer is me

    Open ##1234705

  • @LillyPip@lemmy.ca 2026-01-29 23:27

    But… document your code. Hahahaha for who?!? Uh… for future you! Me to future me: lol no

    Open ##1234706

  • @TomMasz@piefed.social 2026-01-30 15:16

    Arrrggghhhh! It's hideous! Make it go away!

    Open ##1234707

  • @mintiefresh@piefed.ca 2026-01-30 03:35

    I barely remember anything I made from 2 months ago lol

    Open ##1234708

  • @hperrin@lemmy.ca 2026-01-30 02:01

    You mean… yesterday’s code.

    Open ##1234709

  • @mfed1122@discuss.tchncs.de 2026-01-30 06:48

    I am beginning to suspect that 90% of programming memes are made by beginners and 90% of the engagement with them is also from beginners. Maybe I'm just projecting. I remember seeing this stuff when I was starting and just assuming that must be how it is.

    Open ##1234723

  • @TheSambassador@beehaw.org 2026-01-30 03:37

    I can look at old code that I wrote and feel good about the growth I've made. I also can look at old code I wrote, which I need to understand/update, and be really annoyed at my past self. How annoyed I am is entirely based on what I need to do to the code right now. The fact is, it's way easier to be annoyed at myself than annoyed at other people.

    Open ##1234724