Łukasz Wiśniewski

What is a TypeScript Engineer? I keep seeing this pop up in recruitment posts, which means clients are asking for it...right? Has this replaced the FullStack Engineer, which, lets be honest, meant a NodeJS developer. That was back in the good old days when it was only NodeJS. Now we have Bun, Deno, Hono and more. Or perhaps its asking for a Javascript developer...whatever that means in todays world of a thousand js frameworks and evolving ES standards. Or are they actually asking for a Java developer, because someones used Gen AI along the way and it got confused between Java and Javascript (*shudders*) Are they seriously in need of a type system engineer, thats kinda niche. It's hard enough trying to explain what you do as a job to "normal" folk as it is, without this level of obfuscation. How would you even explain this when asked "What do you do?". Do kids nowadays needs to consider themselves experts in everything inside package.json to land a job? When will the industry move beyond this fixation on specific languages? I get it, it's an important consideration, but asking for Typescript Engineers...it's not going to help you find the devs you actually need.

14

7 komentarzy

Why I Broke Up with NavigationView for NavigationStack 💔 Me to NavigationView: "It’s not you, it’s me... Actually, no, it is you. You’re just too... outdated." 😬 💡 NavigationStack slides in: "I heard you like clean, predictable navigation. Let’s make your app drama-free." 🎉 Now, with NavigationStack, navigating between views is so smooth, it feels like I’m swiping on a dating app. No weird reloads, no confusion—just one view at a time. 📱 My app: "Finally, I can stop seeing my views fight each other for attention like it's the Hunger Games." 👀 PSA: If you’re still using NavigationView, it’s like using dial-up internet at a fiber-optic party. Time to upgrade before your code ghosts you! 😂 https://lnkd.in/err3bdJQ #iOSGlowUp #NavigationStackForever #NoMoreViewDrama #SwipeRightOnBetterNavigation

3

📢 On the 27th of November, I'm going to run a 3-hour workshop about Fetching best practices when using Spring Data JPA. 💡 If you want to learn how to speed up your data access layer, then you should definitely join. https://lnkd.in/dcYZn4fJ

25

Repeat after me: clean code alone is not enough to stay secure! I just had a long talk with a company about tools. They are a mid-sized company and believe that tools are over rated. Running without security tools in 2024/2025 is like driving down a dark, windy road with your eyes shut. I put some of my thoughts down in this video. Enjoy. Let me know what you think. As always, stay secure my friends! #CyberSecurity #AppSecTools 

22

11 komentarzy

DevOps guy has to do Code Reviews and Integration and e2e Tests writing too. Because that is the only way to ensure: * Produced micro services are in high quality * Security against the hackers No automatic filters will magically help here. One super skilled programmer has to look at the fingers of less experienced colleagues. He has to be subordinate just to CEO, not CTO. Independence, protection from retaliation. Ability to deny backend updates, and there must be nothing the Programmers can do then. Lazy Programmers with attitude problems must be monitored even more. Even if "the team decided" to not do this or that, someone has to protect the company and do not let sloppy work through. Sometimes the hacker infiltrates the company, and attacks from the inside. Then such control is even more important. Many DevOps Pipelines idea is just like that, and that is what the managers often are asking for. They need Programmers to do professional high quality work. And the Programmers do not do that. How to achieve this level of control? #devops #programming #softwaredevelopment

2

1 komentarz

When evaluating engineers: Soft skills > Coding skills. In software engineering, we often get caught up in the technicalities - the languages, the algorithms, the data structures. But is that all there is to it? Let's take a step back and look at the bigger picture. What is the ultimate goal of software engineering? It's about creating value for customers, using technology as a tool. When hiring software engineers, it's easy to get swayed by impressive tech skills. But I urge you to first look for a product mindset. This is someone who understands that their role is not just to write code but to solve problems and create value. Next, look for creativity. In a field that's constantly evolving, the ability to think outside the box is invaluable. Enthusiasm is another critical trait. A passionate engineer will not only do their job but also do it with enthusiasm, constantly striving to improve and innovate and spread the energy to the rest of the team. Tech skills? Yes, they're important. But they can be learned and honed over time. Remember, we're not just building software. We're building solutions. We're building value. And to do that, we need more than just coders. We need problem solvers, innovators, and passionate creators. So, the next time you hire a software engineer, look beyond the code. Look for someone who can bring value to your product and customers. What do you think? I'd love to hear your thoughts and experiences. #softwareengineering #hiring

53

3 komentarze

New #ddev release that includes: - Automatic port switching to help avoid “port already in use” issues - Automatic time zones - “ddev get” is now “ddev add-on”

27

3 komentarze

