You sound so confident, and yet, so wrong and amusing.
"Where else would the phrase come from?", as though *your* world experience encompasses all that could have ever been.
The needle in question is a device for making haystacks by hand. It is about 2m long and was commonly assembled from three interlocking poles that packed away into a satchel so one could easily carry it around.
Fixing the report is taking care of the customer but, as I said, it is exposing the employer.
Telling the client how long the job will take without passing it by management is exposing the employer and risking failure and therefore risking the scheduling of the client.
It *might* look like taking care of the client but it could all go horribly wrong.
It's not about doing the minimum, overcharging or doing work for free.
It is about your company deciding what they will do, you are there to perform the tasks, the manager is there to manage when and what you work on.
It's not about making a job stretch in order to charge more. Lets assume the job will take 5 days work. During those 5 days all sorts of things can happen that may disrupt things. What if you are ill for a day, or your terminal breaks or a critical bug appears in some old job and you're the best guy to fix it. The project slips a bit and then you've not met your customer's expectations and you could be disrupting your client's schedule. Better to tell them "two weeks maximum" and then deliver in 8 days.
Yes, you're right. I didn't outline the failure of the manager's responsibility to his employee in that situation.
Being angry after the fact and expressing that at an employee is mismanagement. Hurting an employees feelings in that way is just not fair. It sounds like the OP is actually a good worker and as such should have his skills nurtured and chalk such minor mistakes up to experience instead of getting all shouty. That he ended up posting here means they didn't even talk about it properly !
1) Although you know how long it will take you, you do not know how many other projects will be multiplexed into your time. It is your manager's job to decide how long it will take you to complete a task for a client, regardless of how long it will take you.
2) You gave away your time for free, you released code without authorisation which is added risk to your employer.
That only works on Windows, Mac OS X & Linux i686.
Building Mozilla from source is not straight forward so if your vendor doesn't rebuild it then you have to be concerned enough to do it yourself.
If you run your browser in a jail or even just in its own account just like you should do for *any* program that processes untrusted data) then one will know what risk one is exposed to.
Crashing can often be an indicator of a buffer overflow, it's just that the return address you crashed it with doesn't keep it running. Once an appropriate set of overflow values is deduced that leads to an exploit.
One of the approaches to finding buffer overflows in Closed Source software is to do pump loads of data into the inputs until the app crashes, then work backwards by constructing a payload to see if one can get it to jump somewhere known.
Slashdot Mirror
The internet was never "envisaged".
That it can't die is 90s hype
pwn is what the kids say these days,
To them own3d is something your dad would say.
Get with the times, daddio =)
I wish I could, searching for it online is like searching for a needle in a haystack.
You sound so confident, and yet, so wrong and amusing.
"Where else would the phrase come from?", as though *your* world experience encompasses all that could have ever been.
The needle in question is a device for making haystacks by hand. It is about 2m long and was commonly assembled from three interlocking poles that packed away into a satchel so one could easily carry it around.
The problem with country folk is that they have lost touch with nature.
=)
"Like finding a needle in a haystack" is one of my favourites. The needle is not the tiny sewing implement most people think.
You spelt it britan not Britain, notice the extra i
=)
ugh, vile
Lose, my fried, lose.
That would be Britain, I hope you scrutinize your wikipedia entries more closely :)
what are these "anamels" of which you speak ?
Fixing the report is taking care of the customer but, as I said, it is exposing the employer.
Telling the client how long the job will take without passing it by management is exposing the employer and risking failure and therefore risking the scheduling of the client.
It *might* look like taking care of the client but it could all go horribly wrong.
A *real* geek would get a dual dual core ;)
It's not about doing the minimum, overcharging or doing work for free.
It is about your company deciding what they will do, you are there to perform the tasks, the manager is there to manage when and what you work on.
It's not about making a job stretch in order to charge more. Lets assume the job will take 5 days work. During those 5 days all sorts of things can happen that may disrupt things. What if you are ill for a day, or your terminal breaks or a critical bug appears in some old job and you're the best guy to fix it. The project slips a bit and then you've not met your customer's expectations and you could be disrupting your client's schedule. Better to tell them "two weeks maximum" and then deliver in 8 days.
Yes, you're right. I didn't outline the failure of the manager's responsibility to his employee in that situation.
Being angry after the fact and expressing that at an employee is mismanagement. Hurting an employees feelings in that way is just not fair. It sounds like the OP is actually a good worker and as such should have his skills nurtured and chalk such minor mistakes up to experience instead of getting all shouty. That he ended up posting here means they didn't even talk about it properly !
Your manager was right on both counts.
1) Although you know how long it will take you, you do not know how many other projects will be multiplexed into your time. It is your manager's job to decide how long it will take you to complete a task for a client, regardless of how long it will take you.
2) You gave away your time for free, you released code without authorisation which is added risk to your employer.
definatly
finite begat definite begat definitely begat indefinitely
lol, wtf are you on about ?
Wish I knew who I was a fanboy of, it would help me be more predicatle!
moov over and let me at the fire, I'm fresian !!
that would be hilarious, thanks Micro$haft for Virtual WiFi for Linux !!
come on, gimme some space, I'm under a lot of pressure
something like this http://www.archos.com/products/gmini_402_cam/ ?
recent by geological time
UTF was invented and used as the *only* charset in an OS before Windows 95 was even in beta
http://plan9.bell-labs.com/sys/doc/utf.html
my OS is where UTF8 [pdf] was invented.
That only works on Windows, Mac OS X & Linux i686.
Building Mozilla from source is not straight forward so if your vendor doesn't rebuild it then you have to be concerned enough to do it yourself.
If you run your browser in a jail or even just in its own account just like you should do for *any* program that processes untrusted data) then one will know what risk one is exposed to.
Crashing can often be an indicator of a buffer overflow, it's just that the return address you crashed it with doesn't keep it running. Once an appropriate set of overflow values is deduced that leads to an exploit.
One of the approaches to finding buffer overflows in Closed Source software is to do pump loads of data into the inputs until the app crashes, then work backwards by constructing a payload to see if one can get it to jump somewhere known.
s/then/than/