7 ms·
In the context of a startup, I would expect almost all of those to be disappointing. But maybe that's what you're hoping to see. In my opinion, if you're a sta
by Waterluvian 8y ago
In the context of a startup, I would expect almost all of those to be disappointing. But maybe that's what you're hoping to see.
In my opinion, if you're a start-up and you've got all those boxes checked, you're possibly doing the right things in the wrong order, and that's a red flag for me. What I hope to hear are responses like, "so this is how we're doing CI. It's awful, almost non-existent. But that's because at our scale it just wasn't important. But as we grow it will become VERY important, so here's what we're thinking about doing in the next 6-12 months..."
I've experienced a start-up with lots of tooling and process , none of which matters when you take forever to ship (and stay shipped).
- owens99 8y agoThis. As I always say, "If you are building a startup, over-engineering is a far bigger sin than creating technical debt."
- andbberger 8y agoThat's just a cop out! Such a tired meme!
- angersock 8y agoIt's true though. What's your counterargument? Tired memes can be tired because they're true.
- hobofan 8y agoIf you want your startup to run for more than a year (= roughly the time the effects of technical debt start to kick in significantly in my experience), you need to find a good way how to handle technical debt, and keep it in check. I have seen my share of startups where a platform plagued with technical debt was the main limitation for growth, which is a very avoidable situation.
- JumpCrisscross 8y ago> If you want your startup to run for more than a year I've never seen a start-up fail on account of technical debt. Re-engineering is expensive, but it means you have something worth re-engineering. I've seen lots of start-ups fail because money that should have been spent attracting and retaining users got burned on an elaborate engineering process.
- andbberger 8y agoOk but like middle ground exists here. There is a huge difference between thinking carefully about what you need to do right and planning what bits are going to end up as technical debt, and how you can fix it later - and what actually ends up happening in my experience where everything is shit because we're too busy being a s t a r t u p to practice engineering.
- JumpCrisscross 8y ago> middle ground exists here The point is the middle ground exists closer to shitshow than well-oiled shop. If the CEO doesn't understand this, they won't be CEO for long.
- jiaweihli 8y ago> I've never seen a start-up fail on account of technical debt. That's because noone ever says "XYZ startup failed because their code quality wasn't good enough." It's usually something closer to "Their customers didn't renew contracts, they had to slash headcount, and went into a death spiral from there." If you press for details, the deeper reason might be "they couldn't turn around features fast enough" or "the app was slow or their servers went down too much" which is a symptom of too much technical debt (either directly, or because the better engineers on the team choose to leave as a consequence of the technical debt). I agree that early startups don't fail because of technical debt, but I'd bet that many mid-size startups do fail because of it.
- icedchai 8y ago
- ryanSrich 8y agoBut having CI, proper logging, and code review isn’t over engineering. The time, effort and bugs saved by spending 1-2 days putting these policies and procedures in place is valuable early on. Of course, each of those pieces is at risk of becoming over engineered. But hopefully the team has a leader that knows when to move forward and when to pull back.
- mcv 8y agoParticularly CI. If you want to be able to release fast and often, having that automated is going to save you a lot of time. And CI doesn't immediately have to include everything you'll eventually want; just having automated build and deploy will make your life a lot easier. Add some automated testing as soon as you can afford to (which hopefully is right away, because it's not that hard to set up), and you're ready to move.
- kybernetikos 8y agoAnd in many places they go hand in hand - some pieces of code will be massively over-engineered and genericised for a future that will never come, while other, important (but possibly less interesting) pieces will be peppered with // TODO and // THINK ABOUT THIS LATER.
- t0mbstone 8y agoSetting up CI is basically as simple as adding a small .yml config file to your git repo (if you are using a service like Travis or Circle CI) and clicking a couple of buttons to give the tool access to your github repo.
- rjvs 8y agoIf you are writing a web app maybe, if you’re writing a VR app, it’s definitely not that easy.
- retiredcoder 8y agoTrue to that. Software engineering isn’t just web apps.
- flukus 8y agoIsn't over-engineering a type of technical debt? At the very least both can exist simultaneously.
- pandler 8y agoUnfortunately I’ve met some people that take that mentality to a macho extreme in the form of “if you want to be STARTUP, you should actively avoid doing anything that resembles forethought.”
- latch 8y agoI would expect most to be disappointing too, and it's a good idea to avoid those. Proper logging doesn't take more time, it just takes more discipline / giving a damn. People and companies that say: we don't have time to do it right Almost always mean: we don't know how to do it right Talent, not time, is the enemy of quality. (at some point that stops being true, but most companies (startups or not) are soooo far from that). If we are talking about a really young/small startup and you're a senior person, then you need to have a discussion about it with whoever you answer to. If we're talking about a really young/small startup and you're a jr person, you'll just learn a bunch of shitty habits. If we're talking about an older/larger startup, then you have a problem.
- pmart123 8y agoMaybe the context of the answer is more valuable than the answer in this case? i.e. we have 95% coverage on our core IP and CI setup for all of our source code. But, we integrated X for that service to get off the ground quickly, which will be too expensive at scale so we didn’t implement testing around it yet.
- nostrademons 8y agoI think the point Waterluvian is making is that if a startup has all its development practices buttoned down right, it's either not a startup or it's going to go out of business soon. Most people (who are even thinking of working at a startup, at least) would rather have a job that's organized chaos than not have a job at all. The ideal order of tasks for a startup usually looks something like this (and I say "ideal" because very few startups actually take paths resembling anything close to this): 1.) Figure out what & for whom you're building the product. The founders should do this before hiring employees. 2.) Validate that the people for whom you're building the product will use it, and ideally will pay for it. The founders should do this before hiring employees. 3.) Take investment. Ideally this would get pushed as late as possible or skipped entirely, both because you get better terms for that money when you've made more progress and because it often comes with strings that prevent you from going back to step #1 if necessary, but it's usually a prerequisite for step #4. 4.) Build the product. If the founders can do this themselves, they're at a huge advantage, because oftentimes you find you need to go back to step #1 after this is complete. But usually you need employees for this. 5.) Charge money, so that it becomes a sustainable business. 6.) Everything else that goes with being an actual business, from getting HR policies right to development practices to career ladders for employees to working out company mission statements. And if you're doing step #6 before you've completed step #5, there is a very large chance that you've made a critical error in judgment that will kill the company. Why? Because you haven't actually validated step #1, and all the work in steps #4-6 depends upon getting that right. You might have setup a beautiful CI dashboard with 100% test coverage, only to find that all your unit tests & continuous integration need to be thrown out because your product needs to be rewritten in another language because the product concept requires a large & critical library that's only available in another language. You might have spent months developing & building relationships with employees only to find they need to be fired because you need a completely different skillset to build a different product for a different market. It's fine to want a nice, orderly, 100% tested with CI setup and a robust release process development process as your working environment. At an earlier point in my career, I certainly did. But if that's what you want, I would highly recommend not working at a startup and going to Google instead, where you have a full test suite run on 1000s of machines on every commit and the results of it are instantly visible on their code review dashboard. That's what I did, and it was only when I realized that Google in 1999 was about as far away from that as it's possible to get that I became more comfortable with the codebase being a complete mess as long as it works & has happy users.
- e3b0c 8y ago> In my opinion, if you're a start-up and you've got all those boxes checked, you're possibly doing the right things in the wrong order, and that's a red flag for me. In my opinion, that depends on the experience/background of your staff. I have even seen open source projects (not backed by companies) get all the boxes checked in a very short period of time. For a project maintainer who has prior experience, it just takes several hours at most to set up a git hosting server and the CI/CD infrastructure. The time saved for fixing a single regressing can easily pay off the investment.
- TheCondor 8y agoI don’t disagree with you, not entirely. When I was younger, it was all about sprinting full out as long as possible and that is a company that is either going straight to the moon of more often bursting in to flames. I’m quite a bit older and more senior now too and I think there are two slices of startup time, you put in your 45hours doing whatever it is the company needs, often running like hell. Then there is the 5-15 extra hours a week a startup can take and I absolutely think those need to be spent on dividend earning things, logging, ci, documentation, better testing, tooling, etc. Thing is, it can go to the moon or it can flame out but there is this giant middle part of the spectrum where there are good exits and those exits often involve supporting your product and having well documented and tested technology is a positive. Trust me on this, it really sucks to get bought and then explain that it’s going to be a year and a rewrite to do the 10 things the buyer wanted yesterday.
- leonroy 8y agoDunno...one man band here until very recently. I had Github > CircleCI > Heroku automatic deploys on pass implemented on my own with LogDNA + Sentry.io to catch errors and monitor output. Using Clubhouse to manage mine and the other dev's work now and it all seamlessly links up. Took at most 30 mins to a few hours to setup each integration. Only downside is the monthly cost of all of the above but in all honesty if even a small startup doesn't have most of the above I'd consider that worrying.
- retiredcoder 8y agoYeah, that’s pretty easy for a web App. Things aren’t that simple for companies with more complex stack, like embedded systems for example.