@wallhackio i’ve heard you talk shit about your own skills befur after noticing you missed some abstractions while writing choice that would have made your code simpler and better but the fact that you bothered to actually change the code later is to me the actual marker of good purrogramming
@aescling @wallhackio i mean, still probably wise to not write code after midnight, in the vein of devils coffee
@Satsuma @wallhackio true, i’ve had some terrible murrnyawns after
@wallhackio @aescling definitely don’t write code for work after midnight
@Satsuma @aescling @wallhackio Broadly I agree, but some of my better things have been written in a "okay, fine, we're doing this" stint that started somewhere around 8-9pm and may not have ended until 4am. To an extent it depends, I guess.
@wallhackio you don’t need to write S-tier code on your furst attempt. truly good purrogrammers are the ones who review their own shit after the fact and make the effurt to change it fur the better