AFTERSHOX - Tariq Ahmed on Technology :: Management :: Business
  • About Me
  • Resume
  • Contact
  • Learning List
AFTERSHOX - Tariq Ahmed on Technology :: Management :: Business
About Me
Resume
Contact
Learning List
  • About Me
  • Resume
  • Contact
  • Learning List
Career

Quick Plug: HBR’s After Hours Podcast

Just want to give a plug for one of my favorite podcasts: HBR’s After Hours. It’s with 3 really fun, engaging, and lighthearted Harvard professors, and they tackle various business/company topics and implications on society and culture. I guarantee if you listen to a single episode you’ll be hooked. Hook it up!

 

10/25/2019by Tariq Ahmed
Career, Technology

Updated the Master Learning List

Added various additional valuable sources of free books, CSS, and programming related items.

http://aftershox.com/learning-list/

 

07/10/2015by Tariq Ahmed
Career, Featured

If I were 22

[box] I received an email from LinkedIn regarding an #IfIWere22 series for young professionals who are graduating this year and what advice would I give.

This is a re-post of my LinkedIn post.

[/box]

Painting the picture

if_i_were_22If I Were 22 In my early 20’s the Internet and Web were just coming out. It was really only known to techies, and keep in mind this was an era of dial up modems. Which was an incredible time as a technologist as I could see the tremendous explosion about to happen. From a professional level I’ve personally gone through a transformation in my journey starting as a Junior Software Developer to where I am now as the Director of Technology and Engineering at Amcom Technology in Silicon Valley. If I could send a message back in time to my younger self, here’s the advice I would give.

Stick with your convictions and take risks

Back in those days (mid 1990s) it was the tail end of the era where you go about finding a stable job, work your way up the ranks, and retire with a pension. Which is a completely alien concept by today’s standards.

However I recognized that the Internet explosion was around the corner, so my friends and I took a stab at two startup ideas.

Idea 1: Autobank – an online used car listing

I had this idea when looking for my first used car. I found it incredibly time consuming to go through a newspaper to look at car listings and filter for what I wanted. I felt there’s a need to create a web site where people/dealerships could post their cars for a nominal fee, and users could filter and search.

We teamed up with a business partner whose family owned a number of car dealerships, so that gave us the industry expertise we needed. However the Web was so new, and dealerships were so antiquated and conditioned to spending tens of thousands of dollars in radio, tv, and print ads that the idea of spending a buck a month per car online seemed like a scam to them.

They actually said that the Web/Internet is either a scam (because how could it possibly be so cheap), or a fad and that it won’t last. I eventually gave up not being able to achieve any traction.

Of course, a few years later autotrader.com, cars.com, and other such sites came out.

Idea 2: Spyder Web Hosting

At this point in time the non-techie early adopters of the Internet were signing up with their dial-up modem ISPs. The ISPs would give them an email address and 5 MB of space for a personal http://www.yourisp.com/~username website.

I felt this was unprofessional as a business from a marketing and branding perspective, and teamed up with some friends to create a Web Hosting company.

With our T1 into a friend’s basement powered by a Sun Sparc server (both of which were extremely expensive back then) we began to hustle and market.

We ran into a similar problem – businesses felt that the free 5 MB ~username was good enough for their business site. Whereas I was proposing that we help register their yourcompany.com domain and we host it.

I eventually gave up not being able to achieve traction.

Of course, years later you have the godaddy.com’s and all these Web Hosting companies out there along with fierce legal battles over domain names.

Message to Tariq @ 22:

Don’t give up too early. If you have an idea, or really believe your instincts are right don’t give up.

It may seem daunting to give up a nice secure full time job at a stable company, and of course having a real income stream for the first time in your life is amazing and something that you feel would be crazy to give up.

But trust me, the opportunity and ability to take risks goes down over time as it’s proportional to your debt load (mortgage, car loans) and the responsibilities you have (family).

Not that it ever goes away, but the stakes get higher over time.So take calculated risks now.

  1. Try out your ideas, don’t give up on them until you’ve completely exhausted all possibilities.
  2. However your time is valuable. Don’t foolishly waste it chasing something that will not manifest. You have to balance your emotions (passion, ambition, persistence) with logic (critical thinking & data driven decisions) in order to be analytical enough to determine when it’s time to move on.
  3. Iterate over as many ideas as you can.
  4. Take career advancing job opportunities in other parts of the country and even overseas. Moving isn’t permanent, you can always move back.

