Here are a few essential tips that every aspiring or new web developer should take to heart.
π§΅ππ»
1οΈβ£ You Need To Know Way Less Than What You Think To Get Started
So many new developers think they need to become masters to be ready to apply for jobs or look for their first clients.
Here is the truth: This is wrong.
Do you have basic knowledge of HTML, CSS, and JavaScript? Great!
Can you create basic applications that do what they are supposed to do? Awesome!
If you can tick these boxes, start to apply!
2οΈβ£ You Are Paid To Deliver Solutions
Never be afraid that your code won't be good enough because it usually will.
What you are paid for is a solution that works.
If it doesn't need any fancy, clever, or "smart" solutions: great!
The simpler your code, the better.
Your solution should work, and it must be maintainable by you and your team.
As soon as it does what it is supposed to do, is tested, and is readable, go for it. You're done!
No need to spend additional time on anything unnecessary.
3οΈβ£ Use UI Libraries
Especially when working on professional projects, time is money.
Creating a form here and a table there actually takes time.
Using pre-made components saves you time and enables you to focus on the essential part of your development: make it work.
UI libraries enable you to quickly create pages/views without worrying about layout and structure too much.
Add them as dependencies, integrate them, and enable yourself to get into building pages directly.
4οΈβ£ Don't Neglect Documentation
You can do your future self and all your colleagues a huge favor by documenting everything you do.
From how to actually develop the project, to individual features, add documentation.
At some point, someone will have to get back at a feature or a project.
Having documentation ready that enables anyone to get into something within a matter of minutes is worth gold.
It's way better than having to try things out until they finally work.
5οΈβ£ Don't Be Afraid To Ask For Help
Seriously, don't work on a problem on your own for too long.
If you can't figure something out by yourself, ask your colleagues.
Make notes you can get back to later should you ever forget about the problem and its solution again.
It costs you or your employer way more money if you struggle with a problem alone than it costs to ask a colleague for help who might have a solution ready at hand.
And if no one has a solution at hand, they might still know how to effectively google for a solution.
6οΈβ£ Expose Yourself To The Unknown
Don't be afraid to jump into the development of features you have no idea of.
If you want to learn how to do something, you'll have to do it at least once.
Get in, and give your best!
Remember, you can still ask for help or go on the internet and see whether someone else has already done something similar.
Whenever you'll finish a feature you had been afraid of before, you'll notice how much you actually learned.
7οΈβ£ The End
Well, that's it for now.
Thank you for taking the time to read this thread!
If there is anything you would like to add, feel free to respond below.
And if you want more content like this, follow me for more threads and content on web development and Web 3.0! πππΌ
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
We're going to look into what this offer actually includes and how we could build a containerized Lambda function ourselves. π¨π»βπ«
Start your IDEs and open your AWS consoles because we're going in!
π§΅ππ»
1οΈβ£ AWS Lambda Previous To Container Image Support
Until recently, AWS Lambda only allowed you to write some code and upload a zip archive containing all files necessary to run your function.
Some frameworks eased up this process, but that's how it went.
Lambda also imposed some pretty strict limits, especially the 50MB default deployment size limit.
You could technically circumvent this limit by pulling more deployment dependencies from S3 or issuing an AWS Service Limits support request. But this wasn't the most...