<![CDATA[TalkativeTurtles - Career & Education]]>

<![CDATA[TalkativeTurtles - Career & Education]]> https://talkativeturtles.club/ Wed, 05 Aug 2026 13:53:25 +0000 MyBB <![CDATA[Side projects on a CV - what actually matters to employers?]]> https://talkativeturtles.club/showthread.php?tid=124 Mon, 06 Jul 2026 20:35:25 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=124
Answer was roughly:

Is it real? A project with actual users, even 10, beats a perfect todo app every time. Evidence it shipped matters more than evidence it was technically impressive.
Can you talk about the hard part? Does not matter what the project is - they want to hear what broke, what you had to figure out, what you would do differently.
Is it maintained? A repo with commits from 3 years ago and zero activity reads as abandoned. A smaller project with recent commits reads as someone who actually builds things.
Does it match what they are hiring for? Not that much. A well-described systems project on an application for a frontend role still shows you can build things end to end.

Is it real? A project with actual users, even 10, beats a perfect todo app every time. Evidence it shipped matters more than evidence it was technically impressive.
Can you talk about the hard part? Does not matter what the project is - they want to hear what broke, what you had to figure out, what you would do differently.
Is it maintained? A repo with commits from 3 years ago and zero activity reads as abandoned. A smaller project with recent commits reads as someone who actually builds things.
Does it match what they are hiring for? Not that much. A well-described systems project on an application for a frontend role still shows you can build things end to end.

What they do not care about as much as you would think: star count, how polished the README is, whether it uses the right stack.

Take this as one data point. Curious what others have heard.]]> <![CDATA[Building a developer portfolio that actually gets you interviews]]> https://talkativeturtles.club/showthread.php?tid=96 Mon, 22 Jun 2026 14:39:47 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=96
What doesn't work:

Tutorial projects (to-do apps, weather apps, clones you followed step by step)
Projects with no README or documentation
Projects that don't work when you click the demo link
10 half-finished projects

What works:

One or two projects you actually finished and can talk about in depth. A single well-built project with a working demo, good README, clean code, and a deployment beats five unfinished ones every time. Hiring managers run out of time quickly - if your first project fails to demo or load, they often don't look at the second.

Projects that solve a real problem (even a small one). "I built this because I needed X and nothing did exactly what I wanted" is a much better story than "I built a CRUD app to practice React." It shows motivation and product thinking.

Demonstrate the stack you want to be hired for. If you want a Python backend role, your pinned projects should be Python backend. Don't dilute with unrelated projects.

The README matters. Include: what it does, why you built it, how to run it, what you learned or what was interesting about it. Screenshots or a demo GIF. Tech stack. This is what the hiring manager actually reads.

Contributions to real open-source projects are worth more than personal projects if you can get them. Even documentation fixes or bug reports show you can navigate an existing codebase and communicate with a team.

Deploy everything. A project with a live URL is 10x more impressive than one that's only on GitHub. Fly.io, Railway, Render, Netlify, and Vercel all have generous free tiers.

For junior roles specifically: the portfolio matters more than it does at senior level. Spend more time on it. But don't spend so long building the perfect portfolio that you delay applying.]]>
What doesn't work:

Tutorial projects (to-do apps, weather apps, clones you followed step by step)
Projects with no README or documentation
Projects that don't work when you click the demo link
10 half-finished projects

Designing Data-Intensive Applications (Martin Kleppmann) - not free but worth every penny. The most useful technical book I've read. Covers databases, replication, consensus, stream processing properly.
System Design Interview Vol 1 & 2 (Alex Xu) - more interview-focused, covers the walk-through format well. Available as PDFs online if you look.

Free online resources

ByteByteGo newsletter - Alex Xu's weekly system design breakdowns. Excellent diagrams, free archive.
High Scalability blog - real architecture breakdowns from actual companies (Slack, Twitter, Netflix). Aged but the fundamentals are evergreen.
The System Design Primer (GitHub, donnemartin) - comprehensive open-source guide covering all the major components. Good reference doc.
roadmap.sh/system-design - structured learning path with free content.

YouTube

