Kim Liedtke

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!

27

1 Kommentar

Imagine getting a whopping 𝟕𝟓% discount offer! 😲💰 Just the other day, I sat down with a client over coffee in Duisburg. They had software development needs that typically would cost around $𝟏𝟐𝐊 with experienced developers from a German company. However, after some careful analysis, I was able to estimate the project at only $𝟑-𝟒𝐊. How did I pull off such massive savings? Well, it's all about the power of Right Outsourcing! By tapping into the talent pool of South Asian professionals, we're able to offer top-notch services at a fraction of the cost. ✨ With lower living expenses in countries like India and Pakistan, we can pass on those savings to our clients, slashing expenses by 𝟔𝟔.𝟔𝟕% 𝐭𝐨 𝟕𝟓%. But it's not just about the savings - it's about quality too! 🌟 Remote workers from these areas bring a wealth of skill and expertise to the table. And with Right Outsourcing handling all the management and recruiting tasks, clients in Europe can relax knowing their project is in good hands. 🔒💼 Ready to experience high-quality work at an unbeatable price? Send me a DM, and let's chat! #RightOutsourcing #Quality #AffordablePrice

14

7 Kommentare

Systems > SMART goals - especially in software development In April, I participated in the Berlin company run for the second time. So I was interested to see how I did compared to last year. I don't use Strava or heart rate monitors much, so I didn't know what to expect. Still, I was pretty sure I could beat last year's performance. That's because I've been doing a variety of workouts 5 times a week for the past few months. 📌 Set up a good system and the score takes care of itself The same goes for software development. If you want to increase your test coverage, start pair or ensemble programming on tests. If you want to get better at public speaking, find ways to practice in meetups and team all-hands. If you want to make progress on your project, start with a workshop and have regular discussions on Slack and in meetings. SMART goals makes sense when you have predictable processes. I don't find that useful in software development or in my personal life. And not motivating either.

50

6 Kommentare

👉We have been chatting to a couple of new clients in Germany this week, about using freelance Developers/Engineers outside of Germany (Nearshore), the same questions pop up; ✔How do we know if they are good or not? ✔How much can we save? ✔How quickly can they start? 👀Like anything, there is pros and cons to everywhere, but we have built a network of Freelance Nearshore Engineers who have been rigorously vetted with technical expertise guaranteed, that could save you a 50% reduction on your current freelance rates. If you are interested to understand more about this option and how this could help your business. 🚨Feel free to book a call in my Calendly and let’s see if we can help - https://lnkd.in/eygXyhaz

8

3 Kommentare

Vercel Ship 2024 Keynote starting now. At the UpLeveled GmbH #nextlevelcodingschool as one of the view coding bootcamps worldwide we always work with the latest Next.js version out there 👩‍💻🚀 https://lnkd.in/dbvTf8yp #vercel #nextjs #next #viennacodingbootcamp #amsterdamcodingbootcamp #stateoftheart #techstack #codingbootcamp #learntocode #learncoding

8

Do you want to build a new #blockchain AI app and don't know where to start? Good news! Starknet #Berlin Meetup is around the corner and you can learn everything you need to know from experts like StarkWare and Gizatech AG .     👉 23 April, 6 PM! Secure your spot! 👇 👇 👇 https://lu.ma/x5w6qfud We will kick things off with StarkWare breaking the ice, exploring the world of Starknet, and sharing the latest updates on what the Exploration team at StarkWare has been up to lately. Gizatech AG will delve into building and scaling ZKML solutions powered by the Starknet Stack. They will particularly discuss their latest development, Giza Agents — a modular and extensible framework for integrating decentralized ML into on-chain strategy and action. After that, we will wrap up the meetup with a Q&A session and networking, followed by food and refreshments. 🍕 🍻 Don't forget to secure your spot! 👇 👇 👇 https://lu.ma/x5w6qfud #Blockchain #ML #AI #Ethereum #Germany

2

I just checked - today we used approx 1M tokens since the start of today on Azure - our processes span both Anthropic and Azure but this is a lot of inference and output. With 1 million tokens: You can generate approximately 769,231 words. If spoken at an average rate of 150 words per minute, these words would last about 5,128 minutes. That's roughly 85 hours of continuous speech! 🤯 #TokenUsage #DataAnalytics #NLP #AICommunication #SpeechStatistics #TechInsights #BigData #MachineLearning #OpenAI #ProductivityTools

16

2 Kommentare

