Béla Bagaméri

Check out this treasure trove of resources By Arvind Telharkar! Perfect for leveling up skills.

2

1 Kommentar

Copilot and development: What activities are easy to automate? Hear what Marcel Chabot - Development Manager at The TM Group, Inc. uses Github Copilot for: - Writing up to 50 lines of code - Clean up long and complex code - Write documentation - Explain what the code does How have you been using Github Copilot to make your job easier? Want to see the full 34min interview? Click the link in the comment section. Dynamics Compass #github #copilot #microsoftcopilot #msdynamics #microsoftdynamics #msdyn365 #d365

2

1 Kommentar

I strongly think most interview software engineer coding questions are too focused on being clever and miss the point of an interview. Technical questions should focus on integrating new features in an existing code base OR architecting a new solution in a sane and extensible way. This isn't CS 301, I don't care if you know the optimal way to find the nth fibonacci number from scratch with no help and a whiteboard. What I care about is if you can work along with other engineers to figure out how to implement a method that polls an endpoint using fibonacci backoff. What about exponetial? Linear? What is a sane timeout given X scenario? I understand there are a lot of places where being a pro at coding can help immensely. That is not most places. You do not always need 100% optimized code for sorting through a 100 element list. Sometimes you just need someone who knows basic libraries to solve real world business problems quickly. My suggestion? When you do an interview, bring REAL problems you've experienced at your job to the table. See how the candidate reacts to those issues. Ask them how they would improve your architecture. Ask them what issues they see with their proposed solutions. Ask them how they would create unit tests for their own code.

14

2 Kommentare

DVA is not associated with this job posting Senior Product Designer, Import and Integration at GitLab https://lnkd.in/gGJe2Q-8 What youll bring Experience with Information Architecture. Strong experience working with and designing for large amounts of data, making it easy to understand and parse. Strong experience designing for a highly technical product, ideally in the DevOps space. Must have experience designing enterprise focused products. Leadership skills – ability to define and drive a UX vision in cross-functional teams. Driving change across other teams, not just your own. Experience conducting your own research with a variety of methods, and strong decision making skills for when to do research. #business #entrepreneurship #leadership #strategy #innovation #growth #success #management #marketing #sales #finance #productivity #networking #professionaldevelopment #career #teamwork #startup #smallbusiness #digitalmarketing #branding #customerexperience #technology #economy #investing #consulting #entrepreneurmindset #leadershipdevelopment #businessowner #worklifebalance #corporateculture

1

If you are an investor in developer platforms, dev tools or play a role in building any business competing for developer audiences, then you need to pay close attention. 📣 The good folks at DevRel.Agency are committed to elevating the work of Developer Relations and the profession at large (more news on that later). Take my word for it, for a decade now, they have provided the de-facto data driven insights into the talent fuelling developer focused businesses. 📊 This year the State of Developer Relations Report will be richer than ever.🚀 Stay tuned…📺 #developerrelations #devrel #stateofdevrel #developerplatforms #devtools #executivesearch #lawsonbrooke

9

1 Kommentar

My first task as a software engineer was "keeping the lights on" in production. My job was to look out for unusual exceptions and root cause them. I would read exception emails, dig through logs, and communicate with senior engineers. In short, I was the support/on-call engineer. I wanted to make a good impression, and I pushed myself too hard. For the first three days, I hardly slept. On the fourth day, I lay in bed and didn't wake up for 12 hours. When I did, prod was down. 3 missed calls. 12 unread Slack messages. I quickly called my manager to apologize profusely. Me: Hi, I am sorry I wasn't available. __ messaged me. I am checking what the issue is right now. Manager: That's all right Gaurav. Are you okay? We couldn't reach you. Me: I am fine. I overslept. Give me 10 minutes, I am opening the logs. Manager: That's okay. __ has already resolved it. We figured your weren't feeling well. Me: Oh, that's great. Thanks. To be frank, I was a little disappointed. If a bug could be detected and resolved while I slept, wasn't I replaceable? Then I thought of the situation practically. Of course I was replaceable. A company couldn't afford to stop functioning because one engineer fell asleep. The show would go on, with or without me. But what would happen if two engineers were unavailable? What would happen if our emails stopped functioning? This is why Google has something called a "bus factor". The basic idea is that important projects shouldn't stop, even if a bus full of team members die. Morbid, yeah. But it gets the point across. Software systems have a similar concept called 'Single Point of Failure'. If your database collapses, a copy takes its place. But what happens when a monitoring system collapses? Who will report errors then? Both Facebook and Google realized this difficulty with building highly available systems. And they came up with similar solutions: In-Memory Time-Series Databases. Tomorrow at 9 AM IST, I will go through the first time-series database in our live lecture series: Facebook GorillaDB. Specifically, we will discuss its motivations and challenges. Get ready for some awesome deep dives. Cheers! #SystemDesign #TimeSeriesDatabase #LiveClass

436

16 Kommentare

