Cool Secret Service.

This is a Machine Learning Course. Here, I'll teach you how to learn with machines.
First step, go to your favorite browser and type "youtube.com" and search "how to develop in COBOL", which, by the way is a great language that it's getting quite popular.

When something piss you off a lot, think you are neither the only one nor the first one. Most of the times there's a better way to do the things.

Just say value and variable.

@cyberlord64 Didn't have thought of that one. I may use it in the future.

I consider each table as an entity, so each column is a property, and I dont use underscore to name class' properties in my system... so PascalCase is my choice.

(c# guy)

@codePolitics gotta admit I'm not good at design.

@Falk that isnt fair :__(

I've met some clients who ask us to develop apps which then they never use. Awkward, but you get used to it.

@Jop- unibody != non-removable battery. I think in most of smartphones you can replace battery fairly easy (obviously not like before, where a non-techie could do it), specially considering you're into making bombs.

Don't remember who said that is funny thinking that someone who cannot make his code comprehensible can make his comments be comprehensible

@ebroda the OP didn't tell how long it was. Anyway, the only thing I'd ask him for would be to record the meeting while he flips the pages and shouts "Bitch, I made it"

Y'all laugh at him, but he won't ever be fired if he still work at that project.

"Working Effectively with Legacy Code". Get that book.

Tell the client: "Then, we'll have two apps: one for IE people and another one for normal people. Thereby, you can value how much you should spend on us working for each of them"

The next time you spend more than 10 minutes in something "similar", split it and store it into variables, then, look what types have those variables and you may understand what's going on.

I went the other way around half a year ago, and I prefer Code.

A good answer of your colleague could've been telling the client: "Well, I'm afraid to tell you that the only one sounding inexperienced is you"

Actually it's pretty simple. I mean, a video is made of 24 pictures per seconds.
It's going to be a long PDF and they're going to spend a lot in paper and ink, but customer's always right.

In most of devs' life there's a moment when we start understanding that in our culture it's accepted to kinda keep your errors with you. That's not really spread among the rest of people in society.
We got used to it thanks to tools like git, where we dont delete the version where we fucked up, we simply fix it.

That might means two things:
a) We really fucked up in previous version
b) We are afraid of fucking up in following versions, so we're preparing ourselves for it.

Shame on you!
Developer ghosts say "Foo!"

Then, you'll leave that job smarter than now.

Think in terms of pros and cons of a repeated question:

Pros:
1. The user gets answered without having to search during 5 seconds.

Cons:
1. SO has to spend more money on disk usage.
2. There isn't a single source of truth.
3. When you search that question on Google, there will be tons of similar post with similar page rank since most of them have about 2 answers, instead of one post having 20 answers.
4. You will need a good connection to quickly get every post.
5. SO will need better bandwith and more disk usage for caching every little post because all of them are clicked.

.

@LrdShaper I think the problem is not only the time but the sacrifice. I mean, I value my friendship more than my job, but i dont pay my friends the money I get from it.

As a professional, you should learn to estimate (more or less) how deep a project can get (specially when it's for a friend) and decline it in those cases. Do not ever start something which you know you won't finish happily.

It's not only your friend's fault, it's also yours for letting them think that it's easy. They are ignorant about your job and that may be understandable; you are not, so you should tell them and let them know before starting anything.

The curious case of Benjamin Firefox.
Coming soon to theaters.

He probably still regrets having his iPhone's Health app uninstalled.

Dumb devs are the ones who refuse to search on Google for a quicker and more stable solution than theirs, not the ones who search it.

Pride is such a silly thing among programmers, it usually blinds us. You have to be proud of the solution you offer to your client/team/employer, not necesarilly the one you come up with.