932 reputation
920
bio website sourcecontribute.com
location Canada
age 28
visits member for 4 years, 5 months
seen Apr 20 at 17:00

Application Developer, Django/Python, Ruby/Rails, Common Lisp, Scheme, Java


Apr
28
accepted how to convince team and project manager that post-launch deployments are okay for new features
Apr
28
comment how to convince team and project manager that post-launch deployments are okay for new features
@RossPatterson indeed, I checked and the project went over-budget (which is messed up considering we delivered on time and I don't think anyone clocked in overtime) ;p
Apr
25
comment how to convince team and project manager that post-launch deployments are okay for new features
@pdr that's a good call, we don't do any optimization on our projects ever and I missed the most obvious solution...you can indeed setup better indexing with django/python
Apr
25
revised how to convince team and project manager that post-launch deployments are okay for new features
added 149 characters in body
Apr
25
revised how to convince team and project manager that post-launch deployments are okay for new features
added 459 characters in body
Apr
25
comment how to convince team and project manager that post-launch deployments are okay for new features
there's a single server that's hosting the web, application and database servers. there's no perceived issue because the page load time isn't included as a metric for project success, just that we include X features by Y date. should I frame it as a problem or as a learning experience for myself or...?
Apr
25
suggested rejected edit on Should Agile teams deliver new features daily?
Apr
25
revised Effective Ways to Introduce Agile into the Workplace?
added link to the bozo explosion blog post, really useful
Apr
25
asked how to convince team and project manager that post-launch deployments are okay for new features
Apr
3
comment Does a developer really have to know build tools, classpath etc?
If the scope of your usage is small and well-defined I don't see a problem with not knowing the tools, but it will force you into dependence on a whole bunch of other people. It's just as easy to know your damn tools and much less annoying.
Mar
12
comment Are these good reasons for moving to Microsoft web development platform?
good answer, but it doesn't mention the fact that free/open source software makes you feel the warm fuzzies inside ;)
Mar
11
comment is down-casting always bad?
GeneralObject should be renamed to SerializableObject or something and its purpose will be clear. I don't think you need to add the getPerson and getPlace methods to the GeneralObject class, but it doesn't matter much. You know exactly what kinds of objects you're passing around, at some point they're going to be downcast. The LSP is violated only if you're thinking about the code in a particular way. If you want to substitute a Person for a Place, that's no good. if you want to substitute them when creating the message using the System API, that's okay.
Mar
11
comment is down-casting always bad?
@TomSquires don't really understand your comment.
Mar
11
comment In which order should I do comparisons?
Wouldn't readonly variables help to alleviate this issue sometimes?
Mar
11
answered is down-casting always bad?
Mar
11
comment is down-casting always bad?
Downcasting a pointer vs making a generic payload into a specific object are two different things. Are the services actually different processes that communicate or is it all within the same program?
Mar
11
comment Extreme Programming Daily Commits
@BrianKnoblauch at work with former SVN users, I feel weird because I'm the only one committing a crapload of times per day. Committing 6+ times in one day and the last commit was a revert of all the previous commits. Former SVN users are too used to big commits and merges I think
Feb
26
awarded  Constituent
Feb
26
awarded  Caucus
Feb
21
comment How can I tactfully suggest improvements to others' badly designed code during review?
As I said, it's possible to frame it as a learning experience for both developers. Also, having your own code ensures that you're doing the "put up" part of "put up or shut up" which is a situation that isn't fun to be in. I too like discussing solutions but discussion can only take you so far.