Eddy Luten

Is typing

Archive

Common Tags

OpenGL id idTech Win32 XNA Games Visual Basic AI Netherlands Google DirectX Intel Programming Microsoft JavaScript C Whatever Apple Zune Tutorial TTRPG NVIDIA Books MkDocs MSDN AMD AJAX Update .NET WebGL Visual Studio Windows Linux C-Sharp

1 minute read

If you work in a source controlled environment, these are the minimal guidelines that you’ll have to stick to for making your teammates’ lives a bit easier.

  1. Don’t Check-In Broken Code: More than often, you’ll pull down the latest version of a project from your repository only to find that the code won’t build. Please, don’t check-in code to the main project that doesn’t compile, even if you intend to pick up the slack the next day. However:
  2. Don’t Go Home Without a Check-In: Even though you shouldn’t check-in your broken code to the main branch, many source control systems have a way to branch a user’s changes and merge them back later. If you’re using Team Foundation Server, take a look at Shelve Sets.
  3. Use Check-In Comments: Always leave a descriptive comment of the work you’ve done when your check-in. Your teammates weren’t hired to analyze undocumented code, so that 500-line change across multiple files better have a comment.
  4. Check-In Association: If your source control system allows this type of integration, associate your check-in with a work item, bug, or help-desk ticket. If it does not, at least make a reference to the work item’s identifier in the comment section.
  5. Use Check-In Policies: Use check-in policies to ensure that all of the above things aren’t impeding your build if your source control system supports them. These policies make your life easier and disallow sneaky developers from checking-in their broken spaghetti code.

Share any tips you may have!

You may also enjoy

How I Track Tasks and Take Notes

4 minute read

A bunch of notebooks

I’ve been keeping track of my notes and daily tasks using a single method for over a decade, and it works pretty well for me. Someone close to me asked me how I keep track of everything without losing track, so I figured I’d outline it here. The system is easy to use and relatively loose but with enough structure to be consistent.

Read 849 more words...

Foundry VTT on DigitalOcean with SSL and PM2

9 minute read

Foundry Virtual Tabletop Screenshot

I absolutely LOVE Foundry Virtual Tabletop (FoundryVTT). It is by far the best $50 I’ve spent on my tabletop role-playing hobby in years. I can gush about the software on and on, and perhaps I will in a future post. This post, however, focuses on something a bit more practical.

For years, I’ve hosted my instance on AWS, but with the change to their public IP address pricing, it doesn’t make sense to stay with them since DigitalOcean offers a beefier solution at a lower monthly cost.

Read 1,765 more words...

Creating and Publishing a Bluesky Feed

9 minute read

Bluesky terminal feed output

I was recently invited to join Bluesky, a new social media platform. This was mostly motivated by the nightmare that Twitter has become over the past year or so. One of Bluesky’s nice features is the encouragement from the official team to build supplementary software. One way to do it is to build a custom feed. So, I set out to do just that: I built a feed that serves all posts related to TTRPGs on Bluesky. Here’s how I went about publishing mine on a DigitalOcean droplet using PM2, Nginx, and Let’s Encrypt.

Read 1,768 more words...