You want to incentivize paying your employees better but without eliminating the ability to pay executives great money.
All employees that actually do anything, are on fixed, and very inflexible salary. It's ersatz sales drones and arrogant executives, that get any variations.
NDA can't extend to things learned independently from the company, and his "friend" does not represent the company because he was not authorized to do so.
No, he is not. If someone does things he claims to cause returning 0, ( int main(int argc, char **argv) { } ) program will return random value that MAY happen to be 0, or will be 0 if the compiler is in C99-compatible mode.
Behold: $ echo 'int main(int argc, char **argv) { }'> maintest.c gcc -Wall -o maintest maintest.c maintest.c: In function ‘main’: maintest.c:1:1: warning: control reaches end of non-void function $./maintest ; echo $? 64 $ gcc -std=c99 -Wall -o maintest maintest.c $./maintest ; echo $? 0 $
So unless programmer intends to rely on C99-only feature that only exists to cover up sloppy writing, he has to explicitly return 0 from main() just like with any other function.
Programmers ARE engineers. They are not "Professional Engineers", a title that has nothing to do with Engineering, everything with legal systems of some states in US, and is not recognized anywhere else.
At other companies, you might end up getting treated like a data-entry temp.
I have seen code written by an intern in a company other than Apple, however before it was included into anything that shipped, it was checked and heavily modified by a real engineer.
I mean that int main(), just like any other integer function does not return 0 if it reached the end without a return statement, and a two days ago I had to fix a bug that was caused by someone making this very assumption.
But if you start with the mentality that you are building it to throw away -- to learn what it can do, what it should do, and how best to structure things so it will do it -- then its easier to take that step and start again with the knowledge you gained.
Or you turn yourself into the person who can only write code that should be thrown away. Once you start writing crap, you can't go back within your lifetime.
I've never met or even heard of anyone it makes any damn sense to describe as a 'brogrammer'.
Me, neither. And being a developer for two decades, I am sure, I would notice if such a thing existed. I have seen every monstrosity that existed in general vicinity of computer-executable code -- from "analysts" of old, who were equally unable to describe an algorithm in either machine-readable or human-readable form, to copypasta developers, whose relationship with software development can be only described as a modern cargo cult. From MCSE to VMware jockeys. From believers in Microsoft object-management model to people who lost all capability to communicate outside UML with humans and XML with machines. From mediocre students to... plain bad students who memorized some idiots' opinions and basic definitions and called that education. But no, no "brogrammers". Not even on 4chan.
Now if only they abandoned all other crappy software they are using as a part of development process. And by that I mean, the content of their sources.
Religious extremists commit arson and murder in the name of popular belief -- happened for about as long as religions existed. Tiny cult with beliefs that involve intergalactic overlords on airplane-shaped spaceships, attracting famous actors as spokespeople, and suing people for copyright infringement -- what is this I don't even...
Yes, but it's Scientology that sets the standards for acceptable level of nonsense and crazy beliefs, as they push the envelope, not Christian Fundamentalists.
So... what you're saying is that you truly, honestly believe that space entities travelled to earth... through space... in ships that just happen to look like our own current-day airplanes...
Stupid or ignorant is not the same as crazy. Most religions' mythologies looked pretty plausible for a common person a thousand years ago.
All Linux applications work under all Linux desktop environments, therefore multiple desktop environments have very little effect on applications development. All Linux-compatible desktops and laptops run all Linux desktop environments, therefore multiple desktop environments have no effect at all on Linux-compatible desktops and laptops. All Linux distributions have all Linux desktop environments packaged for them, therefore multiple desktop environments have little effect on Linux distributions.
Therefore there is no "market fragmentation". Now go back to claiming that Gimp does not support CMYK or something.
Slashdot Mirror
You want to incentivize paying your employees better but without eliminating the ability to pay executives great money.
All employees that actually do anything, are on fixed, and very inflexible salary. It's ersatz sales drones and arrogant executives, that get any variations.
NDA can't extend to things learned independently from the company, and his "friend" does not represent the company because he was not authorized to do so.
There are many reasons why it could not possibly happen. Last of which was an employee sending you documents that contain trade secrets.
If you don't know what standard you're compiling with, you're a fucking idiot. So yes, he was right.
No, it means that you are writing portable code, and don't rely on inconsistent exceptions included into standards to pander to idiots.
I believe, the result was "Five months before Palestinian State will be established with stable borders and elected government".
No, he is not. If someone does things he claims to cause returning 0, ( int main(int argc, char **argv) { } ) program will return random value that MAY happen to be 0, or will be 0 if the compiler is in C99-compatible mode.
Behold: ./maintest ; echo $? ./maintest ; echo $?
$ echo 'int main(int argc, char **argv) { }'> maintest.c
gcc -Wall -o maintest maintest.c
maintest.c: In function ‘main’:
maintest.c:1:1: warning: control reaches end of non-void function
$
64
$ gcc -std=c99 -Wall -o maintest maintest.c
$
0
$
So unless programmer intends to rely on C99-only feature that only exists to cover up sloppy writing, he has to explicitly return 0 from main() just like with any other function.
Programmers ARE engineers. They are not "Professional Engineers", a title that has nothing to do with Engineering, everything with legal systems of some states in US, and is not recognized anywhere else.
At Apple, interns are writing code that ships.
Oh. That explains everything.
At other companies, you might end up getting treated like a data-entry temp.
I have seen code written by an intern in a company other than Apple, however before it was included into anything that shipped, it was checked and heavily modified by a real engineer.
Why anyone in the world would want an intern with "leadership experience" ( == unproductive manipulative asshole obsessed with controlling people)?
(except in C99, what is not the default behavior for most compilers, and is a stupid idea in the first place)
I mean that int main(), just like any other integer function does not return 0 if it reached the end without a return statement, and a two days ago I had to fix a bug that was caused by someone making this very assumption.
It's also defined as the only function that if you reach the end without a return statement, it is implicitly "return 0;"
No.
But if you start with the mentality that you are building it to throw away -- to learn what it can do, what it should do, and how best to structure things so it will do it -- then its easier to take that step and start again with the knowledge you gained.
Or you turn yourself into the person who can only write code that should be thrown away. Once you start writing crap, you can't go back within your lifetime.
Considering what most programmers are, unions would enforce bad practices.
hundreds of "ui gurus" and "graphical masterminds" somewhere - who are supposed to be coming up with with the ui and ux(in other words specs).
Unity.
I've never met or even heard of anyone it makes any damn sense to describe as a 'brogrammer'.
Me, neither. And being a developer for two decades, I am sure, I would notice if such a thing existed. I have seen every monstrosity that existed in general vicinity of computer-executable code -- from "analysts" of old, who were equally unable to describe an algorithm in either machine-readable or human-readable form, to copypasta developers, whose relationship with software development can be only described as a modern cargo cult. From MCSE to VMware jockeys. From believers in Microsoft object-management model to people who lost all capability to communicate outside UML with humans and XML with machines. From mediocre students to... plain bad students who memorized some idiots' opinions and basic definitions and called that education. But no, no "brogrammers". Not even on 4chan.
Now if only they abandoned all other crappy software they are using as a part of development process. And by that I mean, the content of their sources.
Religious extremists commit arson and murder in the name of popular belief -- happened for about as long as religions existed.
Tiny cult with beliefs that involve intergalactic overlords on airplane-shaped spaceships, attracting famous actors as spokespeople, and suing people for copyright infringement -- what is this I don't even...
Yes, but it's Scientology that sets the standards for acceptable level of nonsense and crazy beliefs, as they push the envelope, not Christian Fundamentalists.
You're a scientologist, but not crazy.
So... what you're saying is that you truly, honestly believe that space entities travelled to earth... through space... in ships that just happen to look like our own current-day airplanes...
Stupid or ignorant is not the same as crazy. Most religions' mythologies looked pretty plausible for a common person a thousand years ago.
Security pros
Microsoft shills and antivirus software makers' PR departments.
and government officials
Propaganda workers and PR departments of military-industrial complex.
sharepoint plugins
Cool story, bro.
s/designer/hipster/g
All Linux applications work under all Linux desktop environments, therefore multiple desktop environments have very little effect on applications development.
All Linux-compatible desktops and laptops run all Linux desktop environments, therefore multiple desktop environments have no effect at all on Linux-compatible desktops and laptops.
All Linux distributions have all Linux desktop environments packaged for them, therefore multiple desktop environments have little effect on Linux distributions.
Therefore there is no "market fragmentation". Now go back to claiming that Gimp does not support CMYK or something.
Can you have a meaningful conversation if you have to point at things instead of naming them? Children can, but it's not much of a conversation.