ByteByteGo channel - animated explainers of system design concepts
Gaurav Sen - good for understanding distributed systems concepts
Hussein Nasser - deep dives on specific technologies (databases, proxies, protocols)

Designing Data-Intensive Applications (Martin Kleppmann) - not free but worth every penny. The most useful technical book I've read. Covers databases, replication, consensus, stream processing properly.
System Design Interview Vol 1 & 2 (Alex Xu) - more interview-focused, covers the walk-through format well. Available as PDFs online if you look.

Free online resources

ByteByteGo newsletter - Alex Xu's weekly system design breakdowns. Excellent diagrams, free archive.
High Scalability blog - real architecture breakdowns from actual companies (Slack, Twitter, Netflix). Aged but the fundamentals are evergreen.
The System Design Primer (GitHub, donnemartin) - comprehensive open-source guide covering all the major components. Good reference doc.
roadmap.sh/system-design - structured learning path with free content.

YouTube

ByteByteGo channel - animated explainers of system design concepts
Gaurav Sen - good for understanding distributed systems concepts
Hussein Nasser - deep dives on specific technologies (databases, proxies, protocols)

Practice
Ask yourself: how would I design [Twitter / YouTube / URL shortener / ride sharing / Google Drive]? Work through it out loud or on paper. Then look up how they actually do it.

The components worth understanding first: load balancers, CDNs, SQL vs NoSQL trade-offs, caching strategies (read-through/write-through/write-behind), message queues, horizontal vs vertical scaling, CAP theorem.]]> <![CDATA[How to actually prepare for coding interviews in 2026 - advice that works]]> https://talkativeturtles.club/showthread.php?tid=70 Mon, 22 Jun 2026 14:16:51 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=70
What interviewers are actually evaluating
Most good interviewers aren't primarily evaluating whether you've memorised the optimal solution to a specific problem. They're evaluating: can you communicate your thinking, do you handle edge cases, can you take a hint and adapt, are you pleasant to work with under mild pressure.

The preparation that matters

LeetCode: medium questions, topic by topic. Arrays, strings, hashmaps, two pointers, sliding window, binary search, BFS/DFS, dynamic programming. You don't need to do 500 questions - you need to understand the patterns.
Implement data structures from scratch. Linked list, stack, queue, binary tree, hash table. Once. You'll rarely be asked to implement them but understanding them makes everything else easier.
Practise talking while coding. Narrate your approach before writing. Most interview failures are communication failures, not algorithmic ones.
Mock interviews. Pramp, interviewing.io, or a friend with a whiteboard. The format is a skill and needs practice separately from the problem-solving.

LeetCode: medium questions, topic by topic. Arrays, strings, hashmaps, two pointers, sliding window, binary search, BFS/DFS, dynamic programming. You don't need to do 500 questions - you need to understand the patterns.
Implement data structures from scratch. Linked list, stack, queue, binary tree, hash table. Once. You'll rarely be asked to implement them but understanding them makes everything else easier.
Practise talking while coding. Narrate your approach before writing. Most interview failures are communication failures, not algorithmic ones.
Mock interviews. Pramp, interviewing.io, or a friend with a whiteboard. The format is a skill and needs practice separately from the problem-solving.

System design (for senior roles)
Read "Designing Data-Intensive Applications" (Kleppmann). Understand: load balancing, caching (Redis), databases (SQL vs NoSQL, indexing, replication), message queues, CDNs, rate limiting. Practice designing Twitter/Uber/URL shortener.

What to do in the interview
1. Restate the problem and confirm constraints before touching code
2. Talk through your approach first, get early feedback
3. Code clean and readable - names matter more than brevity
4. Test with the obvious case, then edge cases
5. Know the time/space complexity of your solution

The honest truth: the prep is boring and takes 2-3 months of consistent effort. There's no shortcut but it's a learnable skill.]]> <![CDATA[Salary negotiation for developers - what actually works]]> https://talkativeturtles.club/showthread.php?tid=113 Mon, 22 Jun 2026 14:06:37 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=113
The key insight: the company has already decided they want you when they make an offer. They want to hire you. Negotiation is about finding the number that works for both sides, not fighting.

