• Richard (unregistered)

    Frist; but possibly because I decided TL;DR

  • Nathan (unregistered)

    Possibly the best part is that reading through those transcripts were fairly entertaining WTFs in and of themselves.

  • Kevin (unregistered)

    Stop the podcast idea. It was painful trying to read your script. In 30+ yrs in the workforce I have never encountered such poor articulation of ideas. I imagine it would be extremely difficult to understand your code comments. Scary to think that some unfortunate developer would have to support your code.

  • Pawel (unregistered)

    This is horrible. I'm not going to listen to a podcast at work and at home, well, I'm at home, I don't want to deal with this stuff. That transcript is undecipherable, BTW.

  • Remy Porter (google) in reply to Kevin

    Honestly, try listening to it. The dude on Fiverr didn't exactly do a great job writing the transcript. We're going with a more expensive, but higher quality, service next time.

  • Eric Lizotte (google)

    Its tough to come up with a good buzzword for that. If we're stuck sticking with the ops on the end, I'd like ConfidenceOps but it seems too long. and ConfOps doesn't sound great. But maybe TrustOps would work. Really though when you talk risk mitigation/managment, it's not so much (in my mind) dealing with the IT operations but with line of business operations. so not sure if it should end with something other than Ops too for separation purposes

  • Eoin (unregistered)

    Ehm, on firefox, at about 4:30 (when your talking about a mass spectrometer) the sound track doubles up for about a minute and once it's done, it's skipped forward to you talking about a websited downloading a thick client? Very confusing. If there was a download link, that would be great...

  • Peter (unregistered)

    The machine generated transcript is like the one that I get from Skype for Business when I miss a phone call.

    The state of the art has improved, but not all that much, and still has a good way left to go (to put it very charitably)

  • Geoff J (unregistered) in reply to Eoin

    Ditto, but using Chrome. I wondered what on Earth was going on when it doubled up, and then after a short while went back to "normal".

    It was indecipherable to listen to or follow.

    Seeing that someone else has had this problem (and on another browser), it seems that the person in charge of production of the audio wasn't paying attention that day, and left another track of a different cut's volume up over the top by mistake. Whoops! Revoke that guy's contract!

  • Barrington (unregistered)

    Can you guys upload this to podcast feeds if this continues? I see in the past you appear to have uploaded to itunes but can you set it up with Google Play Music too perhaps?

  • Rémy Grandin (google)

    I would propose "ZART" as a buzzbord, it would mean "Zero Applicative Bug Target"

    Addendum 2017-02-02 09:07: Zero Active Bug Target would work too

    Addendum 2017-02-02 09:07: Zero Active Bug Target would work too

  • Remy Porter (google) in reply to Geoff J

    That appears to be a glitch with the frickin' Cast editor. I hate that thing. Here's a direct link, and I'll add it to the article:


  • Eric Riese (google)

    I'm having issues subscribing to the feed using BeyondPod, even after having Chrome resolve the link.

    Addendum 2017-02-02 23:45: Works now

  • Joe Malin (google)

    I couldn't follow any of the argument. Sorry, but I don't like this form of podcast as replacement for the blog. If you're presenting something to other people, you need some sort of script. You can have Q & A, you can cover a topic, or whatever, but you can't just riff on each other. Unless your real aim is to avoid communicating anything.

  • A Guest (unregistered)

    I really liked the machine transcriptions of [BREATH] and [SMACK]

  • me (unregistered)

    well i at least thought the angular2 description was great. but i suppose if you're not a js guy then that humor is lost.

  • Link (unregistered)

    Hazard Priority Development as a better term for Software Risk Management. Thanks for the Podcast.

  • other me (unregistered)

    Code is text -- podcasting about coding is like dancing about architecture. Theoretically possible but silly.

  • Kashim (unregistered)

    DangerOps. Everyone wants to work for DangerOps. It has Danger in the name. Lot of solid ideas floated during that podcast.

    For the record: my software department has ended up split into two groups: The Development Team, who does agile work, constantly updates stuff, and does their best to test it, and The Integration Team, who takes their software, puts it on devices, and makes it work with the actual hardware and for specific projects and reports back bugs to the Dev team as if we were users, but before we have alienated our users with a product that doesn't work. The result is a nice mix of saying, "this device will work, and it is the Integration Team's job to make sure that it fulfills all of the project requirements" (a.k.a. good risk management) and "this device has our newest and best software that has all of our newest and most beautiful features on it." I find it to be a nice meeting of both models as we find the borderline between "agile" and "full of bugs that don't have time to be tested".

  • Foo AKA Fooo (unregistered) in reply to Remy Porter

    Fiverr, as in five errors per line?

    Though I do like cross-orange requests. If someone's looking for a new topical username ...

  • Herby (unregistered)

    Risk?? Sounds like risky business to me. Many times I have encountered the "risk" argument, but it seems that nobody ever considers the "risk" of not doing anything, and what that entails.

    Unfortunately there are those who seem to forget that testing is part of the process to verify functionality, and without it the risks are even larger.

  • ok (unregistered)


  • guesty (unregistered)

    "In this episode, Alex and Remy discuss ruining the site"

    Freudian slip?

  • kt_ (unregistered)

    It was a really nice first episode. The idea of risk management in software development/deployment is a sound one and I liked listening to the two of you talking about it.

    A few notes:

    1. It would be great if you used your names once in a while. You have a tad similar voices and before people get used to them well enough they are able to tell them apart, please help us!
    2. It would be nice if you were a bit livelier, especially the first part sounded kinda dull-ish. You know, we can't see you, so the voice has to work alone and that stuff.
    3. A bit too short? I felt that the conversation was ended prematurely, like you had a lot more to say but you had agreed on the 25 mins beforehand, so you didn't want to pass that mark. The best tech podcasts are around 40-60 mins. I know, this could be too much for the first episode, so that's more of a note for the future.

    Overall, I liked it and I'd like to listen to more episodes. It feels like you just need practice, hope you'll get momentum in the next few sessions.

    Thank you guys and cheers! :)

  • I dunno LOL ¯\(°_o)/¯ (unregistered)

    I like how Markdown (?) thinks Remy is a registered trademark.

  • (nodebb)

    A buzz word for Risk Management...

    What we're really talking about here is being responsible enough to put out a product that isn't full of bugs and poor quality. Wouldn't that be "Due Diligence"? Wouldn't a product that was poor quality or a failure be sometimes called a "Dud".

    How about: "Dud Diligence" - "The things that you as a reasonable and responsible developer do to avoid putting out a Dud".

    • Reasonable - you don't need a 1000 page test script for "Hello World"
    • Responsible - you do test for SQL Injection attacks on an application that's accessing a database.
  • (nodebb) in reply to I dunno LOL ¯\(°_o)/¯

    It's not Markdown. Almost certainly the person doing the transcript typed (R) in Word or some similar program and had it helpfully auto-corrected to ®, and either didn't notice or didn't care (or didn't know how to get it back).

  • Merus (unregistered)

    I was looking forward to seeing the knee-jerk negative reaction from the community to literally anything new and they did not... disappoint is the wrong word.

    It's clear some of the commenters didn't even listen to the podcast; one guy is claiming that podcasts about the written word is like dancing about architecture, which was dumb when it was being sniffy about mysic criticism and it's an even dumber argument when about software architecture.

  • löchlein deluxe (unregistered) in reply to Eric Lizotte

    ConOps? Nevermind, I'm not bothering with Mandatory Pod Cast, 'nuff to do.

  • Appalled (unregistered)

    Wonderful News. Now I can stop bothering to visit WTF on Thursdays as well as Fridays.

  • trailmax (unregistered)

    Sorry, don't like podcasts. I read a lot faster then you can talk. Podcast asking 21 minute of my time, but I can read all that in 3-4 minutes. WTF?

  • Steve (unregistered)

    Happy enough with that as a first episode of a new podcast; there are a few random background noises at times? S regards the homework, I suggest ... RiskFarming or UserDrivenCycling

  • JustMe (unregistered)

    "By and large", not "by enlarge". It was originally a sailing term.

  • FooBar (unregistered)

    I enjoyed the podcast, especially for a first episode so keep it up.

    I like ZABT that was proposed earlier, but maybe drop the T and add "App" to the end. I can almost hear execs walking around saying "We're converting to a ZAB App".

    If your soon so budget allows you should look at podcast re-mastering services. I listen to several podcasts that are remastered by Creaky Studies (Declan Quinn) and he does really good work.

  • Rody (unregistered) in reply to Remy Porter

    Your mp3 link is broken in the same way, with overlapping audio of two different conversations.

  • SyntaxError (unregistered)

    Enjoyed it. Had a good laugh. Great content. Sent it to the junior devs, who also liked it.

  • Anonymous Covert (unregistered)

    For anyone going to listen the poadcast: Angular bashing begins around 6:40

  • about:homework (unregistered)

    How about test-I-cal?

Leave a comment on “Episode 1: Traveling Angular”

Log In or post as a guest

Replying to comment #:

« Return to Article