Confessions of a Programmer

#1
If a client is an unbearable asshole during the initial communication, I look for every excuse to pad on the hours for the estimate to get paid more. If a client goes above and beyond in their douchbaggery, I tack on an additional $40/hour.

#2
Sometimes I will present an elaborate solution to a client, but really I'm just reading off the features of a plugin or library I'm going to download or buy after the call. Not because I can't build it myself, but because I'd rather spend more time on other/my own projects.

#3
Clients assume because I know one language, I know them all. Rather than turning down the work, I take a crash course to work in that language, or outsource the work and clean it up afterwards, whichever is more practical at the time.

#4
I use cPanel on a dedicated to manage our client websites. I'm not paid enough to bother with setting up everything manually.

#5
Certain projects I build have a 3-day backdoor built into it. If the client doesn't pay upon completion, a unique hash triggered as a GET variable deletes a core file in my work, rendering the work useless. If it wasn't triggered by the 4th day, the file allowing me to trigger this backdoor is removed. This is only used for clients where the project must be launched on their servers, or if there has been a previous issue collecting payment.

#6
I slip in the initial contract that all preceeding phone calls will be monitored and recorded, and that they acknowledge the recordings are admissable in court. This has saved me from losing money twice now.

#7
I have never used an IDE. (I know, I know, it's really inefficient and dumb, but I'm just more comfortable with Sublime. Plus I often find myself mobile and without my computer, so I have to program from my phone.)

#8
Each day resembles a betting spectacle of which work will be late, which will be rushed out and which will never see the light of day.

#9
I have used "sick" and "family emergency" as an excuse to just sleep in far more than I can count.

#10
When a client from hell crosses over the line in their conduct (such as getting very nasty and personal, or sending threats), I anonymously report them to the BBB and on RipOffReport.

"Don't reinvent the wheel..." - I read it often, still I hate to use foreign code. It's not only that I do it for learning purposes. I just don't trust them. I want to keep the control, I want to understand my application and I want to be to blame when things fuck up.
I would probably through my laptop if my website gets hacked because of some fucking plugin or code I found somewhere on the internet.

So yes, I will invent the wheel new. At least I will spent some time to understand how this particular wheel is made, how it rolls and how I can improve it for my specific situation.

Sometimes my tires have some uncommon profile, but they fit to the stuff they are made for.

How do I don’t over complicate things?

Background: I’m currently working for a game with some base project. It alr has pretty complicated ai and some other system.

Today, I was asked by boss to help him set up a test environment for testing taking damage of a character.

First I tried to read up how the battle system and ai works in the base project. Figured, it’s overkill for this testing purpose.

Then, tried to use some plugin to automate the ai and movement. Make the enemy follow the target and stuff.

Alr spending half day, then suddenly realised all I need is just to make one script that takes damage on collision.

Why am I still a programmer? 😭

So I am getting back into game dev. I keep going back and forth about making a 2D or 3D rpg. Maybe I will end up making a mix.

I also want to make customizable characters in game. I found a decent solution for 2D. An artist is making 2D sprites that allow things to be overlaid. Each component has animations. I can layer sprites and animate them in sync to keep all the pieces moving together.

For 3D this journey of what is possible is a lot longer I think. It is hit or miss finding generic 3D characters with build in morphing. I want to be able to change the body for customization. I think I will have to relearn how to 3D model. As I learn what kind of model I need I am also learning what it takes to do this in Blender. And holy hell, Blender is so amazing now! The stuff I can do easily is staggering. You can sculpt a mesh using sculpting tools. Then do a remesh of that to make a more easily animateable mesh. No remeshing by hand, other than installing a plugin. There are a bunch of plugins that you can buy too. I found one for free that looks promising. But the paid ones are not that bad either. Between $25 to $100 depending upon source, license, and features.

However, being a programmer I want to figure out how to generate 3D and 2D models. There is code out there to do this, but I wonder what the learning curve is on that. The engineer side of me wants to be able to model the shape of humanoids and then auto skin that. I think I will start with modeling a few by hand to learn the way it should work. I want a simple anime look. I did find info on automating face rigs and body rigs. Oh the tools we have now!

Anyway, I am having fun.

Riddle me this

Client wants solution based on open source software.

Any additional software that I write (let's say, an offline store plugin for Feast feature store) to add missing functionality has to be closed source.

Fuck you. Intellectual property my ass. You and me wouldn't even have projects if it werent for OSS.

Good luck maintaining the plugin after I am gone.

I'm doing a lot of work and will have close to nothing to show to future employers.

(BTW, if it were for the old Microsoft model of code source, I would have never become a programmer of any sort. God bless OSS)

If there is anything worse than a bad, not willing to learn programmer is a so called plugin programmer.

Who only knows how to install plugin over plugin to do a simple task.

Just had to fix something on one websites (wp site, I know, just kill me) where the guy had like 25-30 plugins (some where disabled). And most of them were for adding new widget positions.

Hey guys!
Once again, I got a little stumped when writing one thingmajig in Python.

I am normally not a programmer (Work as sysadmin), so I don't really know all the fancy abstract ways things are done "properly", which is why I need to ask here:

I have a program, separated into parts. The "core" is a part that sets commandline argument structure (using the argparse library), loads master configuration file, sets up the main logging facility, and then proceeds to load "plugins" - python files with one or more classes that implement one specific abstract class that forces them to implement a common interface of init, run, cleanup functions.

The core then proceeds to initialize those classes, run the "run" function, and run the "cleanup" function.

If the plugin class throws a Warning, it is only logged and runtime continues. If it is anything else, the program logs it and stops.

Now, the issue is, sometimes, a user may want to continue even if a non-warning occurs.

Lets say that I am creating a user, and the user already exists. Sometimes, the program user might want to continue with further plugin execution. And what I was told was to implement specific commandline switches that force continuation of runtime despite the plugin failing.

How should I implement it? The most obvious thing is to add a specific switch for every plugin, but that is exactly what I am trying to evade. I want to have the core as abstract as possible.

Other solution I thought of is to have a file of some sort that would list extra switches to implement, then it would be up to the class to implement if it uses the switch or not (I pretty much pass the entire Namespace received from parse_args() function), but this also feels kinda hackish.

I thought about having some sort of function that the plugin could call in the core to add a new argument, but at the point that plugins start loading, the argument parser is already compiled and cannot be changed further.

Any other ideas of how to re-implement the program are also welcome! I may not do it this times, but I'd at least learn something new again.