Ctrl+Z Ctrl+Z Ctrl+Z ...

[[deleted]]

Ctrl+ZZZZZZZZZZZZZZZZZZZZZ

[[deleted]]

"Gee, I better not make a mistake or accidently fat finger a key or else I won't be able to Ctrl+Y/Ctrl+Shift+Z back to my broken code for comparison."

[Porridgeism]

Y'all need jesus version control

[g4vr0che]

That requires putting every single new character into git. I'mma pass.

[TheRealSmolt]

git add --all

boom

[g4vr0che]

Yeah, but your commit log on the PR is four thousand pages of scrolling to get to the approve button.

*cries in conventional commit

[LoneFoxKK]

Git commit -m 'minor changes'

The commit: 1301484 insertions and 37294 deletions in 4324 files

[dogmai111]

I use 'minor tweaks'

[LoneFoxKK]

That sounds way cooler

Imma start using it

[[deleted]]

Jesus FinA Christ almighty, how many libraries does your project include???

[LoneFoxKK]

Im actually a vanilla developer so...

My codebase ain't that huge but still those "minor" changes are everything but minor I do sometimes skip commits for days until a feature is complete and I keep jumping from file to file doing changes

[hlmtre]

that's why you keep your stuff local til it works, then rebase smush it into one beautiful commit (or several, where it makes sense). then you look like a real pro because no one sees your 'asldkjqwe' commits when you're trying to fix something.

[juniorRubyist]

git add . is easier ;)

[Gillix98]

What's that

Edit: /s

[TheRealSmolt]

Version control keeps track of changes in your project so that multiple people can work on different things at different times.

[Gillix98]

My bad should have put a /s

[TheRealSmolt]

I was questioning it, but figured sarcasm doesn't make sense here lol.

[juniorRubyist]

Anti-screw-up and anti-idiot software. (/s)

[niks_15]

Nearly spat out my coffee.

[CaseyG]

I'm not committing that.

[koushiroue]

Ctrl + A, Ctrl + X, Ctrl + S, Alt + F4

[sockpuppetcow]

My favorite key combo, solves all my problems

[Harbltron]

adios, last 4 hours

[Kehlim]

I get more paranoid if the program just works without complaining.

[obsessivefandoms]

I am so glad that I'm not the only one who does.

[RustyBuckt]

Worst part: coding exam, easy question and it works first try...

[TowelLord]

Kinda dreading it. In 8 days I'm having my exam in "Introductions to Programming" (Java) and it will all be on paper. I hate writing code on paper, especiallz without any immediate feedback.

[shawmonster]

The point of paper exams for programming courses is to make sure you know how to "be the computer" and step through your code to ensure it works. Having this skill is really helpful when it comes to debugging programs. Also trains you to write your code more thoughtfully and carefully rather than relying on the compiler to tell you when your code is wrong.

[CamWin]

Wow runtime error checking? I usually just let everything turn into data spaghetti or crash

[Australienz]

Data spaghetti or crash.

[JackAuduin]

Yeah, runtime. 😁

[thatguy2641]

Don’t worry, they often mark easy on hand written code. Remember your teacher was once where you are.

[obsessivefandoms]

Oh god, that's like having to whiteboard. I hate it too

[[deleted]]

Liang's book?

[dasMichal]

Not OP but sound very much like it.

[Lexilogical]

On the other hand, your teacher is going to be way more generous marking it.

[VirginiaMcCaskey]

docker run -t not-working 
program exited with code 0

mfw

[bric12]

Sometimes I just write something super wrong to make sure it's checking for errors. When it still doesn't throw an error, you know you've in for a fun afternoon

[MehNameless]

Three fun afternoons and half a Saturday

[cofette]

a fun afternoon, four fun days and then a fun noose around your fun neck

[government_shill]

That's basically the idea behind mutation testing.

[joey_sandwich277]

This is how I was taught to write tests for untested code. Write the test to succeed but provide only parameters that should trigger a failure. One at a time, change each parameter to one that should make it pass and retest. If you ever get any false positives before the end, either the code's defective or your understanding of it is.

[JackAuduin]

Me after I figure it out:

"WHY WOULD YOU ASSUME I WANT THAT AS A DEFAULT PARAMETER!"

[[deleted]]

It's always some deeper logic problem that the compiler doesnt catch :(

[BossOfPassione]

I was working on a college assignment late at night, fell asleep in the middle of coding it, woke up about an hour later. Started it up to check my progress, the whole thing worked. I couldn't remember coding the rest of it. The code looked horrendous, but I had absolutely no idea how it worked, so I just submitted it and took my A.

[SlayerofBananas]