YAGNI: You Ain't Gonna Need It. I was lucky to work at a company where several folks lived by this motto. It was one of the best lessons I learned early in my software engineering career. When writing code (or really anything), it's easy to go down the path of what-if, or it would be nice if it did this. Do you know what that path does? Delays delivering. One of the best ways to deliver quicker? Write less code. And this doesn't even touch on other benefits like hopefully less complex code, less code to maintain, etc. At its core, YAGNI is about doing the minimum to build a new feature or fix a bug. It's preventing flexibility until it's really needed. If you want to learn from my mistakes: I started working on an open-source front-end web code generator about 10 years ago (before I started at the above company). I wanted it to support everything - JavaScript, CoffeeScript (yep...), UI-style frameworks, testing libraries, and even patterns used for developing code. If someone made a feature request, they got it. I said yes to each one. This led to so many permutations that tests weren't keeping up. The code became complex to reason about, and new contributors were rare. When I first heard YAGNI, it was an ah-ha moment. I never fixed the above open-source project, but I did start to learn to say no more (especially to myself!). I firmly believe YAGNI has saved me a bunch of headaches and time over the years. If you don't currently have a good reason to justify writing some code, then you ain't gonna need it. And when you do need it? You'll write it then. #software #engineering #devops

16

Learn how to apply CRaC support for a Spring Boot application using Java-optimized offerings from BellSoft: Alpaquita Linux and Liberica JDK: https://buff.ly/451lra5

1

Attention TaroWorks users! Next week we're hosting our next Webinar Deep Dive: TaroWorks Best Practices. In this session, you will discover tips and strategies to help you get the most out of TaroWorks and improve your frontline operations. 📅 When: December 4 ⏰ Time: 5 PM (EAT) | 8 AM (CST) 👉 Register now: https://lnkd.in/gfp9HmbQ #TaroWorks #FrontlineOperations #Webinar

2

1 Kommentar

*Bracing myself for the response I might get for asking this* Software Engineers: Would you ever consider working on an EQUITY ONLY basis (ie no salary, just owning a portion of the business, the value of which would increase as it progresses and scales)? Assuming: - The product is really interesting and so is the work - The product is in the "tech for good" space and would be a really positive contribution to parts of society - Seed funding is confirmed to be coming with several backers keen & they will able to offer a salary in the near future - The product is super early stage, you would be writing the software from the ground up, but the concept, design and business model once funding is received are all solid I know that there will be many who would never consider this under any circumstances and I totally get why, but just curious to hear if any of you would if it was for a product you believed in enough? And would you look at it on a full-time basis or a part-time basis? It's something I got asked about and so I thought I would throw it out to Linkedin to see what you all think rather than assuming that I know the answer on your behalf. #startup #founder #softwareengineer

39

309 Kommentare

One simple way to retain software engineers. An end of year review. Goal setting for 2025. Proper 1-2-1 time. Where possible, ideally face-to-face. Sounds obvious. But many engineers I speak say it doesn’t happen. People want to feel valued. When was the last time you had a 1-2-1? #retention #endofyearreview #2025goals

8

New Post: Return Stdout, Stderr, and Status From Jenkins sh Script

1

To golang or not to golang. I was turned down for a role because they wanted someone that was primarily golang. I'm okay with that. Golang is useful when you need the benefits of a compiled language with good enough memory protection. Where execution speed matters. Where resident size in memory matters. Where removing tools for attackers matters. For most things I work on the bottleneck is the CI/CD system, the network, physical storage, restful/graphql interfaces, container bring up/tear down, the developer's time. Most of my personal projects are polyglots of BASH and SQL. A few need the extra oomph of Python. A couple interesting ones need javascript for Tampermonkey. At this point I'm fluent enough in golang to fix bugs in in house golang code... and to find when a preferred golang based tool is unsuitable for use as a library. Sometimes it's simple patches against the 3rd party tool to make it usable. Alas, most corporate environments create way too much red tape to submit those patches. So much for mutual aid.

1

The Selfish Round Robin Algorithm: Balancing Efficiency and Individualism - Enhance your coding expertise with @oliver on @OnlyCoders.net Follow @oliver and Read More at https://lnkd.in/ezUJCXYw #programming  #softwaredeveloper #softwareengineer #100daysofcodechallenge #webdevelopment

7

🚀 Software Engineers: Top Programming Languages in Demand! 🚀 As we move through 2024, it's fascinating to see how the tech landscape is evolving. From my experience and recent industry reports, several programming languages are standing out as must-knows for software engineers. Python continues to dominate due to its versatility and ease of learning. It's widely used in web development, data science, and AI projects. The demand for Python skills is only growing, with many startups and established companies seeking Python developers to drive innovation. JavaScript remains a cornerstone for front-end development. With frameworks like React and Angular gaining traction, JavaScript proficiency is essential for creating dynamic and responsive web applications. Many businesses are looking for engineers who can bring their web projects to life with these tools. Lastly, Java is making a strong comeback, particularly in enterprise environments. Its robustness and scalability make it a preferred choice for large-scale applications. Companies are increasingly investing in Java for backend development, ensuring their systems are both reliable and efficient. What programming languages are you focusing on this year? #ProgrammingLanguages #TechTrends #SoftwareEngineering

6

1 Kommentar

Hey folks, I need some advice. -- What are the top 3-5 things you do when making an API? Does your team have a standard way of writing APIs? Do you do api design reviews? Thanks for your help 🚢 #ApiDesign #SoftwareEngineering

170

59 Kommentare

Using strings to build up command lines for execution is error-prone and potentially insecure. Check out why Ruby's %W array-literal syntax is the perfect tool for writing, composing, and executing external commands! Get two weeks of GracefulDev Pro free: https://lnkd.in/d7NRgP7Q

1