Getting ready to build a billion-dollar business

May 4, 2021 michaela 00:52:46

In this episode, I talk to Max Stoiber. Max is a JavaScript Engineer that is in love with React and Node, and also a fellow Austrian. He has a track record in the open-source world, worked for Gatsby, and Github, and also is a successful entrepreneur.

We talk about:

what he learned about software engineering best practices at GitHub,
why he started his newest side-project bedrock,
why building an indie or small lifestyle businesses is not his thing anymore,
and how he prepares to build a billion-dollar business.

Book your awesomecodereview.com workshop! Secure Code Review Workshops are coming soon too!

Links:

Subscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Transcript: Getting ready for a billion-dollar business

[If you want, you can help make the transcript better, and improve the podcast’s accessibility via Github. I’m happy to lend a hand to help you get started with pull requests, and open source work.]

with spectrum you can look at it. It’s, it’s one big Monterey pro basically that contains all of our servers, all of our clients, everything we ever built. It’s all completely open source. It’s terrible code, please. Don’t look at it too, too closely. I love product what we did cause we did a lot of shipping and not a lot of cleaning up, but it works and it’s open social people to look at. It’s a, it’s quite funny because I think spectrum is quite a messy copays personally. Like it’s not, it’s not the nicest code I’ve ever written. I didn’t have as much experience then as I do now. And, and also we were just trying to ship as much as possible. I’m trying to figure out, trying to find product market fit and then eventually the business market fit And it’s funny because sometimes I see tweets of people saying, Oh, if you want to see a really well architect, the copays, go look at spectrum. And every single time I see that I like please, please. Don’t like, that’s not, it’s not that well, I can think of, it’s kind of a pain to work with. I don’t know. Yeah,
Michaela: [00:12:37] I know you cannot respond to every tweet like that. Like
Max: [00:12:41] exactly. Yeah. I can’t really be like, ah, hello. Yeah, please. Don’t look at my work. It’s really bad. That’s not a good idea. I can’t really do that. But it is, it was very interesting. I do think spectrum helped a lot of people think about how they build apps, right. And it has a lot of people to learn and it was quite fascinating to open source it and see how many people actually cared. Because there is so few food products out there that are open source, right? Usually when something’s open source is either a toy product, the toy project that somebody builds, or it’s a library that’s very encapsulated, very small, but very few people open source, entire apps, right. Century being one of the many, many exceptions and one of the most famous ones or ghost, for example, but there’s only like a handful of those. And so adding to that list was quite interesting how much people responded to that and how much they liked it.
Michaela: [00:13:27] Yeah, because I mean, I think so I’m a, for example, I’m learning Peyton things two years now. And I’m also a little bit struggling with, how should I actually go about learning Peyton. Right. And that, that has to do that while I’m not employed as a heightened developer right now. Right. Which also limits, you know, the. The amount that I can actually spend on it or that I spend on it. It also means that I don’t have like a network of people around me that I can learn from, right. Like code reviews that you have. If I would be a Putin developer right now, I would have like my colleagues also writing Python code and I can learn from them. Right. And so open source is definitely something that I’m also sometimes doing. Right. I go and look at Ida patent application to just understand, you know, how ID architecting something, because these are the questions that I still have. Right. I don’t have the question on which type to use or how to do it area or how to do a list, sorta whatnot. Right. So I know those things already from my other programming adventures that I did, but I’m more interested in, Oh, I’m coming from the job are object oriented C-sharp world. Right. So how do you do that in Piketon and, and how would you, you know, structured applications and open source is something that sometimes helps me, but it’s very hard to find like either like a good application again, because sometimes you find application and I’m looking at it. And even though I don’t feel like I’m the expert for piping, I can say, Oh, I shouldn’t call it. What’s going on here. Right. And then it’s big enough that it’s interesting to look at and has, you know, good quality and you can learn something from it. I think it’s very, very valuable. I can totally see how people are. Yeah. Interested in, in doing that and learning more about it. So, but now you, you build spectrum and then it was actually acquired by GitHub. Right. And so you’d done because it was acquired, you worked at guitar building, you know, GitHub or spectrum into get-ups right. And get into YouTube. How did their view changed on software engineering practices on good code? Did you experience something like that that suddenly you were in a team and they are all, you know, like working together and you can learn you know, you can improve your skillset, sat there with, with the input of your peers or how, how was that for you?
Max: [00:15:36] Because we very quickly realized that spectrum just wasn’t built well enough to run a Kitsap scale. It was very fascinating to learn how Kitsap scaled itself, because obviously when they started building gets up 10 years ago or however long that was, they also didn’t build it to handle the amount of traffic that it has now, because GitHub is massive. It’s one of the, I think, 10 biggest websites on the planet, maybe 15 biggest websites on the planet. It’s, it’s massive. It, it gets absurdly much traffic. And so it was very fascinating to be at Kitsap and to see How careful they are about the code they write and how many conventions and constraints they built into their systems, particularly for the developers. So that any code that that is that is written is good enough to run at that scale because most people have never worked at that scale before, unless you’ve worked at Kitsap before, or one of the other 15 companies, that’s this big, you have no idea how to work with that scale. Right? And so a lot of the work that many teams that get to did was building tools for other developers that gets hub to guide them towards success and to avoid expensive database queries, to detect them, to warn people when they were writing them, stuff like that, where they built a lot of internal tooling to make sure that they could run at scale and that they could continue scaling into the future. And I actually think a lot of what I, what I learned there was how important constraints are with programming. You have all the options, you have all the possibilities, you can do whatever you want, but a lot of what it means to be a senior or an experienced developer is knowing which 90% of those options are actually trash. And you probably shouldn’t do them because you’re going to run into problems. Right? A lot of the choices that experience developers make are based on experience and I’m talking to other experience developers and they avoid future problems, right. By, by making good decisions. Now you avoid a lot of future problems and sort of. Avoid running into troubles down the line. And that’s something I’d never done before with spectrum. And so with spectrum, we actually had a lot of scaling problems when there’s this sort of rule of thumb that started people say where every single time you get a new order of magnitude of users, you run into new scaling problems. And for us, it happened like that, like clockwork. When we ran from zero to a thousand users at the, when we onboarded our first community, we immediately hit scaling issues. We immediately had to move away from Firebase, build our own backend because Firebase was couldn’t sustain the load anymore. Then when we went from 1000 to 10,000 people, we hit the next set of scaling problems. As soon as basically as soon as the 10,000 persons joined almost to the day we started having server issues. And so we had to resolve those, then everything went fine. We’re going, we doubled, we tripled, we quadrupled. We went from 10,000 to 9,000 people. No problem. And then as soon as we hit the a hundred thousand monthly active users, the next set up problems, they didn’t get in with them releasing our server. Our servers were crashing constantly. And it was very fascinating how these, this sort of order of magnitude step change of traffic really impacted our stability. And so get ups really focused on making sure no one that gets up some writes code that doesn’t run it, their order of line of traffic, that no one, there can even commit something to the code base, no matter how inexperienced they are or how much they fork rails, for example, that could break their systems. And then when something breaks, they have a lot of infrastructure, of course, around that, to monitor, to fix those issues, to roll back deploys so that when problems do arise, they don’t impact many users. And it was fascinating to see that and to see how many constraints. They put on people, but they were very productive constraints as a developer. They made me free to build the stuff that I wanted to build without having to worry about scaling, because I knew if I did something that was bad, there would be an Arizona. Right. See, I would throw an error. There would be a winter error. There will be a test error, right. Like somewhere, somebody somewhere would catch my stupidity and tell me to do it differently. And so that was actually really fascinating. And they learned a lot about scaling engineering and then organizations there.
Michaela: [00:19:31] Yeah. And so it seems that this is also very specific. So some of the engineering practices, some of the tools, some of the processes are really made for the scale there. But now if you’re going back and I know you’re now building a new startup, so what do you take away from that? What do you say? Well, you know, this is overkill not needed for me right now in my next startup. Right. And what are some of the, the, the practices the knowledge that you acquired your thing? Well, I’m going to build that in from the start and get go, because I don’t want to run into issues. Long-term with maintainability, readability of the code base, many things.
Max: [00:20:08] We, we made many, many mistakes, or I should say I made many of those mistakes as the main technical person, that spectrum, I made many tech choices, mistakes. And one of the main things I really learned is that. Using technology that’s widely used is a very good idea. There’s a reason people use Maya’s quail or now Postgres, right? It’s because those two databases, they run and they keep running no matter what scaling crap, right? Like it’s a famously uses my SQL and is the 15th biggest website on the planet. And I think they’re now starting to hit the limits of that. And they’re starting to have to really work around a lot of these problems. But they managed to become the 15th biggest website on the planet with my SQL. So why would you use anything else? And I’ll be like, there’s no reason to choose anything that is less battle-tested because, you know, if, because if you end up being the 15th biggest website on the planet, you can fix my SQL. If you don’t end up being the 15th biggest website on the planet, it doesn’t matter. Right. It it’ll still work. And at spectrum we chose a database that was a lot less populated. What’s called rethink to be the company behind a shutdown because they weren’t financially successful. And the database system just wasn’t as well built as my, as going reading be. And we ran into a lot of scaling troubles because of our database choice or because of the database choice I made. And so I learned to rely on battle, test that technology, even if it’s under equals boring, even if it’s something that a lot of people use, that’s a good thing, because that means it’ll scale with you. And if you have a problem, you can Google it right with rethink to be almost nobody used it. And so when we ran into problems with our careers, when we ran into problems with the database engine, we Googled them and we found nothing. There were, there was no information, which is very different if you’re using MySQL or Postgres, if you Google any problem, I guarantee you you’ll find 10 pages of Google results with people explaining different solutions to the problem, how they approached it, how they fixed it, how it held up over time, right. And that that sort of Corpus of knowledge and that Corpus of experience is incredibly valuable when evaluating technology choices. That’s really one of the main things I learned, which is obvious in hindsight and is, it’s a common thing to say. Don’t use boring technology, use things that are proven to scale. But it’s really hard to keep that in mind when you’re using technology, because you will, you’ll see something that’s fancy and new and you’re going to want to use it. And it’s, it’s cool and everybody’s using it. And you feel like everybody in Twitter is talking about it, but if nobody’s used it at scale before, you’ve no idea if it works out right. And you can only, I think there’s often these tools have upsides, but the trade off of the missing community, the missing usage, the missing scalability, isn’t worth, there’s some tools where that isn’t the case. So I would still evaluate that sort of as a trader. Right. Does this tool make me so much more productive that I can handle production problems? Is it, is it production critical at all? So there’s like, there’s, you have to think about that, but always err, on the side of choosing boring technology, that’s proven to scale.
Michaela: [00:22:52] Yeah, I think that’s a, that’s such a good advice. And I also ran into dad when I was I was choosing which, you know, static site generator to use. And like, they’re, they’re the ones that, you know, right. Like Gatsby or Jacquelyn, I think like this. And then there are a lot of others, like tiny ones. And I was like, Oh, this is one that nobody knows over there seems really promising and interesting and you know, like shine in you. And I think it was also curiosity. Right? I think that a lot of engineers are very curious. I am curious. So I went with that one. But what I forgot to calculate is how much time I’m actually spending, building my website with that acquiring knowledge, then knowing how to use that thing, but also at the same time, learning that there is not enough support information around to, to get me out of errors that I run into, or maybe it’s even, you know, like the thing itself it’s broken. Right. And it also reminds me of, I actually tweeted, I think recently about this where some tools make me cry. And it was like when we, when I was at Microsoft and I had to use some internal tooling, that was really new and we just build it until we were doc fooding it. And we were forced sort of like to use that new thing, which is it’s a good thing. Right. But on the other hand, I couldn’t just go and search for the problems that I run into because it wasn’t even existing outside. And so internally people were building it, they weren’t really like, you know, supporting others or writing blog posts. So it was really a bad experience and something that made me think a lot about so important that if you’re stuck, that you can find information that gets you out of this, that gets you unstuck, it gets you out of this, you know, stuck situation and maturity of software projects and community and livelihood. Right. It’s definitely something that’s, that’s important here.
Max: [00:24:43] Absolutely. I think this is. Even more critical in areas where you don’t have a lot of experience that the less, you know, about a problem, the more you shouldn’t rely on boring existing solutions. I know nothing about databases, so I should probably use my SQL and Postgres because I know that those are gonna work. And any problem I have, I can find a solution for, I know a lot about react. And so I can, I know I can, for example, use Preact instead of react, because I understand very deeply how react and Preact work and I can debug my own problems. Right. And so a lot of this also has to do, like you said, with familiarity, right? If I’m familiar with, with a certain problem space, if I’m familiar with the tools within the problem space, I have a lot more leeway to use cutting-edge solutions. If I’m in a problem space where I have a NOAA experience where I don’t know how anything works, if that doesn’t make sense to be on the cutting edge, because I’m not gonna be able to resolve my own problems. And so I think, like I said, that that really ties into it, that sort of familiarity that understanding of the ecosystem is really critical. If you’re using something on the cutting edge.
Michaela: [00:25:39] Yeah. Yeah, definitely. And so maybe, I mean, what me too is very often startup founders, especially ones that are new and maybe they don’t even have a tech background. Right. They’re like what tech stack should I use? Grade one? What what languages and so on, should I build up? And most of the time the answer is, well, the ones that you’re mostly familiar with, right? So if you are a Python developer, probably just stick with Python. If you’re a Perl developer, maybe it makes sense, you know, to update your texts. Most of the time you’re like, Peyton is just fine or Ruby is just fine. Right? You don’t have to have, like, you don’t have to learn JavaScript and react if that’s not where you’re coming from. But so now for your new startup, I want to talk a little bit about the app. So you’re going to do something new. How are you going to, you know, how are you going to come up with the idea? And maybe with ties in a little bit here, it’s like bedrock. So recently you released a new product called bedrock and that’s like everything you need to know or everything you need to have to build SAS apps. Right. So it would be authentication. It would be emailing a little bit community subscription payments and all of that. Right? So sort of the pilot plate code of SAS applications that people can use. And when I saw it, I mean, it, it got really viral on Twitter. So people were really like, very happy to get that. And and I think it’s one of those problems that you see people running into. And so how was that for you? I mean, it looked like super popular. Was it also from the sales perspective, was it as successful as you hoped and, and will the next product that you’re working on being that space or will you go somewhere completely Allison? How are you going to, to tackle the next problem? How did you come up with this idea?
Max: [00:27:27] Sure. So I’ll start from the beginning. I I’ve spent the past, basically all of my career building JavaScript tooling. I’m sort of, I would say mainly well known for making a bunch of open-source projects, like react polo plate and style components that are cutting edge, new ways of doing things right. And I have a very deep understanding of react and JavaScript tooling and to have a good overview of the ecosystem. And I know how things work at a very deep level. And particularly at Gatsby now over the past year, I really dove deep into that because Gatsby basically is just a bunch of open source 20 combined in a very nice way. And what I realized was that I kept building SAS products on the sides, but I kept doing the same setup every single time. And every single time, it kind of sucked. Like I have enough experience to know, like I said, to avoid 90% of the bad choices, but in the JavaScript ecosystem, it can sometimes feel like 99% of the choices are bad. And you have to just make that 1% of choices to make all of the tools that you use work really well together. And making all those choices right, is really, really, really difficult and takes a very long time. When I set up my last, my last sort of SAS product feedback Fisher, I probably spent at least a week just setting up the boilerplate code, right. Just setting up TypeScript, prettier easily in payments, authentication database, a GraphQL API, graphical client, all of those stuff, all of that stuff. So that it works well together and sort of is easily usable. And doesn’t just break down after a while. It’s actually really difficult. And even after a week, I wasn’t happy with where I was at, but we just kind of have to build our product at that point. Right. Like you can only spend so much time setting up. And so after that, I actually took what I had after a week. And I said, okay, I’m going to sit down and I’m going to make this as nice as possible. And I spent at least three weeks of evenings and weekends just building Building a boilerplate really like I just plugged together glucose, right? Like it’s basically a bunch of configuration and glucose so that everything just works really well together. And now it’s at a point where, for example, if you change, if you add a required field in the database, your seat data for your end-to-end test is going to throw an error that, that the required field doesn’t exist. And the entire thing from tobacco just works really well together from testing over client, over backend, over everything you need just works really, really well together. And I had that, I had that boiler plate and I was like, well, this is kind of nice. Like, this actually feels really fantastic to work with just yesterday. I set up a new version of change feed one of my SAS apps. Cause we were we, we kind of need to rebuild it because it takes stack. Isn’t very nice that we chose there and slowing us down a lot. And so I basically rebuild all of the core functionality in an hour. Right. I took bedrock. I added a bunch of stuff to the API. I added some fields to the client and it’s ugly as hell. Like the client, doesn’t it it’s completely front-end list. So the client looks likely to sell, but everything works. And that only took me an hour. And of course there’s a lot of stuff to make it production ready into, add to make the build the client of course, make everything nice at onboarding, whatever, but it works right. And it has everything I sort of need. And so long story short, that’s why I thought about selling it. Right. And I was like, well, if I think this is nice and it’s, if it took me, somebody who really understands this problem very deeply into really understands that ecosystem deeply. If it takes me four weeks to set up something that’s good, that that’s really good. And that, that that sort of saves people time and is better than what they could do themselves. Then maybe it’s we are selling that, that sort of knowledge and that experience to people as a boilerplate and people were kind of excited about it. Then I think by now I have about a hundred pre-orders somewhere in that order of magnitude, 105, I think, which is really exciting to see. It’s kind of funny. I, I honestly didn’t expect to get a hundred pre-orders because there, there isn’t even a demo on the landing page. It’s just a landing page to explain what I want to do. It doesn’t even show anything yet. And yet people, a hundred people pre-order, which tells me two things. One, the community really trusts me, which is fricking scary. Like that is very scary to, for me because now I have to deliver and I have to deliver something. That’s actually as good as I promised, which I think I can do, but it’s a lot of pressure. And then secondly, there’s a, there’s a need for this, right. People struggle with setting up JavaScript project very well. And they’re willing to pay for a solution to that problem. And so that’s exciting to see, I don’t think I’m going to make this, my next startup per se, but it’s a really nice product to work on. And it’s just something that I personally really care about and I really enjoy doing. And so it was just like a fun, fun project, if that makes sense. Yeah. When I
Michaela: [00:31:46] started tweet was like, wow, that’s such a great idea because I was exactly imagining something like this that you run into the problem over and over again, you have this expertise, you have the wig Dan sort of, right. So you’re there, there’s obviously more work that you probably could in now to make this even better than what we would do for yourself. But in general, there’s like this foundation. And I mean, especially if people want to start a SARS app or, you know, do their own startup, I hope that they’re smart enough to realize that, you know, I think right now you’re selling it for 150 or 149 bucks. And later it’s like 200. I mean that this is like a bargain, right? Because I mean, if I’m spending a month, I could do. And as you said, they probably spend two months. They could really think about their, their solution. They could talk to customers, they could, you know, find out which problems to solve instead of doing that work for you. So I think it’s really a fantastic idea to, to go that route and do that. And it’s also great to see that people are backing you up. I think, I mean, obviously it’s frightening, right? If you have like, you have a platform, you have like a community around, but it also see you also, I think it’s also really beautiful to see that. They are people who care about what you’re doing and who trust, you know, you and I experienced you as a very authentic, very honest person. Right. So it’s not like, Oh, I’m doing everything that I do is really cool, but like, Oh, I’m making mistakes, but I’m learning from it and I’m sharing it here. Right. And so I think this is definitely something that people can, they realize, and, and this is why they are there right beside you. Right. And so but now we’re coming, you said, this is probably not what you’re going to do for your, for your new startup. So how, how is that? No, dis tricky, first part, like we have this idea, you want to do something and now you have to start in one direction. Right. And so how are you going to tackle that problem? And, and yeah. How do you think that you can set yourself up for success in the right direction? I think,
Max: [00:33:48] Multiple, multiple things. One is being very clear about what I want to accomplish. I want to build a billion dollar startup in my life. That is sort of the thing I want to try next. I’m not right now. I don’t want to build a, a indie hacker business. Right. I don’t want to build something on my own and I I’m perfectly happy to do that. Right. But right now at the life stage, I’m at, I don’t have kids. I’m relatively young, still. I don’t have a lot of commitments. I have the opportunity to try and really build something that changes the world. And so I want to try doing that. And that immediately already tells you a lot about the problems I can tackle, right? There’s problems I can tackle with that, that are big enough. Like the, basically the promise has to be big enough to eventually be worth a billion dollars. Right. They have to be really big problems. If you’re solving something that’s a small problem. It’s never going to be a billion dollar startup. It might be a nice indie hacker product business, but it’s never going to be a billion dollar startup. And so I know that that already deletes 80% of the ideas I have probably if not even 90%. And then the other, the other fundamental assumption, or, or axial I have is that I want to build something that I use, that I need myself. And that doesn’t necessarily mean a problem that I have myself right now, but something that we’re, if it exists, I’m an, I’m a user. Right. And I can think about what I needed and talk to my customers and figure out what they need and sort of reconcile that with my own needs, for the product. I don’t, I’m not very good at building stuff for other people. I would say, like, I, I’m fine at doing that, but I’m much better and much more motivated if it’s something that I want to use myself and that I want to make better for myself, where I see, ah, This part of the app kind of sucks, right? Like I want to fix this NAF part because it’s really confusing. Right. And no one needs to tell me that. I just feel it because I use the thing every single day. And so again, that restricts the problems based on a lot, right? There’s only so many things I know so many problems I care about. And so immediately that restricts the problems I can tackle a lot. And where exactly that Venn diagram of big problems that I have sort of overlaps. And then ideally that the other part of this is that I want to solve something that businesses are willing to pay for it because we spectrum, we had, we built a product that many people found valuable in that many communities found valuable, but we never managed to get anyone to pay for it. We never made any money. And so that’s why eventually we just had to sell because we ran out of money and our server costs were exploding, but we didn’t, we that doesn’t correlate to an increase in income. And so now I want to build something that businesses are actually willing to pay for it that solves a problem for them that they’re willing to pay for. And so again, that restricts the progress based on even more. Right. And so the more of these sort of axioms, I add the more of these properties I want to have in my idea, or in the problem that I want to solve really that the smaller, the space of possible problems kits. And I have no idea what I’m going to build. I have a couple ideas that that I want to maybe explore. We’ll see. But right now I think. The main thing I’m doing is talking to people. Right. And I’m doing a lot of customer research. I’m talking to people I’m talking many to developers because I kind of want to build something for developers, not for again, I want to solve my problem. Right. And so talking to a lot of developers about what they struggled with day to day, what their work life looks like and thinking about how one could make that easier. And we’ll see where that leads. I have no idea. It’s very scary. It’s sort of a pretty scary time in my life right now because I have no idea what I’m going to do. But it’s fun. I’m looking forward to it. I’m looking forward to the challenge and I’m really excited to be back in sort of back in the trenches of trying to figure out how to leave my stamp on the world, if that makes any sense. Yeah. Yeah.
Michaela: [00:37:19] It definitely makes sense. And I mean, I think we are in very different situations, as you said, right? You’re looking at your own situation, do you think? Well, right now I’m really free and I want to tackle this 1 billion thing. And for me it was more like, well, I’m completely not free. Sorry, I’m competing. I have my two kids and I want to spend a lot of time with them. But on the other hand, I want to go. And for me the thing, he was more, how can I use the time that I have right now to set myself up for success in two, three years, right? When my kids are a little bit more grown up. And I think that I’m getting closer and closer to that clip where I feel like, well, maybe, you know, my time to build something really cool will start soon. And And so, yeah, I think this, this all, I, it really resonates with me, like thinking about, you know, what can I actually tackle? What do I want to do? Right. What is really my, my ambition to, to do here and then trying to figure out. But I still think that even if you take this Venn diagram, it’s a huge problem space still, right? So there are so many things that you could tackle. And so if you do something like, do you try to get now this idea by talking to people, or are you going to build a little bit and testing the waters? So, so what will be the next steps to really understand if there is there’s a market for it? Or, or do you say, well, I’m completely committed. This is the idea I’m completely committed. I’m going to build it. I give it a year. Or is it like tiny bats that you do? Like, Oh this week I’m trying out, you know, I’m sending a tweet and see if people respond or I’m building like this little email list about something. How do you, how do you see that? I do all of
Max: [00:38:57] those things. It sort of depends on how serious I am about an idea and how much I believe in it, myself. Right. There’s thanks to my audience. There’s a lot of things I can validate just by tweeting. Like you said, particularly if I’m building something for developers, I can tweet, does anyone else else have this problem? And then I will feel the resonance or not. Right. Maybe nobody will respond or maybe a thousand people respond. Right. And sort of in that spectrum, I can tell how much that problem resonates with people. And then I can think about how would I approach solving that? There’s a, there’s a little validation that happens that way. And then the other thing is that I. Just ping friends and colleagues that I’ve worked with before or people that I know are using certain technologies. And I talk to them about how they’re using them and what they’re struggling with. And usually I go into those calls with some sort of hypothesis, right. I think maybe there’s this problem that maybe I could solve this way. Let’s see if they have the problem. And if you ask people straight up, do you have this problem? Would you pay for a solution if they’re friends of yours? They’re probably just going to say yes. Right. Because they’re friends of yours. They’re like, they’re probably not going to pay for it, but they’re still going to say yes. And so I actually go into those conversations and don’t even talk about my idea of what I want to do. I asked them what their problems are and then I look and listen and see if they even think about that problem at all. Right. And if they sort of stumble upon it themselves, and if they, if they’re annoyed by it, if it’s grinds their dead, their gears, right. Like the sand in the gears that grinds and it’s been really fascinating. It’s helped me invalidate a lot of ideas and, and tell me that people probably wouldn’t really care about them. Which has been really fascinating to do. I learned that from a great book called the mom test. I highly, yeah, I know that one.
Michaela: [00:40:22] Yeah. When you said that, I was thinking I should have mentioned it, but
Max: [00:40:29] it’s really well, it it’s helped me invalidate a lot of ideas. I have very, very quickly by just talking to someone for five minutes and being like, Hey, you know, what are your problems? What are you struggling with right now? What do you care about? And that very simple approach would be to the tests. We do daycare about your. Problem. And then could your solution solve that problem or not? And it also helps us cover other problems, right? Like I’ve discovered other problems that people have. And now I’ve talked to, I don’t know, 10 to 20 people and I’m starting to see patterns. Right. I’m starting to see, Oh yeah. A lot of people care about this one problem. I wonder if we could maybe solve something there, maybe there’s a solution for that. Right. And so that, that process is very, it’s very fun right now.
Michaela: [00:41:02] Yeah. That’s so smart. It’s so smart because it’s not like just, Oh, I’m going to build this and then you build it. Right. And you’re spending so much time doing it. Then I think it felt, feels maybe a little bit slow. And because you’re not really building something, which I think everybody wants to fill it, rightly we want to do, and we want to make progress. And if you just, just talk to people, it doesn’t feel like progress. It feels like, Oh, I’m still, you know, even before my idea phase, but this can pay off. So I mean, tremendously, if you’re studying and you’re going the wrong direction, I actually tweeted recently about that the tiny steps actually bring you the big success and, and, and do you have to be in the right direction? And this is also what I, I try to be very patient with myself thinking, well, you know, my steps are tiny right now, but as long as they are going in the right direction that I want to go and, you know, have a go completely straight. Right. So you, you learn and you bounce back and you think well, but if you’re open enough to see, well, this is the wrong direction. Now I have to go the other way around. And you know, even six sucking your way to success. I think this is so important and I see that. Yeah. I think you will be very successful. I can can see that. And so I’m definitely going to invite you again. Yeah. In, in a couple of years, right? I know we talk about like how it went
Max: [00:42:19] there. Yeah. We should
Michaela: [00:42:22] do that. Like we do that like in a year, maybe we do it, like go on a journey. Right. So in a year we talk again and then in a year we talk again and look how it goes.
Max: [00:42:34] Exactly. Yeah. I do think one of the things you, you said is really important is, is realizing when you’re doing something that’s wrong when you’re building a company or when you’re building a product, you’re so enamored with that product that you forget to think about. Am I even building the right thing in general? Right? You’re so in the deep, in the specifics you’re showing, Oh, which button do we put? Where, what feature do we build next? What features should we not build? What is more important? What do our users care about? Then you stop to think about the higher level. Does it, is this even a problem we’re solving, right. Is this even something that people care about at all? Or should I do something else entirely? Right. And I see a lot of startup founders particularly end up with problems or solutions to problems that no one cares about. And they never stopped to sort of reflect on, am I even working on the right. Thing right now, like, am I even doing something that anyone’s going to care about? And there’s, there’s sort of different there’s different problems to solve, right? Some are more immediate, some are problems that are problems right now. And people try to solve them right now. And then you very quickly learn whether it’s something that people very much care about or don’t care about whether you have product market fit or you don’t, if you sort of want to talk in the startup lingo. But then there’s sometimes there’s founders that are working on stuff that is way in the future, right. They have an idea of how the world should look like in 10 years and they want to help people get there. And that is really, really hard because at that point right now, no, one’s going to care, but maybe in 10 years, people care and you have to have a lot of conviction to sort of stay on your path, stick true to your values and goal the 10 years to see if that’s actually the future. That’s something I’m way too scared to do, right? Like I, I don’t have time to wait 10 years. I only have very limited time on this earth. And I know a lot of funders that are doing that and I respect the hell out of it. Right. But I’m, I’m way too scared of that. I would much rather solve an immediate problem right now where I know that people care about it rather than trying to do something so big. And so future that it would take decades to realize. Does that make sense?
Michaela: [00:44:38] Yeah, I think it’s, it’s painful. I mean, it’s painful to look at what you have invested in what you have spent your time on and to say. Honestly, I have to do something else here. Right. It’s it’s like I was standing, so I was, I was studying in London and then there was this really cool discotheque where you can go in the night. Right. I think it was called February or something like that. I forgot. And so we got a ticket there and we went there probably at, I don’t know, maybe it was like one in the morning or something or 12. And there was a line around like one of these huge buildings and we really wanted to go in, first of all, the ticket was expensive. Right. And say, if we wanted to see it and experience it. And so we stand in line and we stand in line for an hour and I say, you know, we didn’t even come, you know, like sit around. So what are we going to do? But then, because you’re already standing in our, like, it feels like, Oh, any minute, anyway, we stood actually three and a half hours and it wasn’t a morning when we could enter it. Right. And so it, and it was really this problem off, you know, like you’re standing already in line, so are you going away now? Or, and you leave all this waiting time for nothing. I was really horrible. And I think that this happens also to, to pounders. I mean, it, it also happens to me that you feel like, and, and it’s, it’s a blurry line. Like it’s, Oh, is there not traction because I’m doing it wrong? You know, is there not traction because I don’t have an audience yet? Or, you know, nobody goes to, I mean, there’s also build it and they will come if it’s not true. Right. So. It’s a little bit different, I think for especially people that don’t have like a platform and an audience yet to say, well, I’m tweeting about this amazing thing. And it could be that I am getting zero likes. So one like, and it doesn’t green really mean that, that what you’re building is not interesting. And so, you know, it’s not always easy to really understand is that the wrong direction or is it not? And then to be as honest to you and take this pain to say, well, I think it’s the wrong direction. Let’s do something else. Let’s start over. Yeah. So, so what I try to do is I try to have my, my activities always have one purpose that I know it will definitely work out. Right? So I’m doing this stuff and maybe the whole idea of turns out, but at least I know that whatever happens, there are three steps that are going into the right direction, right. Is it building an audience or, you know, building a community or learning something about the tech that I know I will use. Right. So I have, I have a couple of different goals around something where I say, well, maybe it doesn’t completely work out, but I can for sure say that those three checkpoints that are on my way to success, those three are going to work out. Right. I don’t know if that’s something, how you think about things, but this is, this is really my salt pattern pattern for everything I do. And very often it’s just learning right? Learning about. You know how to blog or how to do a podcast or, you know, something like this, which brings me to the right, you know, brings me closer to where I actually want to want to go. And then I know I have it. I have control over that.
Max: [00:47:49] Absolutely. That’s one of the big reasons I joined spectrum was because I said, there’s no downside, right? I get to work with two fantastic designers that I know online that are very famous for their great work. I get to watch them close and learn about design myself. I get to be a technical co-founder, even though I had no idea how to do that, I could learn how to do that through spectrum. And then you worst case scenario, if it doesn’t work out at all in one and a half, two years, I’ve made two new friends, at least if not many more and learned a ton about how to build a startup and what that even means. Right. And so really even if the product itself had gone in a completely mood, I knew there was no, like, I wouldn’t have any regrets about it, but I knew it could only work out and any success at the proton on top of that was just a bonus. Right. There’s the fact that we got acquired, but gets up is just a bonus, right? Like that’s sort of like that happened and it’s fantastic. And it was a great experience, but it’s not something that was required for it to be a success in my mind. Right. It was always already a success just by the fact of me doing it. And I, I think very much in the same way that you do where I sort of consider the, the whole, the, the implication of everything that I do on a sort of broader scale, right. It’s not just, I’m building a startup, is it going to be a success or not? And that sort of binary, the outcome is good or bad, but it’s. How much do I learn? Who do I get to know? What do I, what do I do? Do I enjoy my life? Do I have fun? Right? Like all these things can tie into it and can make something a success. Even if maybe directly it isn’t the success. If that makes any sense.
Michaela: [00:49:14] Yeah. That’s exactly how I approach things in life. So I think I’m fairly new. I’m happy that I got some confirmation bias here.
Max: [00:49:26] yeah, maybe. Yeah. I have no idea.
Michaela: [00:49:30] Yeah. We can see, maybe people can reply to this episode on Twitter and tell us if they are the same pattern.
Max: [00:49:37] I really curious if anybody else thinks that thinks that way. Yeah, absolutely. Please let us know. I’m I’m I’m super curious. I only start
Michaela: [00:49:43] things where I know it can, can only be a success and it can be a bigger success. Right. But it’s sort of the things that I’m doing are already success, right? Independent of how it turns out. I mean, yeah. So, well, I took already much more time than we actually that I actually set out to talk with you. So I already stolen a little bit of your day-to-day, so I I’m going to end it here, but we did promise that in a year I’m going to schedule again and then in a year we are going to talk again because I really enjoy it. I could talk on and on. And so I’m really curious where your journey goes and how, you know, how you think about the things that we talked about today in a year from now and 10 years from now. So thank you so much, max, for being on my show today, talking with me about all. All these really interesting topics and getting, picking your brain and getting a little bit an idea of how you approach things. I think this was so valuable, at least for me, I hope for my listeners as well.
Max: [00:50:39] Thank you for having me. I hope it was interesting were valuable or at least the pertaining, I hope it was at least entertaining. And I can’t wait to be back in a year and see, I, I honestly can’t wait to listen to myself. Talk about what I’ve just done for the past year. Cause I’m really curious to see where I live.
Michaela: [00:50:55] Cool. Yeah. Okay. So I will link everything in the show notes like bedrock and your Twitter profile. Is there something else that you think my listeners should know or, you know, they should check out that that’s important to you?
Max: [00:51:09] No, I think that’s it. If by then I’ll have a, start-up maybe link that to but I don’t know what that is yet. So cuddly can either yet.
Michaela: [00:51:18] Thank you so much for taking the time and enjoy your Sunday and talk to you in a year on this podcast again, hopefully. Yeah.

