All post for category "Dev"
Written by Sebastian on Nov 3, 2017 in Dev
Setting up new projects is always exciting, but if you have done it a few times, it’s getting old quick. I have set up a few projects in the last time and I believe I have a nice setup going which I’m about to share with everybody interested. There is nothing new in here and if you are a seasoned Clojure developer, you might not learn much. If you are just starting out or have some work done in Clojure but need a working setup or some input on your current setup, you are at the right place.
Written by Sebastian on Oct 23, 2017 in Dev
Almost a year ago I wrote my last blog post on this blog. It wasn’t planned, it just happened. I was busy doing other, unrelated things and while I sometimes had something to say, I never took the time to take it to my blog. As with many things which are not top priority, it got lost along the way.
Written by Sebastian on Dec 21, 2016 in Dev
After “The setup” and “The beginning”, my time with Clojure was somewhat limited due to pre-christmas stress. But this gave me time to reflect on what I learned so far, what I liked and didn’t like. I also attended the December Meetup by (clojure ‘vienna) and pair programmed Clojure for a few hours.
Written by Sebastian on Dec 8, 2016 in Dev
After “The setup”, I dove right into Clojure. As said before, I want to get to know Clojure by working on Advent of Code (AoC). I realize that coding puzzles and dojos and katas are not real world applications and one might miss certain things like performance or running an application in production. But they are small enough to provide fast feedback and to not hit a big wall. Even if I am not able to solve one, I can always skip that and keep going with another puzzle.
Written by Sebastian on Dec 5, 2016 in Dev
In the last week I started playing with Clojure. The reason for this are some upcoming projects with the blossom Team. The stack will most likely be Clojure in the backend and ClojureScript in the frontend. So I better up my game. I started with the Advent of Code to have some real world exposure and not just write complicated “Hello, World” code. I’m planning on writing a series of blog posts, documenting my journey.
Written by Sebastian on Feb 29, 2016 in Dev
If you are a seasoned Vagrant user, you know the problem around provisioning. If some software version changes, everybody needs to provision his or her machine again. Otherwise, things will fail eventually. You’ll also run into problems if running the provisioning twice fails for some reason (e.g. because a file already exists somewhere).
Written by Sebastian on Jan 21, 2016 in Dev
Using Vagrant in order to have a reproducible development environment is second nature to me. All projects I work on have a
Vagrantfile and it usually works great.
Written by Sebastian on Dec 11, 2015 in Dev
At blossom, we are running on Google App Engine (GAE). It’s nice to stand on the shoulder of giants and don’t have to worry about servers at all. GAE takes care of scaling up and down for us, handles our database as well as storage and gives us great insight into our production environment.
Written by Sebastian on Sep 13, 2015 in Dev
Many of you might already know it: Soon I’ll be joining the blossom Team on their quest to project management awesomeness. The current development stack of blossom consists of Python and Dart running on Google App Engine. In order to get some experience with both Python and Dart, I started a small side project which is a perfect combination of my two main interests, development and music.
Written by Sebastian on Aug 21, 2015 in Dev
After playing with Dart for a little while, I also looked into testing with Dart and learned that the test library can use PhantomJS to test the code that interacts with the DOM. Being a testing junkie, I wanted to give this a try but learned that I needed PhantomJS 2 to get it working. Beside running it in my VM, I also wanted to have it running on TravisCI. This blog post tells you how to set up both.
Written by Sebastian on Jul 26, 2015 in Dev
Today I switched over this blog to be subject to continous deployment. Whenever I push a new commit (which might be a design change, new blog post like this or some small change), everything is build and automatically pushed to Github Pages, which host this blog.
Written by Sebastian on Mar 25, 2015 in Dev
If you are tasked with managing servers, you might have read about Ansible. If you do not know it, here is a quick intro: With Ansible you can define tasks which should be run on your (remote) hosts and Ansible takes those tasks, opens a ssh connection into your hosts and executes them.
Written by Sebastian on Jan 27, 2015 in Dev
If you are using vagrant on a daily basis, you might already be using something else than the base box suggested by vagrant (which would be the
hashicorp/precise64). If you are thinking about creating your own base boxes or are interested in the topic, read on. If you have no idea what I am talking about, the vagrant documentation can tell you more about Boxes.
Written by Sebastian on Jan 18, 2015 in Dev
Over the past two month, I have been building a new weekend project: cllctr. It’s a CD database you can use to store information about your CDs. Say goodbye to excel lists and over-the-top stuff as discogs or collectorz. cllctr is focused on the right amount of data, balancing the time needed to enter new CDs or organize a exisiting collection.
Written by Sebastian on Oct 28, 2014 in Dev
When I am talking about Vagrant at usergroups and conferences, one thing I always mention is that shared folders are slow, especially with Virtualbox. While it’s true for reading to some extend, the biggest bottleneck I experience is writing to the shared folder. This happens a lot with cache and logs in development mode when you use e.g. symfony2. These folders live inside the project dir and depending on your project structure you might not be able to redirect them to some folder inside the vm.
Written by Sebastian on Jun 28, 2014 in Dev
If you write your blog to also be found through Google, you may have a sitemap which makes it easy for Google and Bing to crawl your page. It might be good idea to inform both if this sitemap changes so they can send their crawlers your way and update their index with the great stuff you just put on their. This can be done by doing a
GET request and passing the url to your sitemap as a parameter. Easy as pie, right?