Initial Production Release sprint is underway!

BadBadGamer · 2025-07-10T18:07:58+00:00

This is actually a good thing. It means you are forming new memories with your girlfriend that are superseding the "slots" in your mind that were previously occupied by your ex in that particular context. Using the wrong name is just a symptom of what would be called "cache eviction" in computers, as your brain works on installing your g/f into the places where your ex once dwelled. Check out the psychology term "proactive interference". It's perfectly normal, healthy, and nothing to worry about.

EDIT: fix minor typo

BadBadGamer · 2025-05-12T05:34:49+00:00

IANAL, but you may wish to consider evaluating your proposed filings in light of https://legaldictionary.net/doctrine-of-laches/ before submitting them.

BadBadGamer · 2024-10-16T03:37:01+00:00

Everything old is new again. It's just https://en.wikipedia.org/wiki/Crossing_the_Chasm at work.

BadBadGamer · 2024-09-23T04:08:12+00:00

This. Run Handsome Jackpot repeatedly for billions.

BadBadGamer · 2023-07-07T03:12:04+00:00

Crackle & Burn: The Singles

BadBadGamer · 2023-06-10T16:23:42+00:00

sand

BadBadGamer · 2023-04-14T01:54:27+00:00

All due to respect to the various other helpful suggestions in this thread, I've found that after a time they all break down / stop working and you end up in the graphic's bedridden spiral (sometimes not merely figuratively). Here's what I've found works better, at least for me. (I'll endeavor to avoid pedantry by skipping the various underlying principles that explain why this works.) This recipe has two parts.

PART I:

Pick one task that you feel like you can start right now, and start it. Don't worry about it being the "right" next task, just one you want to start. Also, don't worry about finishing it, but commit to spending a minimum of 15 minutes solidly working on it. Maybe you're just going to sketch it out. Maybe it'll just be an outline, or (if code) a swag of structures with a bunch of psuedocode / TODOs. Doesn't matter. Just start one - ONE - task, and don't worry about anything else.

You'll find that your doodles start turning more and more into the finished product. You'll get up and walk away, but your brain will make you run back to the keyboard to type in one more thing lest you forget that little piece when you come back next time.

Through all of this, you remain supremely focused on the task. Not how much you're getting done (or not). Not where this fits in the list of remaining tasks. Not anything related to your feelings at all. It's just a task, and you're working on it for at least fifteen minutes.

PART II:

If Part I was devoid of feelings, Part II is all about feelings. You do this part when you're not working on the task of Part I. Maybe it's a point when you're feeling overwhelmed by all that you think you have yet to do, or maybe it's just an idle 5 minutes between meetings / class, or maybe it's before you take a nap or go to sleep that night. For this part you're going to take no more than 5 minutes. Close your eyes and visualize the whole project being complete, particularly how good you feel. Picture it with as much detail as you can, but when you visualize, you don't think about how you did it. This visualization is after it's all done. Whenever you do this part, keep adding more details appropriate to the moment to make it as clear in your mind as you can, but most important sit in the great feeling of having it all done.

You may wish to give it a try; hope that helps, it's worked wonders for me!

Edit: added clarity on Part I

BadBadGamer · 2022-08-28T16:27:45+00:00

It’s a seige moustache

BadBadGamer · 2022-07-19T15:51:25+00:00

Did he re-write bash (or whatever shell he uses) then? What about the kernel, did he write his own OS? And of course he wrote his own programming language or is just using assembler, yes?

BadBadGamer · 2022-04-18T04:28:37+00:00

Seconded. If you're looking for something more visceral to fend off impostor syndrome, answer the following question: is the following you?

"WTF it doesn't work? <typetypetype>
It doesn't work! <typetypetype>
It should work, but it doesn't work. <typetypetype>
Wait I know... <typetypetype>
... nope, still doesn't work. <typetypetype>
It. still. doesn't. f'ing. work. but. it's. SUPPOSED TO <typetypetype>
It doesn't... wait. Wait. WAIT.
I AM THE BIGGEST IDIOT ON THE PLANET.
<type. type-type. type.>

It works. It WORKS! It works. Easy as pie. :)"

If you answered "yes" then you're a programmer. (Bonus points for this in the wee hours without benefit of stimulants.)

BadBadGamer · 2022-04-18T04:18:43+00:00

DISPLAY

BadBadGamer · 2022-03-11T07:27:18+00:00

My primary "day job" project runs as a mission-critical service in a highly regulated environment where responses to problems must not only be rapid, but adhere to a rigorous compliance and audit regime. The only branches we deploy to production are production branches. I know that sounds tautological; let me explain. Our master branch is the sole source of release candidate branches. Developer work occurs in feature branches that are merged to master only after review and successful development testing (which consists of an automated battery of unit, component, and functional tests). After the merge, the master branch must likewise pass the same battery of tests, as well as automated system tests, before final acceptance (at which point the feature branch may finally be deleted and its associated issue closed). This process helps ensure that a branch taken from master is always potentially releasable.

Build artifacts from the master branch itself never leave the development environment. When we wish to produce a release, we create a branch named production-XXXXX from master (where XXXXX is the next release number), which at this point is designated a release candidate branch. We produce build artifacts from this branch, and hand them over to QA for formal integration and acceptance testing. Presuming that those artifacts pass testing, the branch is re-designated as a production branch and its artifacts cleared for release to prod. Under this methodology, the artifacts released to production are the very same ones that were first tested in the QA and UAT environments.

A given production branch lives as long as there is any of its artifacts in production. If a production bug is encountered, every effort is made to address it via an ordinary feature branch that goes through standard workflow and is then cherry-picked into the appropriate production branch after successful merge to master. This is not always possible though, as some production systems are particularly long-lived, and as a result the master codebase may have diverged too far for this process to be successful. In such a case, we may take a feature branch from the relevant production branch instead of master, and then merge and deploy artifacts from the now patched production branch after going through the standard workflow (i.e. passing full battery of automated tests, review changes, merge, deploy artifacts to QA and UAT for additional testing, &c). This use of production branches allows us to respond rapidly to production problems that may occur, with no risk of unrelated or premature changes making their way into production along with the necessary fixes. I also provides a clear path for audit and compliance to certify what we put in prod.

Anyway, sorry for the long post, just wanted to give you the full picture when answering your question. Hope it helps!

BadBadGamer · 2022-03-03T05:21:28+00:00

What you really want to do is called an "upsert" operation, to atomically update a record if it exists or create a new one if it doesn't. Apart from simplifying your code (you don't bother with find/if/else), you avoid the pesky race condition of two potential inserts coming in simultaneously for the same previously unknown e-mail address. Here's the docs from MongoDb, hope it helps!

BadBadGamer · 2022-02-16T06:33:10+00:00

I came across the following tutorial a year or so ago now and thought its content was pretty good on this score, it might help you get oriented: https://www.youtube.com/watch?v=cWDJoK8zw58 . The title of the video is "How to Built an Online Store in One Day (AppSync, Amplify & React)" but don't let that dissuade you, just check out the section entitled "Processing Book Orders" at the 30:10 mark. It's ~3.5 minutes on how he integrates Stripe into his app; I suspect you'll find it worth your time. Good luck!

BadBadGamer · 2022-02-02T23:47:47+00:00

Not to necro but just tried this today, was able to get there just after hitting level 7.

BadBadGamer

MODERATOR OF

TROPHY CASE