Two years of Univjobs
1 - Lets talk about Typescript
Hello I'm assuming that you can hear me. Okay guys so let's talk about typescript. I know that for a long time you probably didn't want to do any type scripts for whatever reason maybe you were scared of types maybe you took a Java class if you hated it not really sure why but for whatever your reason was the answer to that is I think it's time to grow up there's no real reason to be scared of it
Why Univjobs moved to TypeScript Univjobs is platform that I built during my final years while I was at school and I've been working on it ever since it was a prototype that we built node with node and express and it's something that we kind of / together at first and it's taking a bunch of different turns.
Sing about writing Enterprise level software is that need to have good design patterns you need to implement the principles of object-oriented design. This is a whole lot harder when you don't have types so whole lot harder to do things correctly any safety really.
Sure might be a little bit easier to just write things in note buy I think in the long run it's more important to write software that scalable and understandable for people can understand it sometimes a lot of the times when you're writing code in dynamically typed languages you have to play some lot of emphasis on variable names to signify intent to other Developers, it's not really the best thing to do.
I'm not sure who said it but I'm really starting to understand this year is that it really isn't hard to write code but it really is hard to write good code started reading the design patterns by Robert C Martin and one of the things he says is that good architecture means that it doesn't take longer for you to write new code the larger your app gets he's essentially saying that when your app gets larger shouldn't take you more and more times Implement new features if you've done that then you've essentially failed without using types this becomes pretty hard to do because you have to keep track of a lot of different moving things and you have to really rely on your human capabilities to keep track of relationships between classes and objects.
2 - My story building a startup
Building a startup is really fucking hard. It actually takes every ounce of your being to make the needle tick forward even a little bit.
Being a technical co-founder in a startup is challenging. It’s like being a designer, front end developer, back end developer, software architect, network administrator, integration & automation developer all in one.
I’ve had to learn things in the entire scope of real life software development in the workplace, without a whole lot of real life software development experience from the workfplace. Technical things I’ve had to get really good at: - git and git flow, because we need to standardize how we work together and don’t break prod.
- This was a hard one for me and took several months of unlearning things to start to get decent at it. I’m not a designer by practice.
Things I’ve had to learn and pick up:
- How to work on a team
3 - Show some of the new stuff that I'm working on for Univjobs, show the wireframes, etc.
Thoughts? Share the article if you think it'll be useful to someone + join the discussion about this post on Twitter!
Stay in touch!
You may also enjoy...
A few more related articles
Learn how to use DDD and object-oriented programming concepts to model complex Node.js backends.
In software, change is inevitable. The more complex the software, the more it should be enabled to be changed. The SOLID principles are a set or principles all developers should know about in order to design robust, maintainable, and flexible software.
Want to be notified when new content comes out?
Join 2000+ other developers learning about Domain-Driven Design and Enterprise Node.js.
I won't spam ya. 🖖 Unsubscribe anytime.