David Cohen’s Post

I can relate that as I’ve been using Gitlab more than Github as it has very efficient in user experience, has a great dashboard to help divide tasks and other great features.

This post is completely showing a true fact about oppressed developers. Tech companies should be aware of that and should be somehow careful/reasonable with their job requirements when being posted. #hiring #techcompanies #developers #hr #rules #tech #technologies

This! But the advice isn't for beginners. I mean, for the past four months, I've been working only with Bitbucket because that's my clients' preference. Also, no one has ever asked me why my GitHub history is empty because there's evidence of my expertise right in front of them. Flip the coin, it's not the same with a beginner. The urge to have dark green GitHub streaks is the beginning of consistent learning and the urge to learn even advanced parts like PRs and others just to earn the badges. If you're a beginner, or in your intermediate years and there's no critical evidence to support you working professionally, I would advise you to focus and use the "green dots" as self-motivation to keep the wheel rolling. NO RETREAT, NO SURRENDER

Stop hiring developers based on green dots in GitHub profiles. The best developers I know are not even on GitHub. They develop closed-source apps on platforms like GitLab. Git activity shows quantity, not quality. Measure developers based on the value they bring to a repo, not by how often they commit to a repo.

Spot on. I've led teams, built startups, and made many hires. I've seen all sorts of metrics paraded as the gold standard for evaluating developers. Whether it's lines of code, bug counts, or sprint points, none of them tell the full story and can be gamed easily. What really counts is harder to measure: things like problem-solving, communication, and adaptability. I've worked with engineers who barely touch GitHub but can craft code like art. And I've seen folks ace coding tests only to stumble when the real-world complexity hits. At the end of the day, it's about the difference someone makes in the trenches, not the numbers on their profile.

this guy prefers people working on closed-source projects on gitlab to open-source on github if they're trying to say that commits for the sake of filling up the contribution graph is not desirable, i agree with that to an extent but if they're really saying that closed-source is better than open-source, i disagree (except for businesses where open-source would hurt them) and who cares at all whether someone uses GitHub, GitLab, BitBucket, a self hosted git server, whatever I agree that quality >>> quantity, but how is a recruiter ever going to judge your quality without being able to see your open-source commits? you're not going to invite them to a private repository

Great insight, but I beg to differ to an extent. I've come across awesome/top-tier/10x senior devs who main both quantity and quality on GitHub. I would strongly advise - that "green field" on one Github profile does matter(I believe it still strongly does to recruiters). Strive to be consistent enough - be intentional about keeping it green - with both quality and quantity.

#hiring *Software Developer (Java, Springboot, Cassandra, MySQL) - Amsterdam*, Amsterdam, *Netherlands*, contract #jobs #jobseekers #careers #Amsterdamjobs #Noord-Hollandjobs #ITCommunications *Apply*: https://lnkd.in/g2s6bzhX Software Developer (Java, Springboot, Cassandra, MySQLReact, Accessibility, GraphQL) - Amsterdam A Software Engineer owns the execution of technical elements in the tech stack, products and processes. They are responsible for the implementation of technical solutions based on business requirements, they can estimate the effort and impact of the items they work on, and show a high quality of craft in what they deliver. A Software Engineer understands the quality of test automation is as important as the production code and spends time refactoring both to ensure ease of change enabling a sustainable pace of development. Key Responsibilities: Building Software Applications: Develop software applications using appropriate programming languages and tools Write code that is readable and reusable, following standard patterns and libraries Refactor and simplify code when necessary, including the introduction of design patterns Ensure the quality of the application through standard testing techniques and methods Maintain data security, integrity, and quality by following company standards and best practices End to End System Ownership: Monitor application health and performance, set and monitor relevant metrics, and take action when violated Reduce business continuity risks by applying best practices and writing appropriate documentation Reduce risk and obtain customer feedback through continuous delivery and experimentation Independently manage an application or service through deployment and operations in production Technical Incident Management: Address and resolve live production issues within SLA, mitigating customer impact Improve system reliability by producing long-term solutions through root cause analysis Keep track of incidents by contributing to post-mortem processes and logging live issue Architectural Guidance: Advise product teams on technical solutions that meet functional, non-functional, and architectural requirements Evaluate and align target architecture improvements, reframing architectural designs and decisions for various stakeholders Software Systems Design: Evaluate possible architecture solutions, considering cost, business requirements, technology requirements, and emerging technologies Describe the implications of changing or adding a system to a specific area Help grow the business and accelerate software development by applying engineering techniques and standards Design solutions that meet current requirements and are adaptable for future enhancements Critical Thinking: Systematically identify patterns and underlying issues in complex situations Find solutions by applying logic