Anonymous Confessions from Programmers.
Pair programming in my new job has saved my confidence, sanity and belief in others.
I was working on a clients website last night. I was switching their websites onto Cloudflare so I could easily manage their DNS settings. They weren't very cooperative so they gave me access to their emails to reset their domain registrars password. No, I didn't look through their emails. However, later that night I opened up an incognito window to watch some porn. Forgetting that I logged into their google account in an incognito window, and they were still logged in, and their google search history was enabled.. I went to login to remove it, and just as I went to remove the items from the list my network relapsed, and I lost the session. The password has been changed.
Today I realized that the system I designed and built for my company, put 41 people out of jobs, leaving only 9. I feel both mortified and furious that I was never told about this fact.
Our company has written their own version of a Double. It's a List of Integers for the digits, a boolean for Positive or Negative and an Integer for the Exponent.
my company does not have a security policy. we store our passwords in plain text, and we don't have SSL on our servers.
The best part of my day is the 30 seconds I spend running my hands under hot water during one of my 2 five-minute breaks per day. It's the only time at the office I don't spend constantly looking over my shoulder, worrying about my increasingly uncertain future in this increasingly unviable startup founded to support an increasingly irrelevant industry.
It irks me so when I work hard to get the code good and right, then someone comes in and adds the smallest of additions and doesn't care to get the details right. Functionally it works though so I really can't complain because we're already behind schedule and just need to ship something already
My coworkers throw around the phrases "Object Oriented" and "Design Patterns" like they're going out of style, but they write the most disgusting antipattern bullshit full of static classes that work strictly via side effects on other classes... it's really led to me hating Java developers and the Java "community".
I have a colleague that starts complaining about whatever technology he is using when he gets stuck. He gets stuck all the time since he's terrible in problem solving, I'm not sure if he can solve anything. I stopped replying to him when he asks something.
Is there any documentation concerning CC's absolve/condemn choices? Often I want to absolve the author and condemn the practice.
My boss taught himself programming and now dictates incredibly dumb coding conventions. He learned about namespaces. Now our namespace is named "namespace". Functions are called "execute_this", "step1", "step2", "step3", etc.
I love low level technical stuff, like coding drivers, API, optimizing, reading the memory to understand issues, and so on...I also love to design elegant and (hopefully) great object architectures. But sincerely, I hate so much algorithms....I hate it so much that I usually dodge it and solve algorithm issues with architecture...Now I'm programming algorithm in C, and I hate it so much, and avoided it so much, that I feel clueless and almost unable to realize what I was asked to....
Being a father seriously impacts my performance. Family and the long commute take away all my mental energy. I feel mentally drained when I finally arrive to work. I was better when I didn't have things to think about other than work.
I feel my skill set is outdated but I don't know where to branch out to where it's most beneficial to my career.
I can't stand developers who change the framework, language or database more often than their underwear. Rather than become experts they are just monkeys who jump on the hipster bandwagon with all the other idiots.
TFS is a cheap toy. A steaming pile of garbage. Anyone who loves it is not a good developer in my books.
My boss had us remove all error handling form the system because it just "hid" errors. Now if someone submits invalid JSON to our servers they crash. That's our fault because if we had written it correctly it wouldn't crash. Riiiight.
A client has hired yet another web designer to redo their catalog web site. The new design has a page that will display catalog versions and their URIs within the company's internal network. I pointed out publishing privileged information such as internal URIs does not fall in the scope of best security practices. The response was the page will be "secret". Security by obscurity lives on.
I can't trust any other programmer. Even though they pass the interview with hard questions about KISS, DRY, SOLID, MVP, YAGNI, you name it, they still come in and repeatedly copy and paste brain dead shit all over the place.
The head of training at our company, the one who is in charge of making us into better information workers, sent out a slide deck this morning and told us to print it all out on paper to bring to the meeting this afternoon, and to bring our laptops.
I hate having to work with such a nasty codebase at work, so on my personal (open source) projects I am incredibly meticulous; every six months or so I go back over the entire codebase, and if something doesn't immediately make sense I rewrite it. I'll probably never finish any of them, but at least I stuck to my principles.
Once a Jenkins build is blue and sunny, it *must* stay that way. I fix any issues then delete lesser builds to avoid the clouds.
Inherited a codebase from an agency who outsources their development to Pakistan. Some of the worst code I've ever seen, unused variables, business logic in data access, unreachable code...the whole shebang. Thought just the codebase was bad, then I saw our source control is shared with their other clients with full read/write access. Logging is also performed to a publicly accessible MySQL instance, which is also shared between clients with full read/write access.
Sometimes I feel like they don't pay me enough to stand my workmates and this shitty job.
I am earning low salary despite my experience because I cannot sell myself well on the job interviews.
It's been so long that I work with winforms that I fear no one will want to hire me for web developing anymore.
My company hired a new frontend developer. He asked why the backend is on c# and not in .net?
Unless they only consist of simple algorithms, I think programming exams that don't let you actually run and test the program are bullshit. Sure, it's important to be able to trace your code, but it's a huge headache to check each and every line in case you missed a semicolon or parenthesis. And some things might work in theory but won't actually compile because of some stupid crap reason.
My new job has a junior programmer that tries to obstruct the software goals of management and replace them with his own ideas. Ah, to have left that life behind. What a fucking relief. Now I can finally focus on what I'm going to spend all this fucking money on.
I don't comment my code, but proceed to make it opensource.
Everything would be so much easier if I just somewhere in the UTC time zone... wherever that is.
whack_a_bool = lambda v: bool(v) and v not in ["0", "false", "False", "FALSE"]
When I can't get a refactoring scheduled I break the feature by starting the refactoring anyway and do the refactoring during the estimated time for fixing it.
Been coding poorly, and not on this site recently. Wondering if there's any correlation...
I am earning most of my income now retro-fitting websites we built a few years ago to now have responsive layouts. Of course some might say we should have made them responsive in the first place - after all, iphones aren't exactly recent. But why sell a jam donut when you can sell a plain donut and jam later! Of course, five years ago when I should have been taking notice of technology, I was still using tables for layouts, and ignoring deprecation warning in my PHP4 code, and leaving magic quotes runtime on the server! Today, I still don't own an android or iphone.
Our system is so filled with bugs, random errors, half-implemented features and hacked-together components that I seriously fear for the future of this company.
I've believe that many corporations are a breeding ground for incompetence
Here I am thinking I was behind the curve in C# world. Got a new job, and it turns out the senior developers don't know what SOLID really is (although they know what the acronym represents) . I feel so much better now.
I am terrified of disappointing people, so when I am tasked with something I don't understand very well I sit on it having panic attacks, creating awful code smells and wasting time. In reality, all I have to do is ask questions and everything works fine, but that always makes me feel like I'm proving to them that they're misplacing their trust. I am a competent developer when the pressure is off, but as soon as it's on the tears start flowing and nothing gets done.
Found out today after second day on job that we are using enterprise admin credentials in batch ETL processes that basically copies files from here to there and that the credentials are hard code in the source and is in a repository anyone can see. They did this to avoid dealing with pesky ACL's. It seems all the techs know this since they have told me we have access to everything, and they mean everything. The upside is I am now an enterprise admin. The downside is if I report it and make a big deal out of it they may shoot the messenger.
I tried using sed to emulate common command line tools, but grep, head, tail, etc. are so much easier to use, Mac BSD warts and all.
I am tasked with developing a web site for an openly bigoted politician. I'm gay. Let's see how this winds up.
Many programmers are too much about crossing the river and not enough about building the bridge.
My employer bought us a copy of Webstorm, but I never use it. I just can't give up ST3.
Forgive me father, for I have sinned. I got a call to update the front-end of a website. But as soon as I saw the back-end source code, I was horrified. It was filled with bugs and possible security exploits. I did my job as they asked me to, but never told them about those problems..