Often when I work on an issue I make a git branch "issue-1",...

Often when I work on an issue I make a git branch "issue-1", make a total mess and finally I make another branch "issue-2", take the learnings from "issue-1" and fix the issue with minimal changes.

Like 2 Dec 2022 at 14:46 | Open on mastodon.social

6 comments

Evergreen Toot fka Chip Butty

@borkdude so what you are saying is that you really write more code than we initially thought?

2 Dec 2022 at 14:48 | Open on functional.cafe

(λ. borkdude)

@otfrom OMG, you got me, still way too much code ;)

2 Dec 2022 at 14:53 | Open on mastodon.social

Evergreen Toot fka Chip Butty

@borkdude if you had more time you'd be more concise? :blobcatfearful:

2 Dec 2022 at 14:54 | Open on functional.cafe

keithmantell

@otfrom @borkdude Parkinson Law for Programming ? No. Actually the "Mark Twain" law

2 Dec 2022 at 16:16 | Open on mastodon.me.uk

keithmantell

@otfrom @borkdude (I should stop typing this afternoon) "Sorry I wrote such a long letter, I didn't have time to write a short one"

2 Dec 2022 at 16:19 | Open on mastodon.me.uk

LouD

@borkdude I usually forget to even make branches. I create a file and write my tests in there and with Calva and Clojure repl just execute my code scribbles 😁

2 Dec 2022 at 17:38 | Open on mastodon.social

Go Up