Episode 39: From designer to web developer

April 13, 2021 michaela 00:36:51

In this episode, I talk to Annie Liew, who works as a web developer at a startup called Pastel. She transitioned from Design to Engineering, and I want to know how she experienced this.

We talk about:

about her experience transitioning from Designer to Engineer,
the role her Juno Web Development Bootcamp (formerly HackerYou),
her new role as the first engineering hire at a startup,
her drive to learn and level up in public,
and how she managed to build a large Twitter following.

Today’s episode is sponsored by Botany.io – Botany is a virtual coach for software engineers that unblocks essential teamwork and levels up careers!

Links:

Subscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Transcript: From designer to web developer

Michaela: [00:00:00] Hello and welcome to the software engineering unlocked podcast. I’m your host, Dr. McKayla, and today I have the pleasure to talk to Annie Liew. But before I start, let me tell you about botnay.io, yho sponsors today’s episode. Botany is a virtual assistant and personal coach for engineers. It helps you adopt better habits, improve your skills or automate your workflows. So how does that work, you ask. Well, great question. Botany connects to the tools that your team uses and crunches through the data to find opportunities for you and your team to improve your skills, strengths, and collaboration, and improve processes and automate workflows. By gently and smartly nudging or reminding you, you stay on top of open tasks and learning and growth opportunities. In this way, Botany smoothly drives your new skill and habit acquisition. I love how it makes code reviews, and giving and receiving feedback a better experience for the whole team. But I guess it’s best you try it out for yourself. For that hop over to botany.io to request access to the tool. So that is botany.io, but now back to Annie.