Watch Elements of JVM Concurrency by Alexandru Nedelcu during the Scalar Conference 2024 Subscribe to our YouTube channel so you don’t miss the rest of #scalarconf videos.

7

"Slow is smooth, smooth is fast" is exactly how I feel about Rust Foundation, type safety, and software development in general. Rust code takes a bit longer to write (and even longer to compile 😰), but there are significantly less bugs slowing you down. Ref: https://lnkd.in/e72qGT_f

9

In her last post, Miriam brought up the concept of user-centricity in the development of APIs. Our training sessions last week made it clear that there is still a long way to go to make an interface available in a needs- and user-centred way and to allow it to develop over time. Requirements are never rigid. But if we dig a little deeper, this user-centred approach is not that easy. In the literature and daily practice, we find providers and consumers. But is this really the reality? In our API Thinking training , we've mapped this out for a simple case. But what if a provider is also a consumer of a third-party API that brings its service forward? And then things get complicated. This is another reason why we need to understand APIs better instead of just building them with the framework of our choice. A big thanks to Marianne for creating the graphic and thanks to Stefanie Schwilski for the idea with the slide. And as you can see, we always work as a team at codecentric AG . #codecentriccrew

16

Did you know that in Rhapsody you can drag an Interface Block directly onto a Proxy Port to set it as the contract for the port ? Check out these other useful drag and drop tips for Rhapsody here: https://lnkd.in/e2mFafyW

16

I've been a Technical Director for 4 years at RUSH. Before that, I spent 20 odd years coding. Writing code falls mainly within the “Ordered” domain (either Complicated or Clear) in the #Cynefin framework. However, the role of a Technical Director often sits in the “Complex” domain.  These different domains require distinct approaches and mindsets. A problem that seems straightforward when wearing my Developer hat can look entirely different when I switch to my Technical Director hat. Sometimes, these perspectives clash, leading to confusion. I’ve come to realise that this state of confusion aligns with the Aporetic (Confused) domain. That’s exactly where I want to start when thinking about a new problem or project - first identifying which Cynefin domain the problem falls into and then deciding on the appropriate approach.

19

2 komentarze

📢 Threat Alert - PHP CGI - Security researchers found a critical PHP remote code execution vulnerability in Window servers. Please patch your PHP a.s.a.p. and if that's not possible read the mitigations down below! What is going on and why is this a problem? But more important: What can you do to mitigate the risk? Discover it here: https://lnkd.in/g_ycyAVT   Need help? Get in contact with Ken Van Hasselt or via [email protected]   #ThreatAlert #nynoxcanhelp #GlobalProtectGateway #PHPCGI #vulnerability

9

Since my GitLab is no longer functional, I guess it is time to move on. Here's a couple simple authentication tips for anyone tinkering with Atlassian's Bitbucket: https://lnkd.in/dCWQMSeT

2

New Blog Post: How Erlang Powers High-Volume Finance! Do you need help with the challenges of high-volume transactions in fintech? There are many hurdles to achieving low latency and high performance and ensuring security, regulatory compliance, and seamless integration. But there's a solution that can help you navigate them all—Erlang! In my latest blog post, I discuss how Erlang's process-oriented programming model simplifies concurrent programming, making it the ideal choice for building scalable, reliable, high-performing fintech systems. Whether you're dealing with payments, trading platforms, or cross-border transactions, Erlang can transform your approach. 👉 Read the full blog post here: How Erlang Powers High-Volume Finance (https://lnkd.in/dJeTNEkw) Looking to take full advantage of Erlang's strengths? Happi Hacking (https://lnkd.in/ddCXfeu9) can guide you in leveraging Erlang to optimize your fintech systems. And if you need expert help managing Euro and SEK transactions, Kindio (https://lnkd.in/d_MCYZik) is here to assist! 📩 Contact us at Happi Hacking for specialized Erlang consultancy: [email protected] 💼 Reach out to Kindio for your Euro and SEK transaction needs: [email protected] Let’s build the future of fintech together! #Erlang #Fintech #HighVolumeTransactions #Scalability #Reliability #Programming #Finance #HappiHacking #Kindio #DigitalTransformation #RealTimePayments

33

Getting Started with New AutoGen Core API: A Step-by-Step Guide for Developers https://lnkd.in/eQ8H3gA8

2

It was nice to talk about overlooked REST API details that can get someone in trouble at DevFest Vienna ! From the questions it seems many people have doubts about how to use  RFC 9457 to report failures of their APIs. If you use SpringBoot, it is very easy, you just use the built-in  https://lnkd.in/et_ppKBy class. If you don't want to be locked in Spring, you can just include the schema from the RFC (https://lnkd.in/eWf5uJX5) in you OpenAPI spec. #rest #api #java

10

2 komentarze