(no title)
richardbrevig | 5 years ago
But you're right, and I've done that myself. Where I hated a job so badly and just pretended and smiled as much I could until someone hired me out of that situation.
richardbrevig | 5 years ago
But you're right, and I've done that myself. Where I hated a job so badly and just pretended and smiled as much I could until someone hired me out of that situation.
quickthrower2|5 years ago
The problem is i didn’t realise there is really no way to tell what a job wi be like until you’ve done it for 1-2 years! Therefore if you think “oh i really want to work for them because they are offering a good job” that’s the weakness I had - in reality you can’t put stock into how good you think it will be. They are trying to sell you on working there after all. By not putting stock into it “ah this is a another job I’ll do my best work but it may turn out shit might be good” then you can emotionally walk away from their offer more easily, and ask for caveats. “Can I move teams if I decide I don’t enjoy the first team after 6 months” and stuff like that could be negotiated before starting. Oh and get it in writing I’ve been burned by verbal “miscommunications” before.
And finally I’m going to say “Haskell Tax” is a thing and similar dynamic plays here. They might be the only shop in town offering a Haskell job but if you make it look like you have other options “I applied for a blockchain job too. It’s c++ and Scala not Haskell but the tech looks really cool” then you don’t appear to need them as much.
wtracy|5 years ago
I learned this the hard way: Do not let the technology stack be the deciding factor in which job you take.
Skipping the Cobol job is reasonable. Picking the only Haskell job because it is the only Haskell job isn't.