Andrew Jones

You're browsing job postings and keep seeing the same requirements: specific software, certain certifications, technical skills you don't have. And you think: "Guess I'm not qualified for anything." Hold up. Let's reframe this. Skills gaps aren't walls – they're bridges you haven't built yet. And in 2026, building those bridges is more accessible than ever. Here are some free and low-cost upskilling resources: 💻 LinkedIn Learning – Thousands of courses (free trial) 🎓 Coursera – University courses, many free to audit 📚 edX – MIT, Harvard courses available 🔧 YouTube – Tutorials for almost any software or skill 📖 Public libraries – Often provide free access to learning platforms 🏛️ Government programs – Many provinces offer free training for job seekers Stop waiting until you're "ready." Start building skills while you search. Learning doesn't pause job hunting. Do both simultaneously. 🌐 workportal.ca 💼 Your next opportunity is waiting #aboriginalworkportal #upskilling #careeradvice #skillsdevelopment #learning #professionaldevelopment #jobseekers #careergrowth #continuouslearning #jobsearch #skillbuilding #workportalca

3

3 Comments

When a dev leads with “clean architecture,” I pause. If they push for the perfect setup before writing a single feature, I ask why? It’s not that quality doesn’t matter. It’s that context does. Perfect code doesn’t help if no one needs what you built.

7

4 Comments

GitHub just moved AI coding from autocomplete to architecture. Copilot Workspace now handles the entire development cycle—from issue to pull request. Early adopters report 55% faster feature completion. That's not incremental. That's structural. What this means for technical hiring: The value hierarchy is shifting. Junior developers who primarily translate requirements into boilerplate code face compression. Mid-level engineers who understand system design and can validate AI-generated solutions become more valuable. Senior architects who can decompose complex problems into AI-actionable tasks are suddenly force multipliers. This isn't about AI replacing developers. It's about redefining what "coding skill" means. The bottleneck is moving from syntax to judgment. For hiring managers: Start evaluating candidates on problem decomposition and code review capabilities, not just greenfield implementation speed. The engineers who thrive will be those who can effectively collaborate with AI tools as thought partners. For developers: If you're spending most of your time on implementation patterns that Copilot can generate, invest in the layers above and below—requirements analysis and architectural decision-making. The technical interview that asks candidates to write a sorting algorithm from scratch is becoming less predictive. The one that asks them to critique an AI-generated solution and identify edge cases? That's your signal. We're not losing coding jobs. We're compressing the implementation layer and expanding the strategy layer. Adapt your hiring lens accordingly.

4

"Angular is becoming Razor Pages." That’s what my teammate told me today. He was referencing Angular’s new @if control flow syntax and jokingly predicted the death of *ngIf by Angular 21. He ended his argument with the classic hot take: "Dotnet >>> Angular." I had to remind him why we chose Angular for our frontend. While the syntax might look familiarly chaotic to backend developers right now, the behavior is strictly next-gen frontend architecture. We aren't dealing with server-side rendering that requires a clunky full page reload every time a user submits a form. Angular provides an ecosystem that delivers a seamless feel that older backend technologies struggled to achieve on their own: ✅ True SPA Experience: No flickering reloads. The app feels native and fluid. ✅ Signals & Zoneless: We are rapidly moving toward a world where change detection is surgical and incredibly performant. ✅ Enterprise Dependency Injection: A structured way to manage code that other frameworks are still trying to bolt on via third-party libraries. ✅ Deferrable Views: The built-in ability to prioritize exactly what loads when (@defer) is a massive win for Core Web Vitals. We can borrow helpful syntax ideas from the backend, but the User Experience is pure frontend magic. ✨ Are you Team Angular or Team .NET for modern web apps? #Angular #WebDevelopment #RazorPages #UI #SoftwareEngineering #DotNet #Frontend #TechDebate #JavaScript #TypeScript

36

5 Comments

AI isn’t going to take your job. But someone who knows how to 2x productivity by leveraging it will. Recently, I’ve had more and more conversations with candidates who are doing just that....to the point where it feels like more of an AI powered operating system than piecing together a number of tools. Here are some examples pulled straight from my notes in the last 6 months: ✅ built a GitHub Copilot + GPT agent workflow that writes unit tests as they code ✅ created a bot that collects daily standup updates, summarizes yesterday’s commits, and then drops in a group chat ✅ summarizes design docs into TLDR ✅ uses AI as a pair programmer for architectural decision-making You don’t need to be an AI expert to start doing this. You just need to be curious—and willing to stop doing things the hard way. If you want to stand out in interviews, ship faster, and stay relevant in a shifting market— because let’s be honest, it’s tough….figure out ways to leverage AI in your workflow. What are some ways you’re using AI to save time and increase productivity? Asking for a friend 😉

24

3 Comments