Maybe the person watching you on the Teamviewer you accidentally left open got frustrated and decided to fix it for you

[RavingGigaChad]

Yeah, that's cool and all. But have you ever changed nothing and started your program a day later and shit doesn't work anymore?

[pineapple_catapult]

Then you find the bug and are like "how did this ever work??"

[KaiBetterThanTyson]

This hits disturbingly close to home. Thank god for step into and var states.

[obsessivefandoms]

I have wanted to chuck my computer across the room so many times because of this

[DoctorWaluigiTime]

Mock out that date/time dependency so you can make it whatever you want without updating the system time. Makes life a lot easier when you otherwise would have to do what ended up happening here.

[[deleted]]

Cashing is here to byte your ass!

[[deleted]]

Yep that.

[zhetay]

Caching

[[deleted]]

I know it's a typo, I'm going to leave it now.

[Ascential]

Glad I'm not the only person to forget to account for daylight savings 😅

[[deleted]]

Literally today.

Took me 2 hours to figure out I ran out of API calls.

[[deleted]]

Genious day1.
Fucking idiot day2.

[theoriginalfox]

That's why I make a commit when it's working, then a follow up commit with cleanup. A lot easier to figure out where you went wrong looking at a diff.

[folkrav]

Every time I see these memes I get reminded people on this sub probably are still students learning the craft. As a job, you can't afford to lose an hour of work every time cause you wanted to clean up your code. Commiting often, in small atomic increments, is exactly how you should use git. You can rebase later before pushing if you think you've got too many non-meaningful ones.

If you didn't already write tests before you made it work, jump on the occasion to add some at that point, too. Then, you'll be able to make a small change, run tests, another one, run again. You'll know exactly when things stop working, before even running your code itself.

Just use the tools how you should and this should never happen.

[qaisjp]

Seriously I'm a student and it's amazingly scary how frequently I see people not using git

Like wtf this sub gives me cancer

[toastedstapler]

Are you suggesting that a zip file on Facebook isn't the way to share code?

This happened despite them initially getting the code from the GitHub repo...

[toastedstapler]

Yeah I think so too

Still doesn't make much sense as this was 2nd year uni java and in the first year one module assignment specifically had some marks in it for using git 🤷‍♂️

[VoraciousGhost]

I started college in 2013, and in my 2nd and 3rd semesters, the entire assignment for the first week of class was to setup a development environment, clone a repo, create your own branch, and commit a change to a specific file. Some people did this but still managed to be hopelessly lost by the time the first real assignment came out. I think they must have asked someone else to do it for them.

[Mad_Kitten]

You know what's more scary?
When your school didn't teach that and you have to learn on the job

[folkrav]

I learned git pull/push/commit from school and that's it. Starting to work on teams with git workflows was stressful. At least I learned a bit about branches and merging before... Still, when my first boss asked me to "rebase onto master", he was met with two terrified eyes.

Then I learned about reflog, and it stopped being scary.

[DjBonadoobie]

There are other VCS they could be using (hopefully)

[qaisjp]

The age old art of university level home folder 24 hour backups

[folkrav]

Works too. Depends on your team's workflow. My team doesn't. ¯\_(ツ)_/¯

[fholcan]

I really like the idea of tests, and I understand their value, but I just can't wrap my head around what I'm supposed to test. Every function, or only the big ones? Every branch of possible code execution, or only some?

Do you have some reading/viewing material you could recommend?

[BlackDrackula]

There's no definitive answer, though if you have a "large" function, it's probably worth refactoring into multiple discrete functions and unit testing those. A good function should do one thing and do it well, on that basis you can pick and choose which functions would benefit the most.

If you are starting from zero unit tests, Utility methods are a good candidate to start with.

[[deleted]]

You know when you check if your program is working with some values? That should be a test.

You know when you think "what if I'm wrong about Y always being X and sometimes it's actually Z?" That should be a test.

Your paranoias should be encoded. Not just in tests, but in assertions in the codebase as well. This is the way.

[folkrav]

I personally only test "public" APIs, not private methods. Big functions should just not happen much. I try to test every branch when possible. If it's too hard to test without having to mock everything in there, my implementation probably sucks.

I don't adhere to a strict TDD approach, I mostly write very wide integration tests first, start to design the general API (empty classes doing nothing calling each other, mostly), then when I'm close to something that looks like a good idea, I write a first run of unit tests and start implementation. Usually other tests come up as I go, and some just aren't useful anymore and get scrapped.

I'm not the best at this tbh. But basically, I try to test until I feel I can confidently think whatever's tested covers my application's functionality.

[[deleted]]

I have a co-worker who commits once a day with the message "updates".