Never accept the first offer immediately.
Even if it's good. Say "thank you, I'm very excited about this role. I'd like to take a day to review the full package." This signals you're thoughtful, not desperate, and gives you time to think and research.

Research first.
Levels.fyi, Glassdoor, LinkedIn Salary, and asking peers in similar roles all give you data. Know the market rate for your role, level, location, and company size before any conversation.

Give a number, not a range.
If you say £60-70k, they hear £60k. Say "based on my research and experience, I'm looking at £70k" - then stop talking. Silence is not your enemy here.

Counter higher than you expect to get.
If they offer £65k and you want £70k, counter at £75k. You'll likely meet in the middle.

Negotiate the whole package.
Base salary is only part of it. If they can't move on base: signing bonus, extra PTO, remote work flexibility, professional development budget, equity vesting schedule, earlier review date. Sometimes non-salary items are easier to approve.

Have an alternative.
The strongest negotiating position is another offer or being genuinely comfortable walking away. "I have another offer at X" is the most powerful sentence in negotiation - only say it if it's true.

Get it in writing before resigning anywhere.
Verbally agreed offers occasionally don't materialise as discussed.]]>
The key insight: the company has already decided they want you when they make an offer. They want to hire you. Negotiation is about finding the number that works for both sides, not fighting.

Never accept the first offer immediately.
Even if it's good. Say "thank you, I'm very excited about this role. I'd like to take a day to review the full package." This signals you're thoughtful, not desperate, and gives you time to think and research.

Research first.
Levels.fyi, Glassdoor, LinkedIn Salary, and asking peers in similar roles all give you data. Know the market rate for your role, level, location, and company size before any conversation.

Give a number, not a range.
If you say £60-70k, they hear £60k. Say "based on my research and experience, I'm looking at £70k" - then stop talking. Silence is not your enemy here.

Counter higher than you expect to get.
If they offer £65k and you want £70k, counter at £75k. You'll likely meet in the middle.

Negotiate the whole package.
Base salary is only part of it. If they can't move on base: signing bonus, extra PTO, remote work flexibility, professional development budget, equity vesting schedule, earlier review date. Sometimes non-salary items are easier to approve.

Have an alternative.
The strongest negotiating position is another offer or being genuinely comfortable walking away. "I have another offer at X" is the most powerful sentence in negotiation - only say it if it's true.

Get it in writing before resigning anywhere.
Verbally agreed offers occasionally don't materialise as discussed.]]> <![CDATA[How did you break into tech? CS degree, bootcamp, self-taught?]]> https://talkativeturtles.club/showthread.php?tid=55 Sun, 21 Jun 2026 09:42:20 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=55
How did you get your first tech role? What worked, what didn't, and what would you tell someone starting that path today?

I'll share mine: CS degree, which I have mixed feelings about. The theory is genuinely valuable and I use more of it than I expected (data structures, algorithms, networking fundamentals, OS concepts). But the practical job-relevant skills - version control, CI/CD, Docker, how to work in a team on a real codebase - I learned entirely on my own or on the job. The degree opened doors; the side projects are what got me through interviews.

Curious to hear from people who went bootcamp or self-taught, especially those who switched from other fields.]]>
How did you get your first tech role? What worked, what didn't, and what would you tell someone starting that path today?

I'll share mine: CS degree, which I have mixed feelings about. The theory is genuinely valuable and I use more of it than I expected (data structures, algorithms, networking fundamentals, OS concepts). But the practical job-relevant skills - version control, CI/CD, Docker, how to work in a team on a real codebase - I learned entirely on my own or on the job. The degree opened doors; the side projects are what got me through interviews.

Curious to hear from people who went bootcamp or self-taught, especially those who switched from other fields.]]> <![CDATA[[Guide] Tech Certification Roadmaps by Role]]> https://talkativeturtles.club/showthread.php?tid=54 Sun, 21 Jun 2026 09:42:20 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=54
Cloud (AWS)

AWS Certified Cloud Practitioner - Entry level, good for non-technical context
AWS Solutions Architect Associate - Most in-demand AWS cert
AWS Solutions Architect Professional - Senior level, significantly harder
AWS DevOps Engineer Professional - CI/CD and automation focus

Networking

