how do you detail your commit messages
My commit message quality significantly varies depending on the project, issue, and language. If it's a big project that I'm near the beginning / middle of development on then I generally have decent commit messages. For smaller things like bugs or obvious features I tend to get lazier and lazier. The word count and variance of commit messages tends to plateau towards the end. You can see one of my
Java Projects for an example of some of what I would consider decent commit messages.
whats a normal programming flow for you
Considering how long it can take to apply changes, it is generally better to apply changes in batches. That of course is easier said than done, as some of your changes need to be applied in order to figure out what else you need to change. Regardless, I admittedly tend to rush into projects or issues. Usually this works out well, with me being able to quickly resolve or create features. Sometimes it goes horribly wrong, with me missing a core aspect of the project. But, usually, I'm able to quickly and cleanly write out code. It's always important to make sure you don't horrendously break something or make something that could be abused (
cough cough gang sql injection).
whats your directory structure like for a random project
My generic package/identifier is
xyz.msws
. For java or other languages that support packages I do my best to package like classes together. SourcePawn is a bit of a snowflake in that I have slowly grown to resent it. Directory structure tends to be all in one place with very minimal separation of files.
do you use tabs or spaces
I use an auto-indenter. If I ever do actually have to manually indent I
tend to use spaces purely because more often than not if I press tab it tabs to the next field in a web browser. But, if I am specifically in a good IDE I have the settings set so that TABS are replaced with spaces.
(i will fistfight you if you choose spaces)
TABS can be sus, stuff like YAML in Minecraft can instantly crash and stop something from working
you choose red team, have you ran any phishing campaigns
I would prefer to be on the red team, but I don't have any "official" experience with it.
have you done a pen test on the forums
My main concern is not currently on security. Considering my lack of experience with this type of development, I'm sure many other tech members would be more appropriate for this. Chances are there have already been people that figured out exploits (either on Tech or not), and I'm sure that Tech has done a few preventative tests.
what are your thoughts on log4shell
I think Log4Shell was bloated and didn't understand why so many applications used it. If I had known about Log4J's potential (in terms of downloading stuff from URLs) then I definitely would be curious. I personally didn't mess around with Log4J much, with the majority of my experience coming from Minecraft. I think Log4Shell was a massive vulnerability, and I am glad that there was such a quick and appropriate reaction from the communities that I personally am in.
as a red teamer, what are your suggestions to keep scum like you out of my beautiful server rack
Know what you're doing. Sanitize user input. Know what data you're handling. Put cooldowns or timeouts on authentication systems. Configure your firewall, DNS, IPTables, etc. properly. Ask "your" community (StackOverflow, Spigot, etc.) about any potential security vulnerabilities. If you ever install something, know
what it does,
why you need it, and
how it will impact your software.