CareerPlug's purpose is to empower people to reach their potential

CareerPlug

327 Stories To Learn About Leadership

143 Stories To Learn About Career

Let's learn about via these 19 free stories. They are ordered by most time reading created on HackerNoon. Visit the to find the most read stories about any technology. Lessons Learned /Learn Repo 1. How too Much Love for Your Code Can Hurt the Product A story about how important it is to keep a smooth balance between complexity and simplicity while building software. 2. UST/Luna Meltdown & The Lessons That I've Learned So Far The lessons that i've learned from UST/Luna meltdown. 3. Hitting Rock Bottom!! Life-long lessons from a failed interview. 4. What I Have Learned About Reading We all have our peculiar reading tastes that we don’t need to defend — de gustibus. 5. #MambaMentality Went Much Beyond Basketball Courts and Shaped An Entire Generation On Sunday, January 26th, the world suffered the loss of Kobe Bryant, his daughter Gigi, his assistant coach Christina Mauser, Sarah and Payton Chester, the Altobelli family, and pilot Ara Zobayan. For many basketball fans, it was a moment filled with disbelief, shock, and sadness. But as we learned more about the horrific accident from news outlets, reporters and journalists, the world began to look back at Kobe’s basketball career and journey: a 5-time champion with the Los Angeles Lakers, MVP, scoring champ, a plethora of scoring records, and Olympic gold medalist. 6. 7 Years In Tech Leadership: What I've Learned Being a CTO can be hard and frustrating, but also fun and satisfying. During my time in the last seven years as CTO, R&D manager, and software architect both at Walla!NEWS, Careerpage, and Appwrite, I have collected some insights that helped me do my jobs and achieve my company’s goals. For a long time, I have thought about sharing my ideas, and in this post, I will try my best to give away some of those insights based on my personal experiences. 7. Lessons learned from my 4 years in Software Development & Product Designing. Photo credits : Simon Abrams on Unsplash 8. Wise Ideas from 'The Psychology of Money' by Morgan Housel Money does not buy happiness, money buys freedom. Having a bit of wealth means the possibility of taking time off from work when feeling burned out or sick. 9. On Spreading Yourself Too Thin (and Other Dev Career Reflections) ‘The grass is always greener on the other side’ notion seems apt for this tendency. 10. Don't Make These Common Mistakes When Launching Your Website On October 22 I've launched online my first website. I'd like to share with you my experience. 11. What I Learned Working 6 Weeks on a Sh*tty Side Project About a month ago, I started working on Unfluence! It was going to be the perfect side project. In fact, Here is a list of things why it was going to be a perfect side project. 12. I almost quit my job until I learned from these mistakes. Have you ever been frustrated and felt like quitting? Well, wanting to quit one's job is normal, but little did I know. These are my biggest mistakes & lessons. 13. When Big Data Goes Bad: Rehabilitating Data Quality In a data-driven world, having data to make your decision provides a strong advantage... except when the data is bad. See how Datafold can help. 14. Jack Pullen Shares 3 Critical Mistakes Holding You Back in Life Jack Pullen is a young motocross rider specializing in both 65cc and 85cc categories. 15. #Don'tBeAJerk as A Viable Marketing Strategy You won't believe how many jerks a person could meet in one day that just being nice is already a marketing advantage for yourself and your product. 16. The Lessons of Covid-19 for a Digital Decade As we struggle with the Covid-19 pandemic, we are also learning some valuable lessons, and not only about how to handle an outbreak on this scale. We can also learn from the ‘success’ of the virus to build a new economic model that is robust enough to withstand another crisis, as well as creating a dynamic digital finance system to carry us through into the next decade and beyond. 17. Lessons Learned Building A Golden Kitty Award-Winning Product Here's the whole story of how I built One Word Domains from scratch, grew it to 50,000 users, and end up winning the coveted Golden Kitty Award. 18. Perverse Incentives: A Story About Rats, Nails, and Atrocities Errors and atrocities happen when hunting for incentives, and humans manipulate the rules, ravaging natural, moral, or cultural ecosystems. 19. Demystifying Software Engineering: Being Approached to Build a Feature or Tool (Part 1) The aim of this series of posts is to help demystify what it’s like to do software work and tasks in a professional environment. Thank you for checking out the 19 most read stories about Lessons Learned on HackerNoon. to find the most read stories about any technology. Visit the /Learn Repo

