Comment Re:Menial Jobs (Score 1) 187
Is that why I have to idle in a chat room for days while I wait for some customer service? The service industry is a joke.
You get what you pay for.
Is that why I have to idle in a chat room for days while I wait for some customer service? The service industry is a joke.
You get what you pay for.
so why is Foxconn always seen as some evil company doing Apple's bidding?
Mr. Tycho Brahe observes: We must, as conscious beings, observe when we are told things that are strategically lathed not to inform us but to make us fight with one another.
"We stopped at two nuclear bombs"
That is the most optimistic thing I've read all week. It hasn't been a century yet, the time for the third bomb is coming.
I see this thinking a lot, but I honestly don't understand how you can meaningfully compare something you've done with something you haven't.
Practice doing it, and soon you'll be able to do it accurately yourself. Think of a typical website.....the content is different, but the structure is just a bunch of pages, storing stuff in a database, maybe doing some authentication. A difficult project would be inventing a new algorithm. That's rare, and working on projects that are completely unrelated to anything you've done before is equally rare.
If you're working on a two-week sprint, by practicing and noticing how accurate your estimates were, then within two months you'll find that 80% of your estimates are accurate.
Caveat emptor: if you have a manager constantly pushing to make your estimates shorter, then learning to make accurate estimates is very hard.
Agreed. The problem is, they don't listen.
You are not responsible to meet any estimates you don't make. If your manager makes your estimate, let him meet it.
That's a bad example because that's almost never my criteria
Yeah, but you're just some guy.
You must be working in a shop that does the same thing over and over again, year after year.
No. I don't think many people work in that kind of shop.
No excuses. Don't use that as an excuse for bad estimates, it's something you can improve.
Can you even IMAGINE Microsoft saying that 15 years ago? 10 years ago?
Yes, think of the standard pattern:
1) Embrace.
2) Extend.
3) Extinguish.
This fits perfectly in the pattern, it is an echo of "Developers, developers, developers!", it is exactly what you would expect from Microsoft when they realize they are back to the Embrace step.
This is a very insightful post
Thanks!!
Good managers are almost as rare as honest politicians.
Then teach your manager to be better. Reject the corporate structure (it may shift many times while you work at a company, even though not much else changes. That is an indication it's not particularly real), accept that improvement can come from even the lowliest programmer, and then help your manager do better.
If you think that your manager is completely bad in every way, you're not going to be able to help him. You need to be honest, recognize his strengths, and help him overcome his weaknesses.
You'll probably also need to overcome some of your own weaknesses, unless you are perfect. I can tell you one way to not accomplish anything: start a twitter campaign telling the world how bad your boss is. That will not make your system better.
People do not predict well and it is not smart to use it against them.
You can improve. Most programming we do is boring, and similar to something we've done before. For things like that, you should be able to make your estimates reasonably accurate.
Sometimes projects have large unknowns, and it's impossible to know how long it will take. In that case you need to propagate that information up to the people who need it, either managers or salespeople or whatever.
Networking is still painfully slow compared to iOS.
I'm not sure I understand this point, in my experience, the network on Android is as fast as the network on iOS. What am I missing?
I've noticed several design suggestions in your code.