Dimitrios Filippou

There is a practice to propose reviewing real code during the technical interview. Ivan Netreba let me propose #React (more #redux or even pure #javascript) question. What's wrong with the code?

40

20 σχόλια

Hej Network! Java 23 came out couple of months ago now, if you haven't had time to catch this might be helpful. As it's not a LTS like Java 21 which is growing in the market for Java code bases. Mostly the features are a refinement in this version with some new stuff also. A run down for people that want know about the key features, do your own research for all the details. ⏺️Pattern Matching Came in Java 17, allow more complex use cases with deconstructing data ⏺️Structured Concurrency Been around since Java 19, but improved stability from older versions. ⏺️Virtual Threads Again, came in Java 19 and gives better resource management better to use in high Concurrency applications ⏺️Record Patterns First came to Java in this form in 16 and allows are to extend record patterns and deconstruction of record types. Mainly improvements from version 19, 20 ad 21. New features are! ❇️Module Import Declarations  Simplified import of entire modules ❇️Markdown Documentation Comments Write JavaDoc comments using Markdown 💠Generational Z Garbage Collector (not completely a new thing, but due to its new generational mode in 23 it's a good thing. Also, Java 24 not too far away so keep an eye out for that! #Java23 #Java

17

If you are a React developer thinking about switching to Vue.js, it can be challenging (and I'm always happy when someone does that 🤗 ). Check out the article by my colleague, who offers tips to help you get acquainted with Vue, particularly in reusing templates. Discover how VueUse can streamline your Vue.js development: https://lnkd.in/dprpMFfz #react #vue #vuejs #vuedeveloper #vuedevelopment #reactdevelopment #reactjs #reactjsdeveloper #opensource #opensourcedevelopment #opensourcecommunity #frontend #frontenddevelopment

6

And here we are: A Typescript Advanced Course ready to be booked 🚀🚀🚀 ✅ Basics: Overview of TypeScript's basic abilities and limitations. ✅ Type System: How TypeScript's type system works. ✅ Advanced Types: Create flexible types with Union and Intersection. ✅ Utility Types: Use common type transformations. ✅ Never: Represent impossible scenarios in TypeScript. ✅ Generics: Deep dive into constraints and type recursion. ✅ Literals & Template Literals: Use specific types for precise narrowing. ✅ Mapped Types: Create types based on existing ones. ✅ Type Guards: Securely recognize and narrow down types. ✅ Branded Types: Advanced techniques for complex patterns. https://lnkd.in/e5Up8VAj

17

Collapsible sections with native HTML instead of JavaScript? Yes please! https://lnkd.in/dxwV8jKF by Fotis Papadogeorgopoulos #accessibility #a11y #html

4

2 σχόλια

I just published a new php/laravel library look it up here https://lnkd.in/dnYXBxQb, you might find it useful. #php #laravel #mysql #api #programming #software #engineering

2

2 σχόλια

DevOps is a way of working. Every company does it differently.

9

Zuplo was super easy for me to integrate with my web API using only a couple of steps: 1) I needed to forward traffic from Zuplo to my server. This was done with "one line", if I can even call it that, in the Zuplo portal. Given my path on Zuplo, I just had to pick an option in their UI to rewrite and tell it what URL to go to. So far, so good. We like easy. 2) I needed to lock down my server. I want Zuplo to be the "front door" to my web API, but I still have to expose my service so that Zuplo can access it! To do this, I added an API key that my server knows about and Zuplo is configured to use. This means that Zuplo is the only outside source that knows the "secret" to talking with my web API. While my service could technically be discovered and callers could try hitting routes, they'll all be very quickly rejected. 3) ... to be continued! This is where all the *extra* stuff can get added: - Auth - Rate limiting - Monetization - Analytics - Documentation ALL OF IT done through Zuplo. That makes my life MUCH easier 😄 Check out more Zuplo here: https://lnkd.in/giqBk786 Stay tuned for the video coming this Friday on how I modified my ASCII art API to work with Zuplo! This Saturday's newsletter will walk through in more detail. #zuplo #api #webdev #aspnetcore

15

🚀 Elevate Your Frontend Development with Angular 18 🚀 I just published a new article on Medium about one of the most exciting updates in Angular 18— Signals and Signal Stores—and how they revolutionize state management and reactivity when combined with Reactive Forms. In this article, I break down: What Reactive Forms are and why they’re so powerful. How Signals in Angular 18 streamline reactive programming and boost performance. The role of Signal Stores in simplifying global state management. Best practices for protecting state to write more declarative and maintainable code. If you're looking to take your Angular projects to the next level, this is a must-read! Check it out 👇 🔗 Read the full article on Medium #Angular18 #FrontendDevelopment #ReactiveForms #Signals #SignalStores #WebDevelopment #StateManagement #Angular