Annie is a designer who transitioned into software development. I want to talk with her about how she got her first engineering job and how she now build soften his startup as the first engineering hire. So I’m super excited to have any year with me Annie, like come to the show.

Annie: [00:01:27]Thank you so much so happy to be here.

Michaela: [00:01:30] Yeah. I’m really, really glad that you joined. So you have been a designer and then one day you wake up and you say, I now want to be an engineer, or how, how did that happen? And what did you do about transitioning from design to engineering?

Annie: [00:01:47] Yeah. So it’s a bit of a long winded process. To be honest, I studied multimedia design at university and I worked for several years as a designer in Australia and in England. And after that I decided, okay, I wanted to change a pace. I really wanted to move to Japan because traveling is something that I really enjoy. And so I actually went from design to being an English teacher for several years and then decided, okay, I’m going to move to. To Canada and try to get back into design, but because the landscape had changed so much, it was a real struggle. And I didn’t know anybody in Toronto as well. So I basically was in this position where I was just like freelancing on the side, like trying to get my design hustle going. But I was also lot working a bunch of minimal low low-paid jobs to kind of pay the bills at the same time. So I was kind of in this place where I was like, okay, this is not where I want to be. What can I do? How can I level up, how can I get the skills that I needed? And I looked into something called bootcamp. At the beginning, I looked into a lot of UX boot camps, and then I found a school called hacker youth. They’re called Juno now. But at the time, the only. The only boot camp that they offered was a front end web development boot camp. But I really, really liked the community that they built around it. So, you know, I’ve, I’ve built websites in the past before, and it wasn’t something that I really enjoyed. I really enjoyed the designing part of things, but I was always happy to hand off the coding. You know, part two, the developers, however, I did have to build websites and when I did them, I didn’t enjoy at the time, but this time I thought, okay, let’s try again. Let’s see if something has changed. And so I started attending. Small kind of little free, not seminars workshops around the Toronto area. And I was like, okay, what is this? Flexbox what is this? And everything had changed. And so I started getting really curious about it. And so I remember it was really interesting because I never, never thought that I’d be interested in code. But after doing the workshops, I was like, okay, maybe I can do this. And so I applied for the bootcamp afterwards, got a subdued. And as they say, the rest of the street,

