Thoughts from a Battle-Scarred Founder (Part 1)

My blog byline is: “Thoughts, ramblings, and tips from a tech nomad”. I started the blog last year (2015) and posted five or six articles since. Upon review, I’m overdue to make good on the “thoughts” part and, that, I’m certain, will spill over into the “ramblings”, too.

In Which I Catch Up with an Old Friend

So, recently, I met with an old friend, Andrew, for drinks. He was due to leave Ukraine in a couple of weeks to move to Vietnam. We’ve been friends for almost a decade now, fellow veteran expats of wild, wonderful Kiev. Now he’s already in Ho Chi Minh City, establishing a new office for his own startup, a real estate trading platform.

It was a Friday night and we were sitting in a popular, stylish bar, immersed in the type of buzz and bustle you only get in popular, stylish bars on a Friday night. The problems of Ukraine seemed far away from this place with the beautiful girls in stilettos, the fantastic hookahs lit up like lava lamps, the cocktails and champagne, the ambient lounge music. In a strange sort of way it just seemed to bring my own problems nearer.

A Tale of Two Startups

We were comparing notes. Contrasting, actually. Andrew’s business is making rapid progress; he clearly has a vision to disrupt one of the oldest, stuffiest industries in the world, and he’s planning and executing with discipline. My business on the other hand is still painfully tripping over basic hurdles four years after inception, despite it theoretically being positioned to ride on the wave of a dynamic, huge, still-growing industry (mobile app discovery and app marketing).

Bar and restaurant in Kiev

That’s not to say we haven’t made progress, or that I haven’t learned a lot. We have, and I have. Even already having been an early employee in at least three previous tech startups—and put seven years into the last one to see it grow into a $100M company—my present startup, which has kept me perpetually alternating between being broke and stressed, has taught me a great deal more. For anyone who cares to listen, I certainly have a lot to share.

It’s nonetheless with chagrin that I recount the following conversation because apparently I am ready to forget important lessons as quickly as I learn them.

Andrew was already familiar with a lot of my challenges. He also knew about a second idea I was interested in breaking out on my own to work on. “How is that going? Are you still going to do anything with it?” he asked me.

“I’ve been discussing it,” I said. “I’ve got an offer for enough funding for six months of development for a 50% stake.”

“Fifty per cent before you’ve even started? That’s not right! Why would you agree to that?”

“I’m not saying I think it’s good. I guess it’s how we’re used to thinking.”

“Your split of your current business right now is calculated on salary sacrifice and not on contribution, yes? When we talked about that before, you admitted it was set up wrong.”

“We sort of just fell into that business so there’s a reason it is the way it is but, yes, if we were going to set it up properly, we would have done it differently.”

“Okay, but you’ve got time to plan this one. You do realize this new proposal is even worse, right?”

Of course he was right. And it was frighteningly like an idiot doomed to repeat his mistakes that I didn’t realize this enough to see the problem with the proposal the instant it was proposed.

“Yes, okay, it’s bad,” I said, “but how would you do it?”

How (Not) to Slice Your Pie

Slicing Pie. Andrew’s business is structured completely differently from mine. Equity is often likened to a pie. Founders, investors, and key personnel get slices of this pie. The proportions can change over time. The size of the pie can and does change. The size is a theoretical value for your business and your goal is to increase that theoretical value—that’s the point of a business, after all. However, the catch is that how and when you slice, and balance the slicing against the preparation and the baking, deeply affect how that pie grows or shrinks. It’s a magic pie with the potential to grow to colossal size but do it wrong and it shrinks irredeemably, flaws and all.

Andrew placed his whisky sour on its coaster. “It’s simple,” he said. “Let’s say your investor puts in $100,000. Multiply that number three or four times to recognize the risk he’s taking with his cash. The result is the value he is contributing. If it’s 4x, that means the value he’s put in is $400,000.”

“Yes, we used 4x,” I said.

“Okay, so then you build the company to a valuation of, for example, $2 million: that means you have added $1,600,000 of value to that business. The investor’s contribution of $400,000 means his split is 400K out of 2 million, or 20%. Say, instead, you only get a valuation of $1 million, then his split is 40%. What you don’t do is immediately split the business before you’ve even started. That’s just a rookie mistake.”

