Actions
Forum Thread Details
  • Locked Locked
  • Replies 59 replies
  • Subscribers 628 subscribers
  • Views 4284 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What’s the worst mistake/problem you’ve made during a project, and what did you learn from it? We are asking e14 in our Join, Share & Win Competition

E14Alice

Hello Everyone!

Hope you are all doing well. I’m excited to announce that this month's AskE14 question is: What is the worst mistake or problem you've encountered during a project, and what did you learn from it?

Sharing your experiences can help others identify similar challenges and understand how to overcome them. I hope this discussion will be beneficial for those who are just starting out on a project or feeling stuck with a problem.

Here's the question:

What’s the worst mistake/problem you’ve made during a project, and what did you learn from it? 

imageimage

Competition Details

You'll have to be a member of the element14 Community to join in and take part in this “Join, Share & Win” challenge. It's simple, all you have to do is:

1. You need to make sure you are Register  or Login
2. Then answer the following question by adding a reply or commenting!

What’s the worst mistake/problem you’ve made during a project, and what did you learn from it?  

The Community team will then select the best 3 answers to win a Raspberry Pi 400!

This month, we are giving away:

image

Learn more

Terms and Conditions 

imagePDF

Winners 

  

 

 

 will be in touch shortly regarding the prize 

Parents

  • Here is my story from a project in Sweden that I will never forget.

    It was 11 PM in Stockholm. I was finally in bed after two hard weeks installing the ticket system for the Arlanda Express train. Everything was working perfectly.

    Then, my phone rang.

    My boss in Spain was very nervous. He had forgotten to change the "subnet mask" of the X.25 gateway for credit card payments. He was afraid of a big financial penalty. He asked us to go to the airport immediately, change the mask, and not tell anyone.

    We were exhausted and did not think clearly. We forgot to ask the most important question: “If the mask is wrong, why are payments already working?”

    Because of the pressure, we drove through the snow to the station, changed the configuration, and left. We did not perform any tests.

    At 5 AM, as I got home, the phone rang again. It was the railway's Head of Technology. The station was open, the morning rush had started, and no credit card payments worked.

    I explained that we had changed the subnet mask. He didn’t get angry; instead, he was surprised. He told us that he had also seen the problem earlier and had secretly changed his own system to match our "wrong" configuration so the launch would work.

    Both of us made secret changes to "fix" the problem, and that broke everything.

    What I Learned:

    • Transparency is key: If we had communicated, we would have known the other side was already updated.
    • Don’t work when exhausted: When you are tired, you miss the obvious.
    • Always test: There is no such thing as a "small" change in a complex system.
    • Question the "fix": If the system is working, ask why before you change anything.
  • in reply to javagoza
    javagoza said:
    It was 11 PM in Stockholm

    Make sure when you write your memoirs you call this chapter "It was 11PM in Stockholm.".... and don't forget   I want the movie rights to that Northern Africa Marijuana scheme you got tied up in.  Wink 

Reply Children
No Data