Become a professional, then you’ll commit every time you make a small bit of functionality. If you’re doing massive changes like this, you haven’t broken something after multiple days of code enough. When you do that and you have no idea what you broke it with and when, it conditions you towards small iterable chunks.
I learned this the hard way, I forgot to commit for a single day and got burned really bad when my regression tests failed and I could not trace the issue(it is called source control for a reason). I declared it was more efficient to revert back to the last commit than spend time fixing broken code that I had no fucking clue where it was and the only thing I had to go by was that it happened between two commits with a whole work day between.
I work a lot with the local history of the IDE, where I can also set labels to a current state. In addition, it creates its own labels like last time all tests were green etc.
Still, in one of my last project that really lived TDD, they made a good point that I should just push as often as I label, since that also triggers all sorts of other tests which I usually don’t run locally, or not as often.
I had “rearrange code” checked once for a commit, and fortunately, it had automatically saved the exact state before that.
This. Instead of making commits time-based (for example once per hour or once per day), make them purpose-based (say, add a database migration in one commit, and change the color of a button in another one). This also makes it easy to cherry-pick or otherwise backport specific changes to different program versions gor example.
The only people I know who actually call it ess queue ell are either too new to know the “sequel” pronunciation, or the type of person you generally smell before you see.
Here in Germany everyone I know pronounces the letters individually – as German letters that is, which means the Q is pronounced “coo” rather than “cue”. I don’t mind it, it’s not quite as clunky as in English.
I say ess cue ell for the sake of uniformity because it’s not Mysequel nor Postgresequel and the language changed from Sequel to the acronym SQL in the 70s so not really in the “too new” ballpark anymore.
I think those make sense as deviations. I’ve heard “my sequel” but you’re absolutely right about postgresql.
The name is kinda irrelevant like hard vs soft g in gif. People know what you mean when you say either.
But in that same vein, the creator of the “graphics interchange format” says the pronunciation is soft g, but basically everyone says hard g… So “official” pronunciation is kinda irrelevant.
I don’t judge anyone who uses whichever term they want, but I’ve just noticed the general trend in my smallish interaction bubble.
I’m neither, I refuse to pronounce acronyms if it doesn’t make sense to do so.
Same thing with ‘gooey’ for GUI, except I hate that even more because that straight up elicits feelings of disgust, I don’t want anything gooey anywhere near any electronics
With the new AI integration, you can get smart isEven results that return the correct answer 90% of the time and a more creative solution 20% of the time.
How many widgets have we transferred to acme this year?
Simple enough question right?
But then when you look at the data, each region works with acme’s local offices differently. Some transfer using one method, some offices mark the transfer in the system as “other firm”. Oh, and we don’t even get a data feed from the north west region because they still haven’t upgraded their shit so I can request a spreadsheet but it’s in a different format than everything else.
Then inevitably Acme has a different number of widgets that have been transfered. Because if a transfer gets kicked back or cancelled, it’s easier to just create a new transfer rather than go fix an old one because that process is laborious and requires tons of approvals so they just create a new transfer and send it over.
But yea, 20 minutes should be enough time to get you that before your meeting with Acme.
Legislation (which feels similar to programming languages sometimes) seems to have some keywords of its own. I remember seeing a lot of Whereas … and Having regard to ….
Also, if I rewind to the Neolithic and I see a bunch of cavemen, sabertooth tigers and a Schwinn chained to a bike rack, I’m not going to just fast forward from there. I have other questions.
If you have a common folder that you clone projects to (like OP’s ~/coding), then that checkbox lets you trust that whole folder easily when this pop up comes up.
I have a coding folder “repos”. It’s on a remote machine though and I get this every time I connect to my code folder using a new remote host. So annoying!
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.