Celebrating 60 episodes we take live calls from our audience and chat about the topics are their minds. Then we follow up on the indie developer Xbox One situation, read your feedback, and more!

Thanks to:

GoDaddy.com Use our code coder249 to get a .COM for $2.49.

Direct Download:

MP3 Audio | OGG Audio | Video | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

Feedback

• Nehemiah and many others agree that Canonical should buy System76, or launch an effort that focuses on desktop.

Call in Ground Rules

• One call per person
• One or 0 plugs per person
• Keep tech questions broad

Missed your chance to call? Leave us a voicemail:

• 1 (425) 374-4847

Call in Topics

• Ubuntu Edge
• Web dev platforms
• Apple outage
• Your dev workflow
• JavaFX
• PHP
• Azure
• Unity3D
• More

Follow UP:

• Microsoft to allow indie self-publishing on Xbox One, retail consoles will double as debug units

Each $500 unit purchased at retail this holiday will also run in-progress game code, enabling developers to get in on the action all the more affordably (debug versions of game consoles cost far more than retail game consoles, and tend to look slightly different from their retail counterparts). \”Our vision is that every person can be a creator. That every Xbox One can be used for development,\” Xbox corporate VP Marc Whitten said in a statement.

Book Pick:

[asa]0759285780[/asa]

Follow the show

• Email the show
• Join the Coder Radio Subreddit
• Live Monday 9am PST
• Music by: Ronald Jenkees
• Mike on Twitter
• Mike on Google+
• Mike’s website
• Chris on twitter
• Chris on Google+

The post Call In 2.0 | CR 60 first appeared on Jupiter Broadcasting.

From text editors and compilers to Project management tools Mike shares his toolchain for getting projects done.

But we start with fending off the trolls, trouncing Chris over the OYUA, and struggling with nuances of an open sources ASP.NET.

Plus defending a dev underfire for speaking his mind, and we answer a batch of your emails.

Direct Download:

MP3 Audio | OGG Audio | Video | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

— Show Notes —

Feedback

• Jeramy writes:

“Michael failed to mention that Microsoft released ASP.NET to the open source community and now ASP.NET can be run on any server with any database management system.”

• John shares his sister’s web-based calendar: www.keilascode.com
• Folks love the SNES generation

Hoopla

• Aaron Seigo – Google+ RE: In Canonical\’s recent announcement

• Heroku | Cloud Application Platform

Pick of the week

[asa]B002KO9JB0[/asa]
[asa]B001HBCVX0[/asa]

Tool of the week

• Ruby Mine

Follow the show

• Email the show
• Live Monday 9am PST
• Music by: Ronald Jenkees
• Mike on Twitter
• Mike on Google+
• Mike’s website
• Chris on twitter
• Chris on Google+

The post Gandalf the Whiteboard | CR 37 first appeared on Jupiter Broadcasting.

Mike and Chris discuss Mike moving away from Rails and just what the Hell has happened to Rails in the past few years. If you are running or supporting an older Rails site, this is a must listen!

Plus Chris changes his tune a bit on the OUYA, Mike has some thoughts on Java Play, and we answer your emails!

Direct Download:

MP3 Audio | OGG Audio | Video | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

Show Notes:

Feedback

• The Blackberry fans are out in force… Stanko, one of them, shares his FREE BB10 game: https://appworld.blackberry.com/webstore/content/20385954/?countrycode=US
• Sean is “interested in how we feel about writing init scripts in Python” He also welcomes (constructive criticism) regarding his scripts: https://bitbucket.org/sean_m/atlassian-scripts
• Michael says that the current version of NetBeans is “a pretty awesome tool for Java, JavaScript…”

Dev World Hoopla

• OUYA Will Be on Annual Release Cycle
  
  [asa]B0050SZD18[/asa]

Rails Security Check

• Mass assignment bug
• There is no security only YAML

• What the Rails Security Issue Means…

• The FUDless bottom line

• Sinatra

Tool of The Week

• IntelliJ 12

Follow the show

• Email the show
• Live Monday 9am PST
• Music by: Ronald Jenkees
• Mike on Twitter
• Mike on Google+
• Mike’s website
• Chris on twitter
• Chris on Google+

The post Off the Rails | CR 36 first appeared on Jupiter Broadcasting.

When is the time right to launch your project? Mike and Chris discuss how understanding your market can be key to answering that question, building a community, advertising, and when to just ship it.

Plus: Things to tell your IT guy, QA war stories, and a batch of your feedback!

Direct Download:

MP3 Audio | OGG Audio | Video | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

Show Notes:

Feedback

• New Coder wants to when he is considered to “know” a language.

• Luke asks:

“How is it you come to figure out the right tools (languages) for the right job, and once you do that, what\’s the anticipated \’study time\’ that needs to go into learning to use the language well enough to feel like you can actually do what you\’ve set out to do?”

• Eric shares a development contest

• Hayden wants to know what I think of JavaFX

• mdominick.com – Give Duke a Break

Brian’s War Story

Hello Michael and Chris,

I work in a medium sized development shop with about 20 developers working on what\’s essentially an enterprise client side app. I have always considered our process for releasing bug fix updates as being rather backwards and poorly executed. Essentially our head of \”QA\” will send an e-mail one morning to all developers that the code is \”frozen\”.

He will then do a build, test it for 4 or 5 days and then send an e-mail to everyone that the code is \”unfrozen\”. During this \”frozen\” time the developers are still expected to continue fixing bugs but rather than check in their changes they are supposed to \”sit\” on them, usually for several days, until the \”unfrozen\” e-mail is sent out. At this point a free-for-all of code check in commences with all sorts of conflict and collision shenanigans.

That said, there is nothing physically restricting the checking in of code. If a developer doesn\’t see the \”fr eeze\” e-mail or simply forgets after a few days then \”QA\” unleashes their wrath on the poor sod. I\’m sure you can see all sorts of problems with this joke of a build/test/release process and I am even a little embarrassed just describing it. I would like to offer some suggestions to my superiors about ways to improve this and was wondering if you guys had any thoughts or suggestions.

One, perhaps obvious idea would be to switch to using Git as we are still using the ancient CVS for source control. However I\’m still very much a novice and trying to learn it better in my spare time. How would you suggest to use Git in a way that we can improve our build/test/release cycle? Do you have any other thoughts or suggestions to bring our release cycle up to a more sane and reasonable, not to mention modern process?

Thanks for your thoughts and thank you for the awesome show you do each week.

Sincerely,
Brian M.

Launch!

• How do you know when your project is ready to launch?

• Is this really a bug?

  • Bug? or new feature?

• Do I have to be 100% bug free to ship?

  • Is that even possible

• What market?

Follow the show

• Email the show
• Live Monday 9am PST
• Music by: Ronald Jenkees
• Mike on Twitter
• Mike on Google+
• Mike’s website
• Chris on twitter
• Chris on Google+

The post Just Ship | CR 33 first appeared on Jupiter Broadcasting.