7,626 reputation
31940
bio website
location England, United Kingdom
age 38
visits member for 4 years, 2 months
seen 2 days ago

2d
comment Django vs Rails for SaaS Startup
A vs B questions are always quick to close. Also the answer is Rails.
Dec
18
comment Hosted sharepoint 365 howto design a transaction table with a multiple sell/purchase option
This question might fit better on sharepoint.stackexchange.com ?
Oct
31
awarded  Nice Question
Oct
10
comment Typical team size to maintain and improve a 100k line codebase?
I absolutely believe it, but like most of the people who were around when I used to be a regular here, I am no longer sufficiently attached to the site to put myself through the friction of arguing it out. Programmers mostly stopped being a useful resource for me a few years back when it became closure central- I know that is a deliberate focus and I am sure most people enjoy it more, I guess I'm just an old-timey stick in the mud.
Oct
10
comment Typical team size to maintain and improve a 100k line codebase?
@JimmyHoffa That is outside my hands really- everything anybody asks here gets closed within a day or two. As is often stated in Meta, a StackExchange site where every question gets closed is a resource of limited usefulness at the best of times. My assumption would be that this is why programmers.se has lost so many core users over the last few years.
Oct
9
comment Typical team size to maintain and improve a 100k line codebase?
Thanks, this is the route I am taking. I think the point below about every task having to go through me is a useful one as well. I spend a lot of time blocked by routine tasks that do need doing- and prevent bad things happening- but slow down the visible progress that is the main metric the company observe.
Oct
8
revised Typical team size to maintain and improve a 100k line codebase?
A bit more context.
Oct
8
comment Typical team size to maintain and improve a 100k line codebase?
Well, this is the meeting I am shortly going to be having, which is why I asked the question - for the work I'm doing, I think a team of 3-5 would be able to manage it pretty well, but we don't have that budget. Unfortunately there are internal politics at work and the company has no background in software development so although I'm trying to explain what I am doing and why, it's a fairly challenging environment in which to do that. The risk is more that they drop a good product because it is impossible to do magic.
Oct
8
comment Typical team size to maintain and improve a 100k line codebase?
I think the other thing is that as a solo developer you can't hand off the easy tasks to anybody else, so no matter how good you are, your time is unavoidably invested in every task on the list.
Oct
8
revised Typical team size to maintain and improve a 100k line codebase?
Making it clearer that I'm dealing with this amount of actual code, not a lot of autogenerated stuff.
Oct
8
asked Typical team size to maintain and improve a 100k line codebase?
Sep
29
awarded  Yearling
Sep
6
awarded  Good Answer
Sep
5
comment What's wrong with comments that explain complex code?
On a day to day basis I use work in progress comments a lot too- they aren't there for the long run, but dropping in a TODO note or a short section to remind me what I was going to do next can be a useful reminder in the morning.
Sep
4
revised Communication/Updates between units of works/entity framework contexts, colliding with user changes
Added edit at the bottom.
Sep
4
comment Communication/Updates between units of works/entity framework contexts, colliding with user changes
Low user count and an EF back end suggest to me that you might as well update early and update often. I would also have some kind of polling facility to check when the last update was performed so that if User 1 is using the product and User 2 makes an update it can notify them and update their interface directly. I would be more worried about concurrency problems between users than between tabs on a single user's machine.
Sep
4
answered Communication/Updates between units of works/entity framework contexts, colliding with user changes
Sep
3
comment Does Play framework approach necessarily leads to confuse code?
The way to frontload this is actually to do some prototyping/playing around with the platform before you start, so that you know that it does the things you need and get the basics of it's idioms. That saves a lot of time in the long run. My experience with Rails has been that there is no maintainability problem with models and model code, the real problems arise from depending on gems that are subsequently deprecated/abandoned- after a while that starts locking you to old versions of everything.
Sep
3
comment Communication/Updates between units of works/entity framework contexts, colliding with user changes
Are the tabs open at the same time or can the user only see one at any given point? Normally tabs would be the latter, but I want to be clear.
Sep
3
answered Does Play framework approach necessarily leads to confuse code?