782 reputation
710
bio website realsoftwaresytems.com
location Los Angeles, CA
age 53
visits member for 3 years, 9 months
seen Jul 3 at 22:16

Been writing code since 1984 when I created mailing labels from a custom-built multiuser manufacturing system using Business Basic on a Quantel (Mohawk Data Sciences) 7-bit system with removable disk packs. (ever been around a chain printer when the chain comes off?)

Busy learning C#, installers and deployment idiosyncracies now.


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.
Aug
30
comment Is there any “Set” database?
@JohnS - I don't know exactly what you think is so unique about your 'sets', but it's almost guaranteed the basic problem you're trying to deal with has solutions in the "traditional" databases you dismiss so easily. My company's product, using bog-standard SQL Server, crosses & filters hundreds of millions or billions of raw data records with hundreds of thousands of reference elements. It's not real-time, but what kind of performance are you looking for with what data volumes?
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.
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.
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
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.
Jun
15
comment Centrally managing 100+ websites without bankrupting a small company
And if the shared db is in a cluster/failover setup, you don't need to worry much about database failure taking down the whole business.
Jun
12
comment I'm doing 90% maintenance and 10% development, is this normal?
@nicodemus13 - I also disagree with the attitude, but unfortunately acattle is probably right about it being the company's attitude.
Jun
11
comment Is it ok to replace optimized code with readable code?
Well, we're going to have to agree to disagree. Spending an hour changing something to save fractional seconds at runtime for a function that executes really occasionally and leaving the code in head-scratching shape for the other developers is ... not right. If these were functions that executed repeatedly in high-stress parts of the app, fine & dandy. But that's not the case I'm describing. This is truly gratuitous code finagling for no other reason than to say "I made this thing that UserX does once a week fractionally faster". In the meantime, we have paying work that needs doing.
Jun
11
comment Is it ok to replace optimized code with readable code?
They're done because he can. He actually usually saves some cycles, but when the user interaction with the program element takes some number of seconds (15 to 300-ish), shaving a tenth of a second of runtime in pursuit of "efficiency" is silly. Especially when the folks following him have to take real time to understand what he did. This is a PowerBuilder application originally built 16 years ago, so given the genesis of things the mindset is perhaps understandable, but he refuses to update his mindset to current reality.
Jun
11
comment Is it ok to replace optimized code with readable code?
One of the guys I work with now loves to optimise things in areas that the users hit once a month, if that often. It takes time and not-infrequently causes other problems because he likes to code-and-commit, and let QA or other downstream function actually test. :/ To be fair, he's generally fast, quick, and accurate, but these penny-ante "optimisations" just make things harder for the rest of the team and their permanent deaths would be a Good Thing.