I’m going to start by asking a question … are you a jack of all trades? Are you the best at everything you do? Or, are there people who know better than you? This same question holds true with teams you are on.
When you hire a team, or are brought onto a team, the people that are chosen are normally there to expand on the current set of skills that the team has available to them. So, I want to ask, why not trust them to do what they were brought on to do?
Lots of people get lost in the fact that they want to lead a team and by doing that try to control each of the interactions whic occur on it. This sense of control could make it feel like the project is going smoothly and efficiently, but at the say time will likely start to make people feel untrusted which in turn affects productivity. If people are constantly looking over their shoulders, to see if they are being monitored, or feeling pressured to work, the work that they produce will suffer. But not only that, their desire to exceed expectations will likely also diminish.
Instead, in a team situation, you need to really stop and let your just work and do what they were brought on to do.
Of course, there will be times that this trust has been abused but those times generally followed up by some tough conversations where the situation is addressed. If it isn’t, it still is not a reason to not trust the team, it is an issue for the team leads (or managers) to deal with. Lack of trust breeds negativity in the work environment which in turn is counterproductive.
I would like to encourage you to trust those with whom you work. Your team will end up being a lot more productive if you can.
Posted in tools
I’ve always been a lover of the command line and for some weird reason whatever environment I am in, I like to boot up applications from terminal.
This goes from the simplest of tasks, such as opening a Finder window from the current directory:
To opening my text editor:
However, in order to do the previous one, you actually need to set up your Mac with this command. You might think that it is difficult but it is not. It’s as simple as running the following command:
ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
This will make a symbolic link between the Sublime Text app (their command which is built-in) and a folder which you normally have on your path.
Posted in tools
In a data load, we receive some zipped files (*.gz) I found that when you use the regular extraction:
gzip.exe -d -f "foo.csv.gz"
The “foo.csv.gz” file will automatically be deleted by gzip and replace it with “foo.csv”
However, if we are archiving these csv files it will take up a fair bit more space, so we wanted to just store the archived version of the flat file.
Originally I thought that I was going to need to unzip them, then rezip all of the files at the end of the process to get the files ready for archival but this took was just a lot of extra processing.
Finally I came across a way to avoid the deletion of the file If you output the file to standard out you are able to then redirect that output stream into your output file (without affecting the original .gz file).
gzip.exe -d -f -c "foo.csv.gz" > foo.csv
This will take all of the contents from the gz file and push it to STDOUT and then with using the >, we redirect the information written to STDOUT to the CSV file where we need it.
Hope this helps
Posted in tools