Let me ask all the executives at #webagencies and companies who have the final say in #websitedevelopment: Are you frustrated with constant delays 🐌 and escalating 📈 costs❓ Check out pageBody GmbH if you want to speed up🏃‍♀️your #webdevelopment! They have got the right talent and some impressive solutions to make things smoother and faster. Give them a follow❣️

3

These are the basics of a good team

3

On Office Hours this morning: * I answered a question about whether it's worth it to look for Clojure jobs. Short answer: Clojure is a decent selection criterion. But if you find a good JS job, take it! https://lnkd.in/gUUxHYeV * I ramble on about the current chapter of my upcoming book because there were no questions. https://lnkd.in/gw99netY * Then Drew hops on and we get into a discussion of the challenges of REPL-Driven Development. https://lnkd.in/gy5xgRKZ You can always join! https://lnkd.in/gME3H3Kp

19

1 Kommentar

A few years ago I spent a lot of time on a ‘passion project’ - a real labour of love. I was learning how to build apps and came up with the ‘Salzburg Pocket Guide’, a free iOS app featuring the city we lived in at the time and which I absolutely loved. The app turned out to be quite popular, even ranking #1 in several countries. Since then I’ve been collecting anonymised usage data in Google Firebase, but never bothered to do anything with it. Fast forward to the AI boom of today. Curiosity got to me. Could AI uncover insights from my app's data? Data I had never looked at before. With over half a million raw, unprocessed records in JSON format, I uploaded the file to Gemini and then asked for interesting stats - no more and no less. The results were incredible. With no training, Gemini’s analysis totally exceeded my expectations. Within a minute or two, Gemini delivered a really comprehensive analysis: unique users, average usage, top user behaviour, most popular landmarks, peak usage times, and even tips for app improvements (based on usage data). All this from raw data, without needing a database or complex setup. This little experiment demonstrates the sort of game-changer AI can be for small businesses with lots of untapped data sitting there. AI isn’t just about fancy chatbots, but about unlocking really valuable insights that can drive decisions based on data. It has such huge value and potential beyond the usual creative tasks we associate with it. In case you're curious, the ‘Salzburg Pocket Guide’ is still available on the App Store. While some details are a little dated, it's a testament to how a labour of love can show the power of technology. #AI #DataAnalysis #AppDevelopment #SalzburgPocketGuide #Gemini #GBASolutions

29

6 Kommentare

How many of your supposedly internal-only backends are serving critical end-user traffic? Probably more than you think! Most frontend services have many transitive dependencies, and understanding these dependencies becomes increasingly difficult as your system grows in scale and complexity. As a result, it becomes exceptionally tricky to ensure that internal-only backends are fully isolated from end users. Google uses a common infrastructure platform for almost all of its services, internal and external; this provides for a message-passing mechanism common to all of these services. One outcome is that systems engineers can build accurate dependency maps of services; and that we can ensure new services only depend on other services at the same level or higher in the dependency stack. Risky dependencies — in this case, dependencies which place internal-only backends on the critical path for end users — can be a source of major production outages, because the internal-only backends do not generally have necessary reliability or safety guarantees. For example, you might have an externally-visible service that requires high levels of availability and performance, and this system has an indirect dependency on a backend with no availability or performance SLOs. At Google, we found success preventing major and huge outages by clustering services into categories with distinct properties, clear perimeters, and limited blast surfaces. The properties will depend on the guarantees we want to enforce. In this article, we use Google Maps to demonstrate how risky dependencies proliferate in complex systems, and then showcase how clustering Google Maps services into just two categories ("Internal" and "External") can prevent major and huge serving outages. We also outline how OpenTelemetry is used to identify violations of this clustering, which can be fixed before the violations cause a major serving outage. This article is based on a talk at SREcon EMEA, which you can see here: https://lnkd.in/e54b6G6p.

1

Developers are important - we can all agree on that. But as a founder or engineering leader, what would you prefer: one developer, or two, maybe three developers? This is not a trick question. Because you have two options. You can hire locally and have one developer. Or you can hire globally, through a partner, *cough cough* Athyna and you could hire two or three developers for the same price. Same talent, same price, two or three times more people shipping code. If you have investors you basically have a fiduciary duty to use us. Just sayin’. https://lnkd.in/eM7W_YjM

29

22 Kommentare

Talking within our team about how finding proper abstractions will often (always) make code structure just 'click' I remembered the share-pie story from DDD - and luckily found this https://lnkd.in/dzZfVngd . It is also, what I remember most from the book.