2

🥋 In karate, a kata is a choreographed set of movements to be practiced repetitively. Unlike karate, code katas 💻 don’t need to be repeated over and over again–but they are meant to help programmers reinforce concepts and practice writing code! Katas are also a common part of technical interviews, where candidates are often asked to solve a problem using code written on a whiteboard or in a text editor. I get it--katas can be challenging! Code katas are meant for learning and practice, so don’t be discouraged if you get stuck. And if you're having trouble getting started and working your way through katas, this article might help! ✨ #CodeMom #CodeKata #LearnToCode #Interviews #GetAJob https://lnkd.in/d68-_wvs

11

Developers: "I'm a coder" Me: "... No, you are not." Hear me out, and trust me when I say this matters more than you may think: It's time to rethink how you present yourself. Code doesn't matter. Value added to the business in which you work within, does. 1. Shift from "coder" to "problem solver" 2. Emphasize business impact over technical skills 3. Highlight your role as a "value creator" Why? Because: • It aligns with what businesses truly need • It opens doors to more senior-level roles • It future-proofs your career against AI and automation Try this: Rewrite your bio focusing on problems solved and value added, not just technologies used. How has reframing your professional identity impacted your career? Share your experiences! #CareerDevelopment #TechLeadership #ProfessionalBranding #BusinessImpact #ValueCreation --------------------- 🌱 Follow me and hit the 🔔 to never miss a tip on taking your career to the next level 👍 Like if you agree 🔁 Repost if you think others can benefit from seeing this

Most habits a junior developer picks up in the early days of their career will stick. Here are my tips for developing good habits as a junior developer. 🤓 https://lnkd.in/dzWcRH3j

12

Deleting code can feel like an unnecessary risk but it's crucial for maintaining a healthy code base. 💡 Pro Tip: To avoid surprises, use the "Find All References" feature in VSCode and post in your team's group chat what you're removing. This will encourage everyone to "clean as they go". I love seeing more red then green when reviewing PRs, how about you? Need a one-liner? Every line of code is a liability, not an asset! #Technology #SoftwareDevelopment #Coding #Innovation #CleanCode

10

Technical debt is one of the top reasons for complaints among software engineers. It piles up when we cut corners or put off improvements, leading to messy, hard-to-maintain code. Focusing on the code and prioritizing some projects to reduce the issue can relieve us. Still, we'll keep running into big refactoring projects without a solid refactoring culture. We need a culture shift to keep technical debt under control. - Accept that technical debt is a natural part of software development. - Promote and show the benefits of a refactoring culture. Take the lead, and don't wait for someone else to step up. - Understand that shifting the culture takes time and effort. Be prepared, and don't give up (too soon).

16

The #YAGNI principle, which stands for "You Aren't Gonna Need It," is a #SoftwareDevelopment guideline that originated from Extreme Programming (XP). It advises developers to avoid adding functionality to their code until it is absolutely necessary. The core idea is to focus on the current requirements and avoid speculative features that might never be used. Benefits - #Simplicity: By avoiding unnecessary features, YAGNI helps keep the codebase simple and manageable. This complements other principles like KISS (Keep It Simple, Stupid), which also advocates for simplicity in design. - #Efficiency: It leads to faster development cycles and more efficient use of resources by focusing on delivering only what is needed at the moment. - #Flexibility: YAGNI encourages adaptability to changing requirements, aligning well with Agile methodologies that emphasize flexibility and customer feedback In practice, YAGNI is about striking a balance. It is not an excuse to neglect foresight or architectural considerations but rather a guideline to avoid over-engineering. Developers should focus on current needs and be prepared to adapt as requirements evolve. 📣 Join the WhatsApp Channel, for more knowledge sharing: https://lnkd.in/gxQfpuGD

1

I agree, these four books are fantastic. One would hope that it would start you on an unstoppable journey of code craft and discovery. I'd certainly not stop at just those four. The Art of Agile Development, Extreme Programming Explained, Working Effectively with Legacy Code, Refactoring, Clean Code, Beyond Legacy Code, and The Software Craftsman, Growing OO Software Guided by Tests come to mind. I understand, it's hard to just pick 4. Feels like there's a bigger message here, these books are not technology specific, this is about the act of software development, not something that's language specific. Looking at something more than just language model specific and more "meta" about how to perform the act of writing software better is where your journey as an awesome software developer begins.

7

1 σχόλιο

Job listings should stop using non-sense requirements like: ❌ 5 years in C# ❌ 7 years in React ❌ 10 years in enterprise software development They are not only poor metrics but also scare away developers. Judging a developer by the number of years is like judging a book by the number of pages. I know many young developers who are already better than many seniors with 10 years of experience but repeated the same year 10 times. Value developers for the depth of their journey, not the length of it.

1.551

152 σχόλια