|
Not technical lead, but management.
|
|
|
|
|
|
There's a difference in your shop?!? Lucky ruddy you!
N.B. The above expression of technical information and/or opinion shall not be construed as having anything to do with any previous, current, future or potential client; with competitors, successors and/or assigns of the same; nor with any organisation staffed exclusively by individuals each of whom posess at least two functioning brain cells.
N.N.B. The exceptions to the preceding disclaimer should be obvious, self-evident and not in any way identified by (and therefore actionable against) me. So there. 
|
|
|
|
|
Some people like hitting themselves on the head with a hammer. Others even enjoy hitting other people on the head with a hammer. This mental singularity obviously is one who innovates on the second group with a jackhammer.
Jeff Dickey
Seven Sigma Software and Services
Phone/SMS: +65 8333 4403
Yahoo! IM: jeff_dickey
MSN IM: jeff_dickey at hotmail.com
ICQ IM: 8053918
Skype: jeff_dickey
|
|
|
|
|
Can i categorize it with advice ?
http://www.wiltech-center.com
|
|
|
|
|
It's very useful debugging technique, especially in loops, although you can use "Breakpoint Conditions" for that matter:
for(int i=0;i<100;i++)
{
if(i==10)
i=i;
}
Mostly, when you see programmers, they aren't doing anything. One of the attractive things about programmers is that you cannot tell whether or not they are working simply by looking at them. Very often they're sitting there seemingly drinking coffee and gossiping, or just staring into space. What the programmer is trying to do is get a handle on all the individual and unrelated ideas that are scampering around in his head. (Charles M Strauss)
|
|
|
|
|
Mladen Jankovic wrote: It's very useful debugging technique, especially in loops, although you can use "Breakpoint Conditions" for that matter:
sometime I insert quick and crappy code for debugging purposes. But always I comment that portion as being a debug code and not to be included in production. I insert the comment in case I forgot to remove the code and some one may catch it.
Most of the time I use break point conditions
/* I can C */
// or !C
Yusuf
|
|
|
|
|
maybe too much:
drinkType == Whiskey
|
|
|
|
|
this could only be better with getter/setter methods!!
tbDrinkType.Text
{
get
{
return drinkType;
}
set
{
drinkType = value;
}
}
|
|
|
|
|
Management material. Why?
1. discussing what management likes to discuss most, drinking
2. In the way management communicats: repetition and redundancy
3. In the way management thinks: nonsensical
Marc
|
|
|
|
|
Can you explain the horror? At first I thought you were getting a value from a text box and putting it right back into the text box, but after closer inspection I see that isn't the case (assuming the language is case-sensitive).
|
|
|
|
|
David St. Hilaire wrote: Can you explain the horror? At first I thought you were getting a value from a text box and putting it right back into the text box, but after closer inspection I see that isn't the case (assuming the language is case-sensitive).
then what else is the code doing. The only exception is when the text in the TextBox is empty
Yusuf
|
|
|
|
|
The person who wrote this is simply checking if the text in the textbox is empty.
a simple:
<br />
if (tbDrinkType.Text == "")<br />
{<br />
}<br />
would have been quite satisfactory. 
|
|
|
|
|
I worked for a company once where we were developing a website where the powers that be wanted the site to be ultra secure. For whatever reason, they decided to go with a secuirty option offered by a company I'll just call SecuriCorp. SecuriCorp specialized in using a dongle with your website to authenticate. There are no user names, no passwords. I wasn't on the project, but heard all about it since it was the biggest project in the company. Each dongle had hardware set 6 digit keys and every time you pressed a button the next key would come up. The software knew what keys each dongle had and in what order they would appear. Once you logged in with a key, you couldn't use that key or any of the other keys on that dongle (thus eliminating dongle sharing). It seemed like a great idea, until one of the software architects for the project started to look in to how SecriCorp's security model worked. (Coincidentally, this architect was dubbed the "Dongle Doctor")
Their ultra security was setting a plaintext cookie named "Auth" with the value "true" Needless to say, the s$%# hit the fan. From that day on, any time on any project if you talked about security, someone would say "Just set Auth to true." When I left the company shortly after that, they were still in the midst of fighting with SecuriCorp to fix their "security" model.
Broken Bokken
http://www.brokenbokken.com
modified on Thursday, April 17, 2008 9:28 AM
|
|
|
|
|
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
|
The dongle thing is a standard security system. It was implemenred badly- implementation flaw.
|
|
|
|
|
I thought the idea of a dongle for the login was great, but you are right, it was a bad implementation. As a standard at that company, all our cookies were encrypted using Triple DES. It's just sad to see that much money put into a solution less secure than the one we already had working. 
Broken Bokken
You can't carry out a ninja-style assasination dressed as an astronaut. It's the luminous fabric; too visible. - Tripod
http://www.brokenbokken.com
|
|
|
|
|
|
|
Did you know VB.NET has a WriteOnly property to make properties into /dev/nulls?  It even offers IntelliSense to remove the Get accessors!
CLR: Removes tough Java-based stains fast!
|
|
|
|
|
|
Who would use it? A coding horror in VB. And if you use it, it turns your code into a coding horror. 
CLR: Removes tough Java-based stains fast!
|
|
|
|
|
Did you also know VB is straight up just an ugly language?
VB itself is a coding horror.
|
|
|
|
|
This is the type of comment that only can be written by someone that doesnt know the language.
I work on c# but i worked on VB.Net a few years before. The two main diferences i noticed on the transition was that intelisence is a lot better on VB, and on vb i don't have to compile the code to see errors.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
