I'll summarize it: "We don't understand cancer but we'll keep throwing shit at the wall until something sticks, and we're going to write up a bunch of shit and you shits read it so we can pay for throwing more shit."
312 karma · joined December 13, 2010
I'll summarize it: "We don't understand cancer but we'll keep throwing shit at the wall until something sticks, and we're going to write up a bunch of shit and you shits read it so we can pay for throwing more shit."
Weighted shortest path algorithms are regularly used in the freight forwarding space in order to calculate the rates paid for routes. Knowing it off the top of my head is how I got a job at a medium-sized commodity trader. Seeing those rooms full of people securing transport for goods we either owned or were moving for others is what makes me think it could be a reasonable idea.
Tangentially, this is what the book Frankenstein was all about, the effect of education on different individuals, the most memorable of the monster being educated only formally, presumably by being given 'you showed up ribbons', with no family support structure, and growing up... with a rotten brain.
I think the best thing to focus on is hiring a manager that knows a little bit about the processes you guys use day-to-day. If you're an agile team, ask about agile; a requirement document team, ask about documentation experience. Processes sort of follow some high-level patterns due to the large accreditation bodies that profit from selling their own flavors.
Have they managed QA or been involved with continuous integration and automated testing? What task-management systems have they used? Are they interested in promoting strong architecture, is production support a priority; or ask them to list out a set of priorities related to product delivery, production support, architecture, customer service, which helps with discovering any underlying philosophies more than really giving any direct information. Give an example of a time they resolved a conflict.
Asking about what the technology stack was for the team they managed is always good as well. If they can explain it coherently they weren't just doing performance reviews and checking time logs to make sure people were at their desks.
Just some ideas off the top of my head.
Microservices work fine in some situations, agile works fine in some situations, but until you find that you are in one of those situations trying to bend your deliverables to meet a sprint-cycle or some other nauseating jargon will cause, as you put it, over-complication or just poorly targeted effort. (It can also cause enough stress to dramatically affect your health, I know better than most)
Those moments of solidarity between product and effort are real gems that I've only recognized in hindsight.
I'm also not sure why my comments have anything to do with being an American. I think not swearing at work would be universally good advice. I guess if swearing at work is integral to your identity you may be offended by someone declaring that you shouldn't swear at work. But it's generally not a good idea if you're wanting to optimize your career progression.
Don't call people names regardless of your stance on swearing.
Know the audience, all communication should be tailored to who is listening, you should know if the person(s) you are talking to will tolerate swearing or not.
Swearing and using bad grammar or spelling are probably equal in many regards. Sometimes you can get away with it, but know who you are talking or typing to.
Speaking of "broken" memes.
I used to play SimCity like you, until it got an arrow in the cloud. Improve on that please.
Until then they can and will insert arbitrary rules to their advantage... as they should? Maybe, I dunno, depends on whose ethics you're living by.