One of the best features about the new version of Sublime that is now in beta is probably the goto definition. That was actually the main feature that was making me consider the update.
This is a message from the future for you. Yes, you! The guy that is still using Google Reader completely unprepared for what is about to happen.
Well, thinking about that I started not using GR a few months ago and now I’m here to tell you that life is possible without it.
Do you use bootstrap? Who am I kidding, of course you do.
Ok, here’s the problem that I used to have.
I build a lot of back-end applications, most of them are powered by booststrap and one thing that I always found was that it didn’t had many icons to work with.
That’s were Font awesome comes in. You just need to include another css file and you’re done. Now you can use many, many icons and better than that. You can use them in different sizes.
How awesome is that?
Yeah, that’s right. If you’re like me you have a small compulsion to commit every small task you complete. In some cases that can be a good practice. However, when you’re working with a large team, or even on a open source project that has lot’s of contributors that can be a PITA in the long run. Imagine you’re looking for all the changes done while creating a feature, and your history is full of small commits. Finding what you’re looking for is not going to be easy.
So I started digging a way so I can continue on my normal commit rate, but before I push things into my remote(s) I can decide if my code will go divide into all of those commits or if I want to “merge” them into a single commit.
Let’s look at the rebase command and if you’ll see that is one called —interactive. Apparently the most common use for this one is to squash commits. What I mean by that is that you can pick up all your commits and combine them into larger ones.
A word of caution: Only do this on commits that haven’t been pushed an external repository. If others have based work off of the commits that you’re going to delete, plenty of conflicts can occur. Just don’t rewrite your history if it’s been shared with others.
First thing this morning (a little past midnight UK time), a guy by the name of Chris Borgia posted a campaign on indiegogo. The campaign, “Film Laracon” is pretty self-explanatory. In the project summary he pointed out that there were no plans for the talks to be recorded, meaning those of us unable to attend Laracon would be left out of the mix. As it happens, Chris already owns the relatively wide range of gear necessary to record a conference and he’d managed to secure a slot on the guest list, so all he had to cover was the cost of a hotel and parking at a total of $560.
What is FIG?
The idea behind the group is for project representatives to talk about the commonalities between our projects and find ways we can work together. Our main audience is each other, but we’re very aware that the rest of the PHP community is watching. If other folks want to adopt what we’re doing they are welcome to do so, but that is not the aim.
There’s a few ways to get involved into this thing:
- Join the malling list.
- Get on the IRC Chat #php-fig.
- Start using PSR-0 / PSR-1 / PSR-2 / PSR-3 in your code styles.
- Check out the github page for the fig standards.
I just finished reading this book, so it’s now time to give it the review it deserves. First and foremost this is a really small book that you can read in hours. However you shouldn’t judge a book by its weight. Even though the book is small, it’s actually full of useful content.
Well since I’m now working as a freelancer I now have a bit more power over what framework should be used for this or that project. Therefore, I think I’m not going to use Codeigniter by choice anymore. This means I’ll use it if the client requests it. Or if by any chance I’m working with someone else that is only familiar with CI and not Laravel.