If you execute your tests via Grunt or Gulp or manually via terminal, It's very easy to make them work with Travis. But if you are using Testem to run your tests in multiple environments, You might find Travis a pain to use. The reason why is that by default testem shows you a text based UI just like the screenshot above, and wait's for changes in your scripts to run the tests again. This is not what Travis expect. Travis expect to get the tests results as soon as they are finished. Hopefully there is a way around.
It has been two days that I'm struggling with getting MomentJS and a few other libraries work together in RequireJS environment. From version 2.4.0 MomentJS has depricated the global Moment creation. The issue is that some of the momentJS plugins are not 100% AMD friendly. This has caused Moment plugins throwing errors and not working correctly. For example the code below will have the following results:
Today a friend and I were working on a Trello board of our project but we had a little problem and that was limited tag colors. We used color labels to group the tasks in the same backlog. Trello let's you to create labels and asociate a name and a color to them but it has a very limited number of colors. What we wanted was more colors but we realized that if the number of colors were more than that, these colors could be easily mistaken.
Today I found this wonderful service called Modulus. It simply gives you the power of deploying and serving your nodeJS, PHP or even Java applications. I recommend registering an account instead of using your Github. You will need to login to the service via your terminal later. The next step is to install the Modulus package at your local machine. First make sure you have NodeJS installed. Then you can install Modulus like this:
Aug 23, 2015, Posted in Uncategorized
Different jobs require different types of resume, In this post, I’m going to tell you how to make a professional resume for applying to a computer programming job. I’m just a regular programmer and all I’m writing here are personal opinions (with reasonable explanations). It’s not a rule, But rather an advice. Before getting deep down into the details, Let’s see how your resume will be read by employers. There are many ways employers might get in touch with you. they might find you via a friend, visit your Github page or meet you at a conference, But the thing that is more likely to happen is that you or somebody send your resume to them.
Aug 13, 2015, Posted in Clean Code
Hah, It seems silly to you? Why do we have to write a unit test first, when we know it already won’t work? Because it forces us to write the production code? This is stupid, we can write the production code first and later the test. These were the questions in my head until recently I red a book by Robert Martin, “The Clean Coder”. Read that book if you can, trust me you won’t regret a line of that. But back to our question, Why do we have to write tests first, Then the production code?
Jul 28, 2015, Posted in Uncategorized
Starting of a software project is always a fun thing to do. You create folders, you keep your files organized, you try to draw diagrams too wrap your head around your project structure. You also try to write your code as clean as possible. You have many awesome plans to extend your application and everything is fine and as planned. However as you keep going forward these feelings start to fade away and replace by new ones. The joy of adding a new feature is now replaced with fear of breaking old ones, the sure feeling about the correctness of your code is replaced with uncertainty and fuzziness and the quick reactions and speed of development is replaced with frustrating hours of testing the things, that you've already tested a thousand times.
It's hard to debug a promise based function, it get's even harder when you make bad decisions while writing those functions. I did that a few days ago and I want to explain it here with a few examples and after that I'm going to refactor my own code.