Unless the 25% that's done is exactly what needs to be done(bug free, tested, and you don't need to change it) I would rewrite that. Sooner or later changes will have to be made to that part and you'll hate every minute of it :) .
Ask HN: Inheriting a large ASP.NET app, what would you do.
11–16 of 16 posts
Re: Ask HN: Inheriting a large ASP.NET app, what would you do.
#12Unless the 25% that's done is exactly what needs to be done(bug free, tested, and you don't need to change it) I would rewrite that. Sooner or later changes will have to be made to that part and you'll hate every minute of it :) .
Thanks, that's my instinct as well and I'm going for it, looking foward to unveiling it for critique when I have an mvp.
Re: Ask HN: Inheriting a large ASP.NET app, what would you do.
#13So much of this depends on context, some of which you provided. What is your comfort level with these technologies? What would your effective rate be for each of the scenarios? Are there components or databases (sql server) that make particular tech choices more sensible? How much time to tear down and start anew? What pressures or deadlines are you facing from the business?
I have a lot of flexibility. I am equally comfortable finishing up in c#/asp.net or starting over with bootstrap. I have a contract for a certain amount of money+equity to deliver a working web app, and then we are back to the negotions table where my next proposal will be for the mobile apps. As for sql server, i think cassandra, mongo, redis, will work just as well. I'm considering using the c# to js compiler curre…
I don't see anything in your explanation that would push my opinion one way or another, which means that you should probably take the long term view and do the rewrite.
Re: Ask HN: Inheriting a large ASP.NET app, what would you do.
#14If I were you I would see what could be salvaged. Can you rescue a bunch of business objects, data access code, etc.? If the code was written in a half-way competent manner, it shouldn't be too tightly coupled to ASP.NET. If there is a substantial amount of boilerplate code already written that you don't have to rewrite, I would suggest not rewriting it. I too would like to know what you are considering for the serve…
Server Side: I plan to copy those that scaled before me, a mixmash of: pinterest http://highscalability.com/blog/2012/5/21/pinterest-architec... , reddit: http://kev.inburke.com/kevin/reddits-database-has-two-tables... , and instagram: http://highscalability.com/blog/2012/4/16/instagram-architec... architectures. The previous devs managed to get everything tightly coupled at the design stage, which is why I think the…
You might want to have a look at the new .NET Web API if you're planning on leveraging existing code: http://www.asp.net/web-api
Good luck!
Re: Ask HN: Inheriting a large ASP.NET app, what would you do.
#15Earlier quoted context omitted.
I have a lot of flexibility. I am equally comfortable finishing up in c#/asp.net or starting over with bootstrap. I have a contract for a certain amount of money+equity to deliver a working web app, and then we are back to the negotions table where my next proposal will be for the mobile apps. As for sql server, i think cassandra, mongo, redis, will work just as well. I'm considering using the c# to js compiler curre…
I don't see anything in your explanation that would push my opinion one way or another, which means that you should probably take the long term view and do the rewrite.
Thanks!
Re: Ask HN: Inheriting a large ASP.NET app, what would you do.
#16Earlier quoted context omitted.
Server Side: I plan to copy those that scaled before me, a mixmash of: pinterest http://highscalability.com/blog/2012/5/21/pinterest-architec... , reddit: http://kev.inburke.com/kevin/reddits-database-has-two-tables... , and instagram: http://highscalability.com/blog/2012/4/16/instagram-architec... architectures. The previous devs managed to get everything tightly coupled at the design stage, which is why I think the…
You might want to have a look at the new .NET Web API if you're planning on leveraging existing code: http://www.asp.net/web-api Good luck!
Thank you!