# junior Published articles for junior. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Worth Reading 091126 DevFeed: [Worth Reading 091126]() Original publisher: [Read original article]() Author: Russ Published: 2026-09-11T15:39:48Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [Artificial Intelligence](), [data](), [Internet](), [Programming](), [Software](), [systems]() Tags: [ai](), [articles](), [data](), [errors](), [internet](), [junior](), [learning](), [programming](), [rpki](), [software](), [systems](), [worth-reading]() ### AI overview A reading roundup connecting the AI bubble, Internet Route Registry and RPKI safety, silent data corruptions, and the effects of AI-assisted programming on junior developers and software engineering. ### Source excerpt Recognizing that AI is a bubble requires one to apply the right test to the right companies and that requires one to understand the fundamental nature of the bubble in question. Based on the insights from those articles, we now shift attention to which parts of the Internet Route Registry (IRR) landscape can - or cannot - be replaced safely with information from the Resource Public Key Infrastructure (RPKI) system. While many faults manifest as crashes or exceptions, others are far more subtle to identify. Silent data corruptions (SDCs), also known as silent data errors or silent errors, are violations of data integrity that occur without immediate, observable, and explicit indications. Aligning intended learning outcomes, assessments, and teaching practices with the realities of AI-assisted programming. AI is transforming the role of the junior developer. But as routine tasks become increasingly automated, how will the next generation of software engineers master the craft of maintaining complex systems? ## The Ghost Site Resurrector: How Junior Designers Can Turn Digital Abandonment into Cash DevFeed: [The Ghost Site Resurrector: How Junior Designers Can Turn Digital Abandonment into Cash]() Original publisher: [Read original article]() Author: Alex Harper Published: 2026-08-12T11:40:00Z Content type: article Language: en Sources: [Web Designer Depot]() Topics: [Web](), [Artificial Intelligence](), [Google]() Tags: [2026](), [ai](), [ai-web-design](), [building](), [business](), [conversion-optimization](), [design](), [digital-transformation](), [framer](), [framer-ai](), [freelance-web-design](), [freelancing-clients](), [ghost-websites](), [junior](), [junior-designer-tips](), [local](), [local-business-marketing](), [mobile-optimization](), [outdated-websites](), [responsive-design](), [search](), [seo-optimization](), [small-business-websites](), [smartphone](), [ui-modernization](), [ux-improvements](), [web-design](), [web-design-side-hustle](), [website-redesign](), [website-refresh](), [wix-adi]() ### AI overview The article presents the "Ghost Site Resurrector" strategy for junior web designers: identify local businesses with neglected websites, create a visual redesign mockup using tools such as Framer AI or Wix Harmony, and use the transformation to sell website refresh projects. It claims this approach can generate $1,000-$2,000 per project with less than four hours of total engagement. ### Source excerpt Most websites aren't broken--they're just abandoned. That forgotten, outdated site sitting on page two of Google could be a $1,500 opportunity hiding in plain sight. Welcome to the Ghost Site Resurrector strategy--where neglected businesses become your fastest path to cash. ## The Case for Hiring Junior Engineers 🌱 DevFeed: [The Case for Hiring Junior Engineers 🌱]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-12T07:19:52Z Content type: opinion Language: en Sources: [Refactoring]() Topics: [Artificial Intelligence](), [systems](), [code reviews]() Tags: [2026](), [ai](), [code-reviews](), [hiring](), [junior](), [systems]() ### AI overview This opinion argues that companies are making a practical business mistake by freezing junior engineering hiring because of AI. It acknowledges that junior engineers now face earlier demands such as code review, critical thinking, and systems thinking, while arguing that these challenges do not eliminate the value of hiring them. ### Source excerpt Let's flip the narrative that you only need seniors now. ## Your tokenmaxxing is not valuemaxxing DevFeed: [Your tokenmaxxing is not valuemaxxing]() Original publisher: [Read original article]() Author: Phoebe Sajor Published: 2026-08-11T07:40:00Z Content type: opinion Language: en Sources: [Stack Overflow Blog]() Topics: [AI-assisted coding](), [AI Bots]() Tags: [agentic](), [agentic-ai](), [agents](), [ai](), [ai-coding](), [cloud](), [coding](), [developers](), [development](), [infrastructure](), [junior](), [platform](), [podcast](), [pull-requests](), [release](), [se-stackoverflow](), [se-tech](), [skills](), [speed]() ### AI overview A discussion of why token usage is not a useful measure of value from AI coding agents. It considers release speed and PR merges as measures of agentic outcomes, alongside the effects of broader access to skills on junior developers and the talent pipeline. ### Source excerpt Ryan is joined by Coder's Rob Whiteley to chat about why tokenmaxxing isn't proving real value and just triggering Goodhart's Law, how release speed and PR merges can help you measure agentic outcomes with or without a human-in-the-loop, and what the democratization of skills means for junior developers and the talent pipeline. ## One year of platform engineering certifications: What 2,000 students taught us DevFeed: [One year of platform engineering certifications: What 2,000 students taught us]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Software Engineering](), [DevOps](), [site-reliability-engineering]() Tags: [and-best-practices](), [best-practices](), [devops](), [junior](), [platform-engineering](), [survey](), [training]() ### AI overview The article reflects on the first year of Platform Engineering University and the lessons from nearly 2,000 students. It explains that senior platform engineers, platform leaders, and technical strategists became the main audience, seeking validation, shared terminology, and alignment around platform engineering practices. These findings led to a four-tier certification and learning architecture designed for platform teams at different levels. ### Source excerpt Learn what 2,000 students taught us about platform engineering. Discover why senior engineers and platform leaders are the primary audience, and how our single course evolved into a certification architecture for shared team language and best practices. ## What Interviewers Listen for in Behavioral Interviews DevFeed: [What Interviewers Listen for in Behavioral Interviews]() Original publisher: [Read original article]() Author: Stephane Moreau Published: 2026-07-19T11:12:27Z Content type: tutorial Language: en Sources: [Blog for Engineering Managers]() Topics: [Job](), [incident](), [service](), [connection pool]() Tags: [connection-pool](), [engineering](), [guide](), [how-to](), [incident](), [influence](), [interviews](), [junior](), [scope](), [service](), [teams]() ### AI overview This article explains how interviewers assess behavioral answers, emphasizing the scope of ambiguity, influence across teams, trade-offs, and whether candidates actively discovered problems. It argues that these signals can distinguish mid-level engineers from Staff-level engineers before the stated outcome. ### Source excerpt What I'm actually listening for when you answer. ## Earning taste and judgment DevFeed: [Earning taste and judgment]() Original publisher: [Read original article]() Author: Addy Osmani Published: 2026-07-14T00:00:00Z Content type: opinion Language: en Sources: [Addy Osmani]() Topics: [Artificial Intelligence](), [coding](), [Code]() Tags: [ai](), [developer](), [junior](), [junior-developer](), [microsoft](), [race-condition]() ### AI overview An opinionated analysis argues that AI coding agents automate the repetitive work through which junior developers traditionally developed taste and judgment, weakening the path from entry-level to senior roles. It discusses labor-market evidence and suggests that choosing what to build and evaluating its quality are increasingly durable skills. ### Source excerpt Taste used to be a byproduct of the reps. Agents took the reps. So if you're junior you now have to go get the taste and judgment on purpose. A builder's look at the weakening entry level, the two debts we now owe, and concrete ways to build judgment when the machine writes the code. ## Junior data engineers build pipelines. Seniors build trust DevFeed: [Junior data engineers build pipelines. Seniors build trust]() Original publisher: [Read original article]() Author: Sahar Massachi Published: 2026-06-30T13:02:18Z Content type: article Language: en Sources: [DataExpert.io Newsletter]() Topics: [data]() Tags: [data](), [junior](), [pipelines](), [product-owner](), [series](), [trust]() ### AI overview The article contrasts the work associated with junior and senior data engineers, framing pipeline building as junior work and trust building as senior work. It is identified as Part 3 of a data engineering essentials series. ### Source excerpt You are the product owner for data. (Part 3 of our DE essentials series) ## Career milestones do not eliminate imposter feelings DevFeed: [Career milestones do not eliminate imposter feelings]() Original publisher: [Read original article]() Author: Ryan Murphy Published: 2026-05-26T14:54:23Z Content type: opinion Language: en Sources: [The Software Engineering Times]() Topics: [Job](), [Development](), [Object-oriented programming (OOP)]() Tags: [fraud](), [interviews](), [junior](), [money]() ### AI overview The author reflects on progressing from a low-paid first technology job to greater earnings, recognizable company names, speaking engagements, and a larger audience. The article argues that imposter feelings persist despite career milestones and that they may change focus rather than disappear. ### Source excerpt I turned down interviews at Meta, Apple, Reddit, Microsoft and Amazon. The voice in my head still tells me I don't belong. ## I Asked 30+ Engineering Leaders at Apple, Amazon, GitHub and Sony What Junior Engineers Should Do About AI. Here's What They Said. DevFeed: [I Asked 30+ Engineering Leaders at Apple, Amazon, GitHub and Sony What Junior Engineers Should Do About AI. Here's What They Said.]() Original publisher: [Read original article]() Author: Ryan Murphy Published: 2026-05-05T17:03:50Z Content type: opinion Language: en Sources: [The Software Engineering Times]() Topics: [Code](), [GitHub]() Tags: [advice](), [engineering](), [github](), [junior]() ### AI overview The article reports that senior engineers and engineering leaders mostly advised junior engineers to build reliability, ask questions, find mentors, avoid burnout, and learn fundamentals rather than focus primarily on AI. ### Source excerpt I expected most of the advice to be about AI. Almost none of it was. ## Moving from Junior to Mid-Level Backend Engineering Requires Shipping and System Design DevFeed: [Moving from Junior to Mid-Level Backend Engineering Requires Shipping and System Design]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-04-07T12:03:32Z Content type: opinion Language: en Sources: [Eric Roby]() Topics: [backends](), [ci](), [GitHub Actions](), [systems](), [coding]() Tags: [backend](), [ci-cd](), [github-actions](), [infrastructure](), [junior](), [junior-developer](), [skills](), [systems]() ### AI overview The article argues that progressing from junior to mid-level backend engineering involves more than writing code. It emphasizes building valuable products, contributing to business logic and features, understanding CI/CD and GitHub Actions, and making sound system-design and infrastructure decisions. ### Source excerpt The skills that aren't in job descriptions but are on everyone's mind ## Recapping SEV0 London 2025 DevFeed: [Recapping SEV0 London 2025]() Original publisher: [Read original article]() Author: Kate Bernacchi-Sass Published: 2025-11-13T17:44:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Artificial Intelligence](), [ai-coding](), [incident](), [debugging](), [Automation]() Tags: [2025](), [ai](), [ai-coding](), [anthropic](), [automation](), [claude](), [debugging](), [engineering](), [event](), [fundamentals](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [junior](), [keynote](), [learning](), [london](), [outage](), [post-mortem](), [scale](), [slack-incident](), [systems](), [technology]() ### AI overview Recapping SEV0 London 2025, incident.io describes how AI is changing software engineering, coding, reliability, and incident response. The article discusses increased debugging demands, more complex systems, engineer burnout, and the challenge of helping junior engineers develop fundamentals when AI handles repetitive coding work. ### Source excerpt The first annual SEV0 in London exceeded our expectations with some amazing speakers and sessions. ## Stop Calling AI a "Junior Engineer" DevFeed: [Stop Calling AI a "Junior Engineer"]() Original publisher: [Read original article]() Author: Matt McKenna Published: 2025-07-29T17:59:05Z Content type: opinion Language: en Sources: [Matt McKenna]() Topics: [Artificial Intelligence](), [Large Language Model](), [Language models]() Tags: [ai](), [engineering](), [feelings](), [junior](), [llm](), [llms](), [mentorship](), [software-development]() ### AI overview This opinion argues that describing AI as a "junior engineer" is an unfair and misleading analogy. It contrasts human junior engineers' ability to learn, develop judgment, understand context, and grow through mentorship with the limitations the author attributes to language models. ### Source excerpt There's a common shorthand in tech circles: "Treat your AI like a junior engineer." It's meant to set expectations that you need to give it clear tasks, review its work, don't let it push to prod, etc, etc. But the analogy doesn't sit right with me. ... ## I Failed to Implement the Diameter of a Binary Tree in a Coding Interview DevFeed: [I Failed to Implement the Diameter of a Binary Tree in a Coding Interview]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2025-06-21T01:00:00Z Content type: opinion Language: en Sources: [Daniel Doubrovkine]() Topics: [LeetCode](), [coding](), [Code]() Tags: [advice](), [ai](), [coding](), [interview](), [interviewing](), [junior](), [principal-engineer]() ### AI overview A Principal Engineer recounts freezing during a basic coding interview despite decades of programming experience. The article offers advice for recovering from interview failure, including maintaining perspective, practicing, and recognizing the role of luck in LeetCode-style interviews. ### Source excerpt Six months ago I failed a basic coding interview at a FAANG. Yes, I was a Principal Engineer, and yes, I was paid absurd amounts of money, yet I couldn't implement a diameter of a binary tree as a "warm up" exercise, 10 lines of code. The interviewer was very nice about it, and was equally surprised. You see, I've been coding for 35 years, and I am not "rusty" at it, which is a typical excuse for senior ICs bombing LeetCode interviews. At that time I was writing code every day. I simply froze, and couldn't do it. All I could think of was "why the hell am I here doing this to myself?". I couldn't turn my brain around, apologized, cut the interview short, and, while I did ace several coding interviews at other companies for IC roles, went back to management for which I am, obviously, more qualified. Did you just bomb a coding interview? Here's some practical advice of how to deal with it. First, keep your head high and do not let this negative experience get to you. It feels awful, but unless you are blogging about your failure to implement the diameter of a binary tree, nobody other than you and the interviewer will ever know. Most likely the interviewer was also a half asleep drone deep inside the borg, administering a coding puzzle every day to the next sucker, so they will forget about you the next day. I see a lot of junior Engineers affected by failing at these. If you are recently out of college, it's helpful to think of these interviews as a school test, such as an SAT. I never had to take SATs (my children did), but most European schools have oral exams where you get a ticket from a jar with the problem statement. I had slept through too many alarms to attend an 8 AM physics class around 1996 because of a grueling late night partying schedule, and only really knew maybe half the material. Luckily 2/3 questions in my ticket overlapped with those classes I did attend, and so I did well. If you don't like school and prefer video games, think of these interviews ## Engineers Should Take Responsibility for Bugs in AI-Generated Code DevFeed: [Engineers Should Take Responsibility for Bugs in AI-Generated Code]() Original publisher: [Read original article]() Published: 2024-09-24T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Artificial Intelligence](), [bug](), [Git](), [coding](), [trust]() Tags: [ai](), [autonomous](), [bug](), [code](), [coding](), [commit](), [git](), [junior](), [management](), [manager](), [solve](), [support](), [team](), [testing](), [trust](), [value]() ### AI overview This opinion article argues that engineers remain accountable for bugs in code generated with AI. It says attributing defects to AI reduces an engineer's perceived value, and that responsible use requires testing, judgment, and ownership. ### Source excerpt AI didn't write that bug. If you're name is on the commit in Git, you wrote the bug. ## Tropical.rb Conference and Rails Girls São Paulo DevFeed: [Tropical.rb Conference and Rails Girls São Paulo]() Original publisher: [Read original article]() Author: Doximity Published: 2024-05-22T16:12:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Ruby on Rails](), [Ruby](), [Development](), [Programming](), [software-development](), [Software Engineering]() Tags: [brazil](), [community](), [conference](), [developers](), [development](), [engineering](), [event](), [global](), [junior](), [learning](), [programming](), [projects](), [ruby](), [ruby-on-rails](), [skills](), [software-development]() ### AI overview Doximity sponsored the Tropical.rb Rails conference in São Paulo and the following Rails Girls São Paulo event. The events covered Ruby on Rails, its community and upcoming Rails 8 features, while Rails Girls participants collaborated on a mentoring app and received guidance toward advancing their software development skills. ### Source excerpt On April 4th and 5th, 2024, Doximity sponsored Tropical.rb, also known as "The Latin America Rails Conference," in São Paulo, Brazil. This event gathered developers from across Latin America and beyond. It served as a dynamic platform for discussing Ruby on Rails, sharing knowledge, and networking among professionals in the field. The Doximity team at Tropical.rb Doximity has utilized Ruby on Rails since its founding, attributing significant success to the framework. The timing of the recent conference coincided with a resurgence in Rails' popularity, marked by new features and increased adoption among start-ups and new companies.The framework's robust foundation is evidenced by its daily use in major companies such as Doximity, Shopify, AppSignal, and 37Signals. The Tropical.rb conference featured keynotes from prominent Rails core team members Aaron Patterson and Eileen Uchitelle, who provided deep dives into the internals of Rails, explaining some of its magic. Rafael França shared insights on his experiences and the pivotal role of the Ruby on Rails community. The event highlighted numerous success stories of projects and companies built using Rails. Further excitement was generated by discussions on upcoming features in Rails 8, such as Propshaft, Kamal, and Thruster, detailed in Breno Gazzola's keynote. A central theme of the conference was Rails' suitability as a "one-person framework", with Rails 8 advancements reinforcing this concept. Rails Girls São Paulo The day after Tropical.rb, Doximity, in partnership with The Rails Foundation, sponsored the latest edition of Rails Girls São Paulo, a global non-profit initiative dedicated to introducing women of all ages to the world of software development. This edition of Rails Girls focused on empowering women with a programming background to improve their skills and guide them in their journey from junior to mid-level positions and beyond. Our SVP of Engineering, Bruno Miranda, attended the event, along with a fe ## visionOS: Beyond the Basics DevFeed: [visionOS: Beyond the Basics]() Original publisher: [Read original article]() Published: 2024-03-27T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [visionOS](), [Accessibility](), [iOS](), [User interface design]() Tags: [accessibility](), [apps](), [badge](), [course](), [design](), [developers](), [ios](), [junior](), [learn](), [learning]() ### AI overview A learning path for junior to mid-level iOS developers who want to deepen their knowledge of visionOS. It covers accessible app design, the visionOS Human Interface Guidelines, and augmented reality development with RealityKit and Reality Composer Pro. ### Source excerpt This course is for junior to mid-level iOS developers who want to learn more about visionOS. You'll learn to design apps for accessibility and use RealityKit and Reality Composer Pro to create augmented reality experiences. ## Avoiding The Classic Mid-Level Developer Trap DevFeed: [Avoiding The Classic Mid-Level Developer Trap]() Original publisher: [Read original article]() Author: Richard Donovan Published: 2023-08-19T09:12:22Z Content type: opinion Language: en Sources: [The Modern Software Developer]() Topics: [Development](), [Job](), [Software Engineering](), [Learning]() Tags: [career](), [developer](), [job-titles](), [junior](), [learning](), [software-developer](), [tech-stack]() ### AI overview The article examines the ambiguity of the mid-level developer role and describes a "Mid-Level Developer Trap" that can lead to lost focus, demotivation, stalled learning, and job dissatisfaction. It characterizes mid-level developers as having experience with their tech stack, partial self-sufficiency, awareness of their capabilities, and the ability to research problems and seek help. ### Source excerpt Welcome back to The Modern Software Developer. ## Seven Tips for Junior Developers DevFeed: [Seven Tips for Junior Developers]() Original publisher: [Read original article]() Author: Clément Gateaud Published: 2023-05-23T14:06:01Z Content type: tutorial Language: en Sources: [JobTeaser]() Topics: [coding](), [Code]() Tags: [careers](), [code](), [developer](), [junior](), [junior-developer](), [software-engineering](), [tips]() ### AI overview A career-advice article for junior developers. It recommends focusing first on the code needed for the current task, attempting to work through problems before seeking help, and using web resources to investigate issues. ### Source excerpt © Midjourney Whether you're fresh out of school or transitioning from another career, landing a job as a junior developer is a great accomplishment. But it's only the first step on your path to a successful career. Finding your marks in this new position is the next big challenge. In this article I'll share with you 7 tips I would have loved to receive when I started as a junior developer, one year ago. 1. Learn to walk before you run During your first days as a "professional" developer, you will most likely feel overwhelmed by the size and complexity of your company's codebase. "What are all those files? Do we really need millions of lines of code to run our application?". It will for sure look very different from the small side projects you've worked on so far. Don't bother trying to understand the whole codebase and how everything is structured. Just focus on what you need for your current task. If your first task involves a minor fix to a specific behavior, focus on the file that's responsible for that behavior and forget about the rest. It's already a significant challenge to understand the necessary code for your initial task, especially since you'll also be learning about the company's processes, people, and products. https://medium.com/media/12a11f60dbd4c74090fdadd0e0f0fded/href Don't get me wrong, getting a bigger picture is important, but take it one step at a time. You will get more comfortable with the rest of the codebase over time. If you try to assimilate everything, you will assimilate nothing. Choose your fights. Time will do the rest. 2. Getting stuck is great (but not for too long) You'll get stuck on some issues when coding (just like every developer in the history of mankind). It may sound counterintuitive but getting stuck is a chance. Why? Because it is in those situations that you'll learn the most. https://medium.com/media/2776dac640fcf556b334de07293fd1e4/href Do not ask for help right away. Do your best to understand how things work and try ## Effective Kotlin Item 10: Design for readability DevFeed: [Effective Kotlin Item 10: Design for readability]() Original publisher: [Read original article]() Published: 2022-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Kotlin programming](), [Programming]() Tags: [code](), [cognitive-load](), [effective](), [elvis-operator](), [implementation](), [junior](), [kotlin](), [programming](), [readability](), [workshop-learning-programming]() ### AI overview This article explains why code readability matters in Kotlin, emphasizing that developers spend much more time reading code than writing it. It argues that fewer lines or characters do not necessarily make code easier to understand, and that readability depends on cognitive load and familiarity with programming idioms, especially for less experienced Kotlin developers. ### Source excerpt Do we really want out applications concise, or do we rather want them readable? ## How to Attract and Retain Underrepresented Tech Talent DevFeed: [How to Attract and Retain Underrepresented Tech Talent]() Original publisher: [Read original article]() Published: 2021-03-20T18:23:05Z Content type: opinion Language: en Sources: [Emily Kager]() Topics: [Job](), [Requirements]() Tags: [diversity](), [hiring](), [internship](), [junior](), [language](), [mentorship](), [recruiting](), [tech-talent](), [writing]() ### AI overview A developer shares thoughts on attracting and retaining underrepresented tech talent, focusing on broader job-posting criteria, inclusive language, and hiring pathways such as internships and junior roles. ### Source excerpt A very common question I get in my inbox is, "I love your posts! How can I get more women to work at my company??". It's not a bad question but I'm just a developer and have never worked in recruiting or D+I so it's not necessarily my area of expertise. That being said, with the acknowledgement that I have a large San Francisco/Bay Area bias since I've spent my entire career here, I have a few thoughts on how to attract and retain tech talent from underrepresented groups. ## A Junior Software Developer's Journey at Codename One DevFeed: [A Junior Software Developer's Journey at Codename One]() Original publisher: [Read original article]() Author: Sergey Gerashenko Published: 2020-12-07T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Programming](), [Kotlin](), [Mobile]() Tags: [cross-platform](), [developer](), [development](), [java](), [journey](), [junior](), [kotlin](), [other](), [software-developer]() ### AI overview A junior software developer describes joining Codename One, learning Java, adapting to UI development, and working on the Kitchen Sink cross-platform demo application before learning Kotlin. ### Source excerpt Hello Codename One community, my name is Sergey Gerashenko. I'm a junior software developer at Codename One. My journey here began 3 months ago when I passed my first interview at Codename One and my first task was to learn Java within 2 weeks. Learning Java I knew a few programming languages like Python, C and C++ but was unfamiliar with Java or managed languages beforehand. Learning a completely new language in just two weeks seemed like an impossible task at first because it took me around five months to learn C++. ## DeveloperBridge: SoundCloud's Program for Training People from Diverse Backgrounds to Become Engineers DevFeed: [DeveloperBridge: SoundCloud's Program for Training People from Diverse Backgrounds to Become Engineers]() Original publisher: [Read original article]() Published: 2020-07-17T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Programming](), [engineering-leadership]() Tags: [careers](), [code](), [collaboration](), [community](), [course](), [developers](), [diversity](), [engineering](), [engineering-culture](), [junior](), [leadership](), [learn](), [learning](), [programming](), [recruiting](), [skills](), [training]() ### AI overview SoundCloud's DeveloperBridge is a year-long, paid traineeship that gives people without prior professional experience the opportunity to learn engineering, receive mentorship, and potentially transition into full-time roles. The program also aims to improve diversity and inclusion through broader recruitment and support for underrepresented communities. ### Source excerpt DeveloperBridge is a year-long, full-time, paid traineeship program where participants learn from and work with engineering teams at... ## Insights from SoundCloud's DeveloperBridge Trainee Program DevFeed: [Insights from SoundCloud's DeveloperBridge Trainee Program]() Original publisher: [Read original article]() Published: 2018-01-18T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Programming](), [Web Development](), [Web app](), [data-processing](), [JavaScript](), [React](), [TypeScript](), [Ruby](), [Apache Spark](), [SQL](), [User experience (UX)]() Tags: [data-processing](), [diversity](), [engineering](), [javascript](), [junior](), [learning](), [management](), [programming](), [react](), [recruiting](), [ruby](), [spark](), [sql](), [ux](), [web-app](), [web-development]() ### AI overview SoundCloud's DeveloperBridge was a paid, 12-month junior engineering program designed to provide hands-on experience, support hiring into full-time roles, and improve diversity in engineering. A trainee describes working across web development and data-processing projects, including React and TypeScript web-app UX work, Ruby and JavaScript web services, ETL processes, and Spark and SQL data analysis. The article also discusses iterative coding, collaboration, and developing confidence in software engineering. ### Source excerpt Back in 2016, the SoundCloud People Team collaborated with engineering management in an effort to bring more junior engineers into the... [Next page]()