Split (1)

train · 1.04k rows

urn string	text string	type string	firstName string	lastName string	numImpressions int64	numViews int64	numReactions int64	numComments int64	numShares int64	numEngagementRate float64	hashtags string	createdAt (TZ=America/Los_Angeles) string	link string
urn:li:activity:7292228098740101121	Last night, I was working with a mentee at Parsity who just started an internship at a start up. “𝘛𝘩𝘦𝘳𝘦 𝘢𝘳𝘦 𝘴𝘰 𝘮𝘢𝘯𝘺 𝘧𝘪𝘭𝘦𝘴! 𝘏𝘰𝘸 𝘤𝘢𝘯 𝘐 𝘧𝘢𝘮𝘪𝘭𝘪𝘢𝘳𝘪𝘻𝘦 𝘮𝘺𝘴𝘦𝘭𝘧 𝘸𝘪𝘵𝘩 𝘵𝘩𝘪𝘴 𝘤𝘰𝘥𝘦𝘣𝘢𝘴𝘦 𝘣𝘦𝘧𝘰𝘳𝘦 𝘐 𝘴𝘵𝘢𝘳𝘵 𝘸𝘰𝘳𝘬𝘪𝘯𝘨?” Pro-tip: Don’t. Here’s how I approach it: 𝗦𝘁𝗲𝗽 𝟭: 𝗚𝗲𝘁 𝗶𝘁 𝗿𝘂𝗻𝗻𝗶𝗻𝗴 𝗹𝗼𝗰𝗮𝗹𝗹𝘆 - duh 🙄 𝗦𝘁𝗲𝗽 𝟮: 𝗙𝗶𝗻𝗱 𝗮 𝗳𝗼𝗼𝘁𝗵𝗼𝗹𝗱 - identify a core feature/component and try to access it. This could be as simple as navigating to a main page in a web app or a login service in a backend app. 𝗦𝘁𝗲𝗽 𝟯: 𝗕𝗿𝗲𝗮𝗸 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 - update that core component from the previous step by adding a line of code or removing a line. What breaks? Why? 𝗦𝘁𝗲𝗽 𝟰: 𝗙𝗶𝘅 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 - extend the component by adding more data to the API response or changing the color of a button. 𝗦𝘁𝗲𝗽 𝟱: 𝗪𝗿𝗶𝘁𝗲 𝗮 𝘁𝗲𝘀𝘁 - this can be time consuming but will force you to understand the feature you're poking at. At least read a few of the tests to see what the intention of the code is. Lastly - realize that it can take months to feel comfortable in a new codebase. 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝘁𝗵𝗲 𝘁𝗮𝘀𝗸 𝗶𝗻 𝗳𝗿𝗼𝗻𝘁 𝗼𝗳 𝘆𝗼𝘂 𝗮𝗻𝗱 𝗯𝗲 𝗰𝘂𝗿𝗶𝗼𝘂𝘀. Ask why things work the way they do and repeat steps 1 - 5 as needed.	TEXT	Brian	Jenney	3,862	3,862	57	20	0	0.019938	null	2025-02-03 09:11:01	https://www.linkedin.com/feed/update/urn:li:activity:7292228098740101121
urn:li:activity:7291556388982468608	Likes ain't cash or job offers. This is what so many people get wrong about learning in public. I break down 3 reasons you should learn in public, especially if you're trying to break into software and why likes might be the worst metric for you to look at.	ARTICLE	Brian	Jenney	9,330	4,336	48	14	1	0.006752	null	2025-02-01 12:41:53	https://www.linkedin.com/feed/update/urn:li:activity:7291556388982468608
urn:li:activity:7291129678256328704	Hiring is broken and the only winner is LinkedIn. On one side we have candidates spamming job postings with AI. On the other, we have companies filtering out candidates with AI. The result: - 7 round interviews because trust is at an all time low - Interviews that might not be better than flipping a coin (seriously) - Candidate match-making hell So what do we do? The opposite of what most people are doing: - Write online to gain trust and credibility and become discoverable - Traverse your network using BFS to see who’s hiring - Go to main street before wall street - small businesses are the backbone of the US economy and many aren’t on LinkedIn	TEXT	Brian	Jenney	13,131	13,131	72	8	1	0.006169	null	2025-01-31 08:26:17	https://www.linkedin.com/feed/update/urn:li:activity:7291129678256328704
urn:li:activity:7290048599890006016	Here is what I learned after spending 12 months sitting between the 2 best developers in my company: - Clean up the code even if you didn’t write it. - Code isn’t magic. Figure out why things work the way they do. - It’s ok to say “𝘐 𝘥𝘰𝘯’𝘵 𝘬𝘯𝘰𝘸…. 𝙮𝙚𝙩”. - Running towards critical issues is good for your career and your knowledge. - Deleting lots of code > adding lots of code. You know that cliche phrase “𝘺𝘰𝘶 𝘢𝘳𝘦 𝘵𝘩𝘦 𝘢𝘷𝘦𝘳𝘢𝘨𝘦 𝘰𝘧 𝘵𝘩𝘦 5 𝘱𝘦𝘰𝘱𝘭𝘦 𝘺𝘰𝘶 𝘩𝘢𝘯𝘨 𝘢𝘳𝘰𝘶𝘯𝘥 𝘵𝘩𝘦 𝘮𝘰𝘴𝘵”? Same thing can be applied to coding.	TEXT	Brian	Jenney	12,866	12,805	123	16	2	0.010959	null	2025-01-28 08:50:28	https://www.linkedin.com/feed/update/urn:li:activity:7290048599890006016
urn:li:activity:7289665189572919296	At first people laughed. Now, I'm more convinced this is true. As ChatGPT keeps eating search engines, expectations will change. Users increasingly want intuitive ways to navigate a site and it's data. 𝗣𝗿𝗲𝗱𝗶𝗰𝘁𝗶𝗼𝗻: even more pressure falls on full-stack and FE devs to integrate AI into existing products. Things are moving fast and I think they will get even faster. - At work I'm using Typescript, Vercel and NextJS to build an AI product. - After work I'm learning the basics of linear algebra to understand vectors and matrices. I know it's fun to freak out about AI coming for your job. I think it's even more fun to learn the basics and build cool stuff.	IMAGE	Brian	Jenney	20,577	20,514	159	17	6	0.008845	null	2025-01-27 07:26:56	https://www.linkedin.com/feed/update/urn:li:activity:7289665189572919296
urn:li:activity:7288656541124108288	Worst way to spend your weekend? Completing a take home coding project that was supposed to take 4 hours but really takes 2 full days. I know some people like this interview format. I am not one of them. If you MUST participate in these kinds of interviews there are 2 ways you can stand out: 1. Write documentation 2. Write some unit tests You don’t know how to write unit tests? Let’s fix that. Grab this repo and make it get to 100% coverage to learn the basics of unit testing .... it's in comments ;)	TEXT	Brian	Jenney	28,016	27,999	105	33	2	0.004997	null	2025-01-24 12:38:56	https://www.linkedin.com/feed/update/urn:li:activity:7288656541124108288
urn:li:activity:7287506406377693184	I didn’t take my own advice and nearly bombed the interview. I’m such a hypocrite 😬. I passed the technical portion of the interview and was feeling pretty damn good. Then I got hit with a question I’ve told you to prepare for 100 times over. “𝘛𝘦𝘭𝘭 𝘮𝘦 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘦 𝘮𝘰𝘴𝘵 𝘵𝘦𝘤𝘩𝘯𝘪𝘤𝘢𝘭𝘭𝘺 𝘤𝘰𝘮𝘱𝘭𝘦𝘹 𝘱𝘳𝘰𝘫𝘦𝘤𝘵 𝘺𝘰𝘶’𝘷𝘦 𝘸𝘰𝘳𝘬𝘦𝘥 𝘰𝘯 𝘳𝘦𝘤𝘦𝘯𝘵𝘭𝘺” It was like my brain stopped working. Should I talk about something front-end? Back-end? Something I architected? I just froze and went with a story about a component library, which honestly, wasn’t super interesting. After this experience I literally wrote down a group of stories I can use for any upcoming interview. - 1 story for leading team against a deadline. - 1 story about a difficult bug. - 1 story about a complex feature or project. - 1 story about failure and what I learned. I’m curious, what's a good, non-tech interview question have you been asked over the years?	TEXT	Brian	Jenney	66,667	66,637	63	18	0	0.001215	null	2025-01-21 08:28:42	https://www.linkedin.com/feed/update/urn:li:activity:7287506406377693184
urn:li:activity:7287155546833534976	One thing I'm genuinely curious about when it comes to the conversation about AI replacing junior and mid-level devs - who will replace the senior devs? More AI? And who will maintain the AI? Fix critical issues? Review it's code? More AI? 🤔 Why are we scaring off our talent pipeline with speculation and hype?	TEXT	Brian	Jenney	2,985	2,985	32	9	1	0.01407	null	2025-01-20 09:14:31	https://www.linkedin.com/feed/update/urn:li:activity:7287155546833534976
urn:li:activity:7287153228956286976	I’ve spoken with about 700 developers in the last 12 months. I won’t be doing many more 15 minute chats in the foreseeable future. But the truth is, most beginners ask the same 3 questions: 𝘞𝘩𝘢𝘵’𝘴 𝘸𝘳𝘰𝘯𝘨 𝘸𝘪𝘵𝘩 𝘮𝘺 𝘳𝘦𝘴𝘶𝘮𝘦? 𝘞𝘩𝘢𝘵 𝘴𝘩𝘰𝘶𝘭𝘥 𝘐 𝘣𝘶𝘪𝘭𝘥 𝘧𝘰𝘳 𝘢 𝘴𝘪𝘥𝘦 𝘱𝘳𝘰𝘫𝘦𝘤𝘵? 𝘏𝘰𝘸 𝘥𝘰 𝘐 𝘨𝘦𝘵 𝘩𝘪𝘳𝘦𝘥? So I want to answer them for free: 𝗬𝗼𝘂𝗿 𝗿𝗲𝘀𝘂𝗺𝗲 𝗶𝘀 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗮𝗻𝗱 𝘀𝗼𝘂𝗻𝗱𝘀 𝗹𝗶𝗸𝗲 𝗺𝗮𝗻𝘆 𝗼𝘁𝗵𝗲𝗿𝘀. Remove any mention of junior or aspiring and use this framework: did [x] using [y] which led to [z]. Think from the recruiter’s perspective. Do you sound like a risk to hire? Make yourself less risky and don’t tell them everything. Why do they need to know your last job was at a french fry shop? Lead with your developer experience or technical projects. 𝗦𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘀𝗵𝗼𝘂𝗹𝗱 𝘁𝗲𝗮𝗰𝗵 𝘆𝗼𝘂 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗻𝗲𝘄 𝗼𝗿 𝗸𝗲𝗲𝗽 𝘆𝗼𝘂𝗿 𝘀𝗸𝗶𝗹𝗹𝘀 𝘀𝗵𝗮𝗿𝗽 𝗶𝗳 𝘆𝗼𝘂’𝗿𝗲 𝗻𝗼𝘁 𝘄𝗼𝗿𝗸𝗶𝗻𝗴. Really, they should be enjoyable. They’re an alternative to grinding away at toy problems and expose you to challenges which you can give yourself. Want to understand how to implement role-based authentication or get your hands dirty with serverless? Build it out. Also follow John Crickett, he has a ton of cool projects to make. 𝗡𝗼𝘄 𝗵𝗲𝗿𝗲’𝘀 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝗽𝗮𝗿𝘁 𝗮𝗻𝗱 𝘁𝗵𝗲 𝘁𝗿𝘂𝘁𝗵 𝗻𝗼 𝗼𝗻𝗲 𝘄𝗮𝗻𝘁𝘀 𝘁𝗼 𝗵𝗲𝗮𝗿: getting hired is a game of skill and luck. If there is one trait that I see in successful Parsity grads, it is their consistency. They just didn’t stop. They outlasted their fears, insecurities and the fear mongers. They changed what didn’t work and picked a strategy. Mass apply or network or do both. Then don’t stop.	TEXT	Brian	Jenney	100,705	100,636	170	14	7	0.001897	null	2025-01-20 09:05:18	https://www.linkedin.com/feed/update/urn:li:activity:7287153228956286976
urn:li:activity:7286059819348738050	How old is too old to learn to code and change careers? According to the internet - it’s 40. Imagine if Dicky Kitchen Jr had listened to those geniuses. I met Dicky a couple years ago through Instagram. He had good, practical content and was building cool sh*t. His journey from working in physical therapy to software engineer wasn’t short or straightforward. But it did work. If you’re serious about making a career switch into software then Dicky has a path you might find useful. 𝗟𝗶𝗻𝗸 𝘁𝗼 𝗼𝘂𝗿 𝗽𝗼𝗱 𝗶𝗻 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀 (cuz LinkedIn hates links 😅)	TEXT	Brian	Jenney	9,714	9,714	65	22	1	0.009059	null	2025-01-17 08:40:29	https://www.linkedin.com/feed/update/urn:li:activity:7286059819348738050
urn:li:activity:7285679838349156352	❌ Get a job you love and you’ll never work a day in your life. Look, I love to write code and mentor people. It's why I work as a developer and teach others at Parsity. But there’s so much more to software development than writing code and pair-programming. Some of the non-sexy stuff you’ll do as a developer: - meetings - meetings to prepare for other meetings - on-call shifts - writing documentation - debugging code you never touched - maintaining legacy code - reviewing pull requests with > 1000 lines changed - researching poorly documented 3rd party APIs - translating technical limitations to non-coders Coding is my hobby and profession. It’s a job and I 𝘁𝗿𝘆 not to wrap too much of my identity into it. It can be incredibly fulfilling and it can also be a chore.	TEXT	Brian	Jenney	5,361	5,361	63	12	0	0.01399	null	2025-01-16 07:30:34	https://www.linkedin.com/feed/update/urn:li:activity:7285679838349156352
urn:li:activity:7284615671479492608	The dirty secret about coding interviews: No one knows what the hell they’re doing. We all think we have THE way to find the right candidates. I’ve spoken with many of you who are devastated after failing an interview. You believe this is a signal that you are not talented and lack fundamental skills. It may be true. It also could be that your interviewer is not equipped to determine your ability. Perhaps they are biased from their own experience and ONLY looking for solutions which they are familiar with and understand. Maybe they don’t know closures very well or how to explain promises to a 5 year old either. Maybe they’re just having a bad day… 🥲. There is less formal training for interviews than you might imagine. Especially at non-tech companies and startups. Lord knows I’ve failed more than my fair share of interviews. It hurts. I also know it’s a winnable game. Learn from the loss and keep playing.	TEXT	Brian	Jenney	38,048	38,048	114	20	1	0.003548	null	2025-01-13 09:01:57	https://www.linkedin.com/feed/update/urn:li:activity:7284615671479492608
urn:li:activity:7283549792947916801	Solving problems is tough. Solving them without a strategy is tougher. The pattern I share in this article isn't a silver bullet but it's how I approach most coding problems from interviews to my daily work. Hope you find it useful.	ARTICLE	Brian	Jenney	10,851	5,416	79	11	1	0.008386	null	2025-01-10 10:26:32	https://www.linkedin.com/feed/update/urn:li:activity:7283549792947916801
urn:li:activity:7283218924760932352	Well this is it, I’m getting fired. The engineering manager and I were sitting in a small room, frantically trying to fix a program I had released to production that was breaking spectacularly. The code was on a large monitor for us investigate. “What is this code supposed to do?” he asked. I froze. That code had been lifted directly from Stack Overflow and I could not explain it. “If you don’t know what this is supposed to do, it shouldn’t be in this program” he said. Plot twist: I didn’t get fired that day though I wouldn’t have blamed him. I can still feel the embarrassment 9 years later. Don’t make the same mistake I did. With Chat-Gippity, it’s even easier to become a copy-paste developer than it used to be. I’m not saying you should NEVER lift code from another source but for the love of Bob, at least understand what it does so you can avoid my fate.	TEXT	Brian	Jenney	62,335	62,247	400	31	7	0.007027	null	2025-01-09 12:31:47	https://www.linkedin.com/feed/update/urn:li:activity:7283218924760932352
urn:li:activity:7282444807354904576	A look back at software engineering in 2024 (according to social media): - First, Chat Gippity took your job. - Next, Devin AI made programming obsolete. - Applications to McDonald's skyrocketed. Mostly CS grads. - All hiring stopped in software. A total of 0 positions opened up. Reality was more boring: - Hiring creeped up. - The Devin team hired devs made of flesh. - Too many JS libraries were produced. - 100% of companies talked about AI. Just 6.1% of businesses are using AI to produce their products or services (according to Goldman Sachs). The big takeaway here: Stop planning your career based on click bait.	TEXT	Brian	Jenney	32,431	32,388	242	12	4	0.007955	null	2025-01-07 09:15:43	https://www.linkedin.com/feed/update/urn:li:activity:7282444807354904576
urn:li:activity:7282059903991508994	Well, this is awkward. As some of you know, I own an online coding school, Parsity. I firmly believe that mentorship is a tried and true way to get into tech. It's a path I used myself. I also know it's not the ONLY path. Recently I sat down with 2 self taught developers, Wilfredo Diaz and Vanessa Vun who break down how they made a successful transition into tech without a CS degree or bootcamp. You can check it out here:	ARTICLE	Brian	Jenney	3,707	3,707	39	1	2	0.01133	null	2025-01-06 07:46:15	https://www.linkedin.com/feed/update/urn:li:activity:7282059903991508994
urn:li:activity:7281022611940089856	I lured Alex Lau with a box of donuts into coming on my podcast. What are some spicy questions I should ask him about coding careers in 2025?	SHARE	Brian	Jenney	1,073	1,073	13	1	0	0.013048	null	2025-01-03 11:04:25	https://www.linkedin.com/feed/update/urn:li:activity:7281022611940089856
urn:li:activity:7280984712091766784	How does it feel to be the worst developer on a team? I had the unpleasant experience of holding this title when I worked at a small startup. I had more technical growth in the short time I was there than at any other company I’ve worked since. You’ve probably heard the advice “𝘐𝘧 𝘺𝘰𝘶’𝘳𝘦 𝘵𝘩𝘦 𝘴𝘮𝘢𝘳𝘵𝘦𝘴𝘵 𝘱𝘦𝘳𝘴𝘰𝘯 𝘪𝘯 𝘵𝘩𝘦 𝘳𝘰𝘰𝘮, 𝘪𝘵’𝘴 𝘵𝘪𝘮𝘦 𝘵𝘰 𝘭𝘦𝘢𝘷𝘦 𝘵𝘩𝘦 𝘳𝘰𝘰𝘮.” Easier said than done. The guilt and anxiety I felt on a daily basis was difficult to deal with. I was confronted with my own limitations and the realization that 𝘁𝗵𝗶𝘀 𝘄𝗮𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗮𝗹𝗹 𝗶𝗻 𝗺𝘆 𝗵𝗲𝗮𝗱. I could barely keep up with the tasks I was assigned and relied on lots of pairing sessions to get my work done. I could either quit or at least attempt to keep up with the other devs and contribute to the best of my ability. I made a resolution to suck less. - I asked the smarty-pants devs what books they suggested I read - I audited my Javascript knowledge and wrote out what I knew I had to learn to contribute to discussions - enrolled in a course to learn DSA and comp sci fundamentals - someone made a joke about Djikstra… who the hell is that? I would find out I never became the 2nd worst developer at this company, but I grew my technical skills, confidence and threshold for failure. As uncomfortable as it was, I know see just how pivotal this experience was. So if you’re just starting out, or maybe on a new team and discovering just how little you know…good. Embrace the suck, expose your ignorance and be prepared to learn.	TEXT	Brian	Jenney	171,989	171,802	342	24	3	0.002145	null	2025-01-03 08:33:49	https://www.linkedin.com/feed/update/urn:li:activity:7280984712091766784
urn:li:activity:7280654922797211648	Most developers would benefit more from reading “How to Win Friends and Influence People” than “Cracking the Coding Interview”. Here's the thing: Technical skills can get your foot in the door. Soft skills open up the rest of the house. Knowing how to navigate human dynamics, to empathize and connect, articulate your thoughts and influence others – these are the tools that build careers better than learning another programming language. Also - read The Phoenix Project or Alex Lau's "Keep Calm and Code On" if you’re looking for some non-dry coding knowledge that you didn’t get in college 😉.	TEXT	Brian	Jenney	9,962	9,959	82	17	3	0.010239	null	2025-01-02 10:43:21	https://www.linkedin.com/feed/update/urn:li:activity:7280654922797211648
urn:li:activity:7279934062356508673	I don't like that this is true but it is: 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝗶𝗻𝗴 𝗶𝘀 𝘁𝗵𝗲 𝗵𝗶𝗴𝗵𝗲𝘀𝘁 𝗽𝗮𝘆𝗶𝗻𝗴 𝘀𝗸𝗶𝗹𝗹. When I realized this, I really sucked at interviews. - my nerves would get to me (I had a literal panic attack during 1 interview) - I thought LeetCode was the solution to nailing the coding challenge - my solutions didn't follow any pattern or structure As a mostly self-taught developer, I didn't know what I didn't know. I went on to spend thousands of dollars and hundreds of hours understanding how to beat the interview game. Here's what was most effective: - practicing with a human - learning the patterns which make up the majority of coding interview problems - filming myself working through problems Good luck playing the game in 2025!	UNKNOWN	Brian	Jenney	8,445	8,445	81	21	3	0.012433	null	2024-12-31 10:58:55	https://www.linkedin.com/feed/update/urn:li:activity:7279934062356508673
urn:li:activity:7279548506367737856	10 years of workout and diet advice in 2 minutes: - shave your body hair to look 5 pounds thinner - forget fad diets - track your calories - buy a small scale and weigh your food - that cup of rice was never a cup amigo - lift until failure instead of counting reps - there are 3500 calories in a pound - shirtless pics reflect your progress better than the number on the scale - weigh yourself every morning - never at night - you didn’t really gain 5 pounds - that’s water weight - if you’re a dude - train your legs - if you’re not a dude - train something besides your legs - it’s easier to adjust your calories than add cardio - everyone in the gym is too busy looking at themselves to care about you - always do incline bench - sleep, nutrition and walking are your secret weapons - you can’t beat genetics - your calorie maintenance and muscle growth potential will be different than your friend’s - wait 2 weeks before adding or decreasing calories because your weight fluctuates - listen to your body - don’t beat it up and don’t be too easy on it - it’s not a “diet” - it’s just a different way to eat - looking good shirtless is over rated - you’re almost always wearing a shirt - if it’s not fun, you’re not doing it right	TEXT	Brian	Jenney	9,328	9,328	70	18	1	0.009541	null	2024-12-30 09:26:51	https://www.linkedin.com/feed/update/urn:li:activity:7279548506367737856
urn:li:activity:7278478121337561088	I’ve been writing online for a long time. I’m making more video content going forward and I’m not looking to make money from YT. What the hell kind of content do early career coders need to watch? What’s most useful? What would’ve helped you at step 0?	TEXT	Brian	Jenney	2,964	2,964	20	25	0	0.015182	null	2024-12-27 10:33:31	https://www.linkedin.com/feed/update/urn:li:activity:7278478121337561088
urn:li:activity:7277364583026081792	I once worked at a coding bootcamp where a student didn't know how to open their file explorer. I wondered how in the hell they were supposed to keep up with the other students who had CS degrees or worked in QA as we powered through the curriculum. The answer is obvious: they didn't. Zubin Pratap and I were discussing the future of coding bootcamps recently. We're both career changers who got into tech in our 30's from very different walks of life. We're opinionated. We've seen what works and what absolutely will not. It's why we're partnering to create an individualized coaching and instruction program with a VERY tiny numbers of people ... for a long time. It won't be scalable. It won't be easy. It will be highly effective.	UNKNOWN	Brian	Jenney	175,025	175,025	145	51	2	0.001131	null	2024-12-24 08:48:43	https://www.linkedin.com/feed/update/urn:li:activity:7277364583026081792
urn:li:activity:7275551421146558464	10 years of coding advice in 60 seconds: - use a debugger - you can’t cheat time in the saddle - get used to making mistakes - interviewing is the highest paying skill - it’s easier to switch jobs than get a large raise - do stuff that makes you nervous - build something outside work to keep your skills relevant - other people in the meeting are afraid to ask the dumb question you are afraid to ask - write tests - keep a brag document or you won’t remember what you did all year - leave the code better than you found it - never make people feel dumb - it’s bad for your career and your soul - if arguing about coding languages online worked - no one would be using JavaScript - marketing, design, sales, product and legal are just as important as your tech team - in many cases - much more important - understand if your team is a cost or profit center before the market turns - the closer you are to the data, the harder you will be to replace - there’s a lot of smart assholes out there - don’t be one - a walk outside solved more bugs than staring at a screen - be careful who’s advice you take 😉	TEXT	Brian	Jenney	589,279	589,279	5,110	369	356	0.009902	null	2024-12-19 08:43:51	https://www.linkedin.com/feed/update/urn:li:activity:7275551421146558464
urn:li:activity:7274808667479191552	Ok maybe I was wrong about unit testing. I took a team from 0 - 40% test coverage when I first joined a few years ago. It was an arbitrary threshold. The most recent project I'm working on has no threshold or many tests but it’s objectively more complex. It’s also more stable than the previous project with higher coverage. I’m not saying tests have no place. I still write them but only when: - I cannot easily reproduce the functionality I want to test - I am refactoring something and I want to make sure it didn’t break - The code is on a critical path and I want to make sure I haven’t missed an edge case I know some of you hate tests or have never written one. What have tests ever done to you? Install Jest or Vitest or Playwright and write your first test. It won’t hurt too much. [𝘷𝘪𝘥𝘦𝘰 𝘪𝘯 𝘤𝘰𝘮𝘮𝘦𝘯𝘵𝘴 𝘵𝘰 𝘭𝘦𝘢𝘳𝘯 𝘩𝘰𝘸 𝘵𝘰 𝘸𝘳𝘪𝘵𝘦 𝘺𝘰𝘶𝘳 𝘧𝘪𝘳𝘴𝘵 𝘵𝘦𝘴𝘵]	TEXT	Brian	Jenney	29,105	29,105	61	32	1	0.00323	null	2024-12-17 07:32:25	https://www.linkedin.com/feed/update/urn:li:activity:7274808667479191552
urn:li:activity:7274441682450812928	99% of the interview advice you read ONLY applies to the top 1% of tech companies. A few mentees at Parsity have interviews coming up. None of them involve traversing a tree or linked lists. 𝗛𝗲𝗿𝗲’𝘀 𝟰 𝘁𝘆𝗽𝗲𝘀 𝗼𝗳 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗜 𝘀𝗲𝗲 𝗼𝘃𝗲𝗿-𝗿𝗲𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗲𝗱 𝗳𝗼𝗿 𝘄𝗲𝗯 𝗱𝗲𝘃 𝗿𝗼𝗹𝗲𝘀: - build a React component that fetches data - JS trivia including closure, 𝚕𝚎𝚝 vs 𝚌𝚘𝚗𝚜𝚝, event loop and 𝚝𝚑𝚒𝚜 - take home assignment that’s supposed to take 2 hours but is really a full day 😅 (𝘩𝘪𝘯𝘵: 𝘸𝘳𝘪𝘵𝘦 𝘢 𝘶𝘯𝘪𝘵 𝘵𝘦𝘴𝘵 𝘢𝘯𝘥 𝘢𝘥𝘥 𝘥𝘰𝘤𝘴) - coding challenges using 2 pointers, sliding window and array manipulation I’ve met developers who accepted offers after no technical screening at all! This has happened to me twice. While you’re pounding LeetCode, don’t forget to have some answers in your back pocket for questions like “tell me about yourself?” or “why do you want to work here?” Good luck out there.	TEXT	Brian	Jenney	32,876	32,876	117	17	4	0.004198	null	2024-12-16 07:14:09	https://www.linkedin.com/feed/update/urn:li:activity:7274441682450812928
urn:li:activity:7273795622766292993	Not gonna lie - this tweet hit a little close to home 😅	VIDEO	Brian	Jenney	19,946	7,619	175	24	1	0.010027	null	2024-12-14 12:26:57	https://www.linkedin.com/feed/update/urn:li:activity:7273795622766292993
urn:li:activity:7273379583805034496	The best interview prep is free, apparently. A couple nights ago, some mentees at Parsity and I tackled day 1 of Advent of Code. AoC is 31 days of coding challenges based on the trials and tribulations of a group of elves. These little knuckle heads get themselves in all sorts of issues that can only be solved with recursion, sliding windows, graphs and a dash of Chat-Gippity (just a sprinkle). What makes AoC unique and more similar to an interview setting is that you have to sift through a lot of information to get to the meat of the problem. Each year I start off strong and taper off around day 10. If you're on the AoC grind - what's the most fun problem you've seen so far?	IMAGE	Brian	Jenney	4,817	4,817	42	2	2	0.00955	null	2024-12-13 08:53:45	https://www.linkedin.com/feed/update/urn:li:activity:7273379583805034496
urn:li:activity:7266496348646981632	There is a valuable skill that will set you apart from most developers. It will go from a nice-to-have to a requirement if you want to move into leadership: 𝗣𝘂𝗯𝗹𝗶𝗰 𝘀𝗽𝗲𝗮𝗸𝗶𝗻𝗴. If you’re like me, maybe you think you can just hide in your code hole and never speak. I tried this method for a few years and it sorta worked. I didn’t get fired. I also couldn’t get promoted or make much of an impact. Geoffrey Huck knows the struggle. He went from shy nerd to prolific public speaker who now coaches CEOs and software developers on the art of communication. If you want to learn some practical ways to increase your visibility and improve your communication skills then I hope you'll join us for this free event 😉.	VIDEO	Brian	Jenney	2,540	614	41	30	6	0.030315	null	2024-12-12 16:05:10	https://www.linkedin.com/feed/update/urn:li:activity:7266496348646981632
urn:li:activity:7273015070853345281	Nearly a decade ago I started my first day as a developer. The night before the first day, I was barely able to sleep. - Would I be found out as a fake developer and fired immediately? - Would they give me a task I couldn’t figure out? - How long before they realized they made an error in their hiring process? Well, I never got “found out” and took on more than a few tasks I couldn’t figure out… yet. If you recently started a new position or are about to, you may be feeling a lot of the same emotions. Here are some ways I get over my anxiety: - make a 30/60/90 day plan which usually includes delivering a small feature - immediately explore the codebase and identify areas I just don’t understand - ask a bunch of questions while I’m still new enough that no one will judge me - realize I’m here to do more learning than coding in my first month So if you just got hired, congrats! I also know it can be just as stressful as the interview process. Perhaps moreso. What’s your tips for people just starting a new dev position?	ARTICLE	Brian	Jenney	3,963	3,963	44	6	0	0.012617	null	2024-12-12 08:45:18	https://www.linkedin.com/feed/update/urn:li:activity:7273015070853345281
urn:li:activity:7272623260884692992	Maybe you think you can just hide in your code hole and never speak. I tried this method for a few years and it sorta worked. - I didn’t get fired. - I also couldn’t get promoted or make much of an impact. As an engineering manager, my job was a lot of coding but it also involved a lot of speaking. To get over my fear I did a few things: - Write down questions to ask during meetings - Volunteer for a lunch and learn - Explain my code over a video using Loom (I made so many videos I’ve never shared) - Make a commitment to be the first to break the silence in a meeting - even with a dumb question (see #1) You’re probably your worst critic. We’re all much too wrapped up in ourselves to remember the dumb thing you said in that meeting last Tuesday. Tomorrow, I'll be speaking with Geoffrey Huck about how shy developers can overcome their fear of speaking and practical ways to be an effective communicator.	SHARE	Brian	Jenney	1,896	1,896	25	4	0	0.015295	null	2024-12-11 06:48:24	https://www.linkedin.com/feed/update/urn:li:activity:7272623260884692992
urn:li:activity:7272297762203791360	If I was a recent bootcamp grad, frustrated with the job market or just wanting to take a faster path towards that first role, here’s what I’d do: 1. Go back in time, enroll in Parsity and take advantage of our amazing career services. 2. Enroll in David Roberts VIP course for job seekers. 2 is probably easier than 1... for now. I’m not sponsored by David, but I find myself recommending him at least once a week to people who call me and want advice on landing their first role.	TEXT	Brian	Jenney	8,686	8,686	49	12	3	0.007368	null	2024-12-10 09:14:59	https://www.linkedin.com/feed/update/urn:li:activity:7272297762203791360
urn:li:activity:7269368598647705600	❌ You will be replaced by AI. ❌ You will be replaced by someone using AI to do your job. ✅ You will be replaced by someone who doesn’t need to use AI but is using it to do your job.	TEXT	Brian	Jenney	5,475	5,475	44	10	2	0.010228	null	2024-12-02 07:15:32	https://www.linkedin.com/feed/update/urn:li:activity:7269368598647705600
urn:li:activity:7268315169208860672	I've spent thousands of dollars on courses, books and mentorship over the last 10 years. Here are some of the best investments I've made in no particular order: - Kyle Simpson YDKJS book series - particularly his book on FP - CodeCrafters.io (YC S22) - I don't want to watch a tutorial at this stage. I just want to build cool sh*t - Educative - specifically the Grokking the Interview Course which teaches you patterns to solve interview problems - AlgoExpert - finally some front end interview material for those of us outside FAANG - Justin Welsh LinkedIn Operating System - I wrote for years and finally got some traction after using his advice and tactics - Colte Steele's Udemy course on DSA for JS developers 🧑‍🍳😘 Hope that's helpful as you navigate the Black Friday course-stravaganza out there 😉	TEXT	Brian	Jenney	31,656	31,656	122	18	8	0.004675	null	2024-11-29 09:29:35	https://www.linkedin.com/feed/update/urn:li:activity:7268315169208860672
urn:li:activity:7267570612766728192	69 minutes and 132 wtfs later I finally got a Lambda deployed on AWS via GitHub actions. The final result is a 7 minute video for students at Parsity and members at JavascriptProsApp[dot]com to enjoy. When you see those polished 100 hour tutorials where the speaker is just getting things to work on the "first try" - best believe there were no less than 420 wtf moments they just cut out. The unfortunate part is that this is where the real learning occurs. That's why I always recommend you break, re-write and extend the code you're "borrowing" to get yourself into some wtf moments on purpose. If you recently worked with AWS and Lambdas, what were some wtf moments you experienced?	IMAGE	Brian	Jenney	3,877	3,877	57	6	1	0.016508	null	2024-11-27 08:10:58	https://www.linkedin.com/feed/update/urn:li:activity:7267570612766728192
urn:li:activity:7267219349432606720	You don’t need to contribute a single line of code to open source to benefit from it: 𝗦𝘁𝗲𝗽 𝟭 - find a library you actually use and like 𝗦𝘁𝗲𝗽 𝟮 - get it running on your machine 𝗦𝘁𝗲𝗽 𝟯 - break, extend or re-write a feature E͟x͟a͟m͟p͟l͟e͟: Clone everyone’s favorite state management library, ReduxJS, and yarn-link it to your React project. Add a debugger somewhere in the code and try to trigger it. Poke around and try to change some functionality. Now you’ve learned a hell of a lot more than fixing a typo in a README and set yourself up nicely IF you want to make some contributions in the future.	TEXT	Brian	Jenney	11,994	11,994	104	7	3	0.009505	null	2024-11-26 08:55:11	https://www.linkedin.com/feed/update/urn:li:activity:7267219349432606720
urn:li:activity:7266834160609046529	Very predictable, boring advice that most developers don’t follow: - 𝗗𝗼𝗻’𝘁 𝗼𝘃𝗲𝗿-𝗿𝗲𝗹𝘆 𝗼𝗻 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹𝘀 - build something on your own, get stuck and learn - 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀 before diving into frameworks like React, Angular or Vue - 𝗞𝗲𝗲𝗽 𝘁𝗿𝗮𝗰𝗸 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗮𝗰𝗰𝗼𝗺𝗽𝗹𝗶𝘀𝗵𝗺𝗲𝗻𝘁𝘀. It’s nice to look back at your progress when you’re feeling down - 𝗬𝗼𝘂 𝗰𝗮𝗻’𝘁 𝗰𝗵𝗮𝘀𝗲 𝗲𝘃𝗲𝗿𝘆 𝗻𝗲𝘄 𝘁𝗲𝗰𝗵. Be aware of macro trends in your industry and micro trends in your niche. For example a JS developer may need to have some surface level knowledge of Serverless and a deeper understanding of NextJS - 𝗦𝘁𝘂𝗱𝘆 𝗖𝗦 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀. They’re slower to change and give you a strong foundation to understanding concepts outside your core language and tech stack - 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝘆𝗼𝘂𝗿 𝗵𝗲𝗮𝗹𝘁𝗵 as much as your work. What’d I miss?	TEXT	Brian	Jenney	10,814	10,814	93	24	2	0.011004	null	2024-11-25 07:24:35	https://www.linkedin.com/feed/update/urn:li:activity:7266834160609046529
urn:li:activity:7265767158758985729	Diving into an unfamiliar codebase can be scary. As a new developer, I was intimidated by just how many files, services and docs were associated with an app. Some mentees at Parsity have started new positions and are having a similar experience. Here’s how we navigate a new codebase: - Get it working locally - 𝗟𝗼𝗼𝗸 𝗳𝗼𝗿 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 - for a UI app, how is the business logic handled as opposed to presentational logic? - 𝗣𝗶𝗰𝗸 𝗮 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗮𝗻𝗱 𝗯𝗿𝗲𝗮𝗸 𝗶𝘁 - expand the API response or trigger an auth error. Update a route to go to a page you just created - 𝗨𝗽𝗱𝗮𝘁𝗲 𝗮 𝘁𝗲𝘀𝘁 - pick a part of the codebase that could use more testing and write a test - 𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗳* 𝗱𝗼𝗰𝘀 Oh - they don’t exist? - Write the f* docs! Anything you’d add?	TEXT	Brian	Jenney	2,732	2,732	32	9	0	0.015007	null	2024-11-22 08:44:42	https://www.linkedin.com/feed/update/urn:li:activity:7265767158758985729
urn:li:activity:7264660761388449794	The recipe for an amazing side project when you don’t know what to do: 1. Pick an API - OpenAI, Binance, RapidAPI are the first places I’d check. 2. Ideate - what are the features of this API you can build something around? Perhaps a stock tracker that integrates with OpenAI to give targeted trading advice. 3. MUP - what is required to build the minimally usable product? Pick 1 or 2 core features 4. Sketch - a white piece of paper and pen will do. Draw out the main features of the app. Ask “and then what?” For example, they visit your site, and then what? They click on a button and then “what”? 5. Pick 1 or 2 new technologies you want to learn and use them. Maybe this is your chance to learn TypeScript or Cobol. Whatevs. 6. Deploy it and buy a domain on Route53 (or whatever) for like 15 bucks. It will look pro. Get frustrated. Pull out your hair (I don’t have this problem). Learn more than any tutorial can teach you.	TEXT	Brian	Jenney	8,530	8,530	103	10	2	0.013482	null	2024-11-19 07:28:16	https://www.linkedin.com/feed/update/urn:li:activity:7264660761388449794
urn:li:activity:7264336443458629632	I’ve spoken with about 643 developers in the last 18 months. Most beginners ask the same 3 questions: - What’s wrong with my resume? - What should I build for a side project? - How do I get hired? So I want to answer them for free: 1. 𝗬𝗼𝘂𝗿 𝗿𝗲𝘀𝘂𝗺𝗲 𝗶𝘀 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗮𝗻𝗱 𝘀𝗼𝘂𝗻𝗱𝘀 𝗹𝗶𝗸𝗲 𝗺𝗮𝗻𝘆 𝗼𝘁𝗵𝗲𝗿𝘀. Remove any mention of junior or aspiring and use this framework: did [x] using [y] which led to [z]. Think from the recruiter’s perspective. Do you sound like a risk to hire? Make yourself less risky and don’t tell them everything. Why do they need to know your last job was at a french fry shop? Lead with your developer experience or technical projects. 2. 𝗦𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘀𝗵𝗼𝘂𝗹𝗱 𝘁𝗲𝗮𝗰𝗵 𝘆𝗼𝘂 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗻𝗲𝘄 or keep your skills sharp if you’re not working. Really, they should be enjoyable. They’re an alternative to grinding away at toy problems and expose you to challenges which you can give yourself. Want to understand how to implement role-based authentication or get your hands dirty with serverless? Build it out. Also follow John Crickett or CodeCrafters.io (YC S22) if you're stuck on what to build. 3. Now here’s the hard part and the truth no one wants to hear: 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗵𝗶𝗿𝗲𝗱 𝗶𝘀 𝗮 𝗴𝗮𝗺𝗲 𝗼𝗳 𝘀𝗸𝗶𝗹𝗹 𝗮𝗻𝗱 𝗹𝘂𝗰𝗸. If there is one trait that I see in successful grads, it is their consistency. They just didn’t stop. They outlasted their fears, insecurities and the fear mongers. They changed what didn’t work and picked a strategy. Mass apply or network or do both. Then don’t stop.	TEXT	Brian	Jenney	23,129	23,129	128	17	7	0.006572	null	2024-11-18 09:59:32	https://www.linkedin.com/feed/update/urn:li:activity:7264336443458629632
urn:li:activity:7262864954087628801	I've had 15 minute chats with 600 developers in the last 2 years. Here are 3 (and a half) mistakes I see way too often when it comes to learning to code.	ARTICLE	Brian	Jenney	5,200	4,132	48	6	1	0.010577	null	2024-11-14 08:32:22	https://www.linkedin.com/feed/update/urn:li:activity:7262864954087628801
urn:li:activity:7262516939732713472	My mom got turned down for a job at Starbucks as a barista. She’s retired after 30 years working her way up the ladder in corporate America. They don’t care. And why would they? What does working in a bank have to do with being a successful barista? Switching careers isn’t just difficult for people trying to break into tech. It’s difficult across the board. As a junior developer (or barista) you are an inherently risky hire. This doesn’t mean you should quit - it just means that you’ll need to find ways to re-invent yourself and build trust. Because I like you, and chances are you're smart and above average looking if you're reading this - 𝘁𝗵𝗲𝗿𝗲 𝗶𝘀 𝗮 𝗳𝗿𝗲𝗲 𝗰𝗼𝘂𝗿𝘀𝗲 𝗜 𝗰𝗿𝗲𝗮𝘁𝗲𝗱 𝘄𝗶𝘁𝗵 Taro (YC S22) 𝘁𝗼 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂 𝘁𝗿𝗮𝗻𝘀𝗶𝘁𝗶𝗼𝗻 𝗰𝗮𝗿𝗲𝗲𝗿𝘀 𝗶𝗻𝘁𝗼 𝘁𝗲𝗰𝗵. No theory, just super practical application I know can help you. It's in the comments 😎	TEXT	Brian	Jenney	33,557	33,557	84	14	1	0.00295	null	2024-11-13 09:29:29	https://www.linkedin.com/feed/update/urn:li:activity:7262516939732713472
urn:li:activity:7261769886337572864	My favorite mental models for computer science concepts: 𝗥𝗲𝗰𝘂𝗿𝘀𝗶𝗼𝗻 - Russian dolls: Each doll holds another, representing a function calling itself. 𝗟𝗶𝗻𝗸𝗲𝗱 𝗟𝗶𝘀𝘁𝘀 - Train cars: Each train car is linked to the next, just like each node points to the next node in a linked list. 𝗦𝘁𝗮𝗰𝗸𝘀 - Stack of plates: You can only take from the top or add to the top, similar to how a stack operates (Last-In, First-Out). 𝗤𝘂𝗲𝘂𝗲𝘀 - Line to get on a bus: First person in line is first to get on, which represents the First-In, First-Out (FIFO) principle. 𝗧𝗿𝗲𝗲𝘀 - Family tree: Each “parent” node has “child” nodes, and the child can also be a parent with children. 𝗕𝗶𝗴 𝗢 𝗡𝗼𝘁𝗮𝘁𝗶𝗼𝗻 - Traffic on a highway: As more cars (inputs) join, the effect on speed varies depending on the road’s capacity (algorithm’s efficiency). What is a mental models you use for understanding software-y things?	TEXT	Brian	Jenney	6,027	6,027	100	25	4	0.021404	null	2024-11-11 08:00:58	https://www.linkedin.com/feed/update/urn:li:activity:7261769886337572864
urn:li:activity:7260437739324473345	If becoming a software developer was as easy as learning the "𝗿𝗶𝗴𝗵𝘁" technology, then YouTube wouldn't be overrun with videos of coding boot camp grads talking about how hard it is to get hired. Your technology stack is still important, obviously. Don’t think so? Learn Fortran, COBOL and BrainF*ck and please tell me how that works out for you. The real disconnect between learning to code and getting hired is that career change requires a completely different skill set: - building an online presence - project management - job search strategy - time management - rejection handling - self promotion Luckily, a solid side project can help you build these skills. - plan out a complex app that will solve a problem you have - use Trello to break the tasks down into deliverables - deploy the app and try to get users - write about this experience online - use tech you want to learn	TEXT	Brian	Jenney	8,359	8,359	68	12	2	0.00981	null	2024-11-07 15:47:29	https://www.linkedin.com/feed/update/urn:li:activity:7260437739324473345
urn:li:activity:7259588652907810816	𝘏𝘰𝘸 𝘮𝘰𝘴𝘵 𝘴𝘶𝘤𝘤𝘦𝘴𝘴𝘧𝘶𝘭 𝘣𝘰𝘰𝘵𝘤𝘢𝘮𝘱 𝘨𝘳𝘢𝘥𝘴 𝘰𝘱𝘦𝘳𝘢𝘵𝘦: - Looks outside the LinkedIn bubble for opportunities - Has faith that opportunity will present itself - Re-calibrates their approach when needed - Makes coding and learning a routine - Applies consistently and broadly - Has 1 or 2 complex side projects 𝘞𝘩𝘺 𝘮𝘰𝘴𝘵 𝘣𝘰𝘰𝘵𝘤𝘢𝘮𝘱 𝘨𝘳𝘢𝘥𝘴 𝘧𝘢𝘪𝘭: - Relies on motivation instead of routine - Applies to only junior roles - Tutorial - Tutorial - Tutorial - Tutorial - Doesn’t get hired in 3 months - 𝘎𝘪𝘷𝘦𝘴 𝘶𝘱	TEXT	Brian	Jenney	6,529	6,529	50	14	2	0.010109	null	2024-11-05 07:33:31	https://www.linkedin.com/feed/update/urn:li:activity:7259588652907810816
urn:li:activity:7259250246084382720	You can’t get hired because you have no experience. You have no experience because you can’t get hired. Let’s change that. Reach out to your cousin, aunt or that friend trying to launch their music career and offer to build a website. For free. Make them buy a domain. Or buy one for them - f*ck it. Sketch out the site and main features and review them with your cousin, I mean client. Build and deploy. Have them give you a testimonial. Now you have some viable experience, a real deal site to show off and have dipped your toe into freelance.	TEXT	Brian	Jenney	10,760	10,760	77	7	1	0.0079	null	2024-11-04 09:08:48	https://www.linkedin.com/feed/update/urn:li:activity:7259250246084382720
urn:li:activity:7258156409710628865	Excellent question! After learning barely enough to build something, I would build something. That something would be publicly available, solve a problem that I'm familiar with and inform what I write about online, which I'd do 2-3x per week on LinkedIn. I would try my best to get customers for this thing and also write about that. I would be reaching out to my 2nd and 3rd party connections and looking at places where I used to work and old co-workers to see if they can get me in front of a hiring manager. Lastly, I would hire someone to write me a solid resume and LinkedIn profile and then not stop tinkering with these processes until I got hired.	SHARE	Brian	Jenney	5,603	5,603	36	3	0	0.006961	null	2024-11-01 09:42:18	https://www.linkedin.com/feed/update/urn:li:activity:7258156409710628865
urn:li:activity:7257413162256244738	Quintessential junior dev move: Wasting hours solving a problem a co-worker could’ve helped you figure out in minutes. You are ultimately judged on the work you complete, not your ability to slog through problems in solitude. When you bump your head against your technical depth, acknowledge it and ask for help. But for Jeebus' sake please don’t just say “𝘐 𝘤𝘢𝘯’𝘵 𝘧𝘪𝘨𝘶𝘳𝘦 𝘰𝘶𝘵 [𝘹]” Try this: - I’m having an issue with [this specific problem] - I’ve tried [y] but it’s not working in the way I expect which is [this way] - Maybe add a screenshot or documentation - "𝘐𝘴 𝘢𝘯𝘺𝘰𝘯𝘦 𝘢𝘷𝘢𝘪𝘭𝘢𝘣𝘭𝘦 𝘵𝘰 𝘵𝘢𝘬𝘦 𝘢 𝘭𝘰𝘰𝘬 𝘸𝘪𝘵𝘩 𝘮𝘦 𝘴𝘰𝘮𝘦𝘵𝘪𝘮𝘦 𝘵𝘰𝘥𝘢𝘺 𝘰𝘳 𝘱𝘰𝘪𝘯𝘵 𝘮𝘦 𝘪𝘯 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵 𝘥𝘪𝘳𝘦𝘤𝘵𝘪𝘰𝘯?" Don’t let your ego get in the way of progress.	TEXT	Brian	Jenney	61,212	61,212	345	56	7	0.006665	null	2024-10-30 08:28:54	https://www.linkedin.com/feed/update/urn:li:activity:7257413162256244738
urn:li:activity:7256765058410504194	LinkedIn Sucks. It’s full of: - cringy posts from LinkedIn lunatics - fear-mongering - toxic positivity - do you agree? It’s also full of: - strangers willing to lend you a hand - quality content you can learn from - inspiring stories - opportunity LinkedIn, like most social media platforms, will do its best to feed you content it believes you will like. If your LI feed sucks, maybe follow some better people.	TEXT	Brian	Jenney	14,284	14,284	180	26	1	0.014492	null	2024-10-28 13:33:34	https://www.linkedin.com/feed/update/urn:li:activity:7256765058410504194
urn:li:activity:7255612733314772992	If you’re hell-bent on learning data structures and algorithms please don’t JUST do 100 LeetCode problems. Try this instead: - learn common data structures like trees, graphs, linked lists, stacks and queues - write these structures from scratch - learn common techniques to sort and traverse data in these structures - focus on recursion and backtracking after learning trees (𝘐 𝘧𝘪𝘯𝘥 𝘵𝘩𝘢𝘵 𝘪𝘵 𝘮𝘢𝘥𝘦 𝘮𝘰𝘳𝘦 𝘴𝘦𝘯𝘴𝘦 𝘵𝘩𝘪𝘴 𝘸𝘢𝘺) - time yourself solving LC problems - shoot for 30 mins for medium problems and write the space and time complexity next to your solution - learn common approaches to optimize algorithms (𝘩𝘢𝘴𝘩𝘮𝘢𝘱𝘴, 𝘮𝘦𝘮𝘰𝘪𝘻𝘢𝘵𝘪𝘰𝘯...) Just because MAANG exclusively asks DSA, the majority of your interviews as a front end developer will probably be on a combination of: - behavioral and technical assessments - challenges that involve string manipulation and working with arrays && objects - JS trivia (explain closure 🙄) - building small components using ReactJS	TEXT	Brian	Jenney	14,905	14,905	131	19	11	0.010802	null	2024-10-25 09:14:38	https://www.linkedin.com/feed/update/urn:li:activity:7255612733314772992
urn:li:activity:7254877418811768832	❌ Get a job you love and you’ll never work a day in your life. Look, I love to write code and mentor people. But there’s so much more to software development than writing code and pair-programming. Some of the non-sexy stuff you’ll do as a developer: - meetings - on-call shifts - writing documentation - maintaining legacy code - meetings to prepare for other meetings - translating technical limitations to non-coders - researching poorly documented 3rd party APIs Coding is my hobby and profession. It’s a job and I try not to wrap too much of my identity into it. It can be incredibly fulfilling and it can also be a chore.	TEXT	Brian	Jenney	15,952	15,952	61	15	0	0.004764	null	2024-10-23 08:32:45	https://www.linkedin.com/feed/update/urn:li:activity:7254877418811768832
urn:li:activity:7254519140244221953	No one will hire you without experience. But you can't get experience without getting hired. ♾️ Let me make this very simple for you: - Build an app you might actually find useful and deploy it. - Connect with people who show interest. - Write about this experience online. - Try to get users for your app. - Work for free if you have to. Walk down main street and see what business has an awful website they need re-done. Do it for a recommendation from them. Change your title to freelance web engineer. Your mileage WILL vary. I can guarantee you will be hired but I cannot control the timeline. Neither can you. The only thing I know is that quitting is the surest path towards failure and is the most well-traveled.	TEXT	Brian	Jenney	26,468	26,468	160	22	3	0.00699	null	2024-10-22 08:49:05	https://www.linkedin.com/feed/update/urn:li:activity:7254519140244221953
urn:li:activity:7254165594042687488	I had the chance to interview Rahul Pandey recently. He said something I respectfully disagree with: "He was lucky." Something interesting I've noticed about "lucky" people is that they share many of the same traits: - grit - optimism - consistency - they work their a** off Funny how many "lucky" people I've met fit this description. Rahul breaks down what it was like working in FAANG, big fat salaries, why AI isn't the existential crisis you might think it is and what new developers can do to stand out in the market. Link in comments 😎	TEXT	Brian	Jenney	16,800	16,800	75	13	0	0.005238	null	2024-10-21 09:24:13	https://www.linkedin.com/feed/update/urn:li:activity:7254165594042687488
urn:li:activity:7253070973665452033	Every few months, someone roasts the tech interview. 𝘐’𝘭𝘭 𝘯𝘦𝘷𝘦𝘳 𝘵𝘳𝘢𝘷𝘦𝘳𝘴𝘦 𝘢 𝘉𝘚𝘛 𝘪𝘯 “𝘳𝘦𝘢𝘭 𝘭𝘪𝘧𝘦” 𝘵𝘩𝘦𝘺 𝘴𝘢𝘺. 𝘛𝘩𝘦𝘴𝘦 𝘵𝘦𝘴𝘵𝘴 𝘢𝘳𝘦 “𝘣𝘪𝘢𝘴𝘦𝘥” 𝘢𝘯𝘥 𝘧𝘭𝘢𝘸𝘦𝘥! People cheer in the comments. And nothing changes. The reality is that you’re way less likely to encounter data structures and algorithms on the interview grind if you’re not limiting your search to the top tech companies in the world. Honestly, if someone asks you to solve a dynamic programming problem during an interview for a company that is not FAANG, the correct response is probably to just walk out. If you're a glutton for punishment, then maybe this video of me going over a common dynamic programming problem will be useful.	VIDEO	Brian	Jenney	6,099	1,931	35	5	1	0.006722	null	2024-10-18 08:54:35	https://www.linkedin.com/feed/update/urn:li:activity:7253070973665452033
urn:li:activity:7252718611096616962	"𝘈𝘐 𝘪𝘴 𝘤𝘰𝘮𝘪𝘯𝘨 𝘧𝘰𝘳 𝘺𝘰𝘶𝘳 𝘵𝘦𝘤𝘩 𝘫𝘰𝘣!" "𝘛𝘩𝘦𝘳𝘦'𝘴 𝘯𝘰 𝘩𝘰𝘱𝘦 𝘧𝘰𝘳 𝘤𝘰𝘥𝘦𝘳𝘴 𝘪𝘯 2024!" "𝘓𝘦𝘢𝘳𝘯 𝘵𝘰 𝘤𝘰𝘥𝘦?! 𝘏𝘢, 𝘵𝘩𝘢𝘵 𝘸𝘢𝘴 𝘴𝘰 2015." Do these click bait titles sound familiar? I've gone down the YouTube rabbit hole of doom and gloom videos about the tech job market and AI. The reality is much less interesting which is why you won't see much of it on platforms where extreme opinions get the most eye balls. Believe it or not, there are more open tech jobs openings now than at any point in the last 2 years. Here's some other truths: - Getting the first job is difficult. This is not new or unique to tech. - No single tech stack will make you dramatically more hire-able. - AI might take your job as a developer. By that time, we will all be screwed anyways. Lastly, remember that social media rewards extreme opinions over boring truths. 🤷	IMAGE	Brian	Jenney	24,654	24,654	98	20	5	0.004989	null	2024-10-17 09:34:25	https://www.linkedin.com/feed/update/urn:li:activity:7252718611096616962
urn:li:activity:7251983808344784896	My biggest coding hack? Well, I used to be an addict. Maybe I still am? You see, over a decade ago, my life looked a lot more like a music video for a local rapper than an episode of Silicon Valley. Nearly 2 years after my son was born, I had an ultimatum: give up my ridiculous lifestyle or lose my family. I quit [a lot of stuff 😅] immediately with zero plan of how I was going to make it work or if I would succeed. I had lots of time to kill. I had no clue what normal people did for fun. I got introduced to HTML and CSS from a co-worker and my mind was blown. So this is how the internet works eh? How the hell did I not know this? Cue my new addiction. I approached coding with the same unhealthy mindset as I did with, uhhh, previous things. It took over my life. It worked well overall in that I made a transition that even my mother did not really believe was possible. But I don’t suggest it. Eat, sleep, code is a recipe for burnout, not success. Once I incorporated exercise, reading and other hobbies into my life, I was happier, less anxiety-ridden and more confident. I still have a ways to go though, honestly. Even now, I tend to go way overboard with any interest I pick up and while that sounds like a superpower it can also be at the expense of those around me and my own health. Every once in a while, I share this embarrassing piece of my past in the hopes that a few readers will feel less alone who may be in a similar position. Just know that there are quite a few of us floating around out there and most just don’t post it online.	TEXT	Brian	Jenney	9,311	9,311	142	18	0	0.017184	null	2024-10-15 08:54:35	https://www.linkedin.com/feed/update/urn:li:activity:7251983808344784896
urn:li:activity:7251617572641546241	There is a valuable skill that will set you apart from most developers. It will go from a nice to have to a requirement if you want to move into leadership: Public speaking. If you’re like me, maybe you think you can just hide in your code hole and never speak. I tried this method for a few years and it sorta worked. - I didn’t get fired. - I also couldn’t get promoted or make much of an impact. When I became an engineering manager, my job still involved coding but also a lot of speaking. This freaked me out. To get over my fear I did a few things: 1. Write down questions to ask during meetings 2. Volunteer to present at lunch and learns 3. Practice speaking on video using Loom (I made so many cringy videos I’ve never shared) 4. Make a commitment to be the first to break the silence in a meeting - even with a dumb question (see #1) You’re probably your worst critic. We’re all much too wrapped up in ourselves to remember the dumb thing you said in that meeting last Tuesday 😅. What's your best tip for shy developers to find their voice?	TEXT	Brian	Jenney	14,660	14,660	66	17	0	0.005662	null	2024-10-14 08:39:17	https://www.linkedin.com/feed/update/urn:li:activity:7251617572641546241
urn:li:activity:7250521003137609729	My podcast actually makes negative money. I don't offer paid spots, sponsorships or money for shouting out products, people or services. It's not that I'm against any of this at all. Last I checked, we live in a capitalist society. The real reason I don't offer any advertisement slots is because I'm already promoting my own business, Parsity and since I'm not beholden to any particular brand, I can interview and say whatever the hell I want. This weekend I'll be interviewing Geoffrey Huck to learn how shy developers can hack communication and learn the art of public speaking. Leadership is the natural progression for most software developers and yet, when it comes to public speaking, most of us have no freaking clue what to do or how to do it. What are some questions you want me to ask him?	IMAGE	Brian	Jenney	9,146	9,146	64	15	1	0.008747	null	2024-10-11 08:01:55	https://www.linkedin.com/feed/update/urn:li:activity:7250521003137609729
urn:li:activity:7250265616186531840	A decade of brutal code reviews did not prepare me for what I’ve read on TikTok, IG and Reddit about coding. Apparently: - no one should ever use JS. Like ever. - AI is for sure taking over all our jobs... just you wait! - learning to code is a waste of time. Be a wind turbine technician. - You can make 1.5 mil a year as a CyberSecurity Engineer. I messed up. If you’re looking for civil discourse or to learn anything useful, I would stay away. Go old school. Read a couple books by people who took their time to articulate their thoughts and actually research rather than compete to see who can make the most viral and shocking content. Here’s a few I’ve read and would recommend: 𝗧𝗵𝗲 𝗖𝗼𝗱𝗶𝗻𝗴 𝗖𝗮𝗿𝗲𝗲𝗿 𝗛𝗮𝗻𝗱𝗯𝗼𝗼𝗸 - such good advice on the non-tech stuff. 𝗞𝗲𝗲𝗽 𝗖𝗮𝗹𝗺 𝗮𝗻𝗱 𝗖𝗼𝗱𝗲 𝗢𝗻 - I wish I had found this book earlier. The author lays out all the mistakes he made that are so common among developers and how to avoid them. 𝗧𝗵𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗿'𝘀 𝗣𝗮𝘁𝗵: 𝗔 𝗚𝘂𝗶𝗱𝗲 𝗳𝗼𝗿 𝗧𝗲𝗰𝗵 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗡𝗮𝘃𝗶𝗴𝗮𝘁𝗶𝗻𝗴 𝗚𝗿𝗼𝘄𝘁𝗵 𝗮𝗻𝗱 𝗖𝗵𝗮𝗻𝗴𝗲 - the book I bought when I became a manager because I didn't know what the hell I was supposed to do. 𝗞𝘆𝗹𝗲 𝗦𝗶𝗺𝗽𝘀𝗼𝗻’𝘀 𝗬𝗗𝗞𝗝𝗦 𝘀𝗲𝗿𝗶𝗲𝘀 - duh. 𝗧𝗵𝗲 𝗣𝗵𝗼𝗲𝗻𝗶𝘅 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 - learn SDLC and actually be entertained. This book is a great read whether or not you know anything about code. Any good recommendations I should add to my list?	TEXT	Brian	Jenney	55,846	55,846	177	29	5	0.003778	null	2024-10-10 15:07:06	https://www.linkedin.com/feed/update/urn:li:activity:7250265616186531840
urn:li:activity:7249793994208010247	Most stressful scenarios you will encounter as a software developer: - code you just deployed causing a critical error - demoing some code that breaks apart in front of an audience - when it just worked on your machine - notification from GitHub that your code review has 100+ comments - getting a PagerDuty alert on a weekend about a component you aren’t familiar with - cryptic messages to meet to chat with your manager with no agenda - interviews What else?	TEXT	Brian	Jenney	5,159	5,159	55	22	2	0.015313	null	2024-10-09 07:53:02	https://www.linkedin.com/feed/update/urn:li:activity:7249793994208010247
urn:li:activity:7249463605690036228	Let's call him Don. First off, this guy was a genius. I could tell because when we went out to eat on the first day of work with the CEO and CTO - this guy used his hands to eat a salad. Next, he asked if he could go home early because he was tired. He slept on the couch in the office in the middle of the day. Only a genius can get away with shit like that and not get fired on the spot. I was entering my 3rd year as a developer and thought of myself as mid-level at this point. Wrong. Don pair-programmed with me for the first 2 weeks on the job and I quickly learned just how junior I was. Don wrote tests for the features we created using the library he authored for the framework we were using. I had never written a test in my life. Don had keyboard shortcuts to fly around his terminal and code editor. I didn't have the "time" for that. I just wanted things to "work." Don didn't accept my "make it wok by all means necessary" style of work. He refused to work with me until I learned keyboard shortcuts for VS code to make pairing more enjoyable. If I wrote a feature without a test, he would reject it. When I asked for help, he wouldn't give me the answer but tell me where I could probably find the underlying issue. We only worked together for 9 months but I can't think of a more impactful stint in my career. I learned the art of testing, the importance of learning your tools and how to balance getting things done with getting them done correctly. Last I heard, he co-founded a multi-million dollar software company. I bet he's still eating salad with his hands.	TEXT	Brian	Jenney	12,104	12,104	135	20	5	0.013219	null	2024-10-08 10:00:12	https://www.linkedin.com/feed/update/urn:li:activity:7249463605690036228
urn:li:activity:7249070525740711936	We’ve all heard the myth: it takes 10,000 hours to master a skill. The reality is, you don’t need to become a master to be functional or effective. In fact, research shows that 20 hours of focused learning can get you up and running with learning a new instrument, language or coding. It’s not about grinding endlessly, it’s about the right strategy: • build stuff you actually care about • break things on purpose to see how NOT to do things • get feedback on your work and adjust course when necessary I had a conversation with Junaid Akhtar, content architect at Educative , about the science of learning to code. We discussed how beginners can fast-track their way into programming with just 20 hours of focused effort. The link is in the comments.	TEXT	Brian	Jenney	9,555	9,555	102	10	10	0.012768	null	2024-10-07 07:58:14	https://www.linkedin.com/feed/update/urn:li:activity:7249070525740711936
urn:li:activity:7247627778122997760	Bootcamps love the MERN stack. Professional developers love the SERN stack. Honestly, SQL is more intuitive than MongoDB and yet so many new developers don't learn it. Here's a dead simple challenge you can copy and paste into ChatGPT to set up your first SQL database and learn in a hands-on way: 1. 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗡𝗲𝗼𝗻𝗗𝗕 𝗔𝗰𝗰𝗼𝘂𝗻𝘁: Head to Neon, create a project, and access the SQL editor. 2. 𝗖𝗿𝗲𝗮𝘁𝗲 𝗧𝗮𝗯𝗹𝗲𝘀: Use ChatGPT to generate SQL commands for tables like users, orders, and products, then run them in NeonDB. 3. 𝗔𝗱𝗱 𝗦𝗮𝗺𝗽𝗹𝗲 𝗗𝗮𝘁𝗮: Prompt ChatGPT for SQL to insert sample data (100+ rows per table) and populate your database. 4. 𝗥𝘂𝗻 𝗕𝗮𝘀𝗶𝗰 𝗤𝘂𝗲𝗿𝗶𝗲𝘀: Start querying data with simple prompts like selecting usernames and emails from the users table. 5. 𝗝𝗼𝗶𝗻 𝗧𝗮𝗯𝗹𝗲𝘀: Use a LEFT JOIN to show all users and their orders, even if they haven’t placed one. 6. 𝗧𝗿𝘆 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗤𝘂𝗲𝗿𝗶𝗲𝘀: Challenge yourself—find all orders by a certain user or count how many orders each user has placed. What are some good resources you've found for learning SQL?	TEXT	Brian	Jenney	10,184	10,184	72	24	6	0.010016	null	2024-10-03 08:25:16	https://www.linkedin.com/feed/update/urn:li:activity:7247627778122997760
urn:li:activity:7246525531641274368	You cannot simply be a like-able yet terrible coder and expect to get promoted (but I have seen it happen). The best way to get better at coding is to: 1. Write a lot of bad code. 2. Read good code and steal what makes sense (no, not by copy-pasting but "stealing" the patterns and styles of better coders). 3. Read up on common design patterns in your programming language and apply them to your work. 4. Look up design patterns for the framework you use. For example, if you use ReactJS (cuz of course you do) then look up popular ways to compose components, fetch data and construct large apps. The sad reality is that many developers never make it past step 1. Don't do that. You're better than that.	TEXT	Brian	Jenney	26,611	26,611	104	23	1	0.00481	null	2024-09-30 07:25:20	https://www.linkedin.com/feed/update/urn:li:activity:7246525531641274368
urn:li:activity:7245463369602785280	The problem with developers in general and content creators specifically: We use too much anecdotal experience to draw wild conclusions. This creates an echo chamber online which makes you think that certain things are truer than they probably are: - Most devs don’t work for big tech - You’re more likely to work on legacy code than brand new features - Designing a complex system will take weeks or months, not an hour with a whiteboard - Flexible schedules can mean 4 hours one day and 14 the next - Even the best developers fail interviews - Your next interview is unlikely to include a whiteboard - “Real developers” don’t use JS and yet it’s the most popular language in the world 🙄 To get an accurate pulse on what’s really happening in the dev community, 𝗜 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗰𝗵𝗲𝗰𝗸𝗶𝗻𝗴 𝗼𝘂𝘁 𝗦𝘁𝗮𝗰𝗸 𝗢𝘃𝗲𝗿𝗳𝗹𝗼𝘄’𝘀 𝘆𝗲𝗮𝗿𝗹𝘆 𝘀𝘂𝗿𝘃𝗲𝘆, looking at hiring trends in the industry and generally taking what we all say on here with a grain of salt.	TEXT	Brian	Jenney	12,780	12,780	60	9	1	0.005477	null	2024-09-27 09:04:41	https://www.linkedin.com/feed/update/urn:li:activity:7245463369602785280
urn:li:activity:7245094445707091970	One of my biggest struggles as an engineering manager was keeping my tech skills sharp. I went from writing code for most of the day to: - leading meetings - JIRA management - 1 on 1s - sitting in on sales pitches - obsessing over the images in my presentations (the right meme can really make or break it 😅) Sitting through a 100 hour tutorial to type what some other bandicoot was typing just wasn't appealing at this stage. I didn't want to learn JavaScript anymore. I wanted something to stretch my skills. CodeCrafters.io (YC S22) to the rescue. One of my favorite services for preventing skill-rot is CodeCrafters. I started using it years ago to learn more about complex software like Redis, Docker and SQLite by building it from scratch. If you’re over watch-and-type tutorials and want a real challenge, I can’t recommend them enough.	TEXT	Brian	Jenney	5,901	5,901	27	5	1	0.005592	null	2024-09-26 08:38:43	https://www.linkedin.com/feed/update/urn:li:activity:7245094445707091970
urn:li:activity:7244392411307655168	Can we all agree that snapshot tests are pointless 99% of the time? They somehow sneak into our test suites with good intentions. Inevitably they result in false alarms and are ignored. Unit tests are concerned with confirming expected functionality. We make sure that clicking a button actually results in an event happening for example. Now we have these pesky snapshots. They take a pic (a snapshot if you will) of the DOM output and then compare the original code to the current output. If there’s a difference, we get a failed test. Maybe you changed the button color from light-green to not-so-light green. Whoops. Used incorrectly, snapshots give us a false sense of security or get ignored entirely. They contribute to vanity test coverage metrics with no real benefit. Am I way off base here? If you’ve used snapshots in a useful way I’d love to hear about it.	IMAGE	Brian	Jenney	13,170	13,170	27	22	1	0.003797	null	2024-09-24 10:09:05	https://www.linkedin.com/feed/update/urn:li:activity:7244392411307655168
urn:li:activity:7244004446437851136	How old is too old to learn to code and change careers? According to the internet - it’s 40 🙄 Imagine if Dicky Kitchen Jr had listened to those geniuses. I met Dicky a couple years ago on Instagram. I enjoyed his content and what he was building. His journey from working in physical therapy to software engineer wasn’t short or straightforward. But it did work. If you’re serious about making a career switch into software then Dicky has a path you might find useful, no matter your age. A link to our convo is in the comments.	TEXT	Brian	Jenney	37,521	37,521	89	38	3	0.003465	null	2024-09-23 08:27:27	https://www.linkedin.com/feed/update/urn:li:activity:7244004446437851136
urn:li:activity:7242925058602508289	Before you make that TODO app, or watch a 100 hour YouTube video where you basically type what someone else types, try this:	VIDEO	Brian	Jenney	12,282	4,964	185	8	16	0.017017	null	2024-09-20 08:58:20	https://www.linkedin.com/feed/update/urn:li:activity:7242925058602508289
urn:li:activity:7238041938392686592	Something I've learned from speaking with a few hundred of you out there: No one really has a "traditional" path into... anything. Tech is not a magical bullet to solve your problems and changing careers into software is difficult. But it's possible. I'm a little sick of the negativity I read online about coding and the fluffy advice that doesn't really help. Join me and 👾 Aaron Cordova to 𝗯𝗿𝗲𝗮𝗸 𝗱𝗼𝘄𝗻 𝗵𝗼𝘄 𝘁𝗼 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝗸𝗲 𝗮 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗰𝗮𝗿𝗲𝗲𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 𝗶𝗻𝘁𝗼 𝘁𝗲𝗰𝗵 and learn about his path from rapper to New York City Transit worker to writing code at some of the most loved (and hated) tech companies on the planet.	VIDEO	Brian	Jenney	5,619	1,530	49	55	6	0.019576	null	2024-09-18 14:55:53	https://www.linkedin.com/feed/update/urn:li:activity:7238041938392686592
urn:li:activity:7241808386047025152	"You DoNt UndeRStanD hoW BaD the mArkEt is BrOooOooO!" You're right. What do I know? Not like I got laid off and hired this year or learned to code at 30 or helped 100+ developers get hired over the last 10 years. But maybe you're tired of hearing my advice. I recently hosted 👾 Aaron Cordova on my podcast and he has a hell of story. Aaron went from rapping on the streets of New York and working on the transit system to working at some of the biggest names in tech. Career changers have unique challenges when it comes to breaking into tech and need a different strategy to be successful. I'm hosting 𝗔 𝗡𝗼 𝗕𝗦 𝗚𝘂𝗶𝗱𝗲 𝗼𝗻 𝗕𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝗶𝗻𝘁𝗼 𝗧𝗲𝗰𝗵 𝗮𝘀 𝗮𝗻 𝗢𝘂𝘁𝘀𝗶𝗱𝗲𝗿 with Aaron tomorrow to chat about what you should be building, how you should be networking and interview strategies for people without CS degrees. If you can't make it, please drop a question in the comments and I'll pass them along!	SHARE	Brian	Jenney	4,894	4,894	42	4	3	0.010012	null	2024-09-17 07:01:05	https://www.linkedin.com/feed/update/urn:li:activity:7241808386047025152
urn:li:activity:7241471974147850240	No one, and I mean no one, uses JS on the backend. Except: NASA Netflix Uber LinkedIn Trello Walmart PayPal Seriously, don’t use JS on the backend, it’s a recipe for… disaster.	TEXT	Brian	Jenney	101,519	101,519	585	109	10	0.006935	null	2024-09-16 08:44:18	https://www.linkedin.com/feed/update/urn:li:activity:7241471974147850240
urn:li:activity:7239653769263595523	No one is going to pay you thousands of dollars to build a website. But they might pay you to: - improve SEO - get more clients - sell more products - boost their conversion rates - increase awareness of their brand Sometimes, a website can do 1 or all of these things. It’s just about how you’re selling it. Solutions > code. If you’re looking for no nonsense advice about freelancing and the art of writing code for cold hard cash then you should really follow William Ray .	TEXT	Brian	Jenney	15,172	15,172	122	9	1	0.0087	null	2024-09-11 08:19:24	https://www.linkedin.com/feed/update/urn:li:activity:7239653769263595523
urn:li:activity:7238938762062221313	𝗡𝗲𝘄𝘀𝗳𝗹𝗮𝘀𝗵: My podcast about learning to code and creating a solid career in tech is good, BUT 𝗜𝘁 𝘄𝗼𝗻'𝘁 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂: - finish that side project - become a software developer - figure out why that error on line 420 is crashing your TODO list app 𝗡𝗼𝘁 𝘁𝗼𝗱𝗮𝘆, 𝘁𝗼𝗺𝗼𝗿𝗿𝗼𝘄, 𝗼𝗿 𝗶𝗻 𝗮 𝗺𝗼𝗻𝘁𝗵'𝘀 𝘁𝗶𝗺𝗲. 𝗧𝗵𝗲 𝗼𝗻𝗹𝘆 𝘄𝗮𝘆 𝘁𝗼 𝘁𝘂𝗿𝗻 𝗶𝘁 𝗳𝗿𝗼𝗺 𝗮 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗼𝗳 𝘂𝘀𝗲𝗳𝘂𝗹 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗶𝗻𝘁𝗼 𝘁𝗵𝗲 𝗴𝗼𝗮𝗹 𝘆𝗼𝘂'𝗿𝗲 𝗰𝗵𝗮𝘀𝗶𝗻𝗴: 𝗔𝗰𝘁𝗶𝗼𝗻. 𝗜 𝗸𝗻𝗼𝘄 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗜 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝘁𝗵𝗶𝘀 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝘄𝗮𝘆. One summer I read an entire book on HTML (it was 11 years ago, please don’t judge me). I sat down in front of my computer to type some sweet HTML and realized I had no effin’ clue what to do. Have you ever watched a tutorial from start to finish only to wonder what the hell you just built? 𝗡𝗼𝘄 𝗜 𝗮𝗹𝘄𝗮𝘆𝘀 𝘁𝗮𝗸𝗲 𝗮𝗰𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗜'𝗺 𝗰𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗶𝗻𝘁𝗼 𝗺𝘆 𝗻𝗼𝗴𝗴𝗶𝗻. • use a tutorial as a starting point and then extend, re-write or break a feature • open the code editor and write out an example of an abstract concept like closure • write comments next to code in a way that makes sense... to me at least • record myself explaining a topic to see if I actually know what the hell I'm talking about	TEXT	Brian	Jenney	4,837	4,837	49	8	1	0.011991	null	2024-09-09 08:58:13	https://www.linkedin.com/feed/update/urn:li:activity:7238938762062221313
urn:li:activity:7237860486656995329	I’m not optimistic because I’m foolish or naive. I’m optimistic because it’s the most practical strategy I’ve found to get through life and create luck. The photo below is me 4 years ago, getting taken to the hospital in an ambulance on the second day of my new job with a heart condition. I didn’t know if I would come home so I wanted my last picture to be me smiling. I had done all the right things: - Quit alcohol - Had an exercise routine - Lost weight - Wrote tests for my code even when I didn’t have to And yet here I was - maybe about to die. Plot twist: I Iived! Could it happen again? Sure. I have a couple options: 1. Stress everyday, take a bunch of heart pills and avoid strenuous activity 2. Resume life I choose option 2. Your brain is a pattern-finding wizard. It will find “evidence” to support your assumptions. Start looking for proof that things can and will get better and that life tends to incrementally improve and you aren’t the unluckiest person you know. For me, this means limiting local news and social media and generally not hanging around people who always have drama and unfollowing accounts who push fear.	IMAGE	Brian	Jenney	9,839	9,839	145	29	1	0.017786	null	2024-09-06 09:33:32	https://www.linkedin.com/feed/update/urn:li:activity:7237860486656995329
urn:li:activity:7237492492168769536	Junior developers are inherently risky (in every industry, not just tech btw). "𝘉𝘶𝘵... 𝘐 𝘢𝘮 𝘢 𝘫𝘶𝘯𝘪𝘰𝘳", you say. Yeah, I get it, I get it, just bare with me here. The word "junior" is so subjective that it's nearly meaningless. 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗯𝗮𝘀𝗶𝗰𝗮𝗹𝗹𝘆 𝗯𝗼𝗶𝗹𝘀 𝗱𝗼𝘄𝗻 𝘁𝗼 𝗶𝘀 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝘄𝗵𝗼 𝗵𝗮𝘀 𝘀𝗼 𝗹𝗶𝘁𝘁𝗹𝗲 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝗰𝗮𝗻𝗻𝗼𝘁 𝗯𝗲 𝘁𝗿𝘂𝘀𝘁𝗲𝗱 𝘁𝗼 𝗱𝗼 𝗻𝗲𝗮𝗿𝗹𝘆 𝗮𝗻𝘆𝘁𝗵𝗶𝗻𝗴 𝗼𝗻 𝘁𝗵𝗲𝗶𝗿 𝗼𝘄𝗻. • They need significant hand-holding for months on the job. • They will take on the easy stuff and maybe break some things. • They won't contribute much. 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴: nearly every developer will be "junior" when they first join a company unless they are very senior. You don't actually need to a be a mid level developer to be a safe hire. You just need to avoid the tell-tale signs that you are, in fact, a n00b. Quite simply, stop down-playing yourself. • 𝗥𝗲𝗺𝗼𝘃𝗲 𝗷𝘂𝗻𝗶𝗼𝗿, 𝗮𝘀𝗽𝗶𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 from your resume and LinkedIn. • DON'T talk about "the project from your school or bootcamp" • 𝗗𝗢 𝗧𝗮𝗹𝗸 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝗮𝗽𝗽 𝗼𝗿 𝘄𝗲𝗯𝘀𝗶𝘁𝗲 𝘆𝗼𝘂'𝗿𝗲 𝗹𝗮𝘂𝗻𝗰𝗵𝗶𝗻𝗴 - yes, you need to have a project to talk about. • 𝗨𝘀𝗲 𝘀𝘁𝗿𝗼𝗻𝗴 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝘁𝗼 𝘁𝗮𝗹𝗸 𝗮𝗯𝗼𝘂𝘁 𝘆𝗼𝘂𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 and speak to the benefits of features you created. • Instead of "created a full stack app with a laundry list of tech" try "migrated a JS app to Typescript to improve developer experience and velocity".	TEXT	Brian	Jenney	359,301	359,301	571	63	23	0.001829	null	2024-09-05 09:11:16	https://www.linkedin.com/feed/update/urn:li:activity:7237492492168769536
urn:li:activity:7237138697131847683	You ever feel like you’re basically coding the same few features over and over and over? Sometimes your current role doesn’t prepare you for the next role. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝗺𝘆 𝘁𝗼𝗽 𝟰 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗳𝗼𝗿 𝗽𝗿𝗲𝘃𝗲𝗻𝘁𝗶𝗻𝗴 “𝘀𝗸𝗶𝗹𝗹-𝗿𝗼𝘁” 𝗮𝘀 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿: 1. CodeCrafters.io (YC S22) - finally something for the mid → senior level developers out there to get their hands dirty. The GitHub workflow is 😘 👨‍🍳. 2. Scrimba - Some students at Parsity have been using this and I have to admit, it’s an amazing platform to learn front-end. 3. Coding Challenges - John Crickett 🦗has crafted some non-trivial projects to teach you complex software. 4. My site, 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁𝗣𝗿𝗼𝘀𝗔𝗽𝗽[𝗱𝗼𝘁]𝗰𝗼𝗺 - at some point, you don’t want to “learn React” anymore. 𝗜 𝗰𝗿𝗲𝗮𝘁𝗲𝗱 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 𝗯𝗮𝘀𝗲𝗱 𝗼𝗻 𝗺𝘆 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗮𝘀 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝘆𝗲𝗮𝗿𝘀 including API migrations, deploying Lambdas, solving GitHub pipeline issues and creating NPM libraries. I’ve used every single one of these services in the past year and I’m usually explicit that I’m not sponsored. Well - can you believe CodeCrafters.io (YC S22) offered me a sponsorship code? I’m not gonna use it... for now. I sincerely like all these products, mine included and think you should check them out.	TEXT	Brian	Jenney	19,872	19,872	125	5	9	0.006995	null	2024-09-04 09:45:24	https://www.linkedin.com/feed/update/urn:li:activity:7237138697131847683
urn:li:activity:7236745316878667778	null	VIDEO	Brian	Jenney	2,681	1,126	47	2	0	0.018277	null	2024-09-03 07:42:15	https://www.linkedin.com/feed/update/urn:li:activity:7236745316878667778
urn:li:activity:7236742436859846656	“𝘔𝘺 𝘤𝘰𝘥𝘦 𝘴𝘱𝘦𝘢𝘬𝘴 𝘧𝘰𝘳 𝘪𝘵𝘴𝘦𝘭𝘧” “𝘐 𝘥𝘪𝘥𝘯’𝘵 𝘨𝘦𝘵 𝘪𝘯𝘵𝘰 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘵𝘰 𝘥𝘦𝘢𝘭 𝘸𝘪𝘵𝘩 𝘱𝘰𝘭𝘪𝘵𝘪𝘤𝘴” “𝘐’𝘭𝘭 𝘴𝘰𝘭𝘷𝘦 𝘵𝘩𝘪𝘴 𝘭𝘢𝘵𝘦𝘳 𝘵𝘰𝘯𝘪𝘨𝘩𝘵 𝘰𝘯𝘤𝘦 𝘵𝘩𝘦 𝘬𝘪𝘥𝘴 𝘢𝘳𝘦 𝘢𝘴𝘭𝘦𝘦𝘱” I won’t tell you how many of these quotes are directly from me (𝘩𝘪𝘯𝘵: 𝘪𝘵’𝘴 𝘮𝘰𝘳𝘦 𝘵𝘩𝘢𝘯 2 𝘢𝘯𝘥 𝘦𝘹𝘢𝘤𝘵𝘭𝘺 𝘦𝘲𝘶𝘢𝘭 𝘵𝘰 3) Thinking like this was naive at best and hindered my career as a software developer at worst. Turns out I’m not the only one. I sat down with Dagna Bieda to speak about 𝘄𝗵𝘆 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗳𝗮𝗹𝗹 𝗶𝗻𝘁𝗼 𝘁𝗵𝗲𝘀𝗲 𝗺𝗶𝗻𝗱𝘀𝗲𝘁 “𝘁𝗿𝗮𝗽𝘀” as well as her own struggles with communication and how she had to refactor her brain and approach to her coding career to reach the next level. Our convo took a very surprising turn towards the end. (𝙡𝙞𝙣𝙠 𝙩𝙤 𝙚𝙥𝙞𝙨𝙤𝙙𝙚 𝙞𝙣 𝙥𝙧𝙤𝙛𝙞𝙡𝙚) Hope you enjoy.	IMAGE	Brian	Jenney	7,938	7,938	83	5	1	0.011212	null	2024-09-03 07:30:49	https://www.linkedin.com/feed/update/urn:li:activity:7236742436859846656
urn:li:activity:7235285713192153088	Worst way to spend your weekend? Completing a take home coding project that was supposed to take 4 hours but really takes 2 full days. I know some people like this interview format. I am not one of them. If you MUST participate in these kinds of interviews there are 2 ways you can stand out: 1. Write documentation 2. Write some unit tests You don’t know how to write unit tests? Let’s fix that. Grab this repo and make it get to 100% coverage to learn the basics of unit testing: https://lnkd.in/dh_bVgz9	TEXT	Brian	Jenney	12,867	12,867	116	15	5	0.01057	null	2024-08-30 07:02:19	https://www.linkedin.com/feed/update/urn:li:activity:7235285713192153088
urn:li:activity:7235083322987552769	500 15 minute conversations with developers around the world later and I’m convinced that most of us need a sympathetic ear as much as we need career and coding advice. Here’s the thing: coding is fun. It can also be: - lonely - stressful - tedious - confusing Don’t wrap too much of your identity in the code you write. It can be a fickle beast. Sometimes I’m pretty damn good at slinging code. Sometimes I suck. So I hit the gym. Run around a lake. Read stuff. Write on here and Medium. I share what I think might help you on my podcast. When one area drags me down, I use another to lift me up. Outside of coding, what are some hobbies you’ve picked up?	TEXT	Brian	Jenney	4,649	4,649	45	13	1	0.012691	null	2024-08-29 17:38:05	https://www.linkedin.com/feed/update/urn:li:activity:7235083322987552769
urn:li:activity:7234570728459616256	Recipe for terrible 1 on 1’s: Manager: “Anything to discuss this week?” You: “Nah, I’m chilling” Manager: “Nice. Talk to ya next time 👍” 1 on 1’s can devolve into weekly status updates, which is why I think a lot of people like to skip them. I asked 3 engineering leaders how have 1 on 1’s that don’t suck: Nick Cosentino 👇 What you can do is talk about: - 𝗧𝗵𝗲 𝗶𝗺𝗽𝗮𝗰𝘁 𝘆𝗼𝘂𝗿 𝘄𝗼𝗿𝗸 𝗶𝘀 𝗵𝗮𝘃𝗶𝗻𝗴 - 𝗣𝗼𝘀𝗶𝘁𝗶𝘃𝗲/𝗻𝗲𝗴𝗮𝘁𝗶𝘃𝗲 𝗶𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝗼𝗻𝘀 with peers and partner teams so I can help offer guidance or follow up - 𝗥𝗼𝗮𝗱𝗯𝗹𝗼𝗰𝗸𝘀, whether they are technical or with people - 𝗖𝗮𝗿𝗲𝗲𝗿 𝗮𝘀𝗽𝗶𝗿𝗮𝘁𝗶𝗼𝗻𝘀 and whether or not you feel we’re aligned on career progression - Your level of motivation, engagement, excitement, interest, learning opportunity etc… on your current project This time is about YOU and as much as I would love to lead the charge on all of these things: You should take responsibility to do this as well. Ken Corey 👇 Your plans, your dreams, your challenges, where you can improve. - Talk about 𝘆𝗼𝘂𝗿 𝗴𝗼𝗮𝗹𝘀 𝗼𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗰𝗮𝗿𝗲𝗲𝗿 𝗽𝗹𝗮𝗻, as well as your goals outside the career plan. - Talk about how to progress (𝗮𝘀𝗸 𝗳𝗼𝗿 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸). - Talk about 𝘂𝗽𝗰𝗼𝗺𝗶𝗻𝗴 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗼𝗿 𝘀𝘂𝗴𝗴𝗲𝘀𝘁𝗶𝗼𝗻𝘀. - Talk about challenges. - Talk about managing up. Not all TL/EMs are comfortable with these meetings. John Crickett 👇 Your 121 is your chance to 𝗴𝗲𝘁 𝗮𝘀 𝗺𝘂𝗰𝗵 𝘃𝗮𝗹𝘂𝗲 𝗮𝘀 𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂𝗿 𝗺𝗮𝗻𝗮𝗴𝗲𝗿. Ask them for advice, mentoring and coaching. Ask them for help to achieve your career objectives. 𝗠𝗮𝗸𝗲 𝘀𝘂𝗿𝗲 𝘆𝗼𝘂 𝗱𝗿𝗶𝘃𝗲 𝘁𝗵𝗲 𝗮𝗴𝗲𝗻𝗱𝗮 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗯𝗲𝗻𝗲𝗳𝗶𝘁.	TEXT	Brian	Jenney	45,514	45,514	104	17	3	0.002724	null	2024-08-28 07:41:13	https://www.linkedin.com/feed/update/urn:li:activity:7234570728459616256
urn:li:activity:7233898727084605440	Ex-con, ex-cashier, ex-addict, ex-whatever. I've interviewed so many amazing people over the last year and spoken to literally hundreds of you over the phone. Recently 👾 Aaron Cordova reached out to share his story on the Develop Yourself podcast. 𝗔𝗮𝗿𝗼𝗻 𝘄𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗡𝗬𝗖 𝗧𝗿𝗮𝗻𝘀𝗶𝘁 𝗪𝗼𝗿𝗸𝗲𝗿 𝗮𝗻𝗱 𝗿𝗮𝗽𝗽𝗶𝗻𝗴 𝗼𝗻 𝘁𝗵𝗲 𝘀𝘁𝗿𝗲𝗲𝘁𝘀 𝗼𝗳 𝗡𝗲𝘄 𝗬𝗼𝗿𝗸 𝘁𝗼 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗮𝘁 𝘀𝗼𝗺𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗻𝗮𝗺𝗲𝘀 𝗶𝗻 𝘁𝗲𝗰𝗵, including Meta, Coinbase and Docker. Aaron has nothing to sell you. His story isn't really about tech or money, but that's a piece of it. The real story is about refusing to settle, rising above your circumstances and creating options in life when you feel like you don't have any. Aaron reached out to me because he wants to share his story in the hopes it will help others. He and I will be working to get a larger audience together because I know more people than we can reach on the podcast will benefit from hearing it. Link in profile to check out the episode.	TEXT	Brian	Jenney	5,300	5,300	64	9	3	0.01434	null	2024-08-26 11:10:55	https://www.linkedin.com/feed/update/urn:li:activity:7233898727084605440
urn:li:activity:7232424588524105728	Shocking and not so shocking takeaways from the 2024 Stack Overflow Developer Survey: 1. Javascript is STILL the most popular programming language - take that haters 2. 𝗘𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝘂𝘀𝗲𝘀 𝗩𝗦 𝗖𝗼𝗱𝗲 - learn it like a pro. 3. Bootcamps love MERN - 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹𝘀 𝗹𝗼𝘃𝗲 𝗦𝗘𝗥𝗡. There’s never been a better time to learn SQL with offerings like Supabase that make it too easy to start. 4. 𝗙𝗿𝗼𝗻𝘁 𝗲𝗻𝗱 𝗱𝗲𝘃𝘀 𝗮𝗿𝗲 𝗱𝗶𝘀𝗮𝗽𝗽𝗲𝗮𝗿𝗶𝗻𝗴? With ReactJS on the server and the popularity of NextJS does this mean more people identify as full stack? 5. 𝗙𝗲𝘄𝗲𝗿 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝘀𝗲𝗲 𝗔𝗜 𝗮𝘀 𝗮 𝘁𝗵𝗿𝗲𝗮𝘁 𝘁𝗼 𝘁𝗵𝗲𝗶𝗿 𝗷𝗼𝗯𝘀 than last year. A significantly higher percentage of students and people learning to code do see it as a threat. What does it all mean? As usual, reality is a bit different than social media: most developers don't work for FAANG, some of the most hated tech is also the most popular and AI still hasn't destroyed humanity... yet.	TEXT	Brian	Jenney	91,134	91,134	217	57	2	0.003029	null	2024-08-22 09:33:13	https://www.linkedin.com/feed/update/urn:li:activity:7232424588524105728
urn:li:activity:7232029662187511809	Developers universally hate deadlines. Businesses love them. They NEED to know when to expect that button on the "About Us" page. It's going to be a game changer! Learn how to estimate and deliver your work on time and you will be in a small class of developers. I'm still trying to get there myself. 😅 There are entire books written on the magical art of estimation for software projects. 𝗛𝗲𝗿𝗲'𝘀 𝗵𝗼𝘄 𝗜'𝘃𝗲 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝘁𝗼 𝘀𝘂𝗰𝗸 𝗺𝘂𝗰𝗵 𝗹𝗲𝘀𝘀 𝗮𝘁 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝘆𝗲𝗮𝗿𝘀: 1. 𝗪𝗿𝗶𝘁𝗲 𝗼𝘂𝘁 𝘁𝗵𝗲 𝘀𝘂𝗯-𝘁𝗮𝘀𝗸𝘀 needed for delivery of a feature and 𝗺𝗮𝗸𝗲 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗵𝗮𝗹𝗳 𝗱𝗮𝘆𝘀 for all tasks. This includes things like styling. 2. Each day, 𝗺𝗲𝗮𝘀𝘂𝗿𝗲 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝗮𝗴𝗮𝗶𝗻𝘀𝘁 𝘁𝗵𝗲 𝘀𝘂𝗯 𝘁𝗮𝘀𝗸𝘀 and see if you're on track or not. 3. Write the actual time next to your original estimation. 4. At the end of the project 𝘂𝘀𝗲 𝘁𝗵𝗲 𝗮𝗱𝗷𝘂𝘀𝘁𝗲𝗱 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 𝗳𝗼𝗿 𝗲𝗮𝗰𝗵 𝘁𝗮𝘀𝗸 𝘁𝗼 𝗮𝗰𝗰𝘂𝗿𝗮𝘁𝗲𝗹𝘆 𝗳𝗶𝗴𝘂𝗿𝗲 𝗼𝘂𝘁 𝘁𝗵𝗲 𝘁𝗶𝗺𝗲 𝗳𝗼𝗿 𝘁𝗵𝗲 𝘀𝗶𝗺𝗶𝗹𝗮𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀. 𝗜𝗳 𝘆𝗼𝘂'𝗿𝗲 𝗮 𝗻𝗲𝘄 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗼𝗿 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘁𝗼 𝗰𝗼𝗱𝗲 𝘁𝗵𝗲𝗻 𝘂𝘀𝗲 𝘆𝗼𝘂𝗿 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗮𝗻𝗱 𝗮 𝘁𝗮𝘀𝗸 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝘁𝗼𝗼𝗹 𝗹𝗶𝗸𝗲 𝗧𝗿𝗲𝗹𝗹𝗼 𝘁𝗼 𝗺𝗶𝗺𝗶𝗰 𝘁𝗵𝗶𝘀 𝗽𝗿𝗼𝗰𝗲𝘀𝘀. This will help you understand the time commitment for your side project and when you can expect to complete it.	TEXT	Brian	Jenney	21,678	21,678	53	17	1	0.003275	null	2024-08-21 07:23:56	https://www.linkedin.com/feed/update/urn:li:activity:7232029662187511809
urn:li:activity:7231338419505819648	How old is too old to learn to code? According to the internet, that age is 40. I think that's silly. I am fully aware that bias exists. Humans are... human. I also know that in the last 10 years, I've worked with amazing developers of all ages. On my first team, a couple of the devs were over 70. At a small startup in San Francisco, our senior was in his mid-50's. I can't imagine living life based on taking the safest path. It would not only be boring but wildly unfulfilling. This week I interviewed Parsity grad Nils Landsberg who learned to code at 44 and recently started a new role as a software developer after being a professor of music. Wild story. Or is it? Nils' path isn't that different than others who make a successful switch into tech. • He leveraged his personal network • He built software that solved a problem for someone else • He stayed consistent Simple? Maybe. Easy? Of course not. Link to listen in comments.	TEXT	Brian	Jenney	10,126	10,126	88	43	4	0.013332	null	2024-08-19 09:37:10	https://www.linkedin.com/feed/update/urn:li:activity:7231338419505819648
urn:li:activity:7229630369275293696	The reality of the advice you read on social media: Nearly all of it will work, but not necessarily for you. Here’s how you cut through the noise to pick out the gems in a sea of trash: - Has the person achieved the outcome you want? - Do you have anything in common with this person? - Do they seem happy? If the answer to all 3 is NO, maybe don’t take their advice. Here's some people I take advice from that maybe you'll find helpful John Crickett Alex Lau 🌻 Anna Miller Ryan Talbert Eduardo Vedes ✨ Harley Ferguson Neo Kim Nick Cosentino Zubin Pratap (my doppelgänger)	TEXT	Brian	Jenney	4,692	4,692	28	14	1	0.009165	null	2024-08-14 16:30:00	https://www.linkedin.com/feed/update/urn:li:activity:7229630369275293696
urn:li:activity:7228912680705650688	Besides being a professional yapper on LinkedIn, I also write code for cool startup that’s hiring (non-eng position) Check it out below 👇	SHARE	Brian	Jenney	2,287	2,287	13	0	0	0.005684	null	2024-08-12 16:58:09	https://www.linkedin.com/feed/update/urn:li:activity:7228912680705650688
urn:li:activity:7228769748447059968	A few years ago I crashed an app by promoting the wrong branch to production after pretending I knew what was being asked from the lead developer. 𝘛𝘩𝘦 𝘯𝘦𝘹𝘵 𝘮𝘰𝘳𝘯𝘪𝘯𝘨 𝘐 𝘸𝘢𝘭𝘬𝘦𝘥 𝘪𝘯𝘵𝘰 𝘵𝘩𝘦 𝘰𝘧𝘧𝘪𝘤𝘦 𝘢𝘯𝘥 𝘥𝘦𝘤𝘪𝘥𝘦𝘥 𝘵𝘰 𝘨𝘦𝘵 𝘣𝘦𝘵𝘵𝘦𝘳 𝘢𝘵 𝘎𝘪𝘵 𝘢𝘯𝘥 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥 𝘰𝘶𝘳 𝘤𝘰𝘮𝘱𝘢𝘯𝘺'𝘴 𝘎𝘪𝘵 𝘧𝘭𝘰𝘸. Before that, there was the triple-nested for loop that brought our real-time ordering system to a halt. 𝘐 𝘨𝘰𝘵 𝘢 𝘤𝘳𝘢𝘴𝘩 𝘤𝘰𝘶𝘳𝘴𝘦 𝘪𝘯 𝘉𝘪𝘨 𝘖 𝘵𝘩𝘢𝘵 𝘥𝘢𝘺 𝘢𝘯𝘥 𝘸𝘩𝘺 𝘤𝘰𝘥𝘦 𝘳𝘦𝘷𝘪𝘦𝘸𝘴 𝘢𝘳𝘦 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵. How could I forget the Rails project that I updated that launched 1000 emails to every customer? 𝘈 𝘴𝘪𝘮𝘱𝘭𝘦 𝘶𝘯𝘪𝘵 𝘵𝘦𝘴𝘵 𝘮𝘪𝘨𝘩𝘵 𝘩𝘢𝘷𝘦 𝘤𝘢𝘶𝘨𝘩𝘵 𝘵𝘩𝘢𝘵 𝘰𝘯𝘦. 𝘖𝘳 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥𝘪𝘯𝘨 𝘩𝘰𝘸 𝘢𝘳𝘳𝘢𝘺 𝘦𝘯𝘶𝘮𝘴 𝘸𝘰𝘳𝘬. 😅 I've made a lot of dumb mistakes over the years. I thought I was going to be fired more than a few times. I also learned a lot. At the core of these blunders was a lack of communication. I was embarrassed to admit what I didn't know and tried to hide my ignorance. Bad move. I sat down with Alex Lau, author of "𝗞𝗲𝗲𝗽 𝗖𝗮𝗹𝗺 𝗮𝗻𝗱 𝗖𝗼𝗱𝗲 𝗢𝗻" to discuss the biggest mistakes (so far) in our careers as software developers and the lessons we learned. Don't judge us... too much. Link in comments.	TEXT	Brian	Jenney	57,098	57,098	135	17	1	0.00268	null	2024-08-12 07:30:12	https://www.linkedin.com/feed/update/urn:li:activity:7228769748447059968
urn:li:activity:7227704891417223168	Creating a side project is draining. Here's my cheat sheet so you'll never run out of side project inspiration. 4 easy ways to generate quality side project ideas: 1. 𝗦𝘁𝗲𝗮𝗹 𝗳𝗿𝗼𝗺 𝗼𝘁𝗵𝗲𝗿𝘀. Check out sites like WellFound to see what small startups and 1 person businesses are building for inspiration. If they're hiring that might be a good sign the idea has some value. 2. 𝗗𝗼𝗻’𝘁 𝗯𝘂𝗶𝗹𝗱 𝗮 𝗵𝗼𝘂𝘀𝗲. 𝗔𝗱𝗱 𝗮 𝗯𝗿𝗶𝗰𝗸. Check out the feature requests or reviews for an app you’re using. What do people want? Maybe build that. 3. 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝗮𝗻 𝗔𝗣𝗜 on rapidAPI or use OpenAI (everyone’s doing it 😎) and think what you can build around it. For example, can you scrape a user’s top posts as a way to train GPT on their voice and content? 4. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗯𝗼𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝘁𝗲𝗱𝗶𝗼𝘂𝘀. Is there something at work or in your personal life that you do manually that could be automated? Spreadsheets are an easy target. Fix it for yourself and others. You also don’t need to solve anything. A great side project really only has 1 metric for success: you learned something.	TEXT	Brian	Jenney	30,327	30,327	258	17	10	0.009398	null	2024-08-09 08:58:50	https://www.linkedin.com/feed/update/urn:li:activity:7227704891417223168
urn:li:activity:7227319056956096514	Well, this is kinda weird. According to Stack Overflow's 2024 Survey, more respondents identify as students than front end developers. What gives? I don't think front end isn't dying, it's just less "front end" than it used to be. Front-end basically translates to Javascript Developer in many places. "𝘖𝘩, 𝘺𝘰𝘶 𝘬𝘯𝘰𝘸 𝘑𝘚? 𝘎𝘳𝘦𝘢𝘵, 𝘸𝘰𝘳𝘬 𝘰𝘯 𝘵𝘩𝘦 𝘕𝘰𝘥𝘦/𝘌𝘹𝘱𝘳𝘦𝘴𝘴 𝘢𝘱𝘱." "𝘙𝘶𝘩 𝘳𝘰𝘩, 𝘤𝘰𝘥𝘦 𝘱𝘪𝘱𝘦𝘭𝘪𝘯𝘦𝘴 𝘣𝘳𝘰𝘬𝘦𝘯 - 𝘤𝘢𝘯 𝘺𝘰𝘶 𝘚𝘚𝘏 𝘪𝘯𝘵𝘰 𝘵𝘩𝘦 𝘣𝘰𝘹 𝘢𝘯𝘥 𝘪𝘯𝘷𝘦𝘴𝘵𝘪𝘨𝘢𝘵𝘦?" "𝘏𝘮𝘮, 𝘵𝘩𝘢𝘵 𝘲𝘶𝘦𝘳𝘺 𝘪𝘴 𝘴𝘭𝘰𝘸. 𝘊𝘢𝘯 𝘺𝘰𝘶 𝘳𝘦𝘧𝘢𝘤𝘵𝘰𝘳?" "𝘞𝘦 𝘯𝘦𝘦𝘥 𝘢 𝘓𝘢𝘮𝘣𝘥𝘢 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯 𝘧𝘰𝘳 𝘵𝘩𝘪𝘴 𝘮𝘪𝘨𝘳𝘢𝘵𝘪𝘰𝘯. 𝘊𝘢𝘯 𝘺𝘰𝘶 𝘵𝘳𝘢𝘯𝘴𝘭𝘢𝘵𝘦 𝘵𝘩𝘪𝘴 𝘰𝘭𝘥 𝘗𝘏𝘗 𝘤𝘰𝘥𝘦 𝘵𝘰 𝘕𝘰𝘥𝘦?" You - 🙃 Oh and while you're at it.... "𝘤𝘦𝘯𝘵𝘦𝘳 𝘵𝘩𝘦 𝘦𝘧 𝘰𝘶𝘵 𝘵𝘩𝘪𝘴 𝘥𝘪𝘷" Personally, if I was super front end focused I would begin exploring fullstack JS frameworks like NextJS, Remix or at least getting familiar with Node/Express and SQL. 𝗦𝗶𝗻𝗰𝗲 𝗜 𝗹𝗶𝗸𝗲 𝘆𝗼𝘂 𝗮𝗻𝗱 𝘆𝗼𝘂'𝗿𝗲 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗮𝗯𝗼𝘃𝗲 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗶𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲, 𝗜 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗴𝗶𝘃𝗲 𝘆𝗼𝘂 𝗮 𝗡𝗼𝗱𝗲/𝗘𝘅𝗽𝗿𝗲𝘀𝘀 𝘀𝘁𝗮𝗿𝘁𝗲𝗿 𝗸𝗶𝘁 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀.	IMAGE	Brian	Jenney	16,069	16,069	102	9	3	0.007094	null	2024-08-08 07:25:40	https://www.linkedin.com/feed/update/urn:li:activity:7227319056956096514
urn:li:activity:7226952669423132672	All side projects are not created equal. I asked 3 of your favorite LinkedIn tech creators what kind of side project you should be making to be more hire-able. Here's what they said: Nick Cosentino 👇 As a hiring manager, I am personally not looking for people that launched a million dollar app with thousands of downloads -- but that’s super cool if you did that. At least from an interview perspective, 𝗜 𝗹𝗼𝗼𝗸 𝗳𝗼𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘁𝗵𝗮𝘁 𝘀𝗵𝗼𝘄 𝗺𝗲 𝘆𝗼𝘂 𝘄𝗲𝗿𝗲 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗵𝗶𝗻𝗴𝘀 𝗼𝘂𝘁 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴. 𝗜𝘁 𝘄𝗼𝘂𝗹𝗱 𝗯𝗲 𝗴𝗿𝗲𝗮𝘁 𝘁𝗼 𝗵𝗲𝗮𝗿 𝘄𝗵𝘆 𝘆𝗼𝘂 𝗽𝗶𝗰𝗸𝗲𝗱 𝘀𝗼𝗺𝗲 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗲𝘀, 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗹𝗲𝗮𝗿𝗻𝗲𝗱, why you went back to rewrite part of it, etc… I’m excited to see that you were trying to build things, struggled a bit, and had some awesome learning experiences that you can reflect on. Mauro Accorinti 👇 If you’re looking to create a project that’s sole purpose is to help you land a job, I’d say it should check three boxes. This project should help you: ✅ Get noticed and raise your chances of getting the first interview ✅ Showcase your way of thinking and how you work through a problem ✅ Learn new skills, libraries or technologies which challenge you in some way. Finally, it should help you get an interview! So choose a project that you find interesting, is a bit challenging and 𝗯𝘂𝗶𝗹𝗱 𝗶𝘁 𝗶𝗻 𝗽𝘂𝗯𝗹𝗶𝗰! Talk about it, show your work, share around the github repo and 𝗴𝗲𝘁 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 even. Use the project as an opportunity to put yourself top of mind for people looking to hire. John Crickett 👇 The ideal side project to enhance your chances of getting hired is 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗿𝗲𝗮𝗹, 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝗶𝘀 𝗰𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗿𝗲𝗮𝗹 𝘃𝗮𝗹𝘂𝗲 𝗮𝗻𝗱 𝗯𝗲𝗶𝗻𝗴 𝘂𝘀𝗲𝗱 𝗯𝘆 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗼 𝘀𝗼𝗹𝘃𝗲 𝘁𝗵𝗲𝗶𝗿 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀. 𝗧𝗵𝗲 𝘀𝗲𝗰𝗼𝗻𝗱 𝗯𝗲𝘀𝘁 𝗼𝗽𝘁𝗶𝗼𝗻 𝗶𝘀 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗮 𝗰𝗹𝗼𝗻𝗲 𝗼𝗳 𝘀𝗼𝗺𝗲 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲, i.e. the projects from Coding Challenges. Both options show you can see a project through and build something without following a tutorial.	TEXT	Brian	Jenney	21,547	21,547	100	12	15	0.005894	null	2024-08-07 07:09:46	https://www.linkedin.com/feed/update/urn:li:activity:7226952669423132672
urn:li:activity:7226608741494796288	Imagine trying to get in shape watching fitness videos on YouTube. This is what many developers end up doing. If you want to learn about promises, closures and 𝚝𝚑𝚒𝚜 then you need to get your hands dirty. Watching videos or reading can teach you what to do, but without action, the knowledge is worthless. So yes, read books, watch videos, buy that course. Then put it into action. Open up your code editor and write your own example of the concept you learned. - 𝗣𝗿𝗼𝗺𝗶𝘀𝗲-𝗶𝗳𝘆 𝗮 𝘁𝗶𝗺𝗲𝗼𝘂𝘁. - Use closure to 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗮 𝗰𝘂𝗿𝗿𝗶𝗲𝗱 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻. - 𝗨𝘀𝗲 𝗮𝗽𝗽𝗹𝘆 𝗮𝗻𝗱 𝗰𝗮𝗹𝗹 𝘁𝗼 𝗶𝗻𝘃𝗼𝗸𝗲 𝗮 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻 with a variable number of arguments. It doesn’t have to be pretty or even practical. It just has to lead you to those “aha” moments. This is where stuff starts to click.	TEXT	Brian	Jenney	7,185	7,185	73	22	2	0.0135	null	2024-08-06 08:23:07	https://www.linkedin.com/feed/update/urn:li:activity:7226608741494796288
urn:li:activity:7225147897166659585	The recipe for an amazing side project when you don’t know what to do: 1. 𝗣𝗶𝗰𝗸 𝗮𝗻 𝗔𝗣𝗜 - OpenAI, Binance, RapidAPI are the first places I’d check. 2. 𝗧𝗵𝗿𝗼𝘄 𝘁𝗵𝗶𝗻𝗴𝘀 𝗮𝘁 𝘁𝗵𝗲 𝘄𝗮𝗹𝗹 - what are the features of this API you can build something around? Perhaps a stock tracker that integrates with OpenAI to give targeted trading advice? 3. 𝗠𝗨𝗣 - what is required to 𝗯𝘂𝗶𝗹𝗱 𝘁𝗵𝗲 𝗺𝗶𝗻𝗶𝗺𝗮𝗹𝗹𝘆 𝘂𝘀𝗮𝗯𝗹𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁? Pick 1 or 2 core features. 4. 𝗦𝗸𝗲𝘁𝗰𝗵 - a white piece of paper and pen will do. 𝗗𝗿𝗮𝘄 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗺𝗮𝗶𝗻 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 𝗼𝗳 𝘁𝗵𝗲 𝗮𝗽𝗽. 𝗔𝘀𝗸 “𝗮𝗻𝗱 𝘁𝗵𝗲𝗻 𝘄𝗵𝗮𝘁?” For example, they visit your site, and then what? They click on a button and then what? 5. 𝗣𝗶𝗰𝗸 𝟭 𝗼𝗿 𝟮 𝗻𝗲𝘄 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗲𝘀 you want to learn and use them. Maybe this is your chance to learn TypeScript or Cobol. Whatevs. 6. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗶𝘁 𝗮𝗻𝗱 𝗯𝘂𝘆 𝗮 𝗱𝗼𝗺𝗮𝗶𝗻 on Route53 (or whatever) for like 15 bucks. It will look pro. Get frustrated. Pull out your hair (I don’t have this problem) and learn more than any tutorial can teach you. *** 𝘐 𝘸𝘳𝘪𝘵𝘦 𝘴𝘵𝘶𝘧𝘧 𝘧𝘰𝘳 𝘦𝘢𝘳𝘭𝘺 𝘤𝘢𝘳𝘦𝘦𝘳 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴 𝘦𝘷𝘦𝘳𝘺 𝘸𝘦𝘦𝘬𝘦𝘯𝘥. 𝘠𝘰𝘶 𝘤𝘢𝘯 𝘴𝘪𝘨𝘯 𝘶𝘱 𝘢𝘵 𝘵𝘩𝘦 Parsity 𝘴𝘪𝘵𝘦 𝘢𝘵 𝘗𝘢𝘳𝘴𝘪𝘵𝘺[𝘥𝘰𝘵]𝘪𝘰	TEXT	Brian	Jenney	15,598	15,598	152	20	14	0.011925	null	2024-08-02 07:38:15	https://www.linkedin.com/feed/update/urn:li:activity:7225147897166659585
urn:li:activity:7224777291363401729	Seriously, stop with the certificates. No one cares. If you are a dev ops engineer then by all means, get AWS certs or whatever your team requires. For the rest of you JavaScript developers out there - just stop. Learning how to deploy, roll back and automate code going from your machine out to the world is an actual skill. You can 𝗹𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗯𝗮𝘀𝗶𝗰𝘀 𝗯𝘆 𝘂𝘀𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀 𝗹𝗶𝗸𝗲 𝗚𝗶𝘁𝗛𝘂𝗯 𝗮𝗰𝘁𝗶𝗼𝗻𝘀 𝘁𝗼 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 𝗮 𝗯𝘂𝗶𝗹𝗱 𝗮𝗻𝗱 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗰𝗼𝗱𝗲 𝘁𝗼 𝗮 𝗰𝗹𝗼𝘂𝗱 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝗹𝗶𝗸𝗲 𝗔𝗪𝗦. Think through how you would rollback the code if an error happened. - How will you monitor the deployment? - What the hell does a "rollback" even mean? - What git branching strategies make sense for your team? 𝗛𝗼𝘄 𝗮𝗯𝗼𝘂𝘁 𝗳𝗼𝗿 𝗮 𝘁𝗲𝗮𝗺 𝗼𝗳 𝟭 𝗶𝗳 𝘆𝗼𝘂'𝗿𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘁𝗼 𝗰𝗼𝗱𝗲? Googling those 3 questions should lead you down some interesting rabbit holes.	TEXT	Brian	Jenney	96,606	96,606	310	43	6	0.003716	null	2024-08-01 07:05:36	https://www.linkedin.com/feed/update/urn:li:activity:7224777291363401729
urn:li:activity:7223693118171213825	William Ray didn't take my advice and it worked out pretty damn well for him. Years ago, William slid into my DMs after I posted about my struggles with addiction and crime. I waited 8 years to share this part of my life online. I was scared what others might think. I still am honestly. I projected these fears on Will. I told him to play it safe. He didn't. Will now has a successful YouTube channel, a freelancing business and I even got him to sit down and chat with me on the 𝗗𝗲𝘃𝗲𝗹𝗼𝗽 𝗬𝗼𝘂𝗿𝘀𝗲𝗹𝗳 𝗣𝗼𝗱𝗰𝗮𝘀𝘁 where 𝘄𝗲 𝘁𝗮𝗹𝗸 𝗮𝗯𝗼𝘂𝘁 𝗮𝗱𝗱𝗶𝗰𝘁𝗶𝗼𝗻, 𝗰𝗿𝗶𝗺𝗲, 𝗰𝗼𝗱𝗶𝗻𝗴 𝗯𝗼𝗼𝘁𝗰𝗮𝗺𝗽𝘀 𝗮𝗻𝗱 𝗳𝗿𝗲𝗲𝗹𝗮𝗻𝗰𝗶𝗻𝗴 𝗮𝘀 𝗮 𝗰𝗼𝗱𝗲𝗿. If you're not following him, you should. He has an inspiring story and he's one of the few freelance developers online that gives away practical advice about making your first dollar as a coder without a 9-5. If you're hiring, snatch him up. 𝘏𝘦'𝘴 𝘢 𝘝𝘶𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘣𝘶𝘵 𝘸𝘦 𝘸𝘰𝘯'𝘵 𝘩𝘰𝘭𝘥 𝘵𝘩𝘢𝘵 𝘢𝘨𝘢𝘪𝘯𝘴𝘵 𝘩𝘪𝘮 😉. https://lnkd.in/eCANr8tB	TEXT	Brian	Jenney	11,599	11,599	82	16	1	0.008535	null	2024-07-29 07:17:29	https://www.linkedin.com/feed/update/urn:li:activity:7223693118171213825
urn:li:activity:7221921496489766915	You wonder, “𝘈𝘮 𝘐 𝘴𝘶𝘱𝘱𝘰𝘴𝘦𝘥 𝘵𝘰 𝘬𝘯𝘰𝘸 𝘵𝘩𝘪𝘴?” - A new JS framework comes out. - The coding pattern you used for years becomes antiquated. - Some term gets thrown around in a meeting you’ve never heard. As a software developer, you will come face to face with the limits of your knowledge on a regular basis. An apex developer once told me to “𝘦𝘹𝘱𝘰𝘴𝘦 𝘺𝘰𝘶𝘳 𝘪𝘨𝘯𝘰𝘳𝘢𝘯𝘤𝘦, 𝘪𝘵’𝘴 𝘵𝘩𝘦 𝘰𝘯𝘭𝘺 𝘸𝘢𝘺 𝘺𝘰𝘶’𝘭𝘭 𝘭𝘦𝘢𝘳𝘯.” This was after I nodded my head through a marathon pairing session going over a particularly complex unit testing setup. I had never written a single unit test up to this point. I was too embarrassed to admit I was out of my depth. Bring up those things you don’t understand. Ideally, in a public setting so others can benefit. I guarantee your team mates are silently thanking you.	TEXT	Brian	Jenney	5,906	5,906	63	7	2	0.012191	null	2024-07-24 09:57:41	https://www.linkedin.com/feed/update/urn:li:activity:7221921496489766915
urn:li:activity:7221188030861066243	What does one of the top 1% career coaches on UpWork think about my career advice? 😅 I sat down with Megan Elizabeth Dias to get schooled on the tech job market in 2024 and what she's learned from working with hundreds of software developers at different stages in their careers. - why you might want to 𝗿𝗲-𝘁𝗵𝗶𝗻𝗸 𝘂𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 "𝗢𝗽𝗲𝗻 𝘁𝗼 𝗪𝗼𝗿𝗸" 𝗯𝗮𝗻𝗻𝗲𝗿 - 𝘀𝗵𝗮𝗿𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗚𝗶𝘁𝗛𝘂𝗯 𝗽𝗿𝗼𝗳𝗶𝗹𝗲 and when NOT to - the do's and dont's of 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗶𝗻 𝗽𝘂𝗯𝗹𝗶𝗰 - why 𝗽𝗶𝘁𝘆 𝗽𝗼𝘀𝘁𝘀 probably aren't helping your case 😬 You can listen to it here: https://lnkd.in/dw9ucb72 I always like to add the disclaimer that these opinions are... opinions. Your mileage may vary. We can only tell you what we've seen work and not work. As always - I hope you find it helpful.	TEXT	Brian	Jenney	4,158	4,158	36	5	1	0.010101	null	2024-07-22 09:23:09	https://www.linkedin.com/feed/update/urn:li:activity:7221188030861066243
urn:li:activity:7220148884159807488	3 lessons I learned after getting laid off, hired, quitting and hired again in the last couple months! 1. 𝗦𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗶𝘀 𝗮 𝗺𝘆𝘁𝗵. Can you believe that US workers actually have longer tenures now?! That being said, nothing is truly stable. I got the axe with a lot of smart peeps at a big fortune 100 company. Nothing personal, just business. 2. (𝗚𝗼𝗼𝗱) 𝗥𝗲𝗰𝗿𝘂𝗶𝘁𝗲𝗿𝘀 𝗿𝗼𝗰𝗸. I worked with some great recruiters (no I won't share their info without their consent) who helped me find opportunities quickly. They get more hate than they deserve on this platform. 3. 𝗧𝗿𝗮𝘃𝗲𝗹 𝗼𝘂𝘁𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗯𝘂𝗯𝗯𝗹𝗲. I love LinkedIn because maybe I'm a corporate shill. For my job search, I looked outside LI for the most part. Acquaintances, the site formerly known as Hired and Wellfound were places I had success. I know 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗶𝘀 𝘀𝗸𝗲𝘄𝗲𝗱 𝘁𝗼𝘄𝗮𝗿𝗱𝘀 𝗲𝘅𝘁𝗿𝗲𝗺𝗲𝘀. You either read about the person who filled 1000 applications with zero response or the dude who got accepted to Google or founded their next startup. The reality is somewhere in the middle. I break down the lessons that are fresh in my mind from this recent job search with some action you can take: https://lnkd.in/gjXeNh-y Always hope you find it helpful.	TEXT	Brian	Jenney	19,019	19,019	111	6	0	0.006152	null	2024-07-19 12:33:57	https://www.linkedin.com/feed/update/urn:li:activity:7220148884159807488
urn:li:activity:7219352034779512832	LinkedIn or Twitter fame is a silly goal if you’re building in public to land a role. Your real goal is to demonstrate technical depth and showcase your work. You want the right eyes on your profile. You don’t want sympathy for the 1000th rejection you’ve had (or maybe you do, I dunno actually) Instead of fishing for likes, try writing about: - a hairy bug you squished - your deployment strategy - how you’re handling QA - why some obscure library is really helpful - your take on React Server Components If you’re really feeling brave, post a code snippet, seek feedback and watch how anyone who ever wrote a line of code becomes an expert on how you can optimize a for loop 😅 If you're sick of trying to figure out the LinkedIn "game" on your own and feeling stuck - check out John Crickett's upcoming program for building a brand on LinkedIn. He's a guy I s̶t̶e̶a̶l̶ learn from all the time	TEXT	Brian	Jenney	23,472	23,472	166	20	4	0.008095	null	2024-07-17 07:47:34	https://www.linkedin.com/feed/update/urn:li:activity:7219352034779512832

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.