4 ms·

I would add one thing: get to know HTTP. Even a basic understanding will prevent you from making costly mistakes.

by nathanwdavis 16y ago

grayhairmomma 16y ago
Great advice, all. The HTTP protocol skill is something I didn't even consider.
- rchiba 16y ago
  ATM Machine. PIN Number. HTTP Protocol.
  - nathanwdavis 16y ago
    For the less technical it sometimes helps to qualify what something is even if it is embedded in the abbreviation. But considering the audience here, you're right. I will remove the offending word.
  - bluesnowmonkey 16y ago
    You're playing with the capitalization. Gopher protocol. DNS protocol. IRC protocol. HTTP protocol. HTTPS protocol. All fine.
  - cromulent 16y ago
    RAS Syndrome. http://en.wikipedia.org/wiki/RAS_syndrome http://en.wikipedia.org/wiki/RAS_syndrome
takameyer 16y ago
Any recommended resources on getting a good foundation for HTTP?
- jamesbritt 16y ago
  http://www.w3.org/Protocols/rfc2616/rfc2616.html http://www.w3.org/Protocols/rfc2616/rfc2616.html
- gbog 16y ago
  Chris Shiflett wrote a good HTTP handbook, I recommend his blog too. (typing from phone, pasting url not easy)
astrofinch 16y ago
What are a few costly mistakes that can result from lack of HTTP knowledge?
- johnny22 16y ago
  not designing with REST in mind
  - gwtw 16y ago
    oh this is getting TIRING ...
  - DrJokepu 16y ago
    Why is that a costly mistake? REST is great but it's not the only way to do web development. Read up on continuations, for example. In fact, this very website is using continuations (check out how paging works) and it doesn't seem like a costly mistake.
- ericflo 16y ago
  I've seen a number of times when people don't understand the statelessness of HTTP, and try to put megabytes of data in a cookie-backed session--unable to understand why that doesn't work, etc. This is especially prevalent in .NET land, where there are mechanisms for storing data in hidden forms and hiding the statelessness away from the user.

I would add one thing: get to know HTTP. Even a basic understanding will prevent you from making costly mistakes.

grayhairmomma 16y ago

Great advice, all. The HTTP protocol skill is something I didn't even consider.

rchiba 16y ago
ATM Machine. PIN Number. HTTP Protocol.
- nathanwdavis 16y ago
  For the less technical it sometimes helps to qualify what something is even if it is embedded in the abbreviation. But considering the audience here, you're right. I will remove the offending word.
- bluesnowmonkey 16y ago
  You're playing with the capitalization. Gopher protocol. DNS protocol. IRC protocol. HTTP protocol. HTTPS protocol. All fine.
- cromulent 16y ago
  RAS Syndrome. http://en.wikipedia.org/wiki/RAS_syndrome http://en.wikipedia.org/wiki/RAS_syndrome

takameyer 16y ago

Any recommended resources on getting a good foundation for HTTP?

jamesbritt 16y ago
http://www.w3.org/Protocols/rfc2616/rfc2616.html http://www.w3.org/Protocols/rfc2616/rfc2616.html
gbog 16y ago
Chris Shiflett wrote a good HTTP handbook, I recommend his blog too. (typing from phone, pasting url not easy)

astrofinch 16y ago

What are a few costly mistakes that can result from lack of HTTP knowledge?

johnny22 16y ago
not designing with REST in mind
- gwtw 16y ago
  oh this is getting TIRING ...
- DrJokepu 16y ago
  Why is that a costly mistake? REST is great but it's not the only way to do web development. Read up on continuations, for example. In fact, this very website is using continuations (check out how paging works) and it doesn't seem like a costly mistake.
ericflo 16y ago
I've seen a number of times when people don't understand the statelessness of HTTP, and try to put megabytes of data in a cookie-backed session--unable to understand why that doesn't work, etc. This is especially prevalent in .NET land, where there are mechanisms for storing data in hidden forms and hiding the statelessness away from the user.