iiinova — where your digital self keeps evolving

taylor desseyn @tdesseyn.bsky.social · 06/10/2026

day at the pool and then grilling bbq chicken. absolute vibe.

000

taylor desseyn @tdesseyn.bsky.social · 05/10/2026

told yall. dm me if you want a muse code.

100

taylor desseyn @tdesseyn.bsky.social · 05/10/2026

the job market is broken and your resume is not the problem. @mpeditto8 says what nobody else will in this one. 10 minutes, worth every second.

taylor desseyn @tdesseyn.bsky.social · 04/10/2026

the biggest lie in job search: that it's a numbers game. i just wrote up the exact system i'd use if i had to start over. resume, linkedin, referrals, all of it.

000

taylor desseyn @tdesseyn.bsky.social · 04/10/2026

cincinnati devs: i'll be at momentum oct 15 talking about how to stop watching your career from the sidelines in the ai era. $30 off your ticket: make a free torc profile, grab the code in the community hub, use it at checkout: platform.torc.dev#/r/8hOWSuH8/cp

000

taylor desseyn @tdesseyn.bsky.social · 04/10/2026

family vacation. aka parenting in just a different location 😂

if a recruiter knows your lane, send a short monthly update. say what you do, the roles you're after, your range, and what changed. then comment thoughtfully on their posts. be easy to remember, not impossible to ignore.

000

spend your job-search budget where it helps before paying for another tool, decide what bottleneck it solves: finding roles, reaching people, or preparing for interviews. try a free option first. keep paying only if you’re actually using it.

000

how to get noticed by recruiters in 7 minutes. aaron harmon breaks down exactly what makes a recruiter stop scrolling. new on youtube.

000

weekend watch: mike peditto breaks down the job market in 8 minutes. worth your coffee break.

000

skillenai.com/data/skill/k...

000

don't spray "kubernetes" into every application. target roles that need it and tell a production incident story: what failed, what you changed in the cluster, and how you knew the fix held.

110

aws appeared in 28,913 skillenai postings over 90 days ending sep 8, up 15% versus the prior four weeks. a cert alone won't tell the story. pick a system you moved or built on aws, then spell out the architecture choice, the tradeoff, and one outcome. use that example in the resume and interview.

000

dude kids are wild. was on a call today and found out my son pooped himself then proceeded to spread that poop all around our car.

131

tomorrow at 9:30am CT, Dan DiGangi joins me on Guidance Counselor 2.0. we're talking about the jump from IC to engineering leadership, building a team, and why mentoring and mental health matter alongside the technical work. Register: luma.com/torcdo-jg75

000

full West Coast vlog: www.youtube.com/watch?v=0tMH...

000

what's the agenda? where are the slides? sometimes the whole point is getting the right people in a room and letting them talk.

100

Share your videos with friends, family, and the world

building the brand vlogs are all in one playlist now. binge the road notes if you want the bts. www.youtube.com/playlist?lis...

youtube.com

building the brand

000

make follow-ups easy to answer if you haven’t heard back, send one brief follow-up. remind them of the role, mention the relevant work you shared, and ask whether the conversation is still worth having. don’t rewrite your whole application in their inbox.

000

got an offer? ask ai to compare the full package with the market. pull three must-say points and practice the counter out loud. don't memorize a script you'll freeze on when the recruiter goes off-script.

000

000

before your next interview, ask ai to play the hiring manager. one question at a time. after each answer, ask what landed, what was fuzzy, and what you actually did. a result without your role in it is just a number.

000

devops appeared in 8,490 skillenai postings over 90 days ending sep 12, up 53% versus the prior four weeks. replace "devops experience" with one release story: the bottleneck, the automation you owned, and how deploy time or rollback risk changed. that's what belongs in the first resume bullet.

take one thing you did this week and share what you learned from it. a short post with a concrete decision or lesson gives people more to respond to than “i’m open to work.”

if you're job hunting and it feels hopeless, watch this first. mike peditto on the job market in 8 minutes.

020

track your interview patterns after every interview, jot down the questions, where you gave a strong example, and where your answer felt vague. if “how do you use ai?” keeps coming up, prepare a specific demonstration rather than a longer explanation.

going live tomorrow morning with peter bell on guidance counselor 2.0. 9:30am ct. bring your questions.

000

checking in with a recruiter twice a week isn't keeping in touch. it's noise. once a month, send a short update on your skills, target role, range, and constraints. stay on their radar without making them dodge your DMs.

000

use niche job boards deliberately pick two boards focused on the work you want. check them on a schedule, save promising roles, and note who you could contact at each company. a smaller, relevant list is easier to act on than hundreds of open tabs.

000

www.youtube.com/watch?v=UD6n...

000

7% of applications come from referrals, but referrals drive 30-50% of hires. the math is yelling at you. spend less time feeding the portal and more time becoming someone people want to vouch for. help 2 people this week before you ask for help.

100

turn a job description into a dm find one requirement you can speak to. write: “i saw you’re looking for help with [specific problem]. i worked on [relevant example]. would you be open to a quick conversation?” edit it until it sounds like you.

000

pick something you built. write five lines: the problem, your role, what you built, a tradeoff you made, and the result. add the link to relevant applications and outreach messages.

ai and machine-learning tech postings on dice grew 101% year over year in august 2026, versus 18% for tech postings overall. "i use ai" is cheap. bring one before-and-after to your next interview: the task, the prompt or system you built, what you checked by hand, and the hours or mistakes it saved.

give an agent your target roles, skills, location, and deal-breakers. have it collect postings and explain why each might fit. review the results yourself before applying. now your search workflow is also something you can discuss in interviews.

000

if interviewers ask how you use ai, don’t just name the tools. bring one example: what you were trying to do, where ai helped, what you checked yourself, and what you changed when it got something wrong.

000

found a role you want? apply, then find the hiring manager or an engineering manager. send a short note about one problem in the job description you’ve solved before. make it easy for them to see why you’re reaching out.

011

just one shotted this video on opus 5.5 extra in claude @dmessing not bad huh? pretty cool overview of the platform offering at @torcdotdev

000

im having ai run my youtube. and its working.

001

a word-for-word counteroffer script sounds great until the call goes off script. and it will. use ai to research comp, pull three talking points, and practice out loud. know what matters. don't memorize a monologue.

sql appeared in 34,908 skillenai postings over 90 days ending sep 13, up 36% versus the prior four weeks. 3,135 were data engineer postings. stop putting "sql" in a skill cloud. show a pipeline you owned: where the data came from, the query or model you changed, and the time or error it saved.

000

new episode: the job market is broken in 8 minutes with mike peditto. what's actually happening in hiring right now and what to do about it.

landed at 9am yesterday. was out taking my son on his favorite activity. the 4 wheeler that evening. i absolutely love travel but being home with the fam is everything.❤️

030

if your interview answer jumps from problem to result, you're skipping the part they need: what YOU did. ask ai to mock interview you, one question at a time. then ask what landed, what was fuzzy, and where you skipped your part.

000