Forgot your password?
typodupeerror

Comment Requirements (Score 1) 265

I once had a Millenial Agile Acolyte mocking tell me that "Requirements are Waterfall, and we are now Agile..."

I responded in our daily standup with a story from Neil Postman:

A village in Estonia in the 1800's had a problem: a disease was running through the villages that caused you to either get flu-like symptoms and die, or get flu-like symptoms, APPEAR to die, and suddenly recover 3 days later. The villagers decided they needed to fix this problem, so they broke up into two groups to brainstorm.

At the end of the brainstorming session, both groups proposed a solution. Group 1 said, "We have a solution! We will put a tube next to the tombstone that will run into the ground into a hole in the casket near the victim's head. Through the tube, we will place a cord with a ring on it that connects to a bell attached to a metal bar next to the tombstone. If a victim wakes up in the casket, the victim merely need grab the ring and tug, which will ring the bell. The nightwatchman will hear the bell, alert the villagers, and they will all run out with shovels to exhume the living victim.

The (probably Agile) team... (you know, "Fail Fast, Fail Often") proposed a different solution... "We have a better answer! We propose that we mount on the lid of the coffin an 18 inch stake, positioned directly over the victim's heart..."

So what was the problem? Requirements. The first group tried to answer the question, "How do we make sure we don't bury and kill someone who is still alive?" The second group tried to answer the question, "How do we make sure everyone we bury is already dead?" The requirements SOUND similar, but they produce quite different outcomes.

So it seems requirements are kind of important after all.

Comment Laid off 2nd Time as Dev at 49 (Score 4, Interesting) 123

I was a software dev with 25 years of experience in lots of in-demand languages like C++, Python, JavaScript, CUDA, etc. In 2015, I was sitting at my desk, waiting for the daily standup, when the CEO tapped me on the shoulder. He said he wanted to speak with me in the conference room. I knew it wasn't good, because we had been burning through money like there was no tomorrow. When I entered the room, our usually jolly VP was silent, staring forward. Our president looked very somber. The HR lady was CRYING with a box of tissue in front of her. They laid it out for me. I had two choices: 1) take a two month severance, 2) take a job with the same pay and benefits with the parent company downstairs. Being an empty-nester with two kids out of the house, but a wife to take care of, I took the latter. It took me one week to figure out how much I hated being a "Performance Lead Engineer" and how much I hated the parent company.

I had already decided to dip my toe into the waters of cyber security by taking courses and going for my CISSP and maybe my CEH. On the first night of the "Cybersecurity Fundamentals" course at the local U, the instructor mentioned he had his own company. I asked if he was taking resumes. I got my first interview two days later, and I was hired three weeks later. Two and a half years later, I was the CTO, leading penetration testing of all sorts (including physical engagements) and being responsible for the pentesting architecture and processes.

Now, I'm a Red Team Lead at an insurance company, and I do side-gigs (with full knowledge and permission of the company). Being a software dev (with some QA and Linux/Windows admin experience) turned out to be a "secret weapon" in learning how to do pentesting.

The youngsters are amazed that I have over 20 certifications in pentesting / red-teaming, and I have no intention of slowing down. I'm having way more fun than I ever had doing coding... or rather, software dev. (I agree with a buddy that "coding is fun, but software dev usually sucks, because it is usually driven by those who don't understand it").

Leverage that experience to do what you want and what you enjoy.

Comment Three things... (Score 2) 118

Three things I had to explain to my Korean wife when we got the states (that she could just not fathom...)

1) Open Book Tests
2) Curving the Grade (in Korea, you get what you get... doesn't matter if the whole class gets "F's")
3) A 40-hour work week.

35 years later, she STILL works 70 hours a week plus. I can't get her to slow down.

Comment While in the US Air Force... (Score 1) 95

DOOM came out after CW 3D (there was a 2D side-scroller that came out when I was in high school) while I was in the USAF. I was walking among the cubicles, when I saw two of my compatriots playing DOOM on their USAF-issued computers. I said to them, "You guys better knock that crap off before the LAN shop catches you!"

To which they responded, "Who do you think we are PLAYING?"

Back when the Air Force was fun.

Comment Britney Spears (Score 1) 59

I worked with a guy that once submitted a bug report to Sun where their workstations would have their CD players EXPLODE when one put in a certain Britney Spears CD. It seemed far-fetched, but it was repeatable. It turned out that the CD also had some kind of interactive content that would start up when the disk was inserted. The Sun workstation couldn't deal with that, because the CD would spin at an unexpected rate, then faster and faster until the disk shattered and the drive door flew across the room.

The guy is an absolute legend in my town... it seems like all techies who work here have heard of him.

Slashdot Top Deals

Air pollution is really making us pay through the nose.

Working...