Recognize time and value

When you’re young it feels like you have unlimited time. You do not. Time is finite.

20 years ago I felt most things were equally important. Think long and hard about every action you take throughout the day, and ask yourself if that activity generates value.

Value could be personal value, and it can be value at work. Focusing your time on the most valuable activities is what will allow you to achieve maximum progression throughout your life and career. When you’re working, just ask yourself if what you’re doing at any given time is really the most valuable use of your time?

Find ways to achieve the same end result in as little time as possible. E.g. a face to face or phone conversation, as outdated as it’s becoming, is often faster than writing a long articulate Email.

Stay focused

Along the lines of value and time is the need to stay focused.

Focused means saying no. Saying no to distractions, saying no to low value activities, saying no to activity instead of productivity. As humans it’s gratifying to want to tackle easy things in order to get a sense of accomplishment.

However the things worth doing often aren’t easy and thus we tend to procrastinate on them. Push yourself to get the real things done. Done is value. The more you increase your value, that’s what your raises and promotions will be premised on.

Speed vs. Velocity

Recognize the difference between speed and velocity.

Speed is just rate of change/movement. Velocity is speed in a given direction.

You can turn your steering wheel in your car to the left, floor the gas pedal and hit 60 mph. You’ll be moving fast, but you won’t be going anywhere.

In your career you want to be moving somewhere. Make sure your activities, projects, and learning have direction.

To use a technology centric example, number of Agile points completed in a sprint, or count of tickets resolved, is just speed. However if those efforts are iterating towards a path or goal, it has direction.

Don’t just create solutions, solve problems

As a young technologist I often viewed technology as isolated and distinct from business activity. Even mature companies today view I.T as such.

Whether you’re into technology, finance, marketing, or anything else – don’t just create solutions for the sake of creating solutions. Solve problems using your skills. This generates value out of your work (and thus increases your value).

The key however, is to define the problem. When working with others make sure this defined problem is published and clearly understood amongst teammates and stakeholders. The problem I’ve found is that when it is not published everyone has a different perspective on what the problem is, and thus efforts are fragmented and folks are solving different problems.

Develop and maintain your professional networks

You’ll meet many people in your professional journey. Starting fresh in your career your peers will all be at the same entry level that you are now. However as all of you grow, the value of your network will compound.

The biggest mistake you make is lose touch with all the people you meet along the way.

Create alumni user groups email lists, LinkedIn Groups, and of course stay connected through LinkedIn and other forms of social media.

Recognize your strengths and weaknesses

This is hard.

It can take years to develop a strong sense of what makes you distinct and unique. Weaknesses are directly related to strengths, as they’re often two sides of the same coin.

Someone who may be ultra-versatile and adaptive probably isn’t going to be an extreme specialist. Nor will an extreme specialist be versatile. A deep methodical analytical long range thinker may not be adept at making rapid high risk decisions.

Knowing what you bring to the table will help you position your career to best leverage your distinctive attributes in the companies you work for.

As you grow even further, recognize the distinct characteristics in others and then learn how the combinations of certain groupings of skills create a whole that is more valuable than the skills individually. This is the value of a team, and you’ll make far more progress creating and working with the right combinations of people than working individually.

Never stop learning

Graduating doesn’t mean the learning is done. The learning never ends. Always keep learning and improving your knowledge. Learn things directly related to your core job function, as well as things that would help complement your skill-set. Learn things that advance your strengths and minimize weaknesses.

In this day and age where everything moves so fast you run a huge risk of becoming antiquated quickly.

  1. Attend trade shows and conferences
  2. Take classes with industry training professionals
  3. Attend webinars
  4. Join local usergroups
  5. Participate in trade related discussion forums
  6. Subscribe to magazines, and read books
  7. Present a conference or usergroup any topic – it’ll force you to learn as much as you can about it

Failing is learning

Don’t be afraid to fail. Failing is the process of learning.

No one rides a bike for the first time and just goes. You have to take the risk, fall, and develop the balance in order to move forward.

Failing is only failing if you don’t learn from it. So when you fail at something, evaluate what went wrong and what you would do differently if you could go back in time and do it again.

Therefore failing is an investment in your development.

In Summary

