tobiassjosten

6 ms·

1.
The problem with remote teams(vvv.tobiassjosten.net)
1 points by tobiassjosten 12y ago|0 comments
2.
Trading required for easy(vvv.tobiassjosten.net)
2 points by tobiassjosten 12y ago|0 comments
3.
Zero multiplication(vvv.tobiassjosten.net)
2 points by tobiassjosten 12y ago|0 comments
4.
by tobiassjosten 12y ago
So true. Though I think a lot of the insecurity comes from not knowing what is actually the norm. When I started out I thought people were kidding, that it was all a big joke, when they told me their hourly wages. Turns out you actually ne
5.
Charge your clients like a boss(vvv.tobiassjosten.net)
10 points by tobiassjosten 12y ago|4 comments
6.
Tracking with purpose(vvv.tobiassjosten.net)
1 points by tobiassjosten 12y ago|0 comments
7.
Autocompleting language searches(vvv.tobiassjosten.net)
1 points by tobiassjosten 12y ago|0 comments
8.
What do you think of Chaps?(vvv.tobiassjosten.net)
1 points by tobiassjosten 12y ago|0 comments
9.
My professional worth(vvv.tobiassjosten.net)
1 points by tobiassjosten 13y ago|0 comments
10.
PHP REPL for Symfony and Drupal(vvv.tobiassjosten.net)
1 points by tobiassjosten 13y ago|0 comments
11.
RESTify your API(vvv.tobiassjosten.net)
4 points by tobiassjosten 14y ago|0 comments
12.
Blogging schedules(vvv.tobiassjosten.net)
2 points by tobiassjosten 14y ago|0 comments
13.
by tobiassjosten 14y ago
That's definitely an option and to be fair I didn't use any Jekyll plugins up until recently. But my main gripe is still the lacking redirection. I can't lose that ability for this blog and all its accumulated URL fixes over the years. For
14.
by tobiassjosten 14y ago
Varnish would have been fun to play with for a static blog. For one thing you then could use ESI to not have to invalidate the cache as often. But I disagree with one thing — the "git push → deploy dance" is a pro for Jekyll! ;)
15.
by tobiassjosten 14y ago
Glad you like it! Definitely nice when you get to take the time with these kind of projects.
16.
by tobiassjosten 14y ago
Check out Amazon's pricing pages ([1] and [2]) for details. As for resources spent, my own blog has had just over 10k pageviews since Saturday when I launched on S3/CF and for that I'm paying $0.07 (S3) + $0.12 (CF) = a whooping $0.19! Incl
17.
by tobiassjosten 14y ago
Yup! I explain why in my first post: http://vvv.tobiassjosten.net/internet/using-www-for-your-dom...
18.
by tobiassjosten 14y ago
You could probably just slap CloudFront on the existing WP site. Might have side-effects but it would surely bump the performance up.
19.
by tobiassjosten 14y ago
The rate at which these generators pop up is a testament to how awesome they are. I really think you're on to something with the built-in S3 deployment. Any plans for extending it with CloudFront caching?
20.
by tobiassjosten 14y ago
Amen on the Nerd Nirvana! :) Personally I prefer [1] using a subdomain over the bare domain. If your registrar doesn't support www redirection you could always use WWWizer [2]. [1] http://vvv.tobiassjosten.net/internet/using-www-for-your-d
21.
Jekyll blog on Amazon S3 and CloudFront(vvv.tobiassjosten.net)
84 points by tobiassjosten 14y ago|51 comments
22.
JQuery Deferreds promises asynchronous bliss(vvv.tobiassjosten.net)
2 points by tobiassjosten 14y ago|0 comments
23.
by tobiassjosten 14y ago
You could set it up to either accept clients to POST a user to the /users collection, or PUT a user at /users/123. With unknown IDs the latter isn't really viable. This is primarily a matter of idempotence. Several POSTs to /users would cre
24.
Your API is not RESTful(vvv.tobiassjosten.net)
7 points by tobiassjosten 14y ago|3 comments
25.
Google+ and the walled social gardens(vvv.tobiassjosten.net)
1 points by tobiassjosten 15y ago|0 comments
26.
by tobiassjosten 15y ago
I wrote up a few pros and cons on using www a while ago. Basically I think only using the TLD is more pure but in the long run you lose less than you might gain by dividing services on subdomains. Whatever that subdomain may be. http://vvv