1. Did you gain enough practical/technical knowledge before or during undergrad to attack a given problem with a profitable solution?
2. Can you convince an investor of point #1?
989 karma · joined February 3, 2010
sean.t.kennedy@gmail.com https://linkedin.com/in/stkennedy
1. Did you gain enough practical/technical knowledge before or during undergrad to attack a given problem with a profitable solution?
2. Can you convince an investor of point #1?
Overall, a good execution by Google on its first commercial. Putting it on the Super Bowl, all I can think is, "Go big or go home."
If you want to play it safer with the 4-5% return, there are safer mutual funds to invest with. Less risk and less returns. But for arguments sake, will 4-5% cover the inflation you experience as you grow older?
http://web.me.com/agueniot/Data/Flash/cven.html
Pulling out a 2004 link, but it has stayed in my Bookmark archive for years.
Maybe it depends on your specific needs, but I am not sure why you would want any products you develop (regardless of the programming language) to share server resources with the Oracle database. My teams always separate the product load across servers and tiers. If you can afford the $20,000 per processor for Oracle, hopefully, you have multiple tiers to put your code elsewhere.
A day after MJ's death, Google announced they were going to modify their approach.
Mistakes are items that are not clearly defined as a requirement to the client and use cases identified. If your code passes the documented requirement and use cases supplied, then it is a mistake. Further requirements analysis should have been conducted by the client. Mistakes happen as the set of requirements and use cases become very interrelated to make a complex solution.
A bug would be not thoroughly testing the code to pass all identified requirements and use cases.
The dilemma I have previously run into is the balance between client happiness and my own. If you endlessly do free work for the client, they may come to expect it. If you do not, future work may be lost. My opinion would be to go over requirement docs and statements of work with a fine tooth comb, line-by-line. Any holes, plug them. Any questions, clarify them. Make sure the client knows which party owns which set of risks. You should not take 100% of the risk when maybe the client can spend more time identify requirements.