“Okay, that makes sense,” I said. I turned it over in my mind a bit. “Well, like you just said: in the current business, my split is based on how much I’m sacrificing of my old salary from five years ago. At least from that point of view it is sort of dynamic,” I said.

“Yes, I know, but you multiplied the cash investment contribution while not accounting for your contribution, only your time,” Andrew said. “In this case, you are better off getting a job with a good salary. Cash is important but it’s just cash. The business is not a business with just cash. It’s your ability to make and grow a business that gives the business its value. The value each individual brings is how you calculate the splits.”

There’s an excellent book with exactly this name, Slicing Pie (available on Amazon). I read it a while ago and, to me, it offered an effective yet simple recipe for equitably incentivizing and rewarding all the people and resources that must come together before your startup can succeed. It says essentially the same as Andrew had just put in a nutshell. And, yet, in spite of that book, I was considering a structure that ran exactly counter to what I had just claimed to have learned and embraced. That is scary.

Get Everyone on the Same Page!

So here is the next catch, and it’s just as critical as the first I mentioned: if your investors or co-founders do not subscribe to the same approach for structuring a business and apportioning equity, then your business is set up to be an expensive exercise in frustration. In my case, the investor’s primary concern is with how much out of pocket he is. Now let’s be clear: that is fair. That first seed or friend and family investor is putting up precious cash against something that doesn’t really exist yet. That takes a certain leap of faith and trust. So, the multiplier is intended exactly for that purpose: to reward the up-front cash. Nevertheless, if the investor finds it difficult to see past the cash, I believe that in his or her mind their outlay is not balanced out by the sacrifice and contribution of founders like me because said contribution is not cash and cannot be seen or touched, or taken to the store to buy a house or a car or even a carton of milk.

In situations characterized by such disparity in thinking, I would urge you to vigorously adjudge the wisdom of getting into business together at all. Or ask your potential partners to read Slicing Pie. It’s just over 200 very readable pages and practical from the first to last. You need this common mindset, even among the most well-intentioned parties, which by the way I don’t hesitate to declare ourselves to be. Without it, if you have a great idea and an ability to execute, you can maybe still make some money—maybe. On the other hand, I think you avoidably introduce a real risk of failure. If you have the idea and the ability, why would you not want to set yourself up with the best chance to succeed? This is not selfishness in deal-making. Ultimately, your investors and partners also stand to lose in a badly structured venture. In looking out for your own interests, you also save them from probable financial loss and heartache. However, don’t just take my word for it. Go ahead and read some of the 240 reader comments on Amazon for Slicing Pie and see if you don’t get a clear idea of what I’m talking about.

While I’m at it, I should mention another important book, and probably the best-known book on this topic: The Founder’s Dilemmas, also available on Amazon. The Founder’s Dilemmas draws on a decade of research to offer advice on how to avoid these common startup pitfalls.

Parting Advice

I tipped up my glass. Some round lumps of half-melted ice clinked onto my teeth. Andrew raised his hand and looked over at the waiter. He spotted and headed toward us.

“Hookah as well?” Andrew asked me. I nodded. Andrew said a few words to the waiter and then turned back toward me. “Well, bud! I hope you’re clear on what you want your outcomes to be.”

Knowing what I want is not something I’ve been struggling with. “Sure, the first thing is to stabilize our business. That’s my whole focus.”

Andrew leaned forward. “Just don’t forget that time is slipping. It’s good to know what you want but don’t be afraid to give the universe a bit of a push, too!”

“Yes, thank you,” I said, and I meant it.

I understood him. I would have given the same advice to anyone else on my side of the table. Sometimes, however, being reminded of the obvious is valuable. This goes double for startup founders who can get so mired in the daily tumult and noise of their businesses that they actually lose focus, or misdirect it.

If you are a first-time, tech startup founder, I recommend learning and reading widely and constantly. Getting things set up right is like placing a blessing upon the business; getting them set up wrong, a curse. If you think you can just wing it, then the best of luck to you! Or as Meilir Page-Jones said: “May a thousand angry scorpions infest your cubicle.” 1

“Oh, and by the way,” Andrew added, “Never split exactly 50/50.”

When Forrest's mom gives him parting advice

