Ville Hytönen

"Two front-end developers are sitting at a bar. They have nothing to talk about." I first heard this quote from Chris Coyier in 2019 - but it feels even more relevant today. The idea is that that front-end has grown to cover so many different areas that it's *really hard* to be an expert at all of it. Some might be great at HTML/CSS and working closely with designers to implement slick designs and interactions. Others might be entirely focused on mastering a modern JS framework + metaframework to handle data fetching and building an architecturally sound front-end application. These are all important skills, but mastering everything is simply too much to ask of most front-end developers (especially juniors). That's why I think it's important to realize what you most enjoy working with, and then doubling down on that part. Of course it's great to have an understanding of both "ends" of the front-end. But to really excel your career, you probably have to narrow your focus ✌

933

100 kommenttia

Use the Toolbox Panel in Visual Studio 2022 The Toolbox panel is well-known to developers who previously worked with WinForms. It was used to hold controls. In modern application development, we can also use this panel to store code snippets that we frequently use across different projects. ✔️ To open the panel, click View -> Toolbox or use the Ctrl+Alt+X shortcut. ✔️ To add a snippet, select the desired lines of code and drag them into the panel. You can then rename the snippet for convenience. ✔️ After that, you can drag and drop the snippet into the relevant parts of your code in other projects and solutions. Make your coding faster with this simple Toolbox tip. If you found this helpful, please repost it 📢 #csharp #dotnet #softwaredevelopment #visualstudio

44

4 kommenttia

𝗛𝗼𝘄 𝘁𝗼 𝗴𝗲𝘁 𝗮 𝟮𝘅 𝗽𝗮𝗶𝗱 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗷𝗼𝗯 Without burning out searching for it Most developers don't fail because they lack skill. They fail because they apply without a system. They spend hours scrolling job boards, filling the same forms, and getting rejected. The result? Burnout - not better offers. Here is a 7-step system to apply smarter 👇 1️⃣ Identify what you really want → Define your target role clearly: seniority, tech stack, company size, remote/hybrid preference, timezone. → Avoid "apply everywhere" strategy - focus on where you fit best. 2️⃣ Research your market → Look at real salaries (Glassdoor, Levels(.)fyi). → Understand what skills companies pay more for in your stack (.NET, Azure, System Design, Cloud Architect). → This helps you aim for high-value roles, not just "open positions." 3️⃣ Build a reusable application foundation → Prepare a strong master resume and cover letter. → Keep 2–3 tailored versions (e.g., backend-focused, cloud-focused, Tech Lead/Architect). 4️⃣ Automate and filter your job search → Use JobCopilot to skip repetitive, manual job hunting. → It scans verified company career pages - without scams and duplicates. → Apply smart filters like timezone, industry, seniority, and tech stack to find real matches. → JobCopilot auto-fills forms and reuses your answers, so you spend time preparing for interviews - not filling out the same forms again. 5️⃣ Apply consistently, not desperately → Applying to 20 quality jobs beats 200 random ones. → Use JobCopilot's learning system to find closer matches over time. → Let it adapt your tone and resume for each job. 6️⃣ Apply smarter, not harder → Set up daily job scans. → Let your Copilot learn what you like - it adapts with every application. → Run multiple searches in parallel (each with its own filters, resume, and tone). → You will get quality matches and save hours each week. 7️⃣ Track, follow up, and improve → Use JobCopilot's built-in tracker to see where you have applied and when to follow up. → Use the networking assistant to reach out to people on LinkedIn. → Use its mock interview and AI coaching to practice before real interviews. If you're tired of sending applications that get rejected, try building a process that works for you, not against you. Give your job search an upgrade, try JobCopilot here: https://lnkd.in/gjyKXj6e —— ♻️ Repost to help others find better jobs without burning out ➕ Follow me ( @anton-martyniuk ) for more #jobsearch #career #jobhunting #interviews #jobcopilot Thanks to JobCopilot for sponsoring this post

195

70 kommenttia

If you're working on a complex software project, having good architecture diagrams really helps. And in this guide Alex explains what the C4 model is & how it works. You'll go through each level - context, containers, components, & code - in detail. https://lnkd.in/ef34fiwF