CompTIA Network+ - Good vendor-neutral foundation
Cisco CCNA - Industry standard for networking roles, covers routing, switching, basics of security
Cisco CCNP - Advanced, specialise in Enterprise, Security, Data Centre, etc.

Cybersecurity

CompTIA Security+ - Widely accepted entry-level, DoD approved
CEH - Ethical hacking, theory-heavy but recognised by corporates
OSCP - Hands-on pentesting, highly respected, hard exam
CISSP - Management-level, requires 5yr experience, good for senior roles

Linux / Systems

CompTIA Linux+ - Entry level
LPIC-1 / LPIC-2 - Linux Professional Institute, more respected in Europe
RHCSA / RHCE - Red Hat certs, excellent for enterprise Linux roles

General Tips

Cloud certs (AWS/GCP/Azure) have the best ROI right now in terms of salary bump per study hour
Practice exams are more useful than courses for most certs - find Udemy practice tests
OSCP is worth it if you want to go into penetration testing. Nothing else substitutes for it.
A cert without hands-on experience is thin. Build alongside studying.

]]>
Cloud (AWS)

AWS Certified Cloud Practitioner - Entry level, good for non-technical context
AWS Solutions Architect Associate - Most in-demand AWS cert
AWS Solutions Architect Professional - Senior level, significantly harder
AWS DevOps Engineer Professional - CI/CD and automation focus

Networking

CompTIA Network+ - Good vendor-neutral foundation
Cisco CCNA - Industry standard for networking roles, covers routing, switching, basics of security
Cisco CCNP - Advanced, specialise in Enterprise, Security, Data Centre, etc.

Cybersecurity

CompTIA Security+ - Widely accepted entry-level, DoD approved
CEH - Ethical hacking, theory-heavy but recognised by corporates
OSCP - Hands-on pentesting, highly respected, hard exam
CISSP - Management-level, requires 5yr experience, good for senior roles

Linux / Systems

CompTIA Linux+ - Entry level
LPIC-1 / LPIC-2 - Linux Professional Institute, more respected in Europe
RHCSA / RHCE - Red Hat certs, excellent for enterprise Linux roles

General Tips

Cloud certs (AWS/GCP/Azure) have the best ROI right now in terms of salary bump per study hour
Practice exams are more useful than courses for most certs - find Udemy practice tests
OSCP is worth it if you want to go into penetration testing. Nothing else substitutes for it.
A cert without hands-on experience is thin. Build alongside studying.

]]> <![CDATA[[Rules] Career & Education — Forum Rules]]> https://talkativeturtles.club/showthread.php?tid=22 Sun, 21 Jun 2026 09:34:07 +0000 Zero Two]]> https://talkativeturtles.club/showthread.php?tid=22 Career & Education covers job hunting, certifications, degrees, bootcamps, interview prep, salary talk, and professional growth.

Posting Rules:

Be honest about credentials and experience. Fabricating qualifications in advice threads misleads others.
No unsolicited job offers or mass recruiting. If you are hiring, post one clear listing and do not cold-message members.
Salary discussions are encouraged - transparency helps everyone. Sharing your own numbers is fine; demanding others share theirs is not.
No "which is better?" wars without context. CS degree vs bootcamp vs self-taught depends heavily on individual circumstances. Provide nuanced answers.
No paid course spam. You may recommend paid resources but must disclose affiliation.
Protect your privacy. Do not share your full resume or personal contact details publicly - use PMs instead.

]]> Career & Education covers job hunting, certifications, degrees, bootcamps, interview prep, salary talk, and professional growth.

Posting Rules:

Be honest about credentials and experience. Fabricating qualifications in advice threads misleads others.
No unsolicited job offers or mass recruiting. If you are hiring, post one clear listing and do not cold-message members.
Salary discussions are encouraged - transparency helps everyone. Sharing your own numbers is fine; demanding others share theirs is not.
No "which is better?" wars without context. CS degree vs bootcamp vs self-taught depends heavily on individual circumstances. Provide nuanced answers.
No paid course spam. You may recommend paid resources but must disclose affiliation.
Protect your privacy. Do not share your full resume or personal contact details publicly - use PMs instead.

]]>