Reputation
782
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
7 10
Newest
 Yearling
Impact
~52k people reached

Jun
4
comment How do you tell if advice from a senior developer is bad?
@Dave Kaye - the OP says specifically the senior developer is supposed to be mentoring him. This isn't about the general obligations of senior developers to their juniors but the apparent specific obligation of one senior developer to a junior.
Sep
22
awarded  Yearling
Aug
12
comment Safely fixing production database data
@AndrewWhite - frankly, having it be a non-trivial process would seem to be a plus to me. Everyone will be aware of the cost and risk as opposed to the "well, we've done it 23 times before without problems" blase-ness I've seen in a number of places.
Jun
27
answered Secure an Application/Software by expiration with Date?
Apr
17
revised TFS SQL Deployment Data Script
correct product names
Apr
17
suggested approved edit on TFS SQL Deployment Data Script
Apr
16
comment TFS SQL Deployment Data Script
<minor quibble> 'SQL' is a query language standard, 'SQL Server 2005' is a particular database product.
Apr
5
comment Securely storing secret data in a client-side web application
^this. How "secret" is the secret data, and how much time and money is protecting it actually worth? "Industry standard" efforts might be sufficient.
Feb
9
awarded  Autobiographer
Jan
30
comment Name for a bug that disappears when someone else looks at it
To be clear - you might actually be crazy, just not about this bug.
Jan
22
comment Getting non-programmers to understand the development process
@mri - Anyone who's actually built a factory will tell you that no matter how well designed factory machinery is, parts of it will still have to be fit by hand. Our tools may simplify the hand-fitting, but we're no longer (most of us) 'crafting' Assembly code to take advantage of cycles and memory boundaries. Much like the beautiful "hand made" Craftsman-style furniture benefited from the automation of its day.
Jan
18
comment Shorter release cycle with DVCS
+1 @James. My group was used to "release breaks", or "code freezes", when we used a seriously out-of-date version of PVCS. We've moved to TFS (most definitely not a DVCS) and use branches, not "breaks", to stabilise releases. It's hard to break the devs of thinking about a "code freeze" for each release, though.
Nov
7
comment Why does Java use UTF-16 for internal string representation?
@rogerdpack: see en.wikipedia.org/wiki/UCS-2
Oct
23
comment Assembly Language being used in Aircraft System
@JörgWMittag: a UAV might be able to kill people by other methods, but the 'U' means a failure of flight control means it isn't immediately jeopardizing human life. The Java license says it isn't suitable for mission-critical systems, but that doesn't prevent anyone from making that choice.
Oct
1
comment Dealing with selfish team member(s)
Our company splits the bonus basing like so: 30% based on company performance, 50% based on our group, 20% based on the other groups. This makes it more important for the groups to succeed, not for individuals to try to outshine each other. Meeting annual personal goals set by ourselves affects how much our individual total bonus might be, but if I do one or a dozen stories more than someone else that helps our group rating but doesn't push me ahead of anyone else.
Sep
22
awarded  Yearling
Sep
11
comment How to communicate within a company what is being Continually Deployed
@FrancisSpor, it sounds like your development folks like CD but you haven't done a good job of selling it to the rest of your organization. People supporting things in production like stability & predictability. IMO you should consider adding a QA/staging layer like Ryathal mentions, deploy as you do now to that and publish notices like you do now, then deploy QA/staging to production say once a day.
Aug
1
comment Storing plaintext passwords for detecting fraud
@inquam "rigorous internal security plan"? Try "No ... plan survives first contact with the enemy".
Aug
1
comment Storing plaintext passwords for detecting fraud
"never have a security breach" is one damn big bet.
Jul
17
comment Is there something wrong with how we're doing version control?
And they can still make a version branch in TFS based on the v2.0 build datetime.