Michaela: [00:04:10] Okay. Okay. And so you said you were mainly interested by the community. How did you, was it an online community or was it an offline community and how did you get in touch with the community? How have you, you know, like, I imagine that you get access to the community after you joined, but it seems like you have, you knew the community exists even before you joined this particular

Annie: [00:04:33] bootcamp. Yeah, that’s a really, really great question. And that was a reason why I joined the community. I always have this idea that it’s less about what you do and more about who you do it with. I really, really liked this idea. And so the way like the hacker U has a really strong junior college has a really strong community because there’s a lot of past alumni who shared about the journey. So I, I started contacting them and say, and asking them. Hey, how was your experience? Would you meet up for like a coffee so I could talk to you about it. And I, and I went to several events and talk to a lot of them and every single one of them said, this was something that I don’t regret. I a hundred percent recommended it. This was pre COVID. So the bootcamp was an in-person boot camp as well. So it was nine weeks of 10 to six. And then on top of that, you have your assignments and classes. So it was just like a full-time in-person bootcamp.

Michaela: [00:05:30] Okay, so it’s nine weeks. So you make a commitment for nine weeks. You leave everything other aside, right. And you just go and do your work there. And I don’t know. Do you have homework then? Or is that, do you do everything in class and then you go home and then that’s it the next day you do it again.

