01/12: Forty-one and done...
The news is I have a job. "Contract to hire" or as some call it 'rent-to-own'. Six month stint and no strings attaching me to pass up more lucrative or better jobs.
The major plus is I'll be learning web application development; specifically the ASP.NETs. Being .NET is an umbrella for web and desktop application development it shouldn't be too hard to get over the hump.
My concerns coming out of the interview is as follows:
- lack of stable environment. They keep their current version until a new version comes out and flip all new development to that area only to back propagate older apps as needed.
- Lack of stored procedure uses for their databases. Everything is "in code" so they don't have to track down versions, cds, and what not when fixing things. This goes back to the one above - if you have a stable database platform then this isn't really an issue.
- Testing is done by the developer and maybe the client. That's mildly concerning, but easily solved by budgeting time for testing.
- Questionable code reuse and design up front. I'll just have to be better at my game on this end.
All of these are really minor quibbles and I'll just need to get off my 'long term and enterprise wide' development thought process to a more loose and fast development.
To quote Krick "Let the bidding war begin!".
The major plus is I'll be learning web application development; specifically the ASP.NETs. Being .NET is an umbrella for web and desktop application development it shouldn't be too hard to get over the hump.
My concerns coming out of the interview is as follows:
- lack of stable environment. They keep their current version until a new version comes out and flip all new development to that area only to back propagate older apps as needed.
- Lack of stored procedure uses for their databases. Everything is "in code" so they don't have to track down versions, cds, and what not when fixing things. This goes back to the one above - if you have a stable database platform then this isn't really an issue.
- Testing is done by the developer and maybe the client. That's mildly concerning, but easily solved by budgeting time for testing.
- Questionable code reuse and design up front. I'll just have to be better at my game on this end.
All of these are really minor quibbles and I'll just need to get off my 'long term and enterprise wide' development thought process to a more loose and fast development.
To quote Krick "Let the bidding war begin!".