Feature photo: After celebrating New Year’s Eve in Las Vegas in 2009, Andrew and I drove to Los Angeles. This was the sun rising over the mountains as we were travelling through Red Rock State Park, Arizona.


1. Practical Guide to Structured Systems Design (2nd Edition) by Meilir Page-Jones, 1998. This was a remark he made to programmers who choose to ignore proven structured design heuristics.↩

Combine Excel Cells into One

In this post I offer a tiny VBA macro snippet I once wrote to save me a lot of time preparing spreadsheets for my business partner. It’s trivial for a VBA programmer but if you’re not so comfortable with VBA macros, just use this code to address the same problem or even adapt it for any other situation requiring a similar approach.

Concatenate All Contiguous Cells to the Right into One Cell

Say you have some cells like this:

Values split across a number of cells
Values split across a number of cells

But you want to combine the values on each row like so:

All cells to the left combined into the rightmost cell
All cells to the left combined into the leftmost cell

In other words, the values to be concatenated are spread horizontally across any number of contiguous cells. The “target” cells to hold the combined values are in one column (column A in the screenshot above) along contiguous rows.

Of course, there is more than one way to solve this. I’ll mention an alternative later but for now here is a macro that does the job.

Sub Combiner()
    Dim c As Long, r As Long

    Do
        c = 1
        Do While Not IsEmpty(ActiveCell.Offset(0, c))
            ActiveCell = ActiveCell & " " & ActiveCell.Offset(0, c)
            c = c + 1
        Loop

        ActiveSheet.Cells(ActiveCell.Row + 1, 1).Select
    Loop Until IsEmpty(ActiveCell.Offset(0, 0))

End Sub

Before running the macro, make sure the first target cell is currently selected. In the first screenshot, that’s A1.

Note that the macro doesn’t actually delete the contents of the “non-target” cells. You can either do that manually or adjust the macro to do it for you. (If you’re not sure how to do that, please leave a comment and I’ll update this post with the appropriate edit.)

That’s all there is to it. Keep reading if you’re new to macros or are interested in possible alternatives.

Assumptions

To work properly, make sure the values to be combined are in contiguous cells and in contiguous rows. In the screenshot above, if there were a value in A5, it would be ignored by the macro. If there were a value in F1, that would also be ignored (assuming that E1 is blank).

If you can imagine the movement of manual typewriters laterally across and down a sheet of paper, in a “Z” pattern, then that’s the same sort of movement the macro follows.

You can modify and adapt the macro for any other operation where you have a bunch of cells on a lot of rows to process in a similar fashion (i.e. across-across-down, across-across-down, etc).

Primer

Because the solution is a macro, you’ll need to know how to create and run macros. I don’t intend to give a detailed introductory lesson here on macros but below are some pointers in case this is all new to you.

Macros are accessed via the Developer tab on the Office ribbon. (See screenshot below.) The Developer tab is not enabled by default. If you cannot see it, enable it by following these instructions.

The Developer tab on the Office ribbon
The Developer tab on the Office ribbon

To create the macro, click the Macros button on the Developer tab. A dialog box will pop up. In this dialog, enter the desired macro name (I’ve called it “Combiner” in my example) and click “Create”. (See screenshot below.)

Dialog box for creating a new macro
Values split across a number of cells

This should open the VBA editor with an empty Sub called “Combiner” ready for you to fill in. Edit this sub so that it looks exactly like the code provided above.

This way that I just described is much simpler than the explanation in this article but I’ll offer the link anyway for further reading plus tips for speeding up macro execution.

Alternatives

The CONCATENATE Function

If you don’t have a lot of rows to combine, you can use the CONCATENATE function. Here is an article that shows how that function can be used. The values in that article are split across rows, not columns, so you’ll do it slightly differently but the important thing is to know how the CONCATENATE and F9 key together can work.

The sep= Statement for Non-Comma Delimited CSV Files

Originally, I used this macro to “fix” CSV files that Excel was incorrectly splitting on commas it found in the data. By default, Excel treats commas as the field delimiter so, if your CSV data contains commas, Excel will split the string into a new cell at each comma. If the field delimiter is actually a different character, your data is split incorrectly.