Annie: [00:05:48] Yeah, well, it started easy, like off pretty, you know, easy where it was just like the 10 to six, but there’s so much work. And the way that works is that you’re, you’re constantly building, um, projects. So there was no way that you would have been able to do everything just in the 10 to six. There’s been like, it’s, it’s such a fun little, like, it’s almost like a summer camp experience because we all had access to the school basically. And there’ll be nights when it’s like midnight and there’s like all my classmates around me and we’re all just working hard and we have like pizza coming and it’s just a really fun. And that’s what I mean about community as well as it has a really fun atmosphere where you’re doing something difficult. You’re trying to transition into this new career. But they’re doing their best to, you know, support you along the way and make it fun. And, yeah, so it was, I don’t think I actually went to the grocery store for about eight weeks because, and I’m really lucky to have a partner who could do that, but it was just so intense, like the work that I was doing, the purchase that I was doing and what I was learning, I just really didn’t have time. And a lot of people just didn’t really have time to do other things. And

Michaela: [00:06:58] so do you still have contact with a few of those people that you met

Annie: [00:07:02] there? Yes. Yes I do. Yeah. And there’s still a very strong alumni network as well. There’s like a Slack alumni network. I Stu. Do some mentoring and I go back and help, like, you know, current students and I’ve spoken on some panels with them as well for people trying to get their first jobs. So yeah, I’m still an active part of the community. And that’s something I like about the school is that a lot of us alumni are still very active. Yeah.

Michaela: [00:07:31] That’s really nice. And so this thing had helped you also get your first job or how did you make that transition now from, okay. You’re doing this nine weeks and then what happens then?

