Easy FullSail
Programmers vs admins vs dbas vs security folks - one answer - learn to do it all.
End of story.
You created a thread whining about DBAs, you fucking baby. Might want to take a look inward.Easy FullSail
I'd like too, but I'm hanging on because it's a 6 figure salary with the medical benefits. That day will eventually come.Just fucking retire already.
gr8 wyte trash cuckthred juggernaught ya fukn pussyass disgr8c 2 ya own race frenz n famly dat betta off ded 2 smdh lol
Mostly custom.Ngfm what project methodology does your company use?
I'd like too, but I'm hanging on because it's a 6 figure salary with the medical benefits. That day will eventually come.
At first I didn't mind the Mr. Dementia because we thought he would eventually code, but that didn't happen. Others were telling me being the manager was a PITA, so I resigned myself to not getting it. But now I'm totally pissed, especially playing the game of status update. It's goes like this.
Manager: What are you working on?
Me: This program, that program, new file, process.
Manager: When will it be done?
Me: A week.
Manager: Can you send me an e-mail of how it all works? ( I don't send an e-mail)
Manager next day: What was it you were working on again? (Dementia, doesn't remember)
Me: This program, that program.
Manager: Oh yeah, can you tell me how long it will take?
Me: A week.
And when you finish, it all starts over again. What gets me is when you do something really good, solve a complicated problem, they don't care. It's back to "when will it be done?" It's the same robotic conversation over and over when the manager isn't in the trenches with the programmers. I actually do less work now because of this cycle.
The biggest problem is the 'project manager'. She is a DBA with 0 technical skills that has apparently never headed up any project, and she's turned what was essentially a minor firewall issue into a full migration thats not going to fix the issue and has attracted the attention of management.
So, waterfallMostly custom.
We have 3 BAs (Business Analysts). Requests come from the users to a help desk system (custom written in a web language). The BAs see the tickets, assign them to programmers. From the HD (help desk) ticket, we create a work order in our Pick system and program against it logging our time in a custom written log system. Once the coding is done, we write up a QA (Quality Assurance), close the work order, move it to QA status in the HD system. One of the other programmers does the QA (testing the code), the BA accepts this (they also test), and it moves back to the help desk department to patch to our live box and close the ticket. This design was influenced by Sarbanes Oxley rules from a few years ago. Back then we had auditors coming in all the time checking our procedures. We still do, but now we're a private company, so it's not as big of a deal.
i just found out i can only import 2048 mp3s at a time onto my 32gb jeep stereo.
so now i gotta put all the music on multiple sticks and wipe, restart ... ugh
1. Your writing needs to be more engaging with the readers. For example, What shape are her boobs? Are they firm? Do they look firm? What does she smell like?
2. When writing blog try starting with a question? For example "Have you ever found an annoying bitch at work really sexy?"
why not just put all your music on one stick and leave it plugged in?
Rent a car, try for an upgrade that has Sirius/XM radio (usually on the full size cars). Then you can channel surf and the signal doesn't go out (unless you pass under a bridge) because it's satellite.long road trip coming soon.
gr8 wyte trash cuckthred juggernaught ya fukn pussyass disgr8c 2 ya own race frenz n famly dat betta off ded 2 smdh lol