Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


bryanedds bryanedds An ​individuali​st is he who is saving himself from all those who are saving the world.
  • New Channel 9

    So, do we post bug reports about Microsoft Connect on Microsoft Connect?


    And if so, does that make it meta-circular... or merely self-hosting?

  • What Would Make Channel9 Bigger Than Kanye...

    Sven Groot said:
    SlackmasterK said:

    "What the heck is a Kanye?


    Oh yeah, I went there."

    Went where? I honestly have no idea who or what Kanye is.








  • What Would Make Channel9 Bigger Than Kanye...

    Charles said:
    bryanedds said:

    Of course, the usefulness or productivity guarantee in higher order abstraction (like most programming languages and runtimes) is that the programmer (composer)  designing applications  doesn't need to describe  the innerworkings of underlying system at design time, though it never hurts to understand the breadth and scope of the capabilities afforded to you by some  runtime like the CLR or JVM or...


    You don't always need to grab hold of the reigns of the machine to ride a horse. Sometimes you do.


     Just saddle up to the right pony for the right show, pardner.


    Pass the SAL, HAL.


    Not to be argumentative with the man who can produce Herb Sutter... Wink


    ... but when it comes to the domain of real-time embedded software, knowledge of how the code directs the underlying machinery is paramount.


    As I like to say, performance is the ultimate abstraction leak! Big Smile


    (Not that I'm at all happy about it. I'd rather just blithely concentrate on the domain code and write everything in OCaml... er, F#. But such is the limits of the little space in which I reside! Accordingly, I do plan to be bald by 30.)

  • What Would Make Channel9 Bigger Than Kanye...

    Charles said:

    How about, next time he's in town, I interview him. And, how about a lecture series with Herb? It's all very possible. I'll ask him (again).



    EDIT: Mail sent.



    And.... I just drooled all over my keyboard Big Smile


    Man, if you can get him on a series... phew.


    Hopefully he can take us all the way down to the hardware to understand what a true burden our naive C# / VB / C++/ CLI / F# code foists on the poor underlying processor and memory architecture. Perhaps especially on embedded devices like the Windows Phones.


    With so much abstraction that we take for granted nowadays, it may be imperative that we to get back down to the metal to keep the consequences of our code in perspective Smiley

  • What Would Make Channel9 Bigger Than Kanye...

    Okay, get this...


    Herb Sutter.


    On efficient programming.


    Or advanced programming techniques.


    Or anything to do with modern programming at all!


    Head asplode.


    He did one of the greatest presentations on efficient programming I've ever seen -




    Herb Sutter... I've never seen Sutter talk without walking away a more thoughtful programmer.


    So, what do us 9'ers have to do to get Sutter on the screen?


    You say it, I'll do it!

  • Code Review 101

    ScanIAm said:
    bryanedds said:

    Because of the dynamics of the work that we do, it is possible that you might be pulled off of your current project to help another project meet a deadline.  The only way that is possible is if all of the developers follow some pretty specific architecture and coding guidelines.  


    Consultants shouldn't be learning on the job, they should alreay know what they are doing.  I see your point about the learning process, but we see code reviews as moments where I teach you not to do something wrong and you learn not to do it again.



    In practice, of course, you're right.


    In the abstract, the problem is likely intractable. Imagine what a disaster it would be if some international body tried to contrive and impose a world-wide coding style Smiley


    Perhaps it's wisest to pull a Poppendieck and defer to the teams to elaborate their own coding conventions.


    If there are many teams in a company, you can extract what's common from the various conventions and place them into a company-wide standard.


    There is no generalization like a posteriori generalization!

  • The Sysiphus Economy

    ScanIAm said:
    bryanedds said:

    It isn't for everyone, but consulting is a decent way to shove a bunch of knowledge into your head and give you a decent challenge.  W3bbo's description of the potential boredom in some of the available has as much to do with his talents as it does with his lack of working in those potentially boring environments.*

    If I told you the purpose of the software I've been working on for the last year, your eyes would have more glaze than the drainspout at Krispy Kreme Donuts, but I can guarantee that the coding involved in providing that purpose has been the most challenging I've ever had to write. 


    That said, I've also been involved in the hiring process with my company, and what we've found is that many prospects:

    1) lie about their experience

    2) haven't made any effort to keep current in the technologies of the time

    3) expect that they will not have to actually think or create

    4) have the personality of a petulant rock.


    Of all of the above issues, #2 is the worst.  If you are out of work, you'd better be learning new tech.  Otherwise, what ARE you doing?


    If you are having problems finding work, I can't guarantee a job, but I can, at least, get you to to a first interview.  Contact me through this site.


    *ps I hope W3bbo doesn't think this is a dig at him, personally.  I loves me some W3bbo and I'm jealous of his skills.


    Hi Scan!


    That's really great to hear Smiley


    As to number two, I found that the most surprising. To me, one of the upsides to being out of work is the ability to catch up on recent advancements and even learning about new languages like Lisp(s) and Ruby and Haskell and so on.


    I'd contact you, but I'm not sure what you mean by 'contact me through this site'. There doesn't seem to be a messaging feature on Channel9. You can e-mail me your contacts via bedds@redsword.com if you don't mind.



  • Code Review 101

    I have at times tried to explain to my fellow engineers that no amount of standards will keep an inexperienced programmer from writing bad / ugly / broken / unreadable code. They will always find a way to hurt themselves, and that's okay. It's a learning experience. All you can do is keep a close watch on their check-ins and help them understand better ways of expressing their intentions during code reviews.


    It doesn't seem possible to legislate good coding style. Good style takes mentoring, experience, and a lot of practice. Most of all it takes the freedom to expirement and even fail. There doesn't seem to be any shortcuts. By over-legislating, you'll at best force everyone to use a mediocre and overly verbose style that is outmoded in a couple years. The difficult thing is that it can keep your mids and seniors from improving and evolving their personal expression techniques.*


    For a reasonably common sense set of coding standards, I personally use Sutter and Alexandrescu's C++ Coding Standards. For .Net work, I use the applicable parts of that plus .NET Framework Design Guidelines.


    *Of course, the way I personally handle things as an incoming employee is to conform without a fuss. There is a tremendous amount to be said for consistency, in my personal experience.

  • Code Review 101

    Sven Groot said:
    blowdart said:

    Or if, for, do, while... or any control flow, really. Tongue Out

    I dislike SESE because it requires spurious mutable state and hard-to-decipher arrow code. Most terribly, it obscures a key code smell.





    If you discard SESE, you'll find that %95 of the remaining method sub-scopes (uses of { } within a method) can be profitably factored away with 'extract method'.


    By discarding SESE and factoring away sub-scopes, your code will be much cleaner. In a 15kloc C++ project, for example, I have only ten methods with sub-scopes. The average method is 3 - 4 lines long.


    In absense of SESE's artificially-imposed constraints, you will discover that sub-scopes are a serious code smell that generally needs to be factored out. In the presense of SESE, such a smell is badly obscured with obligatory arrow code.


    And don't even get me started on unecessary mutable state! Fuggetabowtit!!!




  • The Sysiphus Economy

    Ray7 said:

    As someone has already said, make sure your CV is available on as many job sites as you can. And keep it lean; only relevant stuff. Don't make recruiters wade through pages to see what experience you have.


    And take anything that is relevant, even if it's not your dream job. Blank months in your CV never look good. And yes, think about taking volunteer work. Aside from giving you a nice fuzzy feeling, it'll keep the CV moving and it might lead to something else.


    Hey Ray7,


    Good advice! Fortunately, I've been a partner with a start-up company for the past year, so while I've have no real income from it, I do have something on my resume to show for it. We will ship another game shortly, so having another released commercial product under my belt probably means something to someone out there.