🌐 𝐖𝐞𝐛 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 𝐒𝐚𝐥𝐚𝐫𝐲 𝐢𝐧 𝐎𝐡𝐢𝐨: 𝐏𝐚𝐲 — 𝐂𝐚𝐫𝐞𝐞𝐫 𝐈𝐧𝐬𝐢𝐠𝐡𝐭𝐬 — 𝐉𝐨𝐛 𝐎𝐮𝐭𝐥𝐨𝐨𝐤 Thinking about starting or advancing your web development career in Ohio? Understanding 𝐡𝐨𝐰 𝐦𝐮𝐜𝐡 𝐲𝐨𝐮 𝐜𝐚𝐧 𝐞𝐚𝐫𝐧 is key before applying for roles or planning your next move. Here’s a quick breakdown: ✔ 𝐖𝐡𝐚𝐭 𝐘𝐨𝐮’𝐥𝐥 𝐋𝐞𝐚𝐫𝐧: • Average salary range for web developers in Ohio — from entry level to experienced professionals • How location and experience influence earnings • Comparison of wages in major Ohio cities like Columbus and Toledo • Top percentile earnings and growth potential 💰 𝐒𝐚𝐥𝐚𝐫𝐲 𝐒𝐧𝐚𝐩𝐬𝐡𝐨𝐭𝐬: • Average web developer salary in Ohio is around $73,000 – $90,000 𝐩𝐞𝐫 𝐲𝐞𝐚𝐫 depending on source and experience level. • Senior, specialized, or highly skilled developers can earn 𝐚𝐛𝐨𝐯𝐞 $100,000. • Cities like Columbus and Cleveland often offer higher pay compared with smaller markets. ⚠ 𝐓𝐡𝐢𝐧𝐠𝐬 𝐭𝐨 𝐂𝐨𝐧𝐬𝐢𝐝𝐞𝐫: ❌ Entry‑level positions typically start lower — experience matters. ❌ Location affects pay — urban centers often pay more than rural areas. ❌ Specialized skills (React, full‑stack, backend) usually command higher salaries. ❌ Freelance or contract roles may vary widely from salaried jobs. With tech demand rising across the U.S., having a clear picture of salary trends in Ohio helps you negotiate better and plan your career growth effectively. Full guide in the comments. Are you exploring web dev jobs in Ohio? 💻 #WebDev #TechCareers #DeveloperSalary #OhioJobs #CareerGrowth #KodersHive

2

1 Comment

This right here! Git rebase is an extremely valuable tool to have in your toolkit. Learning how to use it effectively is essential.

1

🚨 THE INSANITY: I just saw 47,000 applications for ONE junior software developer role 💥 Remember when 200 resumes was considered "a lot of interest"? Those days are DEAD. I'm staring at application numbers that would make your head spin: Then vs. Now: → 2010: 500-1,000 applications per role → 2024: 50,000-100,000+ applications per role What happened? The "Easy Apply" apocalypse hit recruiting like a tsunami. After 24 years in global staffing, here's the brutal reality behind these numbers: The 47,000 applicant breakdown: • 35,000 completely unqualified (74%) • 8,000 somewhat related experience (17%) • 3,500 actually qualified (7%) • 500 genuinely good fits (1%) • 50 interview-worthy candidates (0.1%) The real kicker: Only 2-3 will actually be great hires. What caused this madness: 1️⃣ One-click applications - Zero effort = Zero thought 2️⃣ Remote work explosion - Global talent pool for every role 3️⃣ Job board algorithms - "You might like this job" suggestions 4️⃣ Economic uncertainty - People applying to everything 5️⃣ AI resume builders - Mass customization at scale The hidden cost: → 3 weeks to review applications (vs. 3 days before) → $15,000 average cost per hire (vs. $4,000 in 2010) → 67% increase in time-to-fill → Hiring manager burnout through the roof But here's what nobody talks about: This volume is DESTROYING the candidate experience. Candidates are getting: ❌ Zero feedback on 99.9% of applications ❌ Automated rejections after months of silence ❌ False hope from "we'll keep your resume on file" ❌ Complete disconnect from actual hiring needs The solution isn't better filtering - it's BETTER BARRIERS. What smart companies are doing: ✅ Require cover letters (cuts applications by 70%) ✅ Add pre-qualifying questions (eliminates 60% of unqualified) ✅ Remove "Easy Apply" options (quality over quantity) ✅ Partner with specialized recruiters (access to passive talent) ✅ Use skills-based assessments upfront The uncomfortable truth: When everyone can apply to everything, nobody gets anything. For candidates: Stop spraying and praying. Research, customize, and target. For employers: Make it harder to apply, not easier. The paradox: The easier we make it to apply, the harder we make it to get hired. Pro tip: If you're getting 10,000+ applications, your job posting is the problem, not the solution. It's time to bring back intentional hiring. Question for my network: What's the highest application count you've seen for a single role? Drop your horror stories below! 👇 🔄 SHARE if you've witnessed this application madness 👥 FOLLOW me for more talent acquisition reality checks 💬 COMMENT with your strategies for managing high-volume recruiting 🔔 TURN ON notifications for daily TA insights #TalentAcquisition #Recruiting #JobMarket #HiringTrends #EasyApply #RecruiterLife #StaffingStrategy #CandidateExperience

3

I’ve noticed an interesting shift in my dev habits over the last few months. I’m doing less and less notebooks and more just pure py files. You might ask why? A few reasons: - uv makes it brain-dead easy to create virtual environments and run py scripts - when I do get an error, restarting the Jupyter kernel takes longer than me just rerunning the Python script from terminal - my dev code is becoming cleaner and less all over the place - no more copy-pasta the code from the notebook over the py when I’m ready to move up to prod. #dataengineering

46

28 Comments

Software engineers fear the AI that will take their job while the real danger I see should be in companies and solution owners themselves. Products that you spent years and tons of dollars for buildng selling it for whatever the number of subscriptions is can now be easily cloned and it costs nothing but the Gen AI subscription and some small resources. I am really curious of how the scene will look like after maybe Q2 of 2026. The development that business owners needs to follow “not to fail in the common nokia example” is now talking days not years like all used before!! #ArtificialIntelligence #GenerativeAI #SaaS #StartupLife #ProductManagement  #SoftwareEngineering #TechTrends #DigitalTransformation  #Innovation #FutureOfWork #Entrepreneurship  

5

2 Comments