19 Stories To Learn About Lessons Learned

190 Stories To Learn About Engineering Management

Being a CTO can be hard and frustrating, but also fun and satisfying. During my time in the last seven years as CTO, R&D manager, and software architect both at Walla!NEWS, Careerpage, and , I have collected some insights that helped me do my jobs and achieve my company’s goals. For a long time, I have thought about sharing my ideas, and in this post, I will try my best to give away some of those insights based on my personal experiences. Appwrite 1. Embrace Your Strengths You are not getting paid to do paperwork. For me, being a CTO of a company was about leadership, vision, and creating technology that can give my organization a competitive advantage. Every company sees the CTO position in a different way, and each CTO might have a different set of skills or strengths. It is up to you to make sure your organization is getting the most out of your specific strengths. If you don’t understand IT very well, make sure you have a strong IT manager. If your passion is not dealing with contracts and negotiations, get a good purchasing manager. At the bottom line, you should know where your impact will be most valuable — and where you should delegate your authorities. Just because your predecessor was working all day with paperwork does not mean the same should apply to you. As a CTO, you have the power and authority to set your own agenda and your team’s agenda. 2. Don’t Be Absent A busy calendar is not an excuse. Talk to your managers and employees regularly, set up weekly meetings, and make sure you have enough free time to spend in the team’s open space or offices. People don’t like managers or leaders that are never there, not listening or giving helpful advice. If you want to lead people, you have to be there for them daily, or at least weekly, rather then always finding yourself in C-level meetings. 3. Be Predictable Know your team’s limits and constraints. Prepare for the unpredictable, so you can be predictable. A company needs to plan for strategic moves, and the technology should not be a constraint. Of course, this is not always possible, but it’s up to you to make it as possible as it can be. Know how to balance delivery time and technical debt. Make sure your team has enough time for the maintenance of your products. 4. Don’t Stop Learning Knowledge is power, and your knowledge is what got you to where you are now — don’t neglect it. In technology-oriented environments, all your knowledge is old news within 2 to 4 years, so make sure you are well aware of new trends and technologies. Sign up for a newsletter, read blogs, follow influencers, and attend online and physical conferences. The above advice does not mean you need to change your company stack every two years, but it is definitely very important to be aware of how technology evolves and changes in your industry. This will surely help you better prepare for the future. 5. Preach for Simplicity I have always told my engineers that our job is not only to solve problems — that’s the easy part. Our main job is to simplify problems. Simplifying a complicated problem helps us understand it better, and more importantly, to maintain it more easily and for a longer period of time. One of the worst things a CTO can do is stop all production work for unplanned maintenance and code refactoring. Not only this can be a huge time waste, its the number one indication that we have done something wrong in the process. Simple solutions lead to a much more simple and organized code base and a better decision-making process, which leads to better execution times and much more stable software. 6. Trust People, Not Skill Sets I must agree with the cliche that says everyone is replaceable. Anyone can learn how to code greatly in Python, Node.js, or master a Kubernetes cluster. Being a good person is harder to teach. Trust and embrace good people, and look for potential rather than skillsets. Create great training programs in your organization and make sure each employee has a solid career path opportunity. Your employees are your organization’s most valuable asset. Train them and help them evolve, and you will surely benefit from the results. A common story about the issue is one where a CFO asks the CTO: “What will happen if we train an engineer and he will decide to leave us?” and the CTO answers him unequivocally: “imagine what will happen if we don’t train him and he decides to stay with us.” In today’s world, it is inevitable that good people, with the right passion but without the right knowledge, will find their way to gain the knowledge necessary for them to achieve their desires.

CAREERPLUG

careerplug.com

-- employees

Since n.d.

COMPANY RANKING

CAREERPLUG

EVERGREEN INDEX #2393

Representing this company? Click here to claim and customize this page!

CareerPlug WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

CAREERPLUG

careerplug.com

-- employees

Since n.d.

COMPANY RANKING

CAREERPLUG

EVERGREEN INDEX #2393

RELATED COMPANIESRANK

STORIES ABOUT CAREERPLUG

Representing this company? Click here to claim and customize this page!

CareerPlug WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!