After the hello, goodbye and thanks

After the hello, goodbye and thanks

Summary: It's really hard to believe that it was almost a year ago that Larry Dignan was welcoming me to ZDNet to start this Zero Day blog.  It feels like it was only yesterday I was boarding a flight for the RSA Security conference to take the full-time blogging plunge.

SHARE:
TOPICS: CXO, Browser
12

It's really hard to believe that it was almost a year ago that Larry Dignan was welcoming me to ZDNet to start this Zero Day blog.  It feels like it was only yesterday I was boarding a flight for the RSA Security conference to take the full-time blogging plunge.

A year and 700+ posts later, I'm moving on.   Starting next week, I'll be heading back to Ziff Davis Enterprise to be Editor-at-Large/Security at eWEEK.

I'm not very good at saying goodbye so I'll just sign off with a huge thank you to Dan Farber, Larry Dignan, Mary Jo Foley, David Grober and the rest of the crew at this amazing ZDNet blog network.  You guys gave me an opportunity to be part of a kickass team, motivated me to push myself harder and were always willing to pitch in when I needed your help.  I can't thank you enough.

To the readers and TalkBack commenters, you guys and gals kept me honest and on my toes.  I'm very grateful for that.  I'm still at naraine-at-gmail for those commenters who want to continue to make my life miserable :)

The Zero Day blog will be managed by the estimable Larry Dignan and a team of all-stars.  I'll be reading every line of every post.  You should too.

Best,

_ryan

Topics: CXO, Browser

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

12 comments
Log in or register to join the discussion
  • Best of Luck!

    nt
    D T Schmitz
  • A (modified) traditional Irish blessing

    May the information superhighway rise up to meet you
    May the ACL be always at your back
    The powerboost shine warm upon your wires
    The load balancers fall soft upon your last mile
    And until we ping again
    May QoS hold your packets in the hollow of its cache.

    Good luck! ;-)
    MGP2
    • That's a classic (in a geeky way)

      I hoist a Guinness up to you.
      Larry Dignan
      • Ankyouuuu...

        "Ankyouverrrrmuch", he said in his best Elvis. :-)
        MGP2
      • Aye! Brilliant Man! Brilliant!

        nt
        D T Schmitz
  • Ryan, a good fortune to you

    Yes, a snap-back from time to time, as you say, to help in balance.

    I think actually that you have done a quite good job, and was in fact just thinking for you today that any problems must be in keeping a sense of perspective, when you are looking constantly at what seem 'failure' in the world.

    Actually, I think much of it is just development. Protecting against the level of deviousness present this year simply wasn't necessary for many years. I don't appreciate many things about Microsoft for an example, but their problems in security are like their problems everywhere: a studied dullness in design approach and thinking about relationships.

    What will improve them and all of us is more waking up. I hope you find a way to contribute to that, real development in the world, at eWeek, and can watch carefully to see that you don't find yourself getting jaded. The great danger that is for journalism, and journalists, am sure you will see.

    So, best fortune, truly, and enjoy all the intelligence you can develop, in your field.

    Kind regards,
    Clive (also a certain breeze in Yew trees)
    Narr vi
    • and a going-away present

      as I just noticed a group of squirrels chewing on one of the Apple messages.

      Ryan, it's very late over here (Switzerland), so just a short thought, and I will speak in generalities, even as aware of exceptions, because that approach is a pretty good fit here.

      Then to say, I at least have yet to see any of these exploits that is not effected by a simple buffer-overflow. There may be some others, but certainly overflows are the big game.

      How can this be, when we've had easy tactics to completely avoid the possibility of buffer overflows for more than 20 years?

      Ryan, the problem is that even most 'expert' programmers have not understood much about what they are doing for many, many years. Perhaps this could be due to a peculiar style in which 'computer science' has been taught from its inception, as a kind of failed wing of mathematics. Practical things are looked down upon, and students are let loose without any proper idea of understanding depth and dimension in what they are doing.

      I made a pretty good living for some years, while developing another career, as the kind of consultant that does not come from Accenture - independently, ad at Bell Labs, at BBC, at many industry-serving houses. The number of software people met who actually understood multithreading, or indeed how to use objects to solve problems automatically of this buffer-overflow type, could be counted on one hand, at most.

      So, no, there was not responsibility attached to the design and implementation of these many products which now suffer; and yes, practices often called 'management' are very often also to blame. No leadership to speak of there, as a general case, and with intent to be kindly and accurate, not rude.

      So what you face today is like the Y2K problem: the issue is literally everywhere. I suppose that besides the parameter shakers, a compiler-like approach is the real answer to at least part of the problem, and I'm surprised someone hasn't come forward with runaway success there yet.

      From your view, I think you can help share the ideas and knowledge that will lead into a new generation of both function and safety. I feel that you can do this a lot better by understanding, and that this understanding will help you to keep a head that's wiser, because it doesn't get caught in emotional traps.

      For counter-examples, I think you know at least two places to look.

      So, simple advice. Talk to the best people you can find, always, and understand that they really will be few. Then your own careful thoughts, and you can really contribute - the evidence has bee there also in this year of your column, and that you can grow. I don't think they will easily fill in for you.

      Again, kind regards, and good fortune, Ryan. I will probably have to change the station to get the important information, so don't be surprised if you see a name there.
      Narr vi
  • Best of luck

    Even though I have not contributed much in feedbacks, I have read your blog with great interest for the last few months and liked it, even though in many cases did not agree with your point of view.
    Best of luck
    nilotpal_c
  • Fare well, Ryan

    .
    Thanks for all you have done in this blog.
    TechExec2
  • farewell and good luck in all you do you will be missed

    farewell and good luck in all you do you will be missed
    SO.CAL Guy
  • Thanks for the memories

    Ryan, the year's gone by so quickly. It was a pleasure reading each of your 700+ posts this year, and I look forward to seeing you at eWeek.

    Best of luck.
    Your friend,
    Pete
    petevosspr
  • Au revoir ...

    ... thanks for your work:-)
    Thought I was safe until starting to read your column :-(
    jacksonjohn