[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
▼ Settings Mobile Home
4chan
/g/ - Technology


Thread archived.
You cannot reply anymore.




File: 1793278837513000.png (61 KB, 600x535)
61 KB PNG
Do you commit your code at once or split it between several commits to make it look like you've been working hard?
>>
>>110193549
I do not commit. Why would I share anything I make with a bunch of ungrateful entitled losers I don't even know? My projects are mine and they are for me. Nobody else can use them. Ha. Ha. Ha!
>>
>your code
laugh out loud (lol)
>>
haven't written code professionally since before AI so even my dumb anecdotes are out of date but I used to wait until I accumulated a critical mass of changes that made the mandated code review a lgtm rubberstamp. never did learn my lesson
>>
>>110193876
Okay, claude's or chatgpt's code
>>110193585
But you won't get paid this way
>>
you make feature branches, incrimentally add to the feature in multiple commits until the full project builds, and then you merge. this has been known since vcs was a thing.
>>
File: Real programmer.png (47 KB, 1361x277)
47 KB PNG
>>110193549
>>
>>110193549
I do small commits for myself. It's so easy to just hack around then and do git reset --hard if you fucked up a step
>>
>>110193549
I “work” from home on friday and I never do any actual work at home so I put off my last commit on thursday until friday to make it look like I did something friday.
>>
>>110193549
Please, for the love of God, split your commits. And stop throwing 100+ file PRs right before a sprint ends. If you completed four tickets, at least 4 commits and 4 PRs.
>>
File: gc.jpg (22 KB, 1200x600)
22 KB JPG
I don't use version control.
>>
Whenever I finished a feature or functionality, so I can rollback before I added it. The issue with splitting commits too much is that you have to be sure that you really want it to be be that way, I don't want to commit stuff that won't stick around long-term in my program, so it has to be something finished and something working that I can be sure is here to stay.
>>
File: mf.gif (139 KB, 500x889)
139 KB GIF
>>110194035
I don't write code.
>>
>>110193941
I am employed so it's alright
>>
>>110194114
I don't write. I dictated this to my personal assistant.
Candi honey, attach the chicken fried Ukraine invasion picture. You know the one. Thanks babe.
>>
>>110193549
I let claude commit
>>
File: 1772151418836371.jpg (9 KB, 222x216)
9 KB JPG
>>110194035
Version control? More like virgin control #gotem
>>
>>110194175
What about co-authored by, though?
>>
>>110193549
I only commit before I change something major. The rest of the time I forget or don't care.
>>
>>110193549
I used to split changes into more or less self contained pieces of work, because it was easier to search for bugs with git bisect and trace what was done and when. Now I don't give a shit, because Eeee-Aiiii will take care of it either way.
BTC
bc1qtm4rep7kyp2p28hlkfktpnd0j7uew47vnt2mev
LTC
ltc1q9xlaysse0mpfwf025esd69kt9zu3md22gh23du
ETH
0x6abA18D203520c8F90ca63eE7426a7bC345D98e6
SOL
E5ekoiauCR8yiNp451dmuPzhUxo84P5x3m9WJBK5kxZe
XRP
r3jYXNdMk2Vz5hXhKCKE9re8uz93JQFG1r
DOGE
DSBq5jRWkiwmEh1G7zBwmQDgRkvRr61fmb
XMR
85CTwq5wGjWZw5GgzgwZPrHyZxpLXMK5oZSSSk5j4x9w1bpqzisaWAUZYaAPfh6rP2MZJcaFqF1XmEzkw6YCqJSS2Txu6Z8




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.