Discovered one of the worst db designs ever:

- A cust is inserted in a table.
- The insert trigger is fired, calling a stored proc
- The stored proc being called creates a dynamic sql that builds a create table statement for 8 different tables. These tables will be postfixed with the newly-created cust id and is executed.

When querying info for a cust, a stored proc is used that accepts an id value would be appended to another dynamic sql that creates a select statement across all 8 tables for one customer.

Shoot me now.

Getting that feeling again where I want move to another job but can't because of bills.

Get a screenshot of your colleague's desktop screen with the taskbar in the bottom. Adjust the taskbar settings to hide and move it to the upper side of the screen. Watch as how your colleague bust a gut.

I'm at that point where I want to lash out at our team for not finishing a sprint. I've been doing the scrum master/dev role for months now and each sprint is incomplete since we have started the agile way.

Most of my team members are seasoned senior devs and my team's downfall are caused by not acting as a team. I'm the youngest in the team and have been acting as a babysitter for them.

Happy New Year to everybody!! Wishing you all the best for 2017! 😁😁😁

Happy holidays to everybody! Hope you all have a good one! :)

You know it sucks when you log in your PC first thing in the morning and have to wait for 1 hr before it gets to show your desktop whilst your energy automatically deflates.

I could kiss my productivity levels goodbye.

I just don't get people designing database tables using VARCHAR/VARCHAR2 for columns that have numeric values in them, then use them as row identifiers.

I simply don't.

It makes my blood boil when my colleagues (who have been here for ages) know that maintaining dependencies in code is important but don't even action it because they give the excuse of having no time or the pressure of finishing it on time.

It angers me that I'm now in .dll hell and they don't even consider the time or push a valid case to fix the issue. It also frustrates me as I've realised that they have grown complacent/indifferent, not even attempting to change it.

That debug moment where you have 50+ different vs.net web projects in one solution and each of the said web projects were set up using point-and-click web references, then realised that the developer who created it did not even bother to let people know that you need to run it all simultaneously and did not bother to use host names but instead used the http://localhost:<some-random-port> in IIS express.

Oh, just to rub salt in the wound, each project's programming code files jumps from a mix of vb.net to c# which is a complete waste of time and energy to do.

Whoopdee do. The debug task from hell.

Being dependent on people who are lazy to document but knows everything about the app you are working on is a pain in the neck. Have tried bugging them to do documentation, but no win... Grrrr.....