Annie: [00:07:41] Yeah, definitely. It helped me to get a good job because the school has a lot of industry contacts. And one of the things that they did was that we had an industry day where they invited a lot of potential employee years to a. An industry day where we all kind of showcased our work. It kind of almost works like a blind date. If you think about it, where we all the students were sitting around tables and we had like a, a minute to give out pitch and to talk about ourselves and to share a project that we’ve really proud of. And then the bell rings and then they kind of let go to the next student. So it’s like speed dating. Yeah, it was completely like speed dating, but for employers versus, you know, and like potential employees. So it was really, it was like very stressful because all of us were trying to like practice our speeches and our pitches and, you know, like try to finalize the work that we wanted to show. But as a result of the industry day, I got invited to, to. Interviews with some companies. And I ended up getting an offer, which I accepted a week later. So I was actually the first person from my cohort to accept the job.

Michaela: [00:08:52] Yeah. Very cool. Very cool. And so how long has that a goal?

Annie: [00:08:57] That was, I graduated in summer of 2019 and I started in August. Yep.

Michaela: [00:09:03] And then you worked at that company as a software engineer. Front-end software engineer.

Annie: [00:09:09] Yes. So I was hired as a front end developer and I was there for a year and a year and a quarter. Was

Michaela: [00:09:17] that experience, was that good? Did you feel like now you deepening your, your knowledge or did you learn a lot?

Annie: [00:09:26] So the, the first job I had as a software developer basically was a, I worked for an agency. And what that gave me was a lot of structure around things that you don’t learn in bootcamp. So I got introduced to like agile methodology and stand up and the process of, you know, tickets and JIRA and a lot of soft skills that not soft skills, but a lot of processes, internal company processes that don’t. That you can’t really learn in a bootcamp, but you have to learn them on the job. I also got exposure to one of the very big things was I got exposure to a lot of big, large code bases, some with legacy code, and I also had to build architect sites from. Like the ground-up. So, and I work with so many different websites. It was a, they are a WordPress, VIP partner. So all our sites were done in WordPress, but I was doing like the architecture and, you know, like patient, most CSS and some Jacory as well. But because I had exposure to so many different types of websites and processes, it was a really big, yeah. It was a really big boost I would say, and definitely helped me to get my next job for sure.

Michaela: [00:10:38] And so is the next job that you done accepted? Is that the one that you’re currently at is that the startup that you’re working

Annie: [00:10:44] for? That’s correct. I’ve been there about four months.

Michaela: [00:10:48] And so how does that happen? Like why did you change and why, why did you go from an agency to a startup? What was, what was the interest for you?

Annie: [00:11:02] so I was. I’d been working at the agency for quite a while. And because I was doing a lot of the same type of work, I wasn’t feeling that I was starting to feel like I wasn’t growing anymore. And I was also quite worried about my JavaScript skills in particular, because I was so comfortable doing all the site architecture in patient mode, CSS. And I would basically get, like, I was basically lead in a lot of those. You know, for those projects that came up, but I wasn’t really practicing my JavaScript or react skills. And those are things that we had learned in bootcamp. So it was, I was, I’m going to say that I’m really, really fortunate because Twitter actually played a big part in. How I got this job or this offer, they, the company is called pesto and they were looking for a first hire someone to basically take over the front end. And they had a list of potential people that they wanted to reach out to and interview and invite them to go to the interview process. And I was one of them. So. I didn’t actually apply for this job, but the CTO reached out to me and said, Hey, I’m really like what you’re doing. Sort of some of your work that you’ve shared, and we have this position coming up. Would you be interested in applying for it or going through the process? So I looked at the stack, it was next JS was reacting, was TypeScript. It was all the kind of modern technologies that I really wanted to learn. And so I thought, okay, let’s give this a go. And I did. And I went through like the interview process. I did a coding challenge, which was a take-home challenge for a week. I’d built an entire app for that. It was very stressful. I hadn’t touched react for so long by that point. So it was a lot of learning. I was still working and then trying to do this on the side. Yeah. It was a very, very stressful week. I remembered that, but it was definitely worth it.

Michaela: [00:12:58] So now you are working in that startup and what are your responsibilities?

Annie: [00:13:05] So because they, when they hired me, they, I knew that my JavaScript side of skills, weren’t amazing. And I told them I was very honest with them at the beginning. I said, I’m not going to be like a JavaScript Ninja from the get go, because I haven’t worked professionally with JavaScript for so long. And David very aware of that. So they knew my abilities from the start. And one of my main responsibilities at this moment is just to. Basically level up as fast as I can to get myself to a point where I can just do it really well and eventually be responsible for the entire front end. The other thing I do as well is I build features. We have like a roadmap where we, you know, Look at all the features that we have coming up and I get, and I work on an, on building. Those features. Occasionally we have front end bugs come in as well, which I work on, but the two main things are the side that I am responsible for right now is building features and just like learning as fast as I can to get myself to a spot where I can be super comfortable.

Michaela: [00:14:10] Yeah, I think that sounds like really good next step for you and the ability that you can grow in that role so much, how old is the startup and you know, how does that work? A startup I imagine, right. Like extremely stressful and a lot of pressure or we have to ship. So how does that work in a startup that there’s so much time for you to learn things and how, you know, Is everything actually running smoothly. And so it just doesn’t need that. There’s not too much presser pressure or how does it work?

Annie: [00:14:43] Yeah, that’s a great question. So this startup actually started in March, 2017 and I got hired and started in October, October last year, October, 2020. So they have been going strong for just over four, almost four years, by that point that they hired me and they were. Basically profitable at that point. So they decided to, you know, start growing and becoming like an actual company. So just to give you a bit of context, there’s actually just three people in the startup. Before I got hired, it was the CTO and the CEO and the product guy. So a designer and engineer and operations. So. As they were growing, they realized they needed more help. And that’s kind of what I got hired for, because we’re profitable at the moment. And we have a, our motto of, we have a SAS product that is a subscription model. We know that the money is coming in all the time. So while there is a bit of pressure to ship features and I definitely feel it, I think a lot of the pressure is more the internal pressure that I feel too. Kind of validate that I belong here by shipping features, but I’ve had a lot of discussions with my, my CTO. And basically he said, one of the things that is important is that I’m able to learn to like, basically start slow to speed up later. So. They understand the importance of learning and growing as a junior developer was someone very early on in their career. And they’re thinking the long-term game it’s, you know, I can like probably like try and just like really hustle and ship a lot of features, but would they be like really good features? Well, I actually learned the things I need to learn so that I can do it a lot better. You know, like later on for the company, I think it’s like for everyone involved is really important that we have like a strong foundation built first so that we are able to then, you know, become a lot better and faster later on, I really

Michaela: [00:16:49] liked this long-term vision and long-term thinking it’s something that I think is quite the rare. Even for large corporation that could definitely, you know, invest into their employees. There’s often, you know, a very shortsighted action that I, that I feel like you have to provide value and you have to provide it now. But there are companies that I, that I hear really provide value also to the employees, like for example, automatic and all from several peoples that work there, they have also, for example, I think a really great place to work because. When employees are in trouble, I always heard like they are there, right? Like they give you paid time off or like some time to breathe and to think and so on. And so I really liked that mindset as well, that, you know, they are getting someone on the team and they’re investing in the person and I think. I don’t know about you, but probably it also makes you very loyal to that, to that

Annie: [00:17:46] company. What you said about investment, because that was basically in some of my discussions with my CTO. They are definitely investing in me. So when I got hired, they knew that I had the skills coming in from as a designer and. You know, they didn’t, they wanted someone who could basically have ownership of the front end and not have to worry about, Oh, can you move this pixel here? Can you move that? The light that’s all taken care of. I’m very, very pedantic about those details and let the UX and UI or things. They don’t have to worry about that at all. So he says it’s a lot easier to teach someone to code than to actually care about the product and how it looks and how it feels. So, yeah, totally resonated with everything that you said there. Yeah.

Michaela: [00:18:29] Yeah. And I think this is a really good perspective as well. Right? So you want action to the right people that are caring. And I think also people that feel cared for, and at least from what you’re telling me here, it feels like you, you feel cared for which I think trans translates back. Right. So it’s, it’s like giving and taking. So one thing that I’m super interested in as well is how do you experience. Developing software in a startup, like, what are the processes there? Is it very flexible? Do you have like mentorship? Do you have like code reviews? What about testing? You know, like what you’re telling me, it’s like two people, right? So it’s the CTO and you, so how do you do that? How much, how much formality is there and, and, and who takes over what.