Your career is a journey, and your profession is a craft. Continue to pave the path in front of your career so that your journey continues to flow, while cultivating your craft.

And lastly if there’s anything to remember, remember this. A Roman philosopher by the name of Seneca once said, “Luck is what happens when preparation meets opportunity.” Or as I like to say, “luck is being prepared for an opportunity.”

Good luck!

#IfIWere22

06/14/2014by Tariq Ahmed
Career, Leadership

CIO Pocket MBA at Boston University

Earlier in April I had the pleasure of attending the CIO Pocket MBA hosted at Boston University.

The classes were fantastic, and if you’re in any kind of an I.T Leadership role I highly recommend attending this class.

It’s intense, fast, and covers a wide variety of topics presented by some of the most amazing professors I’ve ever seen. I was a bit skeptical over how current a university could be as I feel that most tend to lag (when it comes to technology) behind what’s happening in the real world.

Topics included:

  1. Managing disruption and change
  2. Economic position of the I.T organization
  3. Performance KPIs for driving results (a financial analysis session)
  4. Creating a customer centric organization
  5. Building a strategy for getting things done
  6. Leading change and innovation

Apart from the valuable coursework, there was value in the networking component where technology leaders from around the world attending (including Europe and the UAE).

For more information visit: http://smgworld.bu.edu/elc/open-enrollment/cio-pocket-mba/

boston1

boston2

Ahmed

 

05/06/2014by Tariq Ahmed
Career, ColdFusion

Dealing with the tight supply of CF developers and CF jobs

Recently on LinkedIn there were two separate threads in ColdFusion related forums regarding the topic of the challenge of finding ColdFusion developers as an employer, and finding jobs as a ColdFusion developer.

The discussion covered a variety of perspectives from telecommuting, the ecosystem, economic, tips on attracting developers, tips to finding jobs, etc…

Below is is an adaptation of my posts…

Telecommuting

I’m the Sr. Manager of a collection of technical teams (DBAs, Developers, and B.I), and we have had a few people work predominantly from home.

Of course there are a number of advantages from the employees perspective in that they get to recuperate time from commuting, expense of commuting, etc… I would say that the biggest advantage is the ability to focus. An office environment, particularly if you’re a key person on the team, can be a non-stop barrage of distraction. And if you are key person, the company benefits the most when you’re focused.

The flip-side

There are of course drawbacks.

We’ve seen that there is an isolation effect. Tools like Skype, WebEx, and TeamViewer are great tools, but nothing is like the experience of a face to face. Studies have shown that telecommuters do not advance as fast as their peers who work in the office. And let’s face it, we’re human beings and have evolved to interact with each other in person (give it another 50yrs and we’ll all be plugging into something like the Matrix and conduct face to faces in digital form).

We also find that the team chemistry and bonding evolves significantly slower among a group of telecommuters. Those side conversations, going out to lunch, sharing challenges while grabbing a coffee… those occurrences are far less with telecommuters.

Growing Jr staff

Another challenge is that Jr staff rely on the Sr staff. You can make progress with screen sharing and conference calls, but it is no way as smooth as quickly walking over to a whiteboard and coaching a Jr member. So if the Sr Developers are telecommuting, your cost to get a Jr ramped up and productive is considerable to the point that a manager would be evaluate if it’s even worth it.

On an individual level, can a person do X work in Y time, regardless if they’re in the office or not, sure.

But on a team building perspective, the chemistry, unity, and bonding to achieve cohesiveness is extremely important. And telecommuting poses some serious hurdles.

One alternate solution is a hybrid approach. We found that worked well with Sr. staff working 2 or 3 days at home, which allows them to focus. And the days that they’re in the office you get the team building, the coaching of the Jr staff, the face to face interaction, etc…

Some studies suggest there is an ROI with telecommuting. The ROI tends to be on an individual level. From a management perspective, you’re looking for the overall output of the team which is more than simply the sum of all individual output.

Company cultures are unique

Each company is unique. And good management recognizes their organization’s strengths, weaknesses, abilities, shortcomings, etc… So although studies and ROI case studies are useful data points, you do have to factor in the unique reality of your exact company.

Not impossible, just recognize the challenges

I’m not saying it’s impossible to achieve success with telecommuting (clearly, companies have), but it’s a significant challenge that management will bake into their staffing & organizational strategies because it may very well be that the company culture isn’t compatible with telecommuting.

