As powerful and useful as Git is, it’s not all fun and games. It can be down right intimidating and hard to use.
But with some customization on your part, and some changes to your team’s Git workflow, Git can become a far more tammer beast to conquer.
Like any working professional, software engineers are extremely busy. There is more code to write than there is time. For this, we can be very picky with which tools we choose to communicate. A normal day can be filled with meetings, email , and then actually trying to write code. For the engineer, we have time for few things, and writing code is top priority. So, what’s the best method for getting a developer’s attention?
Here’s some tactics that will help you get in touch quickly with the guys building the next best life changing tools.
I’m writing this post from Mysore, India where I’m working for the entire month of February.
Coming here was a nail-biter for me, but not because of typical western concerns like bedbugs, heat, smog, or monsoons. What terrified me was the idea of traveling all this way and not being able to do my job effectively. I oversee operations and finances at Grio, participate in business development, and am currently managing two projects. If anything were to prevent me from working, I would need to grab the next flight and go home – arriving a minimum of 40 hours later!
AngularJS is one of the most used Javascript frameworks nowadays.
A characteristic of this framework is the possibility of binding input or output parts of an HTML page to a model represented by standard JavaScript variables.
Looping through arrays and collections is made easy by the ngRepeat directive.
This directive becomes handy when dealing with lists and tables, especially if associated to the AngularJS filters, which allow you to handle pagination, filtering and sorting by adding just one line of code to your html.
Unfortunately, one of the limitations of this approach is that the filtering is done client-side, therefore it wouldn’t be an optimal solution when dealing with a substantial number of rows/records.
I recently reviewed a SQL query that was returning duplicate results. Since I expected, and needed, a single result from the query this was a problem. Here’s an explanation of why this bug occurred, and several different ways it can be resolved.
Core Data is a framework provided by Apple that allows developers to design, build and interact with a database, without ever having any direct interaction with SQL.
This post will explain how to use a new component within the Facebook SDK iOS; I am talking about FBLoginView.
Facebook SDK for iOS has seen several updates and improvements during the last year. During my first project I was asked to refactor the authentication flow, such as login and logout.
Stack Overflow requires that questions be largely objective, but is based around a voting system that would be largely unnecessary if all questions actually were. The requirement for objectivity can be readily tested by asking a subjective question and watching how quickly it’s removed, but it’s also made explicit in their blog posts:
Stack Exchange is about questions with objective, factual answers.
…open-ended questions diminish the usefulness of our site…
and the reasons a question might be closed:
We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion.
The message is quite clear: objective good, subjective bad.
This year I worked on a project which involved populating a huge HTML table (up to 1,048,576 rows by 16,384 columns) cell-by-cell, with data retrieved via ajax calls. Needless to say, performance was not good.