Annie: [00:19:18] Something that we discussed at the very beginning is that with processes, we don’t have processes for processes sake. So that’s because as a startup, we want to basically move fast and iterate on things and be able to push things up. We basically follow a, although not formally, we follow an agile process where we have stand-ups, we do the sprints and we do retroactive at the end of the week to see what has gone well, what could be improved and then kind of reiterate on that. In terms of the, the product development process. We basically have roadmap meetings, roadmap, plannings, every one or two months, basically when we kind of look at the roadmap that we’re building and seeing what features need to be built. And the way we decide what features need to be built is based on the kind of two ideas. The first idea is a, is it something that has been requested? Is it something that customers have requested or is it something that we have some data around how customers are using our app? Is that something that they’re doing often enough? And then the second part of that is what is the potential impact of this feature? So for example, like maybe customers like request something and they requested a few times, but is that going to have a big impact on the company on like the usability of the, uh, like, will it help us to get more potential clients or, you know, so kind of those two things are two things that we think about when we, when we plan out our roadmap and look at all the features that we have available and we didn’t do like a kind of one. One, usually a one month plan where we work on, we prioritize the features that we’re going to work on, and then we just basically go for it. In terms of mentorship, I have a very close relationship. I would say with my CTO slash manager, we do our one-on-ones. We talk very, very openly about things like imposter syndrome, how we want to shape the, the culture of the company, what kind of company that they want to be. One of the things that really impressed me from the beginning was that they said, okay, and this was during the interview process. They said, we are very keen on building a great company culture. They’re kind of the kind of company that people want to come and stay, but we don’t want to have like high turnover. We want our people to feel valued and we want them to have autonomy over their workflow and the things that they do. And we want them to have an impact, but you can definitely, definitely make an impact in our startup. So the TIFA. Management style that they have here is very, very suitable for me because I tend to get bored easily, but in a startup because I’m doing so many different things and have such a, I guess like impact or influence or ownership over the product is I feel very invested in the job and in the company.

Michaela: [00:22:08] When, when I actually started out of university, I thought like, what kind of company do I want to work for? And I was very impressed by these large corporations, but I think it was more the names than everything else. Right. And now over the time, I think my view shifted quite a bit because at a startup you can maybe make the whole, the whole half of the product, right. Or maybe the whole product. There’s definitely something there, which also right now fascinates me more like having more impact, having more, you know, like. Yeah, contributing more and also maybe different heads. That’s something that I liked a lot. Actually, when I was working at Microsoft, I wasn’t a very specific position. Right. It was in the tool engineering teams. And so there, there was a lot of research, a lot of innovation, and that also had like a lot of hats, a lot of flexibility and a lot of impact, to be honest. But then when I wanted to transition, I looked at other teams and said, Oh, I don’t know. I, this is a little bit too restrictive for me. How is that for you? Do you have like several hats while do you have like probably designer hat, then you have maybe the developer hat, but other, other hats, I don’t know, responsibilities that you take over in the

Annie: [00:23:24] company? I wouldn’t say that I have like responsibilities per se, but I would say that I have the flexibility to kind of shape the role that I’m in and. Look into things that I’m interested in. So for example, one of the things that I did probably in the first couple of months is that I joined because with our clients, with our CEO, so that I could like talk to the client specifically and ask them questions about how they’re using the product, how they like it. And so that gave me a lot of. I guess empathy for our users and how they’re using the product. And actually this product is something that I use myself. So I is like, I am the user at the same time as something that I’m building for myself. So it’s interesting, but I also. Yeah. Like, because it’s such a small company, we do a lot of different things. For example, I don’t have to do this. My core responsibility is to build features and like be in engineering. But one of the things that I also do is that. I, you know, sometimes I’ll reach out to people. I think that we get a benefit from, from using pastel. And so that’s something that I do as well. It’s very, very, very, very flexible. It’s I’ve actually never worked in a company that has been so flexible before, like that, like any hierarchy, like structure is like quite flat. So everyone’s just going responsible for everything we have. Like, we communicate very openly and discuss things and it’s very much a process where it’s very collaborative. We all work together. And we’re very intentional about the things that we do that would move the company or move the product forward. So, and also just going back to what you said about mentorship, and one of the things that. Attracted me, I guess, about large companies was the idea of mentorship. And because like, traditionally we feel like large companies have very formal processes in place for mentoring younger developers. So it was something that I was very, very worried about when I first, when I was talking to the CTO, because there is no formal processes. It’s a bit, it’s a bit chaotic in many ways. So I. Asked him about that and we have code reviews. So I think maybe you’re familiar with the idea that code reviews are in many ways, a form of mentorship anyway, because you know, you’re getting your coffee with you. You’re getting a lot of feedback. He’s very good at the feedback as well. He just, he doesn’t tell me, just do this. He tells me the why. And yeah, it’s like very, very detailed and it’s, it’s really helpful. But the other thing that we do very consistently, at least twice a week, if not more, is that we pair on a very regular basis. And that’s been an immense source of mentorship as well.

Michaela: [00:26:04] Yeah, I think to be honest in a company like that’s that small, right? And you have like the CTO as the main engineering person, you have excess. To the CTO, right? I mean, it means that it’s the person that shaped the whole product that knows the architecture. So which means in another company, there will be several layers that you have maybe to go through, or people are really busy maybe also, and here, because there is an investment from the CTO also in you. Right. It’s in both interests to be like pairing and exchanging ideas and learning. And so, yeah, I can imagine that this is actually a really good spot to be in and have like. Almost like, like a really personal mentorship, you know, th there are mentorship programs in larger organizations, but I don’t think that people are that invested right in their mentees. Then probably your CTO is in you. Right. Because there is like higher stakes to make it work for that person. Right. So. One thing that I wanted to touch base, which is a little bit out of context, but you mentioned it at the beginning. And I think it’s interesting for a lot of people that are looking for jobs maybe that are coming out of would come, you know, coming or transitioning or coming out of college or whatnot. Right. And getting a foot into Tash, you said, well, actually by Twitter was super helpful. So. How, how, how are you using your Twitter or how are you building your following? What’s the value that you get out of Twitter and how can you, you know, how can others maybe also benefit from that and let it help them also a little bit in there in the job search.

Annie: [00:27:46] It’s interesting because I was never really a social media person. I had to open our, my Twitter account because my bootcamp made us open the account. And I remember in the very early days, I had no idea how to use Twitter. I was like, okay, I have to tweet something. What do I talk about? How do I connect with people? It was a very confusing kind of landscape for me because it was just a platform that I wasn’t familiar with. And I hadn’t used it before. When it started to change was when I, when the pandemic started and I’d been in my job for awhile and I was very comfortable with what I was doing, but I really wanted to level up. So I joined a hundred days of code and I started sharing my process on, on Twitter. And that was when I started to meet more people, build a community and. Basically, that was how, like my following grow. I, I guess it was very unexpected. I wasn’t expecting it. And it was very intimidating at the beginning, but in terms of why our boot camp made us open a Twitter account, it was because they knew the value of having a online, personal brand. And your Twitter account or any other, like your LinkedIn and stuff, your website is all part of that overarching idea of your personal brand. And it’s really helpful because a lot of companies do checks on you to see what kind of person you are outside of just the code that you do. And people hire other people for soft skills, not just, you know, like they can like, do like a for-loop and stuff, but it’s actually like what, what you bring to the company and. Twitter as is a way to not only kind of show the projects that you’re working on, which I was doing. I was like doing a lot of projects and just showing them, or freely on Twitter and on cold pen as well. But it’s also a chance for them to see who you are as a person. And I think that is the value of like Twitter or some of the other. Um, social sharing social networks as well. Yeah.

Michaela: [00:29:46] Okay, cool. So any, thank you so much for taking the time talking with me. Maybe I want to use the last few minutes to just catch up with things that you wanted to say to my listener, or, you know, like something that you want to leave. People were, I think especially people that are coming from bootcamps would be interested, people that are transitioning. Right. What is your advice for them? What do you think? What should they, yeah. What, how do you think that they could make themselves successful? I set them up for success.

Annie: [00:30:21] One of the things that I heard over and over again was that your network is so important and I really, it was something I really, really. Um, felt when I started to get into coding because when I came to Toronto and I didn’t have a network, it was extremely difficult for me to get into design. I didn’t know anybody. And once I tapped into a network and a community, everything became so much easier. So there is a lot of value in reaching out to people, because at the end of the day, you do the things that you do, you don’t. Build features and products and cold by yourself. You build it in a team with other people and having mentorship and a mentor can also be just someone like who’s a little bit ahead of you. If you can look on your current journey and give you advice on what you can do and just talk to them and kind of encourage you as well, having that kind of connection with someone who is already in the field or with a larger community, I think has a really large impact on, I would say a developer’s career. Something that I heard from somebody I remember this very clearly was that he said that the most successful developers, uh, people who have a large network to draw from, and also they’re not kind of tied into one specific like technology or something. They’re always kind of learning. They’re always open to hearing about like more things and they have like a large depth or breadth of knowledge and. They’re successful because they can draw from all districts areas. And I think that’s, that was like something that had always stuck with me. So. Yeah, like reaching, reach out to people, get involved in community, but also actually do work. The only reason that I was able to probably attract the attention of my current employee was because I was like really, really putting into putting in the hours of all the projects I was doing. And I think it shows as well, like the kind of work that I was sharing. Like I had spent hours and hours on them and just kind of refining my skills, getting better and improving each time. So. Those are things that come across when you’re sharing. And it’s very easy for people, I guess, like as new devs to become very discouraged. When, you know, you’re looking for your first job and you get a lot of rejections and it’s like, it’s really hard. It’s like so crushing, but you kind of have to understand that rejection is not. It’s not personal. It might be just that the company didn’t, it’s not the right fit at the right time, or there’s a lot of different factors and it’s not like really personal and cut you kind of, kind of help you to get over that hump is just to do work that you want to be hired for, or you want other people to see. And I think being able to show and share your work and show that you’re passionate about what you do and that you’re willing to learn is very, is very important.

