• Sociopath (unregistered) in reply to Fred
    Fred:
    I'd been at my new job about 3 days before the old place called and begged me to come back. "The system crashed and nobody can get it started. And we can probably put you in that manager slot now. But we need you back today!"
    This is when you agree to provide consulting at $2500/hr. When they balk at the price, you ask them how much money they are losing by being down.

    ProTip: First hour paid in advance in cash; no exceptions.

  • jim (unregistered) in reply to Cap'n Spanky
    Cap'n Spanky:
    Hey - I worked for that guy, too! Small Linux distro in the early 2000's. The CEO would regularly come out of his glass office and scream at the marketing folks. He went through marketing people like milk through dairy intolerants.
    Come on, how many geeks do you know who've never fantasised about getting rich and starting their own company just so they can abuse the marketing department? This guy's just living the dream.
  • Some Damn Yank (unregistered) in reply to PunctuallyChallenged
    PunctuallyChallenged:
    The owner of a company I once worked for called me the day after he fired me, asking if I would come back as a contractor until he filled the position.
    I was once "surplussed" out of a department and left to my own devices. I found another position within the company, and proceeded to field calls from my former department regarding code I'd maintained - not written, mind you, maintained. I'd had to figure it out for myself, why couldn't they? I finally had enough and said something to the effect of "If you need me so badly, why did you surplus me? Please don't call again, I have work to do here." They never called back.
  • (cs) in reply to chubertdev
    chubertdev:
    I wonder what the longevity is of people that are promoted to managers. I think that it's often a red flag. I've seen it happen often, and it's even happened to me once, where that is used as a substitution for increase in pay. I received more reponsibility with only a few more bucks in my pocket. Awesome.

    The icing on the cake was that the hiring for the people beneath me was done with very little of my input. The PHB would hire people based on his choices.

    When he re-hired a guy that was pretty much the cause for every single problem in our codebase without my input, that was when I walked out the door. Although it helped that I already had another job lined up...

    Oh, and I should add that it took me 4-6 months of being a "manager" to find a new job. After that guy was hired, it took me two weeks to give new two week notice.

    Also, they don't have a chance of calling me up and asking me to come back, since smartphones give me the awesome ability to blacklist numbers. :D

  • (cs)

    On "suffering": Uphill, in the snow, BOTH ways!

  • Some Damn Yank (unregistered) in reply to ¯\(°_o)/¯ I DUNNO LOL
    ¯\(°_o)/¯ I DUNNO LOL:
    Smug Unix User:
    Why not obsqwerty the functions as well? You could even write an interpreter in Access and use your own obsqerty language.
    Why stop there? It should be obvious that if you want to keep things really secure, you need to write your business logic code in Brainfuck.
    Oh, that explains it! All these years I've been dealing with highly secure requirements specifications and didn't realize it. I thought it was just laziness on the part of Management; I didn't realize it was a well-thought-out plan.
  • (cs) in reply to Valued Service
    Valued Service:
    snoofle:
    Obsqwerty:
    I've never actually gone back to the previous company, but I've got on the phone to the recruiter within the first week.
    It's been my experience that if a new job turns out to be unacceptably different from expectations, the LAST person you call is the recruiter that got you the position. If you think about it, their incentive is to keep you there long enough to get their commission (usually 3-6 months). It is NOT in their best interests to help you quickly find another job.

    Yes it would be in their best interest. If they don't help you, you'll call another recruiter who'll be eager to do so, and they lose their investment, plus lose the opportunity for you to return in 3-5 years. If they do help you, they'll find you another position and get the credit from the new job.

    Do you not understand who the customer is in this business relationship? If the employer were to even get a hint that a recruiter might be helping find other employment for an employee they just hired through them, that is the end of ANY future business for the recruiter. This is not to mention the contractual obligations. Really...

  • Anonymous Bosh (unregistered) in reply to Anon

    Luxury! We lived in a lake!

  • Some Damn Yank (unregistered) in reply to chubertdev
    chubertdev:
    I wonder what the longevity is of people that are promoted to managers. I think that it's often a red flag. I've seen it happen often, and it's even happened to me once, where that is used as a substitution for increase in pay. I received more reponsibility with only a few more bucks in my pocket. Awesome.
    There's a certain aerospace giant in the Seattle area with a habit of promoting people to management just prior to a strike, then demoting them back to worker after the strike is over. During the strike they get to sweep floors and clean toilets, but at least they're in management.
  • ¯\(°_o)/¯ I DUNNO LOL (unregistered) in reply to LoremIpsumDolorSitAmet
    LoremIpsumDolorSitAmet:
    faoileag:
    ¯\(°_o)/¯ I DUNNO LOL:
    Why stop there? It should be obvious that if you want to keep things really secure, you need to write your business logic code in Brainfuck.
    Still readable. Too easy. Use Whitespace.
    A clever idea, but in these cases it'll probably be easier to reverse engineer the compiled code instead of attempting to understand the original.
    What compiled code? The Brainfuck/Whitespace interpreter is written in APL, and the APL is run on 6502 machine code.
  • jay (unregistered) in reply to Anon
    Anon:
    faoileag:
    Anon:
    faoileag:
    QJo:
    It in fact took me 4 months to get out of there
    4 months? You were lucky, with only 4 MONTHS! I once started at a company and within a few days realized that things were, well, a bit different there. I started to pass my resumee around after 15 Months, but in the end, since I didn't want to leave town at the time, it took me six years to get out.
    15 Months?!? You were lucky. We lived for three months in a paper bag in a septic tank. We used to have to get up at six in the morning, clean the paper bag, eat a crust of stale bread, go to work down t' mill, fourteen hours a day, week-in week-out, for sixpence a week, and when we got home our Dad would thrash us to sleep wi' his belt.
    Luxury. We used to have to get out of the lake at three o'clock in the morning, clean the lake, eat a handful of hot gravel, go to work at the phone factory every day for a few tuppence a month, come home, and Dad would beat us around the head and neck with a broken bottle, if we were LUCKY!

    Well, of course, we had it tough. We used to 'ave to get up out of shoebox at twelve o'clock at night and lick road clean wit' tongue. We had two bits of cold gravel, worked twenty-four hours a day at mill for sixpence every four years, and when we got home our Dad would slice us in two wit' bread knife.

    Yeah, you think that's tough? When I started out, we had to program in COBOL.

  • jay (unregistered) in reply to Sociopath
    Sociopath:
    Fred:
    I'd been at my new job about 3 days before the old place called and begged me to come back. "The system crashed and nobody can get it started. And we can probably put you in that manager slot now. But we need you back today!"
    This is when you agree to provide consulting at $2500/hr. When they balk at the price, you ask them how much money they are losing by being down.

    ProTip: First hour paid in advance in cash; no exceptions.

    While I've never had the chutzpah to ask for $2500 an hour, I've had several times when a former employer asked me to come back and do some consulting work, I really wasn't very interested, and so I quoted what at the time seemed to me an excessively high rate. A few times they've promptly agreed to pay it, in which case, okay, it wasn't a job I wanted to do, but if they were willing to pay a crazy rate, it was worth it. When they don't agree to pay it, fine, I didn't really want to do that job anyway.

  • jay (unregistered)

    Hmm. This is the moral equivalent of putting a reinforced steel door on the front of your house with the latest, most secure deadbolt lock ... and then hanging a sign on the doorknob that says "key is under the big red flower pot behind the house". In both cases, only people who are willing to take the ten minutes effort required can get in. Good security against people who are both dishonest and incredibly lazy, though.

  • Fred (unregistered) in reply to operagost
    operagost:
    Fred:
    I'd been at my new job about 3 days before the old place called and begged me to come back. "The system crashed and nobody can get it started. And we can probably put you in that manager slot now. But we need you back today!"

    I informed them that basic professionalism would require me to give at least four weeks notice to my new employer, but I wasn't really interested in returning anyway.

    "Four weeks! Are you crazy? You only gave us two!"

    "But I wasn't in a management position with you. I am now."

    I'd go there after I left my new job for the day and charge them $250 an hour for emergency after-hours service.
    Perhaps you missed the part where I mentioned the guy who was murdered. I wasn't kidding about that.

    No one confessed, but the rumors were that the deceased had cornered the company into giving him a little bit more money than the company really wanted him to have. No way was I going to extort those people. I was just glad to be away -- and not at all comfortable that they'd found my new work phone number.

    A few years later I happened to be interviewing elsewhere and the employer saw Mucking Furderers Inc. on my resume. (I'd been there too long to just leave a gap.) He commented, favorably, since he had a friend there.

    I took that as a lucky break and deliberately flubbed the rest of the interview.

  • Ingeneur (unregistered) in reply to jay
    jay:
    Anon:
    faoileag:
    Anon:
    faoileag:
    QJo:
    It in fact took me 4 months to get out of there
    4 months? You were lucky, with only 4 MONTHS! I once started at a company and within a few days realized that things were, well, a bit different there. I started to pass my resumee around after 15 Months, but in the end, since I didn't want to leave town at the time, it took me six years to get out.
    15 Months?!? You were lucky. We lived for three months in a paper bag in a septic tank. We used to have to get up at six in the morning, clean the paper bag, eat a crust of stale bread, go to work down t' mill, fourteen hours a day, week-in week-out, for sixpence a week, and when we got home our Dad would thrash us to sleep wi' his belt.
    Luxury. We used to have to get out of the lake at three o'clock in the morning, clean the lake, eat a handful of hot gravel, go to work at the phone factory every day for a few tuppence a month, come home, and Dad would beat us around the head and neck with a broken bottle, if we were LUCKY!

    Well, of course, we had it tough. We used to 'ave to get up out of shoebox at twelve o'clock at night and lick road clean wit' tongue. We had two bits of cold gravel, worked twenty-four hours a day at mill for sixpence every four years, and when we got home our Dad would slice us in two wit' bread knife.

    Yeah, you think that's tough? When I started out, we had to program in COBOL.

    Psht. When I started out, we had to program in PHP.

  • jay (unregistered)

    Personally, I've only once quit a job after less than a year, and these days I wouldn't quit a job in less than 2 or 3 years unless it was really intolerable. Like the employer demanding that I do something that totally offended my morals, commit crimes that could land me in prison, or something of that sort.

    Because: (a) I don't want to make a snap judgement. Maybe the first week or first day on the job looks really bad, but if I gave it a few months things might get better. I routinely find that new jobs are tough for a while because it takes time to build up credibility, so at first my opinions aren't particularly valued, I'm not given the most interesting work, etc.

    (b) I don't want to get a reputation as someone who job hops. I recall once when I was involved in hiring someone, I saw a resume where the person had three months at one job, two weeks at the next, a year at the next, a few days at the next, etc. And I thought: I don't know if this guy gets bored or frustrated quickly and quits on his own, or if he's lazy or dishonest or incompetent and is quickly fired or forced to leave. But either way, do we want to hire him? No. I threw the resume away. I mentioned it to my boss at the time, and he commented that if someone had one such short job on his resume, okay, he took a job and then realized it was a mistake. No big deal. But when ALL his jobs are like that? The problem is not the job: it's him.

  • Bob (unregistered) in reply to Ingeneur
    Ingeneur:
    Psht. When *I* started out, we had to program in PHP.
    Bollocks. No one programs in PHP. They just copy-paste.
  • (cs) in reply to jay
    jay:
    (b) I don't want to get a reputation as someone who job hops. I recall once when I was involved in hiring someone, I saw a resume where the person had three months at one job, two weeks at the next, a year at the next, a few days at the next, etc. And I thought: I don't know if this guy gets bored or frustrated quickly and quits on his own, or if he's lazy or dishonest or incompetent and is quickly fired or forced to leave. But either way, do we want to hire him? No. I threw the resume away. I mentioned it to my boss at the time, and he commented that if someone had one such short job on his resume, okay, he took a job and then realized it was a mistake. No big deal. But when ALL his jobs are like that? The problem is not the job: it's him.

    Hilarious. We just had a guy like that in here, at first we had assumed it was just contract positions. But when we found out that they weren't, I pretty much said the same thing as you.

  • Lambda Llama (unregistered) in reply to ¯\(°_o)/¯ I DUNNO LOL
    faoileag:
    ¯\(°_o)/¯ I DUNNO LOL:
    Why stop there? It should be obvious that if you want to keep things really secure, you need to write your business logic code in Brainfuck.
    Still readable. Too easy. Use Whitespace.

    Still too easy... We don't need no steenkin' variables, data structures or code constructs. These are "just" declarative languages with funky syntax - let's try something new and completely different.

    ```s``s``sii`ki
      `k.*``s``s`ks
     ``s`k`s`ks``s``s`ks``s`k`s`kr``s`k`sikk
      `k``s`ksk
  • (cs)

    I'm just going to fast-forward and say that I learned to program by training dolphins to jump through two hoops that represented 0s and 1s, but could never get any program to do anything past print the phrase, "so long and thanks for all the fish."

  • Chris (unregistered)

    This is a fail for sure. As a security engineer I would fail this review. In fact I would refuse to review this code in any detail at all.

    http://securityblog.howellsonline.ca - Real lessons on security.

  • HowItWorks (unregistered) in reply to chubertdev
    chubertdev:
    jay:
    (b) I don't want to get a reputation as someone who job hops. I recall once when I was involved in hiring someone, I saw a resume where the person had three months at one job, two weeks at the next, a year at the next, a few days at the next, etc. And I thought: I don't know if this guy gets bored or frustrated quickly and quits on his own, or if he's lazy or dishonest or incompetent and is quickly fired or forced to leave. But either way, do we want to hire him? No. I threw the resume away. I mentioned it to my boss at the time, and he commented that if someone had one such short job on his resume, okay, he took a job and then realized it was a mistake. No big deal. But when ALL his jobs are like that? The problem is not the job: it's him.

    Hilarious. We just had a guy like that in here, at first we had assumed it was just contract positions. But when we found out that they weren't, I pretty much said the same thing as you.

    Likewise, but we didn't find it funny. The new hire was cut lose during the probationary period. The guy interviewed well, but was soon obvious did not have basic understanding of coding, the IDE, or even usage of browsers.

    The added WTF, we noted the frequent job turnover. So we had HR contact previous employers and all gave good reviews and they would hire him again. Left us wondering at that disconnect.

  • (cs) in reply to Roby McAndrew
    Roby McAndrew:
    ¯\(°_o)/¯ I DUNNO LOL:
    to keep things really secure, you need to write your business logic code in Brainfuck.

    You are all reading the comments. The real software is written in whitespace.

    You guys are amateurs. You need to write in a language that looks like it should be readable, but isn't. I recommend forth, or it's modern cousin factor.

  • (cs) in reply to Anon
    Anon:
    faoileag:
    Anon:
    faoileag:
    QJo:
    It in fact took me 4 months to get out of there
    4 months? You were lucky, with only 4 MONTHS! I once started at a company and within a few days realized that things were, well, a bit different there. I started to pass my resumee around after 15 Months, but in the end, since I didn't want to leave town at the time, it took me six years to get out.
    15 Months?!? You were lucky. We lived for three months in a paper bag in a septic tank. We used to have to get up at six in the morning, clean the paper bag, eat a crust of stale bread, go to work down t' mill, fourteen hours a day, week-in week-out, for sixpence a week, and when we got home our Dad would thrash us to sleep wi' his belt.
    Luxury. We used to have to get out of the lake at three o'clock in the morning, clean the lake, eat a handful of hot gravel, go to work at the phone factory every day for a few tuppence a month, come home, and Dad would beat us around the head and neck with a broken bottle, if we were LUCKY!

    Well, of course, we had it tough. We used to 'ave to get up out of shoebox at twelve o'clock at night and lick road clean wit' tongue. We had two bits of cold gravel, worked twenty-four hours a day at mill for sixpence every four years, and when we got home our Dad would slice us in two wit' bread knife.

    Right. I had to get up in the morning at ten o'clock at night, half an hour before I went to bed, eat a lump of cold poison, work twenty-nine hours a day down mill, and pay mill owner for permission to come to work, and when we got home, our Dad would kill us, and dance about on our graves singing "Hallelujah."

  • someone (unregistered)

    So these are the original variable names?

    Not obfuscated/anonymized by TDWTF?

  • (cs) in reply to HowItWorks
    HowItWorks:
    Likewise, but we didn't find it funny. The new hire was cut lose during the probationary period. The guy interviewed well, but was soon obvious did not have basic understanding of coding, the IDE, or even usage of browsers.

    The added WTF, we noted the frequent job turnover. So we had HR contact previous employers and all gave good reviews and they would hire him again. Left us wondering at that disconnect.

    Oh, that's tougher, then. This guy did NOT interview well, and that saved us a bunch of time. The whole issue of interviewees usually being people without jobs really sucks.

  • Anon (unregistered) in reply to wsm66
    wsm66:
    Anon:
    faoileag:
    Anon:
    faoileag:
    QJo:
    It in fact took me 4 months to get out of there
    4 months? You were lucky, with only 4 MONTHS! I once started at a company and within a few days realized that things were, well, a bit different there. I started to pass my resumee around after 15 Months, but in the end, since I didn't want to leave town at the time, it took me six years to get out.
    15 Months?!? You were lucky. We lived for three months in a paper bag in a septic tank. We used to have to get up at six in the morning, clean the paper bag, eat a crust of stale bread, go to work down t' mill, fourteen hours a day, week-in week-out, for sixpence a week, and when we got home our Dad would thrash us to sleep wi' his belt.
    Luxury. We used to have to get out of the lake at three o'clock in the morning, clean the lake, eat a handful of hot gravel, go to work at the phone factory every day for a few tuppence a month, come home, and Dad would beat us around the head and neck with a broken bottle, if we were LUCKY!

    Well, of course, we had it tough. We used to 'ave to get up out of shoebox at twelve o'clock at night and lick road clean wit' tongue. We had two bits of cold gravel, worked twenty-four hours a day at mill for sixpence every four years, and when we got home our Dad would slice us in two wit' bread knife.

    Right. I had to get up in the morning at ten o'clock at night, half an hour before I went to bed, eat a lump of cold poison, work twenty-nine hours a day down mill, and pay mill owner for permission to come to work, and when we got home, our Dad would kill us, and dance about on our graves singing "Hallelujah."

    And you try and tell the young people of today that ..... they won't believe you.

  • Jay (unregistered) in reply to Guanxi
    Guanxi:
    Elron the Fantastic:
    Oh you fortunate kids. I was once a camera man for Rosie O'Donnell; I had to film her every day.
    I used to work in a factory in China assembling Apple products.

    Ooh, get you with you fancy job lording it over the rest of us.

  • Jay (unregistered)

    Oh, I see the WTF now. They tried to define all of those variables as strings, but most of them are actually variants.

    And what's wrong with doing Password = "P" & "a" & "s" & "s" & "w" & "o" & "r" & "d" like the rest of us security professionals do?

  • Spider Flyer (unregistered) in reply to herby
    herby:
    On "suffering": Uphill, in the snow, BOTH ways!

    Which is actually possible, if you are on the top of Hill A and have to go to the top of Hill B.

    (It's just not uphill for the FULL distance...Also, the snow was literally knee deep.)

  • QJo (unregistered) in reply to RichP
    RichP:
    QJo:
    And equally unfortunately it turned out that the person interviewing me was a personal friend of the owner of the company I was blowing out.

    Oh boy did I mis-read that one. At first I had a totally different picture of how you obtained your position.

    +100 (helpless with giggles)

  • QJo (unregistered) in reply to Sociopath
    Sociopath:
    Fred:
    I'd been at my new job about 3 days before the old place called and begged me to come back. "The system crashed and nobody can get it started. And we can probably put you in that manager slot now. But we need you back today!"
    This is when you agree to provide consulting at $2500/hr. When they balk at the price, you ask them how much money they are losing by being down.

    ProTip: First hour paid in advance in cash; no exceptions.

    Damn, that's where I've been going wrong - leaving the documentation in an acceptable state on leaving a job.

  • (cs) in reply to VAXcat
    VAXcat:
    They told me, this was madness. I replied, Exactly so and hung up the phone.
    Wait, what? No Sparta? You botched such a good opportunity...
  • (cs) in reply to Bob
    Bob:
    Ingeneur:
    Psht. When *I* started out, we had to program in PHP.
    Bollocks. No one programs in PHP. They just copy-paste.
    You copy-pasted that from a comment about Javascript...
  • QJo (unregistered) in reply to PedanticCurmudgeon
    PedanticCurmudgeon:
    Roby McAndrew:
    ¯\(°_o)/¯ I DUNNO LOL:
    to keep things really secure, you need to write your business logic code in Brainfuck.

    You are all reading the comments. The real software is written in whitespace.

    You guys are amateurs. You need to write in a language that looks like it should be readable, but isn't. I recommend forth, or it's modern cousin factor.

    Topper hat on ...

    John Horton Conway's Game of Life has been demonstrated to be Turing-complete. Therefore it is possible to construct a virtual machine thathas all the functionality of a bricks-and-mortar computer. For a really challenging obfuscation, get your programming staff to write their programs in the form of a Life configuration on an arbitrarily-large square grid.

  • RRDY (unregistered) in reply to Valued Service
    Valued Service:
    I think I see a pattern here.

    Take previous "had it bad story".

    Shrink size of living quarters. Decrease sanitation of environment. Decrease health, sanitation, environment, and increase working hours and shame of work conditions. Increase brutality of father's abuse. Increase duration of work pay by a factor of larger scale of time measurement, and decrease pay.

    We used to have to live in an atom every day, get up and rearrange the sub-atomic particles so that a hole would open so we could leave for work. On our way out, we'd have to pass through the membrane of a tumor cell, exposing ourselves to radiation therapy in a dying patient at a dirty old hospital. We'd then work on cleaning the hospital's patients in the E.R. ward with our own spit. When we made it home, our father would crush us in a black hole. We did all this for a piece of used toilet paper for dinner.

    They're actually quoting a fairly well-known Monty Python skit.

    captcha: augue: I really don't wanna augue, but you really should know more about Monty Python.

  • Your Name (unregistered) in reply to QJo
    QJo:
    gnasher729:
    We once had an employee leave for another company and received a call on Monday morning 9:10 am asking if he could come back, that is ten minutes after he started work at the new company. He then stayed with us for many years. Must have had a similar experience.

    Happens more often than you'd believe. I can think of at least 5 people I've worked with who have gone away and come back in short order.

    Me, I've never actually gone back to the previous company, but I've got on the phone to the recruiter within the first week. I was lined up with a sweet number too, that first call, offering twice the money and considerably more responsibility - then I made the mistake of explaining that I'd just started in a job I wasn't a good fit for. And equally unfortunately it turned out that the person interviewing me was a personal friend of the owner of the company I was blowing out.

    It in fact took me 4 months to get out of there and into the next port of call.

    Never trust a recruiter, never tell a recruiter anything more than the bare minimum. They are in it for the money and will shit on you if they have to in order to make more. Same goes for companies... for as much as they screw recruits over, they lie even worse to the companies, claiming recruits have skills that are a pure fabrication.

    Companies know recruiters lie. Employees know recruiters lie. Why recruiters even exist is only because they have firmly entrenched themselves between companies and employees.

  • jay (unregistered) in reply to Your Name
    Your Name:
    Companies know recruiters lie. Employees know recruiters lie. Why recruiters even exist is only because they have firmly entrenched themselves between companies and employees.

    So a company is considering two options: 1. Put an ad in the newspaper or on a website advertising a job opening. 2. Contact a recruiter and tell them you have a job opening.

    Option 1 is cheap, maybe a few hundred dollars depending on how long you run the ad. Option 2 is expensive, thousands, sometimes tens of thousands of dollars. With option 1, you'll get a truckload of resumes from people who aren't remotely qualified for the job. With option 2, in theory the recruiter will filter out all the unqualified people and only send you resumes from people who are qualified for the job.

    But in practice, recruiters don't filter out unqualified people. Often they ... ahem ... "reformat" resumes to make unqualified candidates look qualified.

    So what, exaactly, is the advantage of using a recruiter? I suppose they filter out some of the most absurdly unqualified candidates, like if you're hiring for an IT job and the candidate has zero IT education or experience. But how much does that help? Surely you could buzz through resumes and quickly discard those anyway. I'd think you could hire someone to scan resumes like that for a whole lot less than what recruiters charge. If you have a problem with people calling or showing up at the office about a job instead of sending a resume, then don't put your company name or phone in the ad: just put a blind post office box or gmail/yahoo/some such email address. (Anyone smart enough to track down who's behind an anonymous email address should pass the first cut anyway.)

    I'd be amused to hear from a recruiter or an HR person what these folks really do have to offer for the amount they charge.

  • SztupY (unregistered) in reply to gnasher729

    Well, it takes around one minute to tell someone that the company actually uses BobX (or MUMPS).

    Then comes 8 minutes of constant struggle to resist a fatel hearth attack.

    And one more minute needs to be spent on the resignation letter.

    Yep, that's 10 minutes.

  • Gruntled Postal Worker (unregistered)

    Confession:

    I once helped design and build a system where finally security was a functional requirement from the start. We really did our research, followed best practices and reviewed everything thoroughly, then ended up adding an 'admin/password01' account for administrative convenience.

  • Friedrice The Great (unregistered) in reply to jay
    jay:
    Personally, I've only once quit a job after less than a year, and these days I wouldn't quit a job in less than 2 or 3 years unless it was really intolerable. Like the employer demanding that I do something that totally offended my morals, commit crimes that could land me in prison, or something of that sort.

    Because: (a) I don't want to make a snap judgement. Maybe the first week or first day on the job looks really bad, but if I gave it a few months things might get better. I routinely find that new jobs are tough for a while because it takes time to build up credibility, so at first my opinions aren't particularly valued, I'm not given the most interesting work, etc.

    (b) I don't want to get a reputation as someone who job hops. I recall once when I was involved in hiring someone, I saw a resume where the person had three months at one job, two weeks at the next, a year at the next, a few days at the next, etc. And I thought: I don't know if this guy gets bored or frustrated quickly and quits on his own, or if he's lazy or dishonest or incompetent and is quickly fired or forced to leave. But either way, do we want to hire him? No. I threw the resume away. I mentioned it to my boss at the time, and he commented that if someone had one such short job on his resume, okay, he took a job and then realized it was a mistake. No big deal. But when ALL his jobs are like that? The problem is not the job: it's him.

    I once left a job after 6 weeks. Why? I received a job offer paying $19K per year more!

  • eric bloedow (unregistered)

    mostly unrelated, but it stuck in my head: in a multi-player game, there were "gold spammers", who did nothing but send in-game messages advertising illegal gold-trade sites... and their usernames were "asdfasdf" and "sdfasdfa" and "dfasdfas" and so on...

Leave a comment on “Security by Obsqwerty”

Log In or post as a guest

Replying to comment #:

« Return to Article