935 reputation
819
bio website sourcecontribute.com
location Canada
age 27
visits member for 4 years, 4 months
seen yesterday

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


Mar
10
comment Are software developers who ignore quality/standards better for the company?
that ignores future costs created by sketchy quality
Mar
10
comment How to Code Faster (Without Sacrificing Quality)
I dislike this answer because it can be too easily taken the wrong way, just like "throwaway prototypes" never really seem to be thrown away.
Mar
10
comment how to introduce a culture of quality into the work environment?
would the question be less broad if I asked about how to counteract the bad attitude towards quality?
Mar
7
comment Sprint pressure causes quality issues?
There's also unaccounted for tasks that don't go into the project management tool or aren't written down anywhere (babysitting server deployments, fixing 3 bugs that were discovered in order to fix the one bug that's been assigned to you, doing research, creating a prototype, etc.)
Mar
7
comment How to stop / avoid Over Time on a Scrum Team?
Exactly. If you're using a tool like JIRA and estimating the hours of a task, you can see the number of hours of work your team can realistically accomplish.
Mar
7
comment Scrum Daily meeting: Punctuality over Full team presence?
except that in the real world the team doesn't always take responsibility and it's a manager or half-manager who takes control of the meetings and forces them and enforces the rules.
Mar
7
comment Can I use GPL libraries temporarily for prototyping and make the future code closed source?
@Deduplicator if they're separate applications that's not enough, they have to be treated as a separate code base, you're right. Kinda like what Twitter does with Bootstrap and what Facebook does with all its libraries. Non-core open source with core proprietary code.
Mar
7
comment How do you handle regular latecomers at the stand-up meetings?
when did the daily standup, meant to be run and decided on by the development team, become a mandatory thing. People over process <-- that's agile. Not this mandatory status meeting shit.
Mar
7
comment How do you handle regular latecomers at the stand-up meetings?
If even one person is late or skipping the meeting, you have to question whether the daily standup meeting is needed. If your team communicates their status over the course of the day and everyone has visibility into what's happening, the standup isn't needed (even if a manager says it needs to happen).
Mar
7
comment How do you handle regular latecomers at the stand-up meetings?
great point; if the team is communicating properly, the daily standup may not need to happen at all. The point of the standup is to have a short status meeting to make progress visible to managers and the rest of the team. Unfortunately, managers like forcing it into a daily thing that they can plan around instead of allowing it to ebb and flow as the tide of development/communication needs changes.
Mar
7
comment How do you handle regular latecomers at the stand-up meetings?
I think the comment thread here touches on a good point; a manager sets an expectation, the "late" developer fails to meet it. The manager set the expectation without consulting the developer. Should the developer, who continues to Get Shit Done, be punished for being late to a 15 minute daily status meeting that's meant for developers? I think this is another case of "butt in chair" but transferred over to daily standups.
Mar
7
comment What should we do to make Morning Standup meetting better and effective
In terms of the meeting time I would even say let the developers decide on it. Instead of "10am" or "9:30am", make it "before lunch" so that it covers anyone who's supposedly "late", it would give everyone enough time to review what they did and what they're working on.
Mar
7
comment What should we do to make Morning Standup meetting better and effective
I would even say rotate who "leads" the meeting. I've seen tech leads who are half-management who act like management and just dominate the meeting and turn it into a mandatory status meeting which the whole team hates.
Jan
20
comment using a wiki for requirements
DokuWiki is great, very easy to setup and it includes LDAP support if you're working within an Enterprise.
Jan
14
comment Breaking dependencies on remote APIs
@mgw854 I'm already mocking things out for unit tests, I'm mainly wondering if I should have mocks when I'm manually testing frontend-related changes.
Dec
16
comment Do gantt charts have a role in agile software development?
the whole point of Agile and XP is to clear the air and allow you to give good solid estimates without too much political pressure in providing the right numbers.
Dec
15
comment How to deal with a valuable person going in all directions?
daily status meetings and daily emails can sometimes feel burdensome and feel like micromanaging.
Nov
27
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
new company, less than 1 year old and they just added time sheets and we're told "it's about finishing the project! not about butts in seats!" yet we're working 9+ hrs every day because of shitty deadlines. 40hr work week? HAH.
Nov
3
comment What causes overtime and how can it be avoided?
@MikeM. the reason we demand that is because there's a multiplier on productivity of a programmer based on how well they can think. Casual dress, flex time, free sodas all facilitate that in small ways. Accountants and other jobs have a hard limit on how much can be done. 1 motivated programmer can increase profits immensely. This is why Google, Amazon, Apple, MSFT all make more cash than accounting firms.
Nov
3
comment How to code on a very tight schedule?
@SteveEvers when you're in the middle of a project raising concerns about shitty time estimates is discouraged.