Michaela: [00:33:24] And so was that work that you showed and that you did, was that outside of work or were you able to showcase the work that you did for work?

Annie: [00:33:34] It was outside of work and that was because the work that I was doing at work belongs to the company and. I was comfortable with the job that I was doing this. So I wanted to learn other skills beyond the work that I was doing at work. And actually this brings out a really good point because something that, that maybe like you kind of feel, feel this as well, like tech is one of those industries where there’s almost an expectation to work outside your job. And I just want to clarify and say like, that is not expected and you definitely shouldn’t do it because like a doctor doesn’t, you know, practice like operations in like his or her free time. And like, I don’t like the feeling that I have to, you know, work outside of my job, but it was something that I wanted to do personally to kind of level up because I wasn’t getting the kind of skills I needed. At my current job at that time. So that was the reason why I did it.

Michaela: [00:34:35] I also think like building up those profiles, then we just touched on before, right. Is something that’s really hard if you’re employed, because most of the time the code doesn’t belong to you. Right. And it’s not something that you can easily share and say, Oh, look at my guitar. There’s my code that I write for my employer. That’s confidential. Right. So if you want to fill your GitHub with nice stuff, it somehow. It means that you are doing stuff outside of work, but yeah, we have to be ready. The realistic that a lot of people are not, you know, they don’t have the position to do because they have like a full-time job they have to care for. Right. So, yeah, I think I understand. And they understand that this probably has a big impact, but it’s also. I also, as you said, I’m not advocating or at all right. That people should, should need to do it, but it’s, it’s definitely interesting to, to hear that that’s the way how you grow your following, how you grow your skills, right. So there is a trade-off that you have to make and, you know, if you’re in a position to do it, then that’s great. And I think it’s okay. Also not good to forbid people to do something outside. Right. I mean, sometimes it’s what you have to do. That’s how it is.

Annie: [00:35:48] Right. And in lieu of that as well. I also think that’s why having a network is so important because that’s how you can get your next job without having to do all the extra work of learning outside of your full time job. Yeah,

Michaela: [00:36:00] exactly. Yeah. Yeah. Okay. Any, thank you so much for taking the time and talking with me today, it was really a pleasure to have you. I wish you all the best for your job and that you learn a lot and I will. Continue following you on Twitter and see what you’re doing. And I’m really excited for you. Thank you so much for being on my show.

Annie: [00:36:20] Thank you for having

Michaela: [00:36:20] me. Yeah, it was my pleasure. Okay,

Annie: [00:36:23] bye.

Michaela: [00:36:26] I hope you enjoyed another episode after sup engineering unlocked podcast. Don’t forget to subscribe and I’d talk to you again in two weeks. Bye.

Episode 26: Software success through community building

September 15, 2020 michaela 00:48:02

In this episode, I talk to Chris Biscardi, an independent software consultant about how he became successful through open source and community building.

We talk about

how he niched down to only work with open source companies
how he build the Party Corgi community by showing up and leading by example
and what he thinks it takes to start your own successful software business in 2020.

Links:

Michaela’s awesome code review workshops
Digital Garden of Chris
Twitter profile of Chris
Party Corgi Comunity
Description of missing stairs

Episode 20: Fundamentally Changing How We Develop Software

June 9, 2020 michaela 00:45:04

In this episode, I talk to Tudor Gîrba, CEO and co-founder of Feenk, a software consultancy. Over the last 10 years, Tudor researched new ways to develop software – called moldable development. In this interview, I did deep to understand what that exactly means, and how he started to work on a novel IDE that enables moldable developments.

We talk about:

how reading code slows down software productivity,
building developer tools,
starting your own software company,
transitioning from consultancy to product company,
and applied research.

Episode 16: Running A Successful Dev Shop with Martin Gratzer

April 14, 2020 michaela 00:56:55

In this episode, I talk to Martin Gratzer, CEO, and founder of Topmind. Topmind is a successful boutique dev shop in the heart of Carinthia in Austria. Martin shares with me, how he managed to build a striving development agency far way from Silicon Valey and other tech hot spots.

We talk about:

why he decided to start his own company,
what helped him get started on his entrepreneurial journey,
how he managed to be successful by focusing on a niche,
what he advises others that want to freelance or build up the dev shop,
and behind the scenes info on what it means to develop software as an agency.

Episode 14: What developers should know about security with Troy Hunt

March 17, 2020 michaela 00:58:14

In this episode, I talk to Troy Hunt, a leading security expert. Troy is a successful Pluralsight author and runs security workshops all around the world. He also is person behind the popular web haveIbeenPwned, which allows everybody to check whether their data has been exposed in a data breach.

In this episode, we talk about:

how to prevent data breaches,
what software engineers have to know about the security and software vulnerabilities,
how to take your career in your own hands and
how he started to teach security to millions of developers worldwide.

Episode 12: Starting a Profitable Business in Six Weeks with Courtland Allen

February 18, 2020 michaela 00:48:35

In this episode, I talk to Courtland Allen, the founder, and chief-indie hacker of the Indie Hacker community. After many years of trial and error, Courtland launched the widely successful indie hacker community and the indie hacker podcast.

We talk about:

how he managed to build a lively community from the scratch
his tips for first-time founders
why he wanted to code as little as possible, and still coded as much as possible
his four-phase success plan for kick-starting a profitable community-based business.

Episode 7: Troubleshooting systems through Observability with Charity Majors

November 19, 2019 michaela 00:42:19

In this episode, I talk to Charity Majors, founder, and CTO of honeycomb. Honeycomb is a tool for introspecting and interrogating your production systems. It represents the new generation of monitoring systems that can handle highly distributed and complex systems. Charity shares with me what observability means and how we can make systems more reliable and maintainable.

We talk about:

the new generation of DevOps,
how and why we should assess systems in production,
the flaws of staging areas,
what it takes to make on-call a good experience,
how to assess engineering excellence,
and how and why she founded honeycomb.

Episode 5: Being the first engineer at a startup with Alper Kemal Koç

October 22, 2019 michaela 00:45:58

In this episode, I talk to Alper Kemal Koç, who was the first engineer building a low code platform called Kuika, that helps users develop mobile applications. Alper shares with me how he build this startup from idea to serving over 15 customers, and which cultural differences he observed when building software in Turkey, the Netherlands and the rest of the world.

We talk about:

why and how he joined this startup,
how he decided on the right tech stack,
how customer feedback influenced their direction,
which engineering practices he values at this startup,
and which relationship they have with their investors.

Episode 3: Building a developer community with Sandeep Panda

September 23, 2019 michaela 00:51:42

In this episode, I talk to Sandeep Panda, CEO and Founder of Hashnode, a friendly and inclusive developer community. Sandeep shares with me his entrepreneurial journey and all the lessons he learned along his way.

We talk about:

building a developer community from scratch,
getting investors to fund your projects,
the ups and downs of entrepreneurship,
transitioning to remote work,
and software engineering practices in a startup,
code reviews, testing, deployment, and keeping technical debt at bay.

Startup

Getting ready to build a billion-dollar business

Subscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Transcript: Getting ready for a billion-dollar business

Episode 39: From designer to web developer

Subscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Transcript: From designer to web developer

Episode 26: Software success through community building

Episode 20: Fundamentally Changing How We Develop Software

Episode 16: Running A Successful Dev Shop with Martin Gratzer

Episode 14: What developers should know about security with Troy Hunt

Episode 12: Starting a Profitable Business in Six Weeks with Courtland Allen

Episode 7: Troubleshooting systems through Observability with Charity Majors

Episode 5: Being the first engineer at a startup with Alper Kemal Koç

Episode 3: Building a developer community with Sandeep Panda

Search

Archives

Pages