archcoder

Taking {nerd life balance} one day at a time.

  • Home
  • Nerd Life
  • I Am Dev
  • Let's ChatGPT
  • Projects
  • Developer Parables
  • Resume
SubscribeFeed icon Facebook pageFacebook icon Twitter pageTwitter icon
  • Sign up
  • Sign in
archcoder © 2025
Published with Ghost and Paperleaf

Engineer for Serendipity

The title of this post is a quote from Roy T. Fielding (he had a hand in creating the HTTP 1.1 spec [http://www.w3.org/Protocols/rfc2616/rfc2616.html] in 1999, basically defined / put into words the architecture and behaviors of the internet as a hypermedia system – REST »

Web dev - Back to the basics

Some of the most important aspects of creating web based API, or any web based application is messaging and behavior - user experience. Back in 1999 when the HTTP 1.1 protocol was defined and the HTML 4.0.1 spec was released the web began to get more lively. »

Fearlessly tweak IIS

I find that I wreck my development machine often, either because I over-tweak or because I a messing with something that I have never messed with before. IIS on Vista / Server 2008 is one of those things where messing with it outside of the configuration interface can really jack things »

RESTful architecture simply explained

I can't believe I missed this gem that Roy T. Fielding [http://roy.gbiv.com/] put out in October! If you're not up for reading the monster dissertation [http://www.ics.uci.edu/%7Efielding/pubs/dissertation/top.htm] at least read this post [http://roy.gbiv. »

RESTful thoughts - OAUTH and statelessness

I keep a copy of Roy Fielding's 162 page dissertation [http://www.ics.uci.edu/%7Efielding/pubs/dissertation/top.htm]in my laptop bag, yeah I know - ich bin ein nerd, but hey it only adds another 2~3 lbs to my bag and I like rules »

RESTful thoughts - Why ASP .NET MVC?

Let me begin by building the frame of how we approached the idea for a new API before I go into the details of the technologies we chose. We needed an API that would address the following: 1. Secure 2. Follows common community standards / practices 3. Public interface 4. Extremely »

Automating - 7 Controller actions with Visual Studio templates

I am not big on repeating code or typing more than I have to. So, as I started adding entities to a RESTful API (which is built on .NET MVC) I quickly saw a need for automation. It seemed that I was almost always building out my controllers using the »

WS-Deathstar how I hate thee

WS-Deathstar how I hate thee

Long ago, in a web far, far away Microsoft brought us .NET SOAP (JAVA the Hut was also part of the SOAP movement) propagating WS-* ("Deathstar [http://en.wikipedia.org/wiki/WS-*]") principles and practices. The WSDL [http://en.wikipedia.org/wiki/Web_Services_Description_Language]entered into »

RESTful thoughts - versioning

RESTful thoughts - versioning

I've done a lot of thinking on versioning for an API [http://experience.fellowshipone.com/blogs/intelligentdesign/archive/2008/06/14/dc08-restful-rewind.aspx] I've been working on. I feel that the mystical nature of API versions should not be the last consideration of an API implementation »

Burnt toast and expired milk

Burnt toast and expired milk

I was marveling at the mysticism of software dev yesterday when I stopped by to talk to our scrum master about some technical debt we've accumulated. After talking to him, I realized something... Software is a product with a shelf life, but often times we forget to put »

Arrow left icon Page 7 of 7
archcoder © 2025
Published with Ghost and Paperleaf