Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:Okay! Let me shed a tear for Apple! (Score 1) 269

I would agree that I am speaking without knowing all of the facts. I do find it interesting that Apple has a hard time finding talent to work for them though. I just wonder if they thought about opening an engineering center somewhere else than Cupertino since that is obviously an area where good talent is at a premium due to so many tech businesses.

Comment Re:Okay! Let me shed a tear for Apple! (Score 1) 269

Wish you had not posted this as Anon because I think you have some good ideas.

Personally, I think a good avenue is to get into the markets that smaller business's really require. As an example, provide some type of cloud based email/calendaring solution for smaller businesses (think Google for Business here). Most of which seem to like using their Macs so that would support their existing products. They could provide something like Google does for Outlook so the PC people could make use of as well. With that, there is a natural extension for storage needs which would fit well. I am not a fan of cloud solutions, but most smaller companies have moved that direction so why not leverage that direction.

Comment Re:Poor thought process (Score 1, Informative) 101

Well, that might work for you, but I would suggest to everyone else that you ALWAYS take a gun to a knife fight if you want to win. I can have my gun out just as fast as some idiot can pull their knife out....PERIOD. Here is a hit, don't walk around oblivious to your surroundings, and you will always be in a position where your side arm (even concealed) can be accessed long before issues arise.

Comment Re:The old talent doesn't understand the new stuff (Score 1) 229

Personally, I haven't worked with any senior engineers that weren't opposed to new technologies. They were just very skeptical because they have been burned so many times by the empty promises and worse, dealing with unintended issues that result because very rarely is the happy path ever taken. As we all know, it it the edge conditions that cause the issues because a generic frameworks many times cannot anticipate all edge conditions so they just don't handle it.

The young engineers are always ready to change for the sake of change many times, and they have never seen results when things go bad. They also don't seem to understand the full cost ($$$) of the situation of the upgrade. This includes the internal costs of testing as well as the potential cost to the customer for their internal testing. Rarely do I see a true risk analysis done which can be translated into a "risk versus reward" understanding of is the change worth it. All of this comes from experience: it just can't be taught, it must be experienced.

Comment Re:The old talent doesn't understand the new stuff (Score 1) 229

I think you and I need to go have some beers and discuss the scars we have on our backs from being forced to go down the same roads.

If I hear one more person tell me about this great new frameworks that will solve all of the problems, I believe I might beat that someone to death with my stapler.If I hear one more project manager tell me about this great new development approach which will solve the delays, I will take my keyboard and beat them upside the head. What the heck ever happened to good engineering practices..*sigh*.

And now, everyone, please get off my darn lawn.

Comment Re:What country do you live in? (Score 2) 165

The big issue with contract work is that you experience the ebbs and flow of the current market conditions immediately. If the market is good for employees (meaning full employment), then I have seen contract workers pull down wages that are better than full-timers. The problem right now is that the market is good for employers because there are so many people looking for work so they can get lower wages.

Comment Re:No "new" (Score 1) 497

I really hoping you are being sarcastic because if not, you really haven't worked on any projects of real size. What you describe is really nice for an app that does addition and subtraction, but when you have connections with multiple databases, have several dozen static sockets connections going while processing messages from those sockets, your suggestion of not using objects is naive at best.

Slashdot Top Deals

"One lawyer can steal more than a hundred men with guns." -- The Godfather