260

5 kommenttia

✨ First open source PR in years. First blog post ever. First time adding Cassandra support to Testcontainers-dotnet? Yep, Gavin de Kock just did all three. And it was smooth sailing. 🚢 From spotting a missing module to contributing it with ease, Gavin shares how friendly the Testcontainers OSS community is—and how simple it is to spin up Apache Cassandra for .NET integration testing using Docker. A fun read and a great reminder that open source is open for everyone. 🙌 Check out the post and try it yourself: http://spklr.io/6048APQn #Docker #Testcontainers #OpenSource #DotNet #ApacheCassandra #IntegrationTesting #DeveloperExperience

40

2 kommenttia

#ADRs (Architecture decision record) are like event sourcing. ADRs are written down decisions about architecture. Why did you chose React? Why not Angular? What were the Pro and Cons and why was that solution the winner? They make it easy for developers new to the company or new to the team to understand the decisions BEHIND the current tech stack and architecture. So they can make better decisions themselves. A side effect of ADRs is that you do not have the same discussion over and over again. How are they like Event Sourcing? ADRs have not the downside of normal documentation. Normal documentation is hard to keep in sync with reality. It's a tedious process, and nearly impossible if you did not find the right level of documentation (deep enough, but not too deep). ADRs do not change. They are write-one-read-often, they are read only. They don't need to be maintained, they are always correct. In this way they are like events in Event Sourcing. Those also do not change. And ADRs can be seen as an event, and to get an understanding of the current state of your architecture, you need to read and aggregate those ADRs, just like events in event sourcing. https://adr.github.io/

28

2 kommenttia

🚨 Hot Take: TDD is Annoying I get it—Test-Driven Development (TDD) sounds like a great idea. Write tests first, ensure perfect code, and never fear refactoring again. But let’s be real: TDD often feels more like a bureaucratic hurdle than a productivity booster. Here’s why I struggle with TDD: 🔹 It fights how we naturally think. Engineers are problem-solvers—we design features, not test cases. Forcing tests before code is like asking a chef to write the recipe before tasting the dish. 🔹 It can lock in bad design. Ever written a test for code that doesn’t exist yet, only to realize the API was wrong? Now you’re refactoring tests instead of improving the product. 🔹 It’s not the industry standard for a reason. Most top tech companies prioritize pragmatic testing over TDD dogma. If it were truly indispensable, wouldn’t everyone mandate it? Am I saying tests are bad? Absolutely not. Tests are crucial—but slavishly following TDD can hurt more than it helps. A better approach? ✅ Prototype first, test later. Let the design evolve before locking it down. ✅ Focus on high-impact tests. Integration/E2E tests catch more bugs than unit tests anyway. ✅ Trust your team. If you ship reliable software without rigid TDD, why force it? The Bottom Line TDD is a tool, not a religion. Use it where it helps—discard it where it doesn’t.

562

378 kommenttia

On Thursday, Marvin Beckers and I will talk about Dynamic Multi-Cluster Controllers With Controller-runtime. Within sig-multicluster we are working on https://lnkd.in/dSnYsxxq, an extension of controller-runtime to write controllers that talk to many clusters. https://sched.co/1txFM

63

Typescript will now be 10x faster. Anders Hejlsberg today announced Project Corsa. Here's a TLDR around it. - Typescript was having performance and scalability issues ( for system-level operations ) due to the underlying JavaScript runtime. - Reached the limit of what could be squeezed out of JavaScript. - Decision was made to port the TypeScript compiler and tools to native code. - "Why not C++? Why not Rust?" : They tested various languages and found out that Go is the most suitable for the kind of workload they deal with. - Compile time for VScode ( the codebase they tested on) was 10 times faster with Go. - All performance benefits came from 2 things: Being native and having concurrency. https://lnkd.in/g4ZWuk_c

19

Ok, here is a thing. "We all know" that a managed instance can be collected during the method call. But do you know that an instance can be GCed **before** the instance method is called? This works in Release mode only due to the tracking the JIT does via GCInfo.

21

11 kommenttia