I originally used my macro to recombine all the cells before using the Text to Columns feature to split on the real field delimiter. That is, until I discovered that I could specify the field delimiter by inserting sep=field_delimiter_character as the first line of the CSV file. The second answer in this post explains how to use the sep= statement to split on non-comma delimiters.

I might have overcomplicated the task by writing so much on it. However, if it is helpful, it will have been worth it!

UPDATE: 13 JANUARY 2015
One caveat about the macro: if you have many columns and/or rows to process (e.g. tens or hundreds of thousands of cells), the macro may be optimized by not updating ActiveCell once for every lateral cell it encounters. Instead, try updating ActiveCell only once per row. I can imagine a couple of ways to do this (e.g. slot the cell values into an array of strings and then concatenate them using the Join function; preallocate a fixed length temporary string variable and insert cell values into the appropriate offsets within this string variable. Whatever the approach, I would prefer to avoid concatenating to a string variable cell-by-cell because VBA is notorious for being slow when concatenating to variable length strings in a loop.

Again, if you run into this issue and need more info, please leave a comment and I’ll respond with some suggestions or even some new code.

VB6 and the Dinosaurs

The heading below was originally my working title. The title above is the replacement after I realized the first couldn’t have been drier if I’d tried. I needed something a little more interesting. So I played with some word associations: dinosaurs were an easy association to make. Prehistoric, big, dominating virtually every corner of the globe for an eon—the legacy, enterprise-scale VB6 system still exists in many forms today.

Issues in Upgrading Legacy VB6 Enterprise Applications

Fairly recently, I consulted to a company to solve the thorny problem of how to upgrade their enterprise-scale product from VB6.0 to .NET. At the end of the assignment, I handed over what we all agreed was a workable and realistic strategy. It was an interesting project. There were things I’d forgotten about how things were done a decade ago; not just in code, but in documentation, meetings, decision-making, everything, too.

Taking a trip back in time
Enjoying my trip back in time

Large Scale VB6 to .NET: Still a Common Challenge

One of the most notable things I learned was that this is still a fairly common situation: there are many VB6 large applications still in production, still being actively supported and maintained. I couldn’t find any reliable figures for the number of installations in operation today in 2015 but there are certainly indications that the number is not small.

One article on InfoQ calls it a “looming crisis”, and outlines the problem well—in contrast to some of the comments, which came across as simplistic or naive—some suggesting, for example, that COM Interop (“for me, it is not theoretical. I’ve done it for years, and it works great,” says one) and migration tools (“upgrading VB6 applications to modern .NET (C# or VB.NET) using automatic tools is very easy and accurate,” says another who describes himself as a CTO) are the comprehensive solutions that have somehow inexplicably escaped everyone else who have not yet applied them. The article’s title does seem a little alarmist, though. On the other hand, if a business loses competitiveness and market share, if the business discovers too late that an upgrade will take a year and almost as much money as it took to build the original in the first place, then that is pretty much a crisis, from that business’ point of view.

The .NET Framework was released in 2002 and from the outset Microsoft and partners were already offering migration tools and services. In 2002, Microsoft Press released a complete technical guide called Upgrading Microsoft Visual Basic 6.0 to Microsoft Visual Basic .NET (download the free PDF from Microsoft). More than a decade later, why are there still any major line-of-business VB6 applications in production? Okay, there will be the cases where a system will never need any maintenance or extension ever again, or the need isn’t great enough to justify the cost, and these should be left in VB6. However, for the rest, even if a business had decided to put off a complete rewrite till after the release of .NET 3.5 and Visual Studio 2008, that rewrite should already be in production by now, eight years later. Clearly, the situation or the solution is not always straightforward.

There are still a number of vendors offering products, papers, and services for migrating from VB6 to .NET. They are found readily enough with an Internet search, so I won’t elaborate on them. If you’re just starting to look into this topic now, a good place to start is Microsoft’s own list of resources and partners. I will mention though that I consider the innovative approach taken by one particular vendor, VB Migration Partner, to be the most compatible with the strategy I developed and recommended to my client. (I’ll outline the approach in an upcoming blog post.)

Note that what I’m saying here is that converting code alone should not be the whole strategy. There is more to migration of a large application than simply sucking code in at one end, spitting out different code at the other, then testing the crap out of it. There are other serious considerations such as business continuity, training, resourcing, expertise in both old and new and dissimilar technologies, changes in project methodologies and practices and the tools that support them, just to name the most obvious examples.

A representation of a typical Windows DNA system.
A representation of a typical distributed Windows application. These systems are typically written almost entirely in VB6 except in web pages and the database.

What is Enterprise Scale?

Just to clarify: I’m referring generally to those systems with hundreds of thousands or even a million lines of code, with some form of distributed architecture comprising server-side tiers, including databases and middleware, and a separate fat or thin client.

A typical configuration is a client-side VB6 standard EXE installed on workstation PCs, often packaged with several custom/third-party controls and client-side DLLs, connected via DCOM over the local network to server-side COM+ components that handle: transactions, queuing, and connectivity to one or more databases—typically MS SQL Server or Oracle—via stored procedures or direct queries. There may also be other server software or services involved such as MSMQ or Queued Components, ASP, IIS, and Active Directory. All this is admittedly a rather jumbled outline, but anyone who has worked with classic VB6/COM+/MSSQL n-tier systems should immediately recognize the setup I just described.

The diagram below is a conceptual representation of the legacy application I worked with. Some particulars the migration would need to address:

  • The system was large—approximately a combined million lines of VB6 and SQL, a hundred forms, excessive number (hundreds) of classes, etc
  • The main client EXE referenced dozens of different custom and third-party components and controls, some (critically) without source code or vendor and for which COM Interop was not a satisfactory remedy
  • Lots of code violated the intention of the layers in which it lived (e.g. ADO connections in form code, SQL queries passed as strings from the client to the server)
  • There were over 1500 stored procedures containing over 90% of the business logic
  • A large COM+ “business” layer that consequently did nothing more than shunt requests and responses to and from the stored procedures
  • Many deployments of the entire system working standalone were being maintained on customers’ sites, hosting their own servers and networks

I’m not critiquing the original system, mind you. I mention these issues because there will be other businesses with similar issues, and those other businesses may be interested to know how we were going to handle ours. There must be very few “pure” architectures left in the VB6 world, after all…

A simplified depiction of the business' technology stack, written entirely in VB6 and SQL Server stored procedures and functions.
The technology stack, written entirely in VB6 and SQL Server stored procedures and functions, of one business I consulted to.

So, what about the non large/enterprise-scale applications? In addition to the “enterprise” applications, there are far greater numbers of smaller applications and utilities in the wild. As a former VB6 programmer in consultancies, I saw in every company I worked with typically 10, or many more, smaller applications and utilities. Although these standalone applications may also present a potentially real and costly risk to the business, my focus in this post is on those monolithic line-of-business systems, where the complexity and cost of dealing with obsolescence is many times larger.

Having said that, in your own planning, don’t forget to consider any smaller applications that depend on any part of the migration candidate system, directly or indirectly. This may include database schemas, server components, data exports/imports, work processes, etc. You don’t want to be scrambling for workarounds and kludges in the event that something is unexpectedly impacted by your migration.

Not Acting is Acting (Unwisely!)

By the time I was engaged to work on the strategy, my client had already poked for a few years at getting an upgrade underway. As time wore on, they realized they needed to take some definite steps or risk eventually being back-footed by circumstances outside their control.

VB6 was released in 1998, a full 17 years ago—an eternity in IT terms—and declared legacy in 2008. New programmers are not being taught nor opting to learn VB6. Even though classic Visual Basic still ranks #13 in the TIOBE Index for October 2015 of most popular programming languages, it would be irresponsible of any decision maker not to assume that the pool of VB6 programmers available to help with any migration effort will eventually dry up. Businesses will not be able to run Windows XP or XP Mode forever. (Technical support for XP and XP Mode was discontinued on April 8, 2014.) Despite polls and petitions to revive VB6, the language as a mainstream business tool is a dinosaur (obviously ignoring VBA in this discussion). Businesses will eventually be forced to resolve the issues presented by legacy applications and operating environments, and the competition for the last VB6 programmers will become stronger. Yes, all nice and fascinating (like Rasputin’s refusal to die might be fascinating), but of course the critical concern is what needs to be done in the face of inevitable obsolescence.

Failing to decide is clearly itself a decision, and the least prudent at that. Not to put too fine a point on it, but if the application concerned is mission-critical, failing to make strategic decisions and plan for continuity is tantamount to negligence.

Velocity Can Matter, Too

There’s another aspect to “acting” that may be relevant to you, and that is the pace of action. Any way you slice it, migration is a major undertaking and chances are that it will take you a long time. Depending on size, complexity, approach, and experience, a migration project could conceivably take from a few months to a couple of years, and that’s if the business makes it a top priority. That’s a long time for a line-of-business system to be in a state of transition. Working against this is the pace at which traditional VB6 “shops” move. I don’t think it is controversial to observe that development moved way slower back then.1 VB6 programmers grew up in a time of Unified Process, UML, PMBOK and project managers, heavyweight documentation, centralized version control and Visual SourceSafe, physical servers and server configuration, RPCs and LANs, tricky integration and package and deployment activities, etc. Now, we have unit testing, behavior-driven development, dependency injection, continuous integration, Lean principles, Agile/Scrum, test automation, distributed version control systems like Git, SOA and RESTful services, virtualized machines and databases and operating environments and services in the cloud. Going from the old to the new means acquiring many new skills and a different mindset.

VB6 organizations need to be more agile
VB6 organizations need to be more agile

I suspect that many VB6 shops will experience growing pains. Taking too narrow an approach to the strategy will make the pain greater. I included in my strategy the heads and principles of where I believed the organization needed to grow. Early in 2014, I wrote (optimistically, it turns out) that they should aim for a first-stage migration “before the end of 2014” and, by that time, “we will be agile”. Almost two years later, I’ve noticed some terms like “agile” and “sprint” have crept into their marketing literature but they have not yet made the real transformative leap.

And so I think progress may be disappointingly slow for many businesses. One client, for example, gave themselves five years(!) to complete migration. Even so, to be in the ballpark of that timeline, they will need to adopt and embrace many changes, even down to their culture. How? Obviously, an appropriate level of commitment and budget are critical. Just as important is the realization that much is new and changed in one-and-a-half decades past and that they must find a new passion to learn about them. Practically, it is important to find leadership in “new school” experience and skills; find practitioners of Scrum/Agile, and experienced .NET programmers with contemporary competence with modern tools and practices. Even better is a senior who has lived in both the “old world” and the “new world”.2 And best of all would be such a person who has worked on a migration project before.

To close out this post, here is an example of how old ways might hinder migration success. Back when VB6 programmers roamed the Earth, when a change to a system was proposed to the VB6/COM+/SQL system, the architect or technical lead first prepared a feasibility report or analysis. She analyzed existing code, played with new tools or libraries, perhaps retrieved some old technical documentation (then discarded it when he realized it wasn’t up to date). After many days, a draft version is emailed to all stakeholders and a review session scheduled. Everyone attends with printed copies of the document in hand and, for the next hour, steps through and debates the contents. The architect modifies the document accordingly; after a few such iterations, the document is signed off and accepted by the decision maker. Then follow the next stages of the waterfall, gathering increasing numbers of stakeholders and participants, producing thicker and more detailed documents along the way. Days can turn into weeks, weeks into months. Our strategy document was distributed for final review mid-July; we conducted that review in September.

In my next post, I’ll look at some migration options and how our choices were affected by stated project goals, desired migration benefits, and some specific technical issues.

Feature photo: I took the photo at the top of this post when I visited Uluru (Ayers Rock) during a singing tour to Alice Springs in February, 2014.


1. None of this impugns VB6’s major strength as a rapid application development tool. I used to fire up Visual Studio 6 anytime I wanted to try something quickly, the way many people fire up Excel to try plugging values into a table. I loved that I was immediately in the editor with no fuss and I could immediately start dropping controls onto forms or typing code—sometimes I didn’t need to do anything more than type in the Immediate window. It is everything else in and around the world of VB6 development that is slow.↩
2. Apologies for the use of vague terms like “old world” and “new world”: they’re just a convenience to refer to all the tools, techniques, environments, practices, etc used in two different eras of Microsoft programming.↩

Wild and Woolly Tech Blog

This is the second post to my new blog, Wild and Woolly Tech. What will my blog be about and why the title?

I’ve been in I.T. for over 20 years now. That’s the “tech” in a nutshell. My career started out traditionally enough, but it didn’t stay that way. From COBOL programming for a bank in Melbourne, Australia, in the early 1990s, through pioneering development in Chennai for a startup in LA, to writing this post in the office of a struggling startup in Ukraine, post-revolution and presently still at war, “wild and woolly” describe both my career and some of the locations to which my career has taken me.

Bridge over canal in Venice
Photo I took of a bridge in Venice in 2011. I should have done something about the blown out light in the sky either while taking the photo or post production… but just feeling a little lazy at the moment, I guess!

I intend to write some articles about issues and topics in tech management and the industry, lessons I’ve learned along the way, some of the stories, and some more or less technical articles. I hope you’ll stick around!

Can You Just Read a Book to be a Programmer?

Is this a serious question? To a programmer, very possibly no. One wouldn’t search for that one great book to learn to be a doctor or accountant. By the same token, programming should be accorded that same level of respect. Sure, those other professions are governed by professional bodies and require formal qualification even to begin to practise, whereas anyone (assuming a requisite minimum level of intelligence and aptitude) can become a programmer without formal qualifications. However, I’m talking about programming as a professional and, in that context, notwithstanding qualifications formal or otherwise the fact is that professional programming requires several high-level skills (of which the central skill of coding is but one) that take hundreds to thousands of hours to develop into expertise. And even putting all that aside, technology changes so quickly that it should be clear to anyone prepared to give a moment’s pause that any single book able to adequately school and equip the wanna-be technologist simply cannot reasonably be expected to exist.

Still, it’s a real question that, along with others just like it, get asked often. I attribute it to the rise in interest in programming in the face of increasingly pervasive technology and very public, out-of-this-world valuations. On those valuations, I still find it difficult to get my head around some of the numbers, though I follow the tech press daily. Multi-billion dollar valuations are difficult to really imagine—like imagining a finite universe (or an infinite one). The combined wealth in this comprehensive list of unicorns is beyond mind-boggling.

Browse “Learning to Program” on Quora and you’ll see questions like:

  • “How can I learn C++ in two weeks? This is making me depressed!”
  • “My dream is to become a software engineer preferably at Google. I’ve been trying to learn programming for the past couple months. I feel like I’m not learning enough to actually be worthwhile. What should I do to learn programming that would actually help me pursue my dream?”, and this gem—
  • “I am confident that I am going to build a search engine that will compete with Google at least in the smallest scale possible first, but for now I don’t know any programming. What should I do?”

I don’t want to give the impression that I’m looking down on anyone who genuinely wants to learn and is prepared to earn their dues. Much to the contrary, I would love to be able to offer any useful advice to such individuals who ask for it. And for those who do persist to the point of competence, respect! Some of these questions proceed not from self-delusion but from naivety, and that’s totally understandable. This question (that I answered) seemed to fall into this category: “What book should I read for building my app since I’m not a programmer?”

I gave a much longer answer along the same lines to this question: “What do you recommend someone who wants to learn how to think in programming?”. My answer included the following:

I presume you want to know how to develop yourself into a coder, starting from zero.

As others have said, you will learn most by doing. And you will learn a lot by asking for help: most programmers are very generous with their time (when you ask the right questions!) to help others…

From absolute zero, I would recommend one of the many online courses available today. Check out the list of resources in this article, which talks about the 17-year-old who sold his company for a cool $30 mil.: Learn To Program Like The Kid Millionaire Who Sold His Company To Yahoo…

A word of caution, if you don’t mind: a lot of people want to get into the industry because they know there’s a huge amount of money in it and, at the very least, they can get an above-average salary. By all means, learn if that is the reason, but you have to be prepared to persevere for many hours and endure no small measure of frustration. Ultimately, you will have to enjoy it or it just won’t be possible for you to succeed as a programmer… For me, it is one of the most satisfying, rewarding feelings in life for me when I’ve helped write something and then see it DO something and, best of all, when people use what I wrote to get shit done!

So, can you just read a book to be a programmer? Obviously, no. But that does not mean that you should not read programming books. You should, and then some. I’ll let this article be the final word on this topic: http://blog.codinghorror.com/programmers-dont-read-books-but-you-should/

Create your own website, free on WordPress.com.Create your own website.
Start free