I worked with many pro developers in the last decade who preached the same ideas. Adopting them made me an efficient problem solver today.

Here are 10 tricks that only experienced developers know: 🧵👇

#software #programming #developers
1. Always have a plan

Planning helps you learn about the problem, analyse it, and carefully think about the trade-offs. Jumping right into the code is often a sign of inexperience.
2. Optimize only when needed

Pro developers focus on getting things to work rather than wasting time looking for the best possible solution.
3. Improve your algorithms & problem-solving skills

What makes you a programmer is how you approach problems not the number of tools you use. The more you practice the basic algorithms, and problem-solving better you get at it.
4. Programming fundamentals go a long way

The fundamentals can be used with any programming language or tool. It will help you not get stuck in a specific stack forever and be flexible and ready to help in any environment.
5. Use the right tool for the job

The reason there are so many tools to solve problems is that someone was trying to solve a particular problem, not all of them. Always research the best tool instead of fighting a tool to work for your problem.
6. Failure is a friend

Failure is just a reminder to do better, not to give up. We know that developer who is great. What we don't realize is how much they failed to get there. The only difference between you and them is they failed more than others.
7. Test, debug & documentation are skills worth having

None of us would be good developers if no one did this work. Tools can only do so much to help that's why you should do your best to write tests, and documentation.
8. Mentoring is the best way to learn

If you can't explain it, you don't understand it. Great solutions often come to us when we try to explain the problem. The ability to communicate knowledge and ideas is most important to advance in a career.
9. Communication/Collaboration is the key

All pro developers are team players and supporters. A good developer is coachable and open to new ideas and suggestions. Knowing how to work and support others is an essential and humble skill to have.
10. Progress over perfection

Developers often stress over perfection because they want to appear better than they are. Never wait to feel ready, more skilled, or perfect to make a career or programming move. Seek progress, not perfection.
These are the tips and tricks that you only learn through years of trial and error, and they can make a huge difference in your workflow and the success of your projects.

Thanks for checking this out.

Follow @pragyanatvade for more threads.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Pragyan Tripathi

Pragyan Tripathi Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @pragyanatvade

Dec 28
If you are struggling you grow your customers & bring new customers open this: 👇

While building @vadelabs, I am learning about how to drive maximum value for our customers.

Here are 10 essential customer funnels you need to know to take your business to the next level🧵
1. The Awareness Funnel:

Your potential customer becomes aware of your company. You must focus on generating interest and curiosity in your product and service. Involves running paid ads, attending events, or creating content.
2. The Consideration Funnel:

Your potential customer actively considers whether or not to buy the product. You must focus on providing more information about the product, features & benefits over your competitors. Involves creating case studies, demos, or educational content.
Read 12 tweets
Dec 27
As a DevOps engineer, you should be familiar with several metrics to effectively monitor and maintain the performance and reliability of a system.

Here are the 10 most important metrics you must know: 🧵👇 Image
1. Availability: This is a measure of the proportion of time that a system is operational, taking into account both the MTBF and MTTR.
2. Mean Time Between Failures (MTBF): This is a measure of the average time that a system operates without failing.
Read 12 tweets
Nov 29
Kubernetes is a complicated beast. There are many moving parts under the hood. Simplifying Container orchestration isn’t easy

Here are 11 Resources that will make you a Kubernetes wizard in no time 🧵👇

#DevOps #DevOpsCommunity #Kubernetes #K8S
1. A Beginner’s Guide to Kubernetes

A comprehensive introduction to Kubernetes architecture.

🔗 medium.com/containermind/…
2. A Guide to the Kubernetes Networking Model

An in-depth run-through of Kubernetes networking.

🔗 sookocheff.com/post/kubernete…
Read 13 tweets
Oct 26
Building reliable software is complex.

Here are 16 lessons I learned the hard way in the last five years as a DevOps engineer 🧵👇

#DevOps #DevOpsCommunity
1. No in-code fallbacks for configs:

If the service can't load the config on startup for any reason, it should just crash. It's easier to diagnose than the result of one borked instance going down an ancient code path due to misconfiguration.
2. Stringent RPC settings:

Zero retries and a timeout like 3X the p99. We are striving for predictability here; sprinkling retries and long timeouts as quick fixes lead to a week-long investigation and headache a year from now.
Read 18 tweets
Oct 24
Networking protocols are the most important concepts to excel as a DevOps engineer.

Unfortunately, most of them don't seem to understand the basics.

Here's a crash course to make you an expert in OSI Model 🧵👇 Image
OSI stands for Open Systems Interconnection. It provides a standard for different computer systems to be able to talk with each other.

7 layers of OSI model are defined as follows : Image
L7. Application Layer:

It interacts directly with the user. Browsers rely on it to initiate communications. Responsible for protocols and data manipulation that the software relies on to present meaningful data to the user. Like HTTP and SMTP Image
Read 11 tweets
Sep 14
17 roles you must know to run a successful software development team🧵👇

For building a successful software product, you need to have a strong software development team. These are the following roles crucial to run the software business👇

#software #programming #developer
1. Project Executive

Experienced professionals with a good grasp of business serve as project executives. An individual with this role must be granted the required authority to take any rational business decisions for the project.
2. Product Owner

The product owner is responsible to make sure all the requirements of the project follow the business needs. An individual having such a role must be familiar with the strategic aim and objectives of the project.
Read 19 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(