Or likewise, if there is no team then there is no issue. So for very specialized skillsets, solo acts, multi-location organizations… it may be a no brainer in those cases.

Supply is limited

The supply is constrained on both sides, and are cause and effect of each other. Hard to find expertise will cause company strategy to change which expertise is needed. Fewer opportunities will cause the talent to move on to other technologies.

Thus, both companies and individuals need to be prepared to at least go national when recruiting/job hunting.

Tip for developers

  • As developers, I’d avoid branding yourself as a developer of a specific technology. Go for versatility, technologies will come and go. E.g. don’t be a “ColdFusion Developer”, be a “Web Developer” who has expertise in various technologies.
  • Developers, you need be involved in the community, building up your professional network, finding opportunities to network with future potential employers (e.g. touch base with guys who have influence over hiring decisions, send your resume in just so that they have it on file).
  • If you’re one of those guys that picked up CF to fulfill a need, but don’t have a formal software engineering background, and feel you don’t have that strong understanding of programming fundamentals – build an application using an MVC framework (FW/1, ColdBox, etc…). It’s one of the easiest ways to take your skills to the next level. Reading books gets you good theory, but real learning comes from real world experience. This will give you an edge interviewing wise for the rare CF job that does come up.
  • An even better step is to build a real world application using a language you don’t know using its most popular framework. Learning another language will actually boost your CF abilities as you’ll realize you can apply concepts from that other language to CF.
  • Some  hot up and coming languages right now include Groovy/Grails, Clojure, and Scala.
  • What to build? Volunteer to build something for a non-profit. Look at the company you work for and look at what is being done manually or what is a cumbersome process, and build a tool to solve for that problem. It needs to be real.

Tips for employers

  • As employers, we need to be looking for strong developers in general. At Amcom Technology, we’ve found people who have a strong understanding of programming fundamentals and software design, strong problem solving abilities, and are quick learners are the key.
  • The recruiting needs to begin long before a position even exists by forming relationships with people. And that needs to happen on both sides of the equation.
  • Employers need to be forming relationships with the community, so that if an opportunity opens up you have relationships already formed with folks who potentially are fits for the position and it’s not a cold call (err email).

Lastly

The most important tip I can give, is send me your resume, or feel free to at least touch base. Ok, that is shameless. 🙂 But we have opportunities that come up from time to time, and I’d like to get to know you! tariq [at] amcomtech . net.

04/27/2012by Tariq Ahmed
Career

Career tip – increase your value to progress your career

A number of things can influence career progression and salary such as results, professional networking/relationships, and ambition.

The biggest factor is the value you bring to the table, and creating new value that results in the progression. You may get mediocre cost-of-living adjustments by merely doing your current job, with the current level of responsibilities, at the current level of output. But big raises and significant career progression only occurs AFTER you’ve increased your value FIRST.

Why would you get a raise for doing what you’re already paid to do?

