8 ms·
Every time I spin up a new project, I try to answer the following question honestly: "Am I using this project as an excuse to learn some new technology
by aaronbrethorst 12y ago
Every time I spin up a new project, I try to answer the following question honestly:
"Am I using this project as an excuse to learn
some new technology, or am I trying to solve a problem?"
Trying to learn some new technology? Awesome, I get to use one new thing. Since I already understand every other variable in my stack, I'll have a much easier time pinning down those 'unknown unknown' issues that invariably crop up over time.
Trying to solve a problem? I'm going to use what I already know. For web stuff, this'll be a super-boring, totally standard Rails web app that generates HTML (ugh, right? How last century), or maybe a JSON API if I'm trying to consume its output in a native app. For mobile stuff, this'll be an Objective-C iOS app.
Waffling about it and saying 'well, I am trying to solve a problem, and I think maybe a new whiz-bang technology is the best way to do it' is the simplest path to failing miserably. I've watched incredibly well-funded startups with smart people fail miserably at delivering a solution on-time because an engineer was able to convince the powers that be that a buzzword-laden architecture was the way to go.
You don't know what the 'right' solution is unless you understand the tools and technology you'll use to deliver that solution. Anything else is just cargo-culting.
- stevesearer 12y agoI do the same thing and usually end up trying to solve a problem using WordPress which is probably cringe-worthy to a lot of people. Most of the things I come up with are basically content-publishing so it works really well for hacking around and making something fun. My latest creation is a instagram-style feed of the beers a few friends of mine have been enjoying recently. It works just fine and none of my non-technical friends have cared that they add beers in their mobile browser rather than via an app or something.
- mandeepj 12y ago> "Am I using this project as an excuse to learn some new technology, or am I trying to solve a problem?" How about both?
- aaronbrethorst 12y agoYou may well eventually solve the problem, but not on a timeframe that will be useful to anyone besides yourself.
- smikhanov 12y agoUsefulness to yourself is sometimes the only thing that matters. I'm not trying to be snarky here: your own self-development is not anyone's interest, except yours. If you're a PHP developer wanting to start some Python, your boss would love you to continue working with legacy codebase using PHP instead of migrating parts of it to Python. At the expense of your future career prospects, of course.
- aaronbrethorst 12y agoI'm talking more about delivering value and less about self-improvement. Both have a time and a place, but your boss is unlikely to look kindly on you saying "I'm interested in learning Python, so I've decided to rewrite our 1mm user web app in Python instead of fixing the bugs you asked me to, because I think I could make more money with that than PHP."
- kasey_junk 12y agoActually, as a boss I frequently do look kindly on that. I'd much prefer to have that built into assumptions and explicit upfront. Sometimes I may say "can we do that on our 1K user side project instead?" but I think that if you are managing developmental resources and you are not allowing them learn new things, you are not following a strategy that is likely to work out long term.
- aaronbrethorst 12y ago> I'd much prefer to have that built into assumptions and explicit upfront. How do you build unbounded learning time and an unguessable set of work items into a schedule?
- pothibo 12y agoThat's a great approach. By restricting yourself to one new thing, you can evaluate it in isolation. Then, when you make your decision about that new thing, you'll know why you like/dislike it. Your decision won't be clouded by arbitrary things like libraries inter-dependencies.
- snowwrestler 12y agoHow much can you learn if you're not trying to solve a real problem, though? My personal experience is that I can dink around with a new technology all I want, and not learn half as much as when I'm trying to apply it to do something real.
- aaronbrethorst 12y agoSorry, I was more vague on that initially than I should've been. I've answered this elsewhere, but: what I was referring to was delivering value on behalf of someone else vs. using a given problem as an opportunity to learn something new. Delivering value (e.g. adding a new feature to your product, fixing a bug in a shipping product, identifying and attacking a market opportunity) shouldn't be seen as an excuse to learn a new technology unless you have absolutely no pressure to ship that work on any sort of schedule at any presumed level of acceptable quality. I'm the same way: I need a real problem to work whether I'm applying skills I know or skills I want to learn. I just don't ever promise anyone (except myself) anything when I'm applying technologies I don't yet know to the problem.
- Scarbutt 12y ago(ugh, right? How last century) Its not really about a "last century" thing, "last century" most apps need not multiple front-ends like today, unless you are 100% you won't need multiple front-ends, doing a json api from the start simplifies things a lot.
- aaronbrethorst 12y agoI was being a smartass :) unless you are 100% you won't need multiple front-ends, doing a json api from the start simplifies things a lot. This also presumes that I already know Backbone, Ember, React, Knockout, Batman, Angular, or whichever new JS single page app frameworks have appeared in the last 30 seconds. Would you agree that it's easier[1] to write a web app that emits HTML than it is to write a web app that emits JSON which is consumed by a single page web app written in Javascript? [1] Where I define "easier" in this context to mean requiring less wall clock time to get something showing up on-screen and doing something useful.
- mbell 12y agoYou don't have to use a JS MVC framework just because you built your core logic behind a JSON API. You can just as easily have a server side rendering app talk to the JSON API instead of the directly to the datastores. You get to stick with 'what you know' while still maintaining flexibility for later.
- Scarbutt 12y agoyes, but it will more complex and take up more time, which I think is what he is talking about.
- nostrademons 12y agoLast century most apps absolutely did need multiple front-ends. Don't you remember the days when there was a Windows version, a Mac version, a Java version, if you were lucky a Linux version, and maybe a web version for the bleeding-edge developers? Relatively fewer apps were network-enabled, but even then, there were a bunch of technologies like CORBA, DCOM, and RMI to marshal communications. There were also a bunch of custom binary protocols; back then, it was common for software developers to work on all levels of the stack, and the culture of library re-use was not as entrenched (at least in the enterprise) as it is today.
- shebson 12y agoI generally agree with your post, but I think there is a critical difference between your argument and that of the blog post. Of course teams are more productive with technologies they know, but that isn't necessarily an arbitrarily-defined "boring" technology. To pick on one specific example in the post: Node.js is popular enough that there are lots of teams and engineers that are most comfortable and productive working with it. For these teams, choosing Node certainly wouldn't cost an innovation token, while deciding to build some service in Python, Ruby or PHP (if we take at face value that this is more "boring") may end up being more costly.
- fineline 12y agoYep, what's "innovative" for one person or team is "boring" for another, and vice versa. NodeJS / PHP is a good example.
- wdewind 12y ago> For these teams, choosing Node certainly wouldn't cost an innovation token, while deciding to build some service in Python, Ruby or PHP (if we take at face value that this is more "boring") may end up being more costly. It absolutely does if it is only one team in the organization. If the entire organization is using PHP and, let's say, you acqui-hire a team based on NodeJS, unless they are doing something absolutely fundamentally different they should learn PHP and push code in your existing infrastructure. This way you have one way to deploy, one type of application server to support, one set of gotchas relevant to your domain, one set of QA tools etc. Building good products is about far more than just shipping the product, it's also about the cost of long term support. Because what you are doing is fundamentally automation, the less you have to manage the more benefit of the automation you are getting, the more you can forget about it and focus on shipping other things. What you are describing is pretty much definitionally local optimization and is exactly what you shouldn't do in large engineering organizations.
- mentat 12y agoDepends on your increment of isolation. This is, in theory, why microservices with APIs mean that it really doesn't matter. As long as there are sufficient hire-able engineers who know that technology, it can be used.
- emmanueloga_ 12y agoComments here are geared against picking a technology just because it is brand new and exciting, but sometimes you need to pick up something that is just different from what you or your team know well. In a project I worked on once, we went with "what we knew" (standard normalized SQL schema) to build an analytics engine. The problem with "going with what you know" is you are likely to badly reinvent well-established patterns. If we had stop for a minute and learnt about star schemas, the project could have ended in a much better shape than it did, and maybe the effective time to release would had been shortened. BTW, learning "new things" is almost always useful but isn't always precisely exciting. Data warehousing is one example :-). Becoming proficient with a selected set of technologies is still a good idea, but I'm willing to learn and try new things all the time. First thing I ask myself is if a problem was already solved by someone else, and how.
- mwsherman 12y agoFWIW, maybe the approach in this case is traditional normalization to get the product out the door. When it becomes untenable, hire someone for whom star schemas are boring. Put another way, the star schema was known to be a better approach only after the fact. Had your team researched “exotic” (unfamiliar) approaches early on, there is no guarantee you would have landed on a star schema.
- woah 12y agoEehhh... I knew about star schemas already, although I've never used one. I do think my cursory knowledge would have caused me to research them when starting a project like that though. Obviously it's all got to be a balance, but I think that the OP is probably a little bit too conservative. Especially if you are working for other people, we are paid to innovate, and we are paid to learn stuff until it is boring. We've got to stick up for ourselves and learn on the job when we can. One new thing a project sounds great to me.
- neverminder 12y ago> I'm going to use what I already know. Using what you already know may not always be the best approach, because of "When your only tool is a hammer every problem looks like a nail" phenomenon. I would do my research and use what makes sense and what is best in the long run, despite of me being experienced or not in the technology. When you're a software engineer with years of experience under your belt, picking up the next one will not be a big challenge.
- collyw 12y agoYes, I think this is where experience comes into it. Knowing when it will likely pay off in the long run. As a junior its difficult to differentiate between hype and genuine usefulness.
- ehurrell 12y agoGreat advice. Also extends to teams, 'What do we all know well enough to execute?' should trump 'What would be fun?' every time. I've worked in situations where someone saying 'Oh I decided to write this in Clojure, even though I'm the only one here who knows it and we're running out of cash' cost significant time and resources to fix (the fix was rewriting the project in plain ol' Python myself). It just isn't a sensible risk to take.