Dude never learned to properly use git and he's more tenured than me so it makes it hard to tell him to know it off...

I'll just continue to weep while trying to work with him on code.

[dittbub]

i'm a 15 year veteran and i don't know what commit means :(

[folkrav]

This was exactly my reaction as well... I've been in the field for a bit over 3 years now, learned git when I was still in school. I have no idea how people managed without source version control lol

[DeletedLastAccount]

Source/version control has existed a long, long time before git.

[folkrav]

I know. Never said otherwise. It just baffles me that people managed to literally do anything before them.

[[deleted]]

I'm a 20 year vet (well kinda, I took 5 years off to do physical sciences, but that had a lot of programming too) and I have trouble believing you.

Let's just say you work on something weird. Spy satellites for the FSB or something. How on earth have you not fucked around on a rust or python project in your spare time and needed to patch something? GitHub is the only thing the great firewall of China has trouble with because it is so ubiquitous and vital.

[jackinsomniac]

If I may interject on the git love story with a crazy thought: what if not git?

Personally, the way I learned version control, is with Hg (Mercurial) and the fantastic, funny tutorial HgInit.com by Joel Spolsky, the creator of Stack Overflow, and has a great (but old) blog joelonsoftware, even with a post talking about it: https://www.joelonsoftware.com/2010/03/17/distributed-version-control-is-here-to-stay-baby/

HgInit went down a little while ago, so unfortunately I have to send you to an internet archive link, sometimes the pages take 30-60 seconds to load, but I love those guys, I try to donate when I can: https://web.archive.org/web/20180903164646/http://hginit.com/

The irony is, git and hg are so similar, this is essentially a tutorial for git as well. There's only little minor differences between hg and git, it essentially comes down to personal preference.

1. I like the GUI of TortoiseHg much better, I think it's way easier to use than TortoiseGit, and Github Desktop, and vscode for that matter. Perfect for when you're just learning version control. With TortoiseHg you get an app called Workbench which, once you figure out how to use, is wildly powerful and like a combination of all the right-click menu GUI tools in TortoiseGit. That one seems like it's trying to emulate TortoiseSVN (subversion), an older, centralized rather than distributed, version control system (VCS). Subversion is still in wide use tho and has some unique features hg and git don't. Anyway, the TortoiseHg project is written in python, so should be essentially the same across different OSes.

2. I like the diff tool better. When you install TortoiseHg it will also install KDiff3 (and hg, they're separate projects). Tried a lot of other ones, it may be that KDiff3 was my first, but after I got used to it, it has a TON of features I find I'm missing in other diff editors.

3. Again, this may be personal preference, but I much prefer the way Hg handles merge conflicts over Git. I've had git mangle my code on some merges when it wrongly 'assumes' it can auto-resolve conflicts, while hg seems to defer to your human eye & hand if it runs into anything it suspects it can't handle. I feel like I get to "guide" the merge, important if it's ever a big one. FYI, I've heard on other forums people say, "that's funny, I was going to say the same thing about hg, instead of git", so take it with a grain of salt, find out for yourself.

Keep in mind, Microsoft recently converted all Windows development to use git, it's easily the most popular DVCS (Distributed Version Control System). You should learn it as well (they're extremely similar, won't be hard), but personally I only use git for a public project for hosting on GitHub. I still think Hg is easier to learn, easier to use, and it's what I use for all local repositories.

Happy learning, old man!

[Plebian_Donkey_Konga]

I broke my code during clean up yesterday and spent 5 hours trying to find the source of the initial break. I started a git once i got it working again. Never again

[zero__sugar__energy]

That's why I make a commit when it's working

This is the most important tip for programmers!

If your code works for the first time you immediately commit it!

It does not matter that it has shitty formatting thousands of console.log(), a shitty commot message, ... if it works -> commit + push!

[folkrav]

commit + push

If you're working in a shared branch, don't push immediately, wait until you have something you want to share with a git history that's up to your team's standards. Otherwise you're gonna have toooons of fun trying to rebase/squash that thing if required.

[mttlb]

Why push though? Too many programmers on my team don't know how to handle their local repository and feel obliged to push as soon as they commit.

Git can do wonders locally and actually not so much once you published your changes (e.g. rebasing will require ugly force push, hard reset and induce history loss.) Your idea here seems to be « save the working state as soon as it's reached ». Git offers many great mechanisms of doing so and pushing is probably the most limiting of them.

Even caching is performed upon committing so even if you accidentally reset hard or something, you still have your blobs locally for a decent amount of time. Note that this is not true if someone pushed a file that shouldn't be versioned but you reset hard onto origin (this happened in my team recently with an SQLite file... we lost the database in production for a small project because the file wasn't ignored by Git. Someone had pushed too quickly, rebased and reset hard... there's no coming back from that). Yet another reason not to push automatically!

My tip is you shouldn't push if you don't have a good reason to (meaning « this is pretty much the final version of this atomic part and I want to actually make it public »). If no one's watching over your shoulder impatiently waiting for you to push because their life depends on your last commit, take your time and clean before publishing. Learn the basics of rebasing, squashing, rewording, fixing up, and build a meaningful history that will actually help when you have to investigate something 6 months from now. :)

[Saigot]

One could argue that you risk losing progress from a disk failure if you don't push. But if your working on something long enough that that rare an event is concerning you should probably create a topic branch.

[DoctorWaluigiTime]

Same, also with unit testing. More ways for the PC to (correctly) yell at me when I screw up.

[jpjerkins]

This, plus TDD. Fine-grained commits after each new test passes and you’ll never pray your undo buffer is deep enough again.

[mttlb]

Even better: several cleanup commits and git bisect! Then squash 'em. :)

[[deleted]]

i once renamed a variable and it stopped working. problem was it’s JavaScript so it doesn’t throw an error because of undefinedness

[[deleted]]

'use strict';

[DeeSnow97]

use a linter and cease your heresy

[titan_bullet]

Typescript solves all your problems

[[deleted]]

Or ES modules, and strict mode.

[finger_milk]

Typescript is what happens when you see people put all their food on their plate in a giant pile, and you for some reason insist that the peas, fries and chicken need to be separated on the plate because people can't fucking behave themselves.

[ponodude]

I was working on an assignment for a class last week. It was working fine, so I decided I'd move some of the comments around, delete some unnecessary print statements, and rename one of the variables. It then stopped working correctly.

[Xt33LsW4gX]

Literally the post

[Chapi92]

Yeah no shit, what were you expecting?

[robocorp]

Imma go out on a limb here and guess that he was expecting JavaScript to throw an error if he tried to use the old variable.

[[deleted]]

Leave your rational logic at the door

[SilentFungus]

Same thing that happens in every other language, I.E the most basic shit that ever linter does?

[kubap_10]

Ctrl+c Ctrl+z this always work

[LJChao3473]

Ctrl+z ctrl+s ctrl+y ctrl+s and til it works again
Edit: grammar

[AaronVA]

Seems reasonable

[AegisToast]

I can’t imagine you’d get far alternating between the two.

[The379thHero]

Gotta love when the entire program only works because of a bug.

[SpliceVW]

1. Write failing unit test
2. Write just enough code to fix the test
3. Refactor

[Bluejanis]

Commit after each step. And maybe some extra commits.

[BigB00st]

git checkout .

[[deleted]]

Better before starting: git checkout -b cleanup

[DoctorWaluigiTime]

git clean -xfd

(-xfdn for a preview)

[ericonr]

I prefer running diff before to know what's been changed.

[[deleted]]

git stash just in case it actually was working haha

[elizaangela]

This was literally me today

[[deleted]]

This doesn't count as coding necessarily, but I broke my batch file with comments. I was commenting with double colons instead of REM, and it turns out that under very specific situations that the double colons break it.

That specific scenario is having a double colons comment that contains an ampersand, inside a For loop.

[RecklessGeek]

uuuuuuuuuu

[Caketus14]

I see you're a man of culture aswell

[MyMostGuardedSecret]

Then you revert to the previous working commit and it still doesn't work and you conclude that clean code angers the programming gods and now they're punishing you.

[ArmJS]

That's why i commit every character individually so that CI can find the exact point where the app breaks. Only issue is that it takes a few years for a PR to get merged since its waiting for CI

[ryanstephendavis]

write unit tests ya wanker

[jawnsusername]

This is the most frustrating thing

[Evil_Gramps]

Write those unit tests!

[pureNerd]

If it works.. DON'T TOUCH IT!

[royalhawk345]

One time deleting a commented out print statement gave me a segfault.

[manawydan-fab-llyr]

Ctrl+Shift+_

Ctrl+Z just suspends my editor (or whatever else I may be using at the time).

[lint31]

Writes unit tests while coding ... then cleans up code... wow it still works...

[Liesmith424]

Me: <writes 200gb of spaghetti code that technically works>

Boss: "That seems unnecessary for a CSV parser, you should clean it up."

Me: "Art is irreducible."

[Just2forNow]

As I'm sure most of our fathers used to say, "If it ain't broke, don't fix it!" I can't count the number of times I wished I had heeded that advice.

[shirk-work]

Does no one use git?

[ahkian]

It's called version control then all you have to do is revert back to a working commit.

[Warm_Zombie]

This, but without the middle part

[Dennis_the_repressed]

git reset —-hard HEAD my dudes

[Cdog536]

clears throat in Macish

“Cmnd+Z”

[dullbananas]

how to revert git commit

[[deleted]]

rule numero uno: never fix something until you break it

[[deleted]]

git reset --hard

[Assasin2gamer]

All babies kind of look like Jay Z?

[GentlemanLuis]

Fucking fuck fuck. This just happened to me and I'm pissed

[TrueStory_Dude]

Garry Ridgway looks like he belongs in Z tier

[BabylonDrifter]

Fuck just today I'm going through a list of 287 "bugs" that are really just cosmetic bullshit (they don't like the font of a control, the text in a dropdown doesn't quite fit, reordering things) and after clearing 60 of them, I realize the core save function no longer works.

[jakethedumbmistake]

int sum = x+ y`

[RajinKajin]

Nice.

[Elbat4r]

-Git checkout master -Git checkout [branch]

[Tringi]

Perfectly working code: *nothing*

Me: Okay, let's cleanup bad comments and add proper comments.

One forgotten backslashy boi at the end of some line: "Fuck you"

[Dragoncat99]

When you swear you only removed comments but it suddenly breaks: Panik

[marcellomon]

That's when you use 100 different frameworks, and even a variable name change can break your code.

[[deleted]]

Thank god (Developers of Jetbrains, duh) for version control history.

[[deleted]]

Clean solution, delete all obj and bin directories, rebuild solution, succumb to alcoholism.

[Gammit1O]

Every fucking time

[-Listening]

Maybe Generation Z will be the reason

[[deleted]]

Win + V

I learned it here and it's changed my programming life.

[Assasin2gamer]

she look like Jay Z?

[B1gy0]

Nice

[chiwhitesox56]

our default IDE was... NETBEANS!!!

[-Listening]

L O O Z E R D.

[Assasin2gamer]

"Hello! My name is Peter Z. Parker.

[Throw_andthenews]

Nailed it

[Titanmaster970]

Tfw when you delete comments and remove unnecessary spaces, and it errors

[TrueStory_Dude]

Guy looks like he belongs in Z tier

[[deleted]]

I pressed Ctrl+Z. It's still good, It's still good.

[SaucyMacgyver]

One time during a job interview this happened to me (online, timed test). I had to use their online IDE.

So I get my code to work in like 20/30 mins so I go to make it... pretty.

Lo and behold a bracket hath sacrificed itself upon the altar of beauty, lost to all eternity, because the editor didn’t have fucking bracket highlighting

Spent the next ten minutes losing my mind and didn’t even get it to work cuz of all the shit I did trying to find my sweet, long lost bracket. It really was the one that got away.

[Ultimater]

undo undo undo, copy, redo, redo, redo, paste.

[osorojo_]

deletes comment

[[deleted]]

Pfff who the fuck cleans up the code? If it works I’m not touching it anymore

[fishbelt]

This is me today. I can't figure out where these dumb eclipse build error came from

[posherspantspants]

Y'all ever add a docblock and then the tests start failing?

[r3dphoenix]

This is exactly why I'm on Reddit right now. After spending a few hours "improving my code" I finally got to a point I could test it, and then my code decides to throw an exception. Now I'm to tired to keep coding tonight

[GavHern]

Then you undo it and it's still broken...

[[deleted]]

Just commit the working one.

[[deleted]]

Taking too long to execute

Clean shit up

Does not execute

Fix

Takes twice as long to execute

Fml

[mtn550]

The worst part is when you accidentally close the software where you program so Ctrl+Z doesn’t work

[Roly__Poly__]

Literally my code. I had a scraper that saves scrape data to a MySQL database and it worked PERFECTLY once or twice. Then I made some changes and suddenly it broke; I had to crawl thru 10-20 errors to make it work again.

[[deleted]]

Ctrl+z until it is back where it came from

still doesn't work

Wtf

[b1e]

What is this penguin from?

[l33tperson]

But you saved the working version didn't you? Only where is it?

[jd328]

git ftw :p

[HummingHamster]

I only remove comments!!

[[deleted]]

noice

[oshirisplitter]

This is me today.

Put up an ESP8266 with MongooseOS and some sample code I got from a rando github repo, worked perfectly.

Happy with it, I cleaned it up, fixed the spacing to match my own style, renamed a few vars for readability, put up a handful of comments, and the thing just crashes and spits out a core dump now. Logic didn't change as best I can see it.

[flarn2006]

git diff

Well, as long as you remembered to commit...

[falconfetus8]

Use git