With the number of old-fashioned people at snoofle's WTF Inc. I'm surprised this memo actually got implemented - unless there's an underground printing black market going on in the company. This is probably one of the craziest WTFs I've seen from snoofle. Time to tell the chairman to work only by the light of your cellphone, snoofle.
OhNoDevelopment
@OhNoDevelopment
Best posts made by OhNoDevelopment
Latest posts made by OhNoDevelopment
-
RE: Cost Savings
-
RE: Make a decision already
This would not have been an issue at my company. We default everything to strings.
-
RE: It's a Safe Thing to Do
@bridget99 said:
@Mcoder said:
@OhNoDevelopment said:
At least you have FKs. Here, we don't use them because everyone thinks FKs are too hard to use. I think I'm starting to cry.
Around here the policy is to not use them either. As our leggacy code base gets bigger, I'm gathering arguments for using them, but I'm sure it'll take time.
What's the anti-FK argument? The only drawback I see is that they sometimes seem to get in the way during bulk data loads. That's easy to work around, though.
Two big anti-FK arguments here are:
- It's inconvenient
- We don't know how to delete data with FKs turned on
-
RE: It's a Safe Thing to Do
At least you have FKs. Here, we don't use them because everyone thinks FKs are too hard to use. I think I'm starting to cry.
-
RE: Let's open our MySql server to anyone!
Would you even want to download their software for free given how they handle the purchases?
-
RE: Electrify that server!
@Paddles said:
Wow, just wow. What is your employer's purpose? Manufacturing new and interesting layers of WTF?
This calls for a nickname for snoofle's company. The WTFactory? ProblemFactory?
-
RE: Hit with the stupid branch...
The lack of branching knowledge is a common wtf everywhere. I suspect no one knows how to branch correctly. Even I don't think I'm doing it right.
I recently pushed a "branching process" to my team. The process consists of working from a development branch and then merging it with head/trunk before release. I am relatively new to branching, so I hoped the much more senior devs on my team could share their wisdom. I assumed the reason no one was branching before was not due to lack of knowledge, but due to laziness or other behavioral reasons. It turns out no one even knew what branching was.
I insisted on the branching process in hopes everyone would learn how to branch properly. No one cared to learn, but instead blamed the process whenever a merging issue occurred. Now, I'm considering reverting my source control back to having no branches, since it seems to cause more headache than productivity for my team.
I was once told, "Enable smart people to do good work, and they will figure out the implementation details themselves." Either the statement is wrong, or my assumptions about my team are wrong.
-
RE: Legenderror'd
@Sutherlands said:
@OhNoDevelopment said:
League of Legends has made it somewhat easier so you do not need to control pets. For example, a pet will attack any unit you attack, but critics say there is not enough control with this scheme and the AIs are stupid.
Actually for those champions with pets, if you shift-right-click, it will move the pet or cause it to attack what you click on.Most pets you cannot control. As mentioned, Zyra's plants and Heimerdinger's turrets. Malzahar's voidling and Elise's spiders also come to mind.