Tag Info

Hot answers tagged

46

If all you have is 2 days and no time to prototype or even read upon all the alternatives then there's really only 2 options: ask someone who knows and follow their advice. This may not necessarily mean asking an individual but spend the 2 days searching through blogs and articles to glean enough information to make a slightly-better-than-uninformed ...


18

It may seem that I am going against the stream, but I have recently read the book Creativity, Inc. by Ed Catmull and there was a really nice paragraph tackling this situation: Andrew Stanton spoke next. Andrew is fond of saying that people need to be wrong as fast as they can. In a battle, if you're faced with two hills and you're unsure which one to ...


9

gbjbaanb makes some very good points. I just thought I'd add a bit. It's obvious you don't have enough time to make a perfectly informed decision. Your only option is to try and make a decision that will minimize future pain. I'd suggest: Clearly document the nature of the situation: Send an email to your manager(s) and CC their managers and the ...


5

Since they've effectively given you little time to do more than pick candidates out of a hat, I'd adopt the following approach. Select technologies that: Have a large user base Have active support (via whatever channels) Are being actively developed By definition, this would rule out any bleeding edge technology, however good it may be. Also, resist ...


4

As much as I like to learn and experiment new stuff, under time constraints the best option is always to go for whatever is or feels more comfortable to work with. Stick to what you know. Even if in the long run it becomes clear you didn't choose the best option, anything you developed meanwhile continues being valuable and wraps a kind of field knowledge ...


3

You need to do it from time to time in development to check that it works correctly and isn't adding any additional bugs. It shouldn't be a step that you're using just in your release process, because that should be happening post-testing. You shouldn't be doing it for every small change you make, but from time to time you should absolutely be checking ...


3

2 days is a very short period for making that kind of decision, but since you have to do it in 2 days list following, What are the target platforms What are the custom / third party components used in current app where it might require considerable effort to port. for example : chart components, grid components, reporting components, etc.. How is the ...


2

Make a list of the factors that should go into choosing, things like: Performance security cost ease of use ability to do X ability to do Y developer familiarity time to market etc. This should take less than an hour (actually it should take less than 15 minutes), then sit down with management and have them prioritize those factors. (The chances of their ...


2

Without knowing more specifics, it's hard to identify actual problems with your approach. However, based on my experience facing the same issue in the past, I think the biggest thing you can do (aside from hiring a full time front-end developer who specializes in UI design) is to remember that less is more. Take a look at the UI elements that most modern, ...


2

Maybe you could create a third project on your source control, which contains only the shared libraries. So in short, your other two projects will reference this shared group of source files. This would allow you to have a group of shared libraries which are self contained, and are not stored within the context of another project. This assumes that you ...


1

It is more common to use source control branching in order to control what features are available within a particular version of the software. That said, applications that offer tiered functionality within the same version level will sometimes use the technique you describe. Usually, you'll see two main uses of the conditional definitions. The fist uses ...


1

It is important to do this in development only if you are not 100% certain that the script-mangling step doesn't introduce errors. Personally, I think using a tool that you can't be 100% certain of to transform your entire code base is unprofessional and you should never do it, but I recognize that getting the job done in the real world sometimes requires ...



Only top voted, non community-wiki answers of a minimum length are eligible