Miles Gordenker’s Post

We've all had those moments when we're just waiting and waiting... especially when the markets and our personalized lists are delayed! 📉 But, don't worry, it's just a temporary glitch in the matrix of life. 💻 Meanwhile, keep yourself entertained with this programmer's joke: Why don't programmers like nature? 🌳 Because it has too many bugs! 😄 Laugh it off and let's get ready for the amazing things this week will bring. #programmersjoke #technology #lifeofasoftwareengineer

Hey, Software Engineers! We've got something for you: a compiled a playlist that captures the triumphs and tribulations of the engineering life 📻 From the heart-pounding rush of a working solution to the existential dread of a stubborn bug, these tracks resonate with the rollercoaster ride we all know and love. What song gets you in the zone during a coding sprint? Share it with us by commenting below! #SoftwareEngineerLife #TechHumor

When I was starting out, I once spent an all-nighter turning a client's slide-deck demo into a full-fledged, deployed product demo. I was happy with what I built. Demo didn't go well. Nothing came from it. Then I took a sick day because I completely burned myself out on something no one asked for. I had boundless energy and optimism, not hemmed in by reason and work-life sanity. Now I routinely find myself looking to protect the leisure time of energetic, optimistic software developers who, unfortunately, have to report to me. I still have the optimism, but not always the energy to keep up. Pushing for results every now and then is good, but let's not get used to pushing, and pushing, andpushingandpushing. We need to make space between the pushes. Or people will take sick days and leave us.

What’s your Testing Emotions today?

As a SWE (software engineer) how do you feel about deep dev? Or just meetings in general. Where, as a team you must come together to discuss some sort of deeper conversation about a current piece of software your team is working on in that sprint? I sometimes feel like those meetings can be lackluster. Like we are all missing the point that each of us are trying to bring to the table. Does anyone feel that meetings should start off with a solid baseline of what type of topics we will discuss? Followed by a sort of study session to make sure we are all on the same page with each topic. Or am I just discussing some form of exploratory testing?

In my latest newsletter I dive into 5 pieces of advice I would give to Junior Software Engineers starting their first job: 1. I won't expect you to know sh*t but I will expect you to give a sh*t. 2. Set your off-time/personal life boundaries early. 3. Stay away from brilliant a**holes. 4. Never let your mentor touch your keyboard. 5. Make sure the expectations for success in your role are clear from day 1. See my latest newsletter where I go into much more detail and I dive into exactly why you want to stay away from a**holes and why you need to embrace the struggle. https://lnkd.in/dHGbNWwX

Beta Testers wanted. We’re trialling a new story-as-a-service product. Aimed at tech start ups and scale ups, it’s an affordable way of finding and sharing your story with the world. Why do stories matter so much? You know how useful it is if you can talk about your business in a way that’s free from jargon, in language that your clients understand. It’s all about being likeable and making connections. Stories can help you build even deeper roots into the hearts and minds of your clients. A great story can help your customers see the woods for the trees, and guide them towards a greater understanding of what you do, and how it can help them. But it's not easy to do from the inside. An outside perspective really helps when it comes to finding a story that resonates with your audience. And that's where we come in. We've got five places available for the story-as-a-service trial. Let me know if you're interested in finding out more

Hi all, New year and new meetups, first one in two weeks time! Sign up! Happy to say that we are back with new content to share with Jani Grönman and Szilard Szell, see you all on Wed Jan 17th at the Hidden Trail office. The theme of the event is Quality mindset and how to focus it right to make the whole development process (and team!) part of your quality assurance efforts. We will explore the theme with two games. #Agiletesting #qualityassurance #testing #devops #meetup #Finnistestingmeetup

👇 Software Engineers, are we really just ticket pushers? If you want to set yourself up for success as a SWE... ⛔ Don't just blindly follow ticket specs. 💭 Ask yourself... 🤔 Why should we do this in X way and not Y? 📝 Who uses this, and how is the feature useful for them? 🤔 Wait—What if I suggest that we do Z instead of W? It might be just as valuable to the clients and way easier to implement. 💡 Identify the team's pain points. How can we improve our processes? Understand the whole picture 🖼! You're way more capable than a mere ticket pusher 👨💻 ! Please share 🔁 if you agree / found it useful ✅ How do you set yourself apart as a software engineer?

If you are a software engineer you have to fix this ASAP... Software engineers are great at problem-solving and learning new tech really quickly. However, in doing so, they often forget to communicate their ideas with their colleagues. I've seen many software engineers who are unable to explain or share their thoughts. The problem is that most of them are introverted by nature, which is why they chose this field in the first place. They just need a laptop, internet, and a corner. But if they add the power of communication skills by exposing their knowledge, then no one can stop them from joining the 1% club. Showcasing your skills on a public platform will give you: 1. Recognition of your talent 2. Entry into the community of like-minded people 3. Exposure to how to express your ideas 4. Unexpected opportunities Moreover, by doing so, you can inspire thousands of junior engineers out there. They can learn how to: Write clean code Write reusable code Implement patterns and architecture Learn new tech Develop a problem-solving approach Isn't it amazing that the platform I am using to write this post was developed by a team of software engineers? And we know nothing about them. Although they have GitHub, I know, but you guys can grow your brand here too 🚀 P.S: Someone once said, if you share your knowledge, it will only grow or not degrade. Follow for more such stuff :D Vivek ✌