If you have an old app that works, but it has some problem spots, it might make sense to use microservices to fix these issues.
Sometimes rewriting core modules or classes in an old app, is just not feasible. In these cases, using a microservice to bypass the old code is the way to go. This strategy can work wonders in breathing new life into an app, saving you the cost and headaches of writing a brand new app from scratch.
Bypassing the Apps old ORM with a much quicker ORM
As an example, we recently fixed a huge speed issue (with an old app) that was using an old slow ORM. An ORM is a layer of code, used to interact with a relational database. ORM is short for Object Relational Mapping … just in case you don’t know.
So we used the micro-service pattern (strategy,) to leverage a new faster ORM.The end result: records that took minutes to load, now loaded in 1-2 seconds!
Sometimes you have to break the nerd-rules
We had to duplicate some fields in the database (typically a big no-no,) to make this work. But by using database transactions and database triggers (to keep up the data integrity,) it made sense to break these rules in this situation.
… Besides, these were fields whose value rarely, if ever change.
We deployed Sunday night (as usual) just in case something went wrong on the live server. I am happy to report, all went well.
Even the most experienced developers will be referring to videos, support forums and books to keep refreshing and building their skills. Yes, once you’ve done certain things a few times (ex: setting up an MVC framework like Laravel, designing databases) you will be able to do them without any help. But I can guarantee that other aspects of the project will send you researching!
… It’s the nature of development.
Experience makes you quicker
That said, as you continue to build more and more apps, you will be doing less research and more coding. You will also be able to build apps much more quickly, and even be able to research new things much more quickly.
… That’s why most of the time, it is cheaper (in the end) to pay an experienced developer a lot more than a junior. So you noobs just starting out, don’t be offended if you are making 1/4 of the what the top nerds are getting paid – they are worth it. But in time, you will be too.
Coding in the dark
I remember back in the day when I first starting coding, many times I would be writing code that I wasn’t exactly sure how it worked. My advice: just write the code and move on.
Eventually you will have the AHA! moment, and it will all make sense. Then in a few years, you will forget the basic syntax! 🙂
… But no worries, the principles of the code will stay with you.
In the end, what separates the good coders from the bad: a good understanding of the basic principles and techniques.
Whatever you do, learn jQuery … although, you don’t have to learn everything about it. Just get an overview and understand the basics. jQuery is big and trying to learn everything might be a waste of time.
… It’s good to know WHAT a framework can do, so you can consider it for projects you are working on. But don’t use a framework for the sake of using it. People often think that they should be looking for a way to use a framework. No … use a framework only if you need to.
So much, and too much to learn!
The thing about learning tech skills, is that you have to learn to filter – there is so much to learn, you can never keep up. You have to pick and choose.
My advice is to first learn the basic concepts and techniques that are universal. Things like OOP, MVC design pattern (and others), separation of concerns etc … then get into more advanced programming concepts. Once you have that, you can poke around some frameworks, keep your eye on what is out there, but keep in mind that it is not possible to learn all things.
I lost 10% of my hair in the 1990’s, trying to learn too much!
Back in the 1990’s when I first cut my coding teeth, I used to drive myself bat shit crazy trying to keep up with all the ‘hot’ amazing nerd-tech hitting the Web. Most of the time, the new amazing thing wasn’t really much better than what was already there, and many a times, you would sacrifice some advantage in one library, framework or language … for another.
Again, know the basics well, learn the key libraries/frameworks so you at least know what they can do. But don’t go nuts. Personally, in the JS world, I would learn jQuery first and foremost. But not all of it.
Developers sit around all day (and night!) coding. If you slouch, or have a crappy chair, you are setting yourself up for lower back pain. But there are a few simple things you can do to reduce, or completely relieve the pain.
Flash was dead a few years back when Steve Jobs put the hit on it, by not allowing Flash on iOS. Then Firefox slapped Flash off the side its’ head, by blocking it. Then Facebook’s security chief ripped into Flash, calling for it to be trashed.
… But wait, there’s more!
Now Google is blocking Flash ads (at least) and that my nerd friends, means the end of Flash. It is no more, and we shall not speak of this passe, bloated, security risk again.
Ahh, how technologies come and go – a very short version of the dead-tech list:
… Is Ruby next?
If you want to do ‘flashy’ things, use HTML5. It’s just better.