KMS Lighthouse’s Post

Will you join the recruitment call of Zoltan? In the meantime come talk to me about the opportunities we have for Latam Developers at Foothill Solutions, focusing on Latam talent for positions of all seniorities, sure mainly seniors 🤷♂️ , but that does not mean I'll pass on Junior talent ready to face new challenges 🤟 . Focusing on 🕵♂️ : Fullstack Devs - .Net 6 - Microsoft SQL Server - Microservice architecture - Designing Web API's React Native Developer - Strong understanding of React.js and its core principles, along with Redux. - Experience with popular React workflows (such as Redux). - Experience with RESTful APIs and mobile libraries for networking. Excelsior!

This is how semantic versioning works

Most of us have come across enterprise frameworks. This could be a good core principal to adapt by all the home grown framework leads

I once found a front-end engineer strangling a back-end engineer. From experience, I didn't try to stop him. I just asked him why. "He changed the client version from 1.1.3 to 1.1.4." the FE explained. "So?" "So? SO?! He made a breaking change on the patch update!! The company stock is down 15% and the CEO wants to know my current location!" This is a good time to talk about API versioning. Versioning has the following format: MAJOR.MINOR.PATCH (1.1.3) 1. MAJOR: May break expectations (not backwards compatible). 2. MINOR: Adds some new features without breaking anything (safe to move). 3. PATCH: No new features, just bug fixes and improvements (very safe). How does it work in real life? - Let’s say your current version is 2.5.3. - You fix a bug → next version is 2.5.4. - You add a cool new feature → next version is 2.6.0. - You change a core part of the software that breaks existing functionality → next version is 3.0.0. If you are an engineer, you would be wise to follow this system. It lets dependent systems update their libraries safely. No engineers were harmed in the telling of this story. ----------------- I talk about API contracts here: https://lnkd.in/dhFtXvqK #API #Versioning #SystemDesign

Versioning is crucial because it helps keep track of changes made to a project in a clear and organized way. My supervisor often emphasizes this because proper versioning makes it easier for both developers and clients to see the differences between updates without needing to launch them in production or other environments. It provides a clear record of what has changed, making it easier to manage updates and avoid confusion.

Backend Developer

🚀 **Experience at Delivery Go as a Full Stack Developer** 🚀 I recently worked on phase 1 of a project at Delivery Go, initially implemented in Guatemala with great acceptance ### Technologies Used: - **Frontend:** Angular with Ionic - **Backend:** NestJS - **Databases:** DynamoDB and SQL ### Challenges and Achievements: - Implemented connections to multiple databases in different countries, ensuring accessibility and consistency. - Consumed data from an SQL database to create reports, which were stored in DynamoDB. - Developed efficient and secure APIs with NestJS. ### Team: The technical and non-technical team was fundamental in delivering value to the end users, ensuring that all implemented solutions aligned with their needs and expectations. ### Experience: This project not only tested my technical skills as a developer but also my knowledge in administration, which is part of my professional background. Another key factor was thinking about delivering value before writing code, ensuring that each development brought tangible benefits to the users. I am looking forward to continuing to improve and seeing the application being used in more countries. This project allowed me to strengthen my technical skills and face complex challenges in dynamic environments. #FullStackDeveloper #Angular #Ionic #NestJS #DynamoDB #SQL #DatabaseManagement #Teamwork #AdminSkills #ValueDelivery

How do you classify a Full Stack Developer against a dedicated Back End Developer or Front End Developer? I'm not suggesting for a second that one is "better" than the other! Don't get me wrong, but I've had some interesting conversations with other developers over what makes a Full Stack Developer "Full Stack". For me, a Full Stack Developer is someone who can apply themselves obviously anywhere in the stack and can upskill and apply themselves very quickly to new tech and new parts of a tech stack. But, I don't believe a Full Stack Developer, even senior, should be a specialist in all of these areas, but should know enough to be productive in all areas. Whereas, a dedicated Front End or Back End developer is very much a specialist in this role and should know their part of the tech stack inside out, understanding best practices for the frameworks in use and understand fully how to optimise everything about their part of the stack. Ultimately for me it comes down to, are you a generalist or a specialist? Both require different skill sets and both can be challenging in their own right with different career paths. I'm a generalist and proud! Do you agree?

Why Hiring Software Developers in Colombia Makes Business Sense Colombia is quickly becoming a hub for software development talent. But why should your business hire from there? Colombian developers are known for their technical skills, innovative mindset, and adaptability, making them a valuable addition to any tech team. Top reasons to hire from Colombia: 👩💻 Skilled Workforce: Access to highly qualified and experienced developers. 🕒 Time Zone Advantage: Alignment with US business hours for seamless collaboration. 🌎 Cultural Compatibility: Easier communication and teamwork. Check it out here>>> https://buff.ly/4dC2Fcl Up for a chat?

One of the most important reasons to hire a Junior Developer.