Krzysztof Gajewski

Over the past few months I’ve written an extensive tutorial on how to build software applications with Node.js and React. I’m sorry to tell you that this experience didn’t teach me anything about B2B sales, though. But hopefully, it’s still useful for some people out there. From the introduction: The approach of this tutorial is to teach its readers how to build a fully working software application from zero to production. This means two things: 1. You are not required to have done any kind of software development before getting started with this tutorial. It will introduce and explain everything that is needed to build applications in full detail, assuming no prior knowledge or experience. This is the “from zero” part. 2. Building on the foundational knowledge it teaches in the first half, the tutorial will then, step by step, guide you through the process of building a real, full-fledged, and completely working software application, again explaining every detail along the way, and shows how to “deploy” that application — that is, how to make that application available on the Internet for anyone to use. This is the “to production” part. Speaking of B2B sales: I’m afraid you cannot buy this tutorial. That’s because I’m making it available for free, as a series of posts on my blog. The first three parts are already published: https://lnkd.in/e2XCYm3p https://lnkd.in/eW7wUc_d https://lnkd.in/eAU6kgH9 No, you do not need to sign up to my newsletter to get access to the tutorial. That’s mainly because I don’t have a newsletter. Also, no need to follow me (although admittedly, it might help to get you notified whenever I’m publishing a new chapter). Furthermore, please don’t be disappointed if clicking on the tutorial links won’t present you with a cookie banner. That’s because my blog doesn’t use any cookies. No, not even those from Google Analytics, as I’m not using that either. This means I will have no idea how many people will read the tutorial — which makes sense because let’s face it, who is going to consume this kind of long-form, deep-dive technical content nowadays anyway. And in text-only form, of all things! Should you nevertheless decide to dive into the text, expect to learn how to program using JavaScript and TypeScript, how to use these languages to build rock-stable backend applications with Node.js as well as elegant frontend applications with React and Redux, and finally, how publish a complete and integrated software solution on Amazon AWS. Ok, that’s it. If you want to access the bonus chapters, simply subscribe to… — just kidding. There are no bonus chapters. Everything you need to learn to build useful software products is right in the… normal chapters, I guess? Happy reading!

30

1 komentarz

🌟 Is Node.js the Best Framework for Backend Development? 🌟 I've noticed a growing trend: many companies are on the lookout for backend or full-stack engineers highly proficient in Node.js. This skill is in high demand, but it seems that finding candidates with the right level of experience can be challenging. 🙌 Calling All Hiring Managers and Developers: Hiring Managers: Have you struggled to find suitably experienced Node.js engineers? What are the main challenges? Developers: Can Node.js truly be the primary backend language for tech companies? What has been your experience? Let's discuss and share insights on the potential of Node.js in backend development. #NodeJS #BackendDevelopment #FullStack #JavaScript #TechHiring #WebDevelopment #Programming #TechTrends

26

14 komentarzy

Kotlin's windowed function gives a sliding window view of a collection. It's a neat way to dissect a list and gather insights. Want to explore this more? Check out Functional Kotlin by Marcin Moskala.

7

🚀 Looking for a Free Tinkerwell Alternative? Check out TweakPHP, an open-source PHP debugging tool with Laravel support, Monaco Editor, and more. Perfect for developers! 🖥️👨‍💻 Read the full article here: https://lnkd.in/dw-U838X #PHP #Laravel #TinkerwellAlternative #OpenSource #WebDevelopment #CodingTricks

1

Writing good tests can often require more creativity than writing the actual code. But this challenge is precisely what makes them so valuable. Good tests should encapsulate business rules and performance goals—they serve as living documentation that evolves alongside your application. Having experienced the challenges of working with an untested application, I know how grueling it can be to reverse engineer business rules from incomplete or unclear code. Tests are more than just a safety guard; they’re the best friend of your future colleagues, ensuring smooth onboarding and reducing the learning curve. Investing in good tests today not only protects your code but also paves the way for your team’s future success.

8

1 komentarz

How can a software development agency bring most value to their client? It's simple. It's not easy, though: 1. Understand the client's pain point. Every client has an idea what they need. But this is not where you should start from. We need to start by understanding what is it that creates pain for our client. How to do this? Ask questions. A LOT of questions! 2. Understand the client's budget and timeline. Not all clients will be upfront about this. But through open communication you can explain that the reason you need this is to see what best you can do to eliminate their pain point and remain within the budget and timeline. Sometimes the best outcome can be that you eliminate 80% of the pain while remaining within the timeline and budget. Sometimes it will be to remove 100% of the pain, but exceed the budget by 50%. But the software development agency and the client need to have an open and direct conversation about this. 3. Cure the pain point within time and budget as agreed. If you've done the first two steps correctly, this one is simple - it is something the software agency does on a daily basis and really shouldn't have any problems with. #softwaredevelopment

5

I changed as an engineer (its ok for you to change too) In 2010 I was the PHP guy In 2011 I became the Java guy In 2013 I was the full stack guy In 2015 I was the UI guy In 2016 I was the solr guy In 2019 I was the big data guy In 2020 I was the streaming guy In 2024 I am becoming the Gen AI guy In 2025 I am not sure what guy I will be So, whats all this is about? When you work in a tech or domain too long, you either feel married to it, or are afraid of making changes. Not because, you can't do it. But because, you can't think of it. I talk to 100s of you on LinkedIn. This is what I hear: - I have been in automobile domain for 10+ years    ↳Can I move to ecommerce domain now? - I have been a hardware engineer for 6+ years    ↳Will they accept me as software eng now? - I am in XYZ part of country or world,    ↳Shall I move to Bangalore or US? Now listen to me, (next 4 lines are critical) - you are what you "believe" in, not what you actually are - you lift 20 kg dumbbell first from mind, then from hand - nobody is going to stop you from making any change - you don't need anybody's validation to make change (but CJ, what if...., ok, let me answer those what ifs) Automobile -> Ecommerce Now instead of AUTOSAR, you need to know OPS Hardware -> Software Now instead of h/w friendly language, constructs, you need to know abstract language, API, MVC etc XYZ -> Bangalore/US Now instead of your fav food, friends, you will need to consume what is available there. Is this challenging? Yes, a bit in the beginning, but it will not last more than 6 months. Nobody cares what kind of guy you were at ABC time People care what value you can deliver today People care if you are ready to learn You will have to keep adapting yourself with time. This is one of the 4 things I have been doing. Thats the only guaranteed way to grow. Now, throw that belief that is holding you back. Take control of the keyword, and cursor. And hit that ENTER button right away. I am already doing it. Are you?

178

33 komentarze