Here’s a list of ways you can increase your value:

  1. Increased responsibility
  2. Increased ownership
  3. Increased knowledge (of the systems, of the business, subject matter expertise, technologies, etc…)
  4. Going above and beyond (working extra hours to meet a deadline, taking it upon oneself to fix an issue ailing the team, etc…)
  5. Increased quality of work
  6. Increased reliability (e.g. can be counted on to deliver something as promised, etc…)
  7. Increased speed (what used to take 2 days you can now get done in 4hrs, faster turn around time, etc…)
  8. Increased commitment
  9. Increased dependability, predictability, availability, etc…
  10. Increased ability to rapidly solve complex issues/problems
  11. Increased output/results (e.g. # of tickets/user stories resolved)
  12. Increased sharing of knowledge (documents, knowledge base articles, presentations to the team)
  13. Increased savings to the company.
  14. Increased profits to the company.
It’s all about new value!
If you have any others feel free to add via comments.

 

08/01/2011by Tariq Ahmed
Career, Management

Communication tip – keep it as short as possible with executives

Have you ever cleared your inbox down to zero? It’s the elusive dream we all hope to one day achieve.

One of the challenges we face in this information overloaded work culture of ours is that the sheer volume of information requires constant grooming, categorization, and prioritization.

Consider that your manager is probably getting about 5X-10X more email than you as they’re cc’d on every discussion, decision, and meeting minutes pertaining to the team. Consider that his/her manager is yet another order of magnitude as the scope broadens, and continues to get worse as you go up each management level.

At the executive level you’re going to employ techniques that help you stay on top of what’s going on with the business by prioritizing where your time needs to be spent. Which means they’re going to assess within 2-5 seconds how important an email is and either act on it right away, read and absorb in detail, delete it as non-actionable, or file away for further reading (which they’ll never get around to).

We live in the detail

The problem with people in the technical industry (developers, analysts, project managers), is that our lives revolve around detail. Detailed plans, specifications, unit tests, coding standards, acceptance criteria, etc… it’s all low level detail – and thus our brains are optimized to think at that level.

Executives however operate at a higher, broader, bigger picture perspective. They swoop down to lower level gears when they need to roll up their sleeves, but for the most part they’re focused on where the business is headed.

Follow these tips

Thus the style of communication that works for people who work with low level detail isn’t optimal for executives, so here are some tips to maximize your communication delivery and impact with executives:

  • Don’t use narratives

I had always felt that the application could run faster, so I was looking into server performance and by running a number of queries through query analyzer I determined that performance could benefit by adding a number of indices (see initial results below). So I took it upon myself to add a number of non-clustered compound indices that my research has shown to be used in the commonly used join statement, and…

    • Narratives are that story telling style of explaining things, where you end up with paragraph after paragraph only to get to the point at the very end.
    • They’re time consuming to produce because you’re going to be meticulous considering the audience, and even worse they’ll just quickly scan through it.
    • Or if they do want to read the detail, they’ll put it in the read-later category when they have more time, which they rarely do have more time.
  • Strategically title your subject
    • Don’t use one or two word subject titles, e.g. “performance”. It’s too generic, and not actionable.
    • The goal is to try engaging them into reading your email.
    • If you have good news, or are trying to pitch an idea that can really help the company – then try to pitch that in the subject line. Many execs deal with a lot of issues, so it’s nice to have an email come in that won’t cause your blood pressure to rise if you read it.
    • Tag your subject with the content type, e.g. [idea], [kudos], [proposal], etc…
    • E.g.
      • [idea] quick solutions to improve application performance
      • [proposal] side project to improve performance
      • [kudos] Jeff Wilkers landed the Amcom account
  • Start with your conclusion/proposal/point first
    • The technical/analyst/PM thing to do is build up a case leading to a conclusion. Stating observations, criteria, supporting data, assumptions, etc… Execs don’t have time for this. Get to the point, first.
    • Make the rest of your email support that point.
    • This opening statement has to be very brief! No more than two sentences. It has to capture the essence, and be written in such a way that it can be absorbed at a glance.
Good news, we’re able to improve application performance by 30%.
  • Structure your content
    • The reason why resumes are easy to digest is that they employ a predictable and repeatable pattern.
    • Resumes are also very (or should be) very succinct and to the point.
    • Dump long winded narrative/story telling paragraphs and break sections apart, delineated by a section title with a distinct color. Within each section, use bullet points where you try to avoid wrapping as much as possible.
    • If the exec has an extra coupla of seconds to scan through your email, the goal here is that they’ll be able to absorb most of the content as its structure is optimize for scanning.
07/19/2011by Tariq Ahmed

Who is this dude?

Tariq Ahmed Howdy! My name is Tariq ("Ta-Rick") Ahmed, and a Director of Software Engineering at New Relic where my time is focused on creating developer experiences through our developer websites, APIs, CLIs, SDKs, and ability to build your own custom apps on the New Relic One platform. I'm most passionate about finding amazing people, growing talent, and building amazing teams in order to accomplish meaningful breakthroughs in technology that ultimately create great user experiences.
Twitter feed is not available at the moment.

Categories

  • Agile (11)
  • Business Intelligence (1)
  • Career (7)
  • ColdFusion (7)
  • Collaboration (1)
  • Featured (5)
  • Flex and AIR (2)
  • Groovy / Grails (6)
  • I.T Systems (1)
  • Innovation (4)
  • Leadership (6)
  • Management (8)
  • Project Management (1)
  • Software Development (1)
  • Startups (2)
  • Technology (7)
  • Uncategorized (2)

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Blogroll

  • LinkedIn
  • Teletrac Navman

"This blog is all about sharing thoughts and experiences in my journey as a technology leader. From the technology itself to the processes, practices, and teams needed to make it happen."

Find more at LinkedIn.