3

2 Kommentare

How many of your supposedly internal-only backends are serving critical end-user traffic? Probably more than you think! Most frontend services have many transitive dependencies, and understanding these dependencies becomes increasingly difficult as your system grows in scale and complexity. As a result, it becomes exceptionally tricky to ensure that internal-only backends are fully isolated from end users. Google uses a common infrastructure platform for almost all of its services, internal and external; this provides for a message-passing mechanism common to all of these services. One outcome is that systems engineers can build accurate dependency maps of services; and that we can ensure new services only depend on other services at the same level or higher in the dependency stack. Risky dependencies — in this case, dependencies which place internal-only backends on the critical path for end users — can be a source of major production outages, because the internal-only backends do not generally have necessary reliability or safety guarantees. For example, you might have an externally-visible service that requires high levels of availability and performance, and this system has an indirect dependency on a backend with no availability or performance SLOs. At Google, we found success preventing major and huge outages by clustering services into categories with distinct properties, clear perimeters, and limited blast surfaces. The properties will depend on the guarantees we want to enforce. In this article, we use Google Maps to demonstrate how risky dependencies proliferate in complex systems, and then showcase how clustering Google Maps services into just two categories ("Internal" and "External") can prevent major and huge serving outages. We also outline how OpenTelemetry is used to identify violations of this clustering, which can be fixed before the violations cause a major serving outage. This article is based on a talk by Pierre Theo Klein at SREcon EMEA, which you can see here: https://lnkd.in/e_cyxv_A. Jennifer Steiner Klein collaborated on turning the talk into an article.

39

Arey bhai! Inventing terms will help if it’s done to simplify or surface key concepts. But when done just for the sake of it, will only add to the confusion. Product Market Fit - this beautiful term already includes the idea of a market, an idea of a product and the idea of fitment. Product is the carrier of value that the market is seeking and is willing to pay for, this is the fitment that is being sought after. The so called position is embodied within this definition. Without positioning your product vector with the need vector of the market, how will you get fitment or alignment? So please don’t add to confusion by inventing terms randomly. #productmanagement #productmanager #productconcepts

12

4 Kommentare

What do users want from Bonterms? That when they send out a Standard Agreement it's quickly accepted by the other side. That's why for our Cloud Terms (SaaS) we: • started from a template that had already supported billions in SaaS revenue • went through six drafts, three sub-committees and multiple meetings over seven months by (our now) 100-lawyer Committee to get the balance right between customer and provider. Our Cloud Terms have been accessed over 26K times and we have all kinds of evidence that we got the balance right (more on that soon). But it's always nice to hear it from someone else: 𝗕𝗼𝗻𝘁𝗲𝗿𝗺𝘀 𝗖𝗹𝗼𝘂𝗱 𝗧𝗲𝗿𝗺𝘀 𝗵𝗮𝘃𝗲 𝗮 𝟳𝟬% 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗙𝗮𝘃𝗼𝗿𝗮𝗯𝗹𝗲 𝗿𝗮𝘁𝗶𝗻𝗴 𝗳𝗿𝗼𝗺 TermScout (top of the list). ("Customer Favorable" is the coin of the realm in these rankings as they otherwise compare agreements 𝘸𝘳𝘪𝘵𝘵𝘦𝘯 𝘣𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴.) Bonterms Standard Agreements cover the full stack of enterprise commercial transactions and are free to use. Link to the TermScout report and our Standard Agreements below. Have you met your customer (or vendor) on a Standard Agreement yet? #standardagreements #sales #procurement  

13

3 Kommentare

I've been a developer for 15+ years. I honestly do NOT understand grumpy developers, who just slag everyone off, and constantly have a negative attitude towards everything and everyone. They do not see how human relationships (with colleagues / management / clients) is actually the most important thing in their careers, and one of the main things (and only things!) that will keep them employed when ChatGPT is trained well enough to do what they do. You work in one of the most sought after industries, you (usually) make a lot of money, and all you're required to do is to sit in front of a laptop, in a nice office, and be professional and pleasant. This is such a privileged and amazing position to be in, yet so many developers are so unhappy, failing to see how lucky they are. And their negative attitude - is actually one of the main things that holds them back. Obviously, you'll sometimes see wrong decisions being made. Obviously, on occasions, you might have to deal with annoying people. But who doesn't? And does it really justify making your whole personality - a grumpy, cocky, and unpleasant one? Absolutely not.

129

25 Kommentare