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:7219009049151877121	Is copy/pasting really so bad? Honestly, it’s how I’ve survived over the years as a developer. Every new workplace where I went and every contract I completed, I took note of what the smarter developers were doing. - what books had they read? - I read their pull requests, even when I wasn’t the reviewer. - I copied their styles for writing tests, React components and backend code. - I asked how they investigated and debugged critical issues. - I imitated their mannerisms and studied how they spoke in meetings. I’ve been lucky. I copied from the right people at some amazing companies and worked with developers who I truly think might be genius. You don’t have to get lucky though. Nowadays, through LinkedIn, open source and the University of YouTube, you have the ability to learn from other amazing developers and copy what makes sense to you. 𝘐 𝘨𝘰𝘵 𝘵𝘰 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸 𝘰𝘯𝘦 𝘰𝘧 𝘮𝘺 𝘧𝘢𝘷𝘰𝘳𝘪𝘵𝘦 𝘠𝘰𝘶𝘛𝘶𝘣𝘦 𝘱𝘳𝘰𝘧𝘦𝘴𝘴𝘰𝘳𝘴 𝘳𝘦𝘤𝘦𝘯𝘵𝘭𝘺, Jack 🤔 Herrington 𝘰𝘯 𝘵𝘩𝘦 𝘋𝘦𝘷𝘦𝘭𝘰𝘱 𝘠𝘰𝘶𝘳𝘴𝘦𝘭𝘧 𝘗𝘰𝘥𝘤𝘢𝘴𝘵 (𝘭𝘪𝘯𝘬 𝘪𝘯 𝘱𝘳𝘰𝘧𝘪𝘭𝘦 😉)	TEXT	Brian	Jenney	15,826	15,826	71	18	1	0.005687	null	2024-07-16 09:04:39	https://www.linkedin.com/feed/update/urn:li:activity:7219009049151877121
urn:li:activity:7218634891528134659	"𝘛𝘩𝘪𝘴 𝘪𝘴 𝘢 𝘵𝘦𝘳𝘳𝘪𝘣𝘭𝘦 𝘵𝘢𝘬𝘦 𝘰𝘯 𝘵𝘩𝘦 𝘫𝘰𝘣 𝘮𝘢𝘳𝘬𝘦𝘵. 𝘠𝘰𝘶 𝘰𝘣𝘷𝘪𝘰𝘶𝘴𝘭𝘺 𝘥𝘰𝘯'𝘵 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘺𝘰𝘶'𝘳𝘦 𝘵𝘢𝘭𝘬𝘪𝘯𝘨 𝘢𝘣𝘰𝘶𝘵." Maybe getting on YouTube wasn't a great idea. I recently dropped a video with some advice I think might be helpful for people trying to break into tech and it received more negative comments than any other video I've done. 𝗜𝘁'𝘀 𝗯𝗼𝗿𝗶𝗻𝗴 𝘀𝘁𝘂𝗳𝗳 𝗵𝗼𝗻𝗲𝘀𝘁𝗹𝘆: tips for your resume, LinkedIn, GitHub and how to get more experience when you have none: - 𝗱𝗼𝗻'𝘁 𝘀𝗵𝗮𝗿𝗲 𝘆𝗼𝘂𝗿 𝗚𝗶𝘁𝗛𝘂𝗯 𝗶𝗳 𝘁𝗵𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗱𝗼𝗻'𝘁 𝗹𝗼𝗼𝗸 𝗴𝗼𝗼𝗱 and you don't have to OR create some things you're proud of - 𝗿𝗲𝗺𝗼𝘃𝗲 𝗮𝗻𝘆 𝗺𝗲𝗻𝘁𝗶𝗼𝗻𝘀 𝗼𝗳 "𝗮𝘀𝗽𝗶𝗿𝗶𝗻𝗴" 𝗼𝗿 "𝗷𝘂𝗻𝗶𝗼𝗿" from your profile - no experience? get some by 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝘀𝗶𝘁𝗲 𝗳𝗼𝗿 𝗳𝗿𝗲𝗲 (𝗼𝗿 𝗮 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻) if you have to - understand your timeline will be different from others I'm beginning to think some people have a problem for every solution.	TEXT	Brian	Jenney	43,988	43,988	70	28	0	0.002228	null	2024-07-15 08:17:53	https://www.linkedin.com/feed/update/urn:li:activity:7218634891528134659
urn:li:activity:7217526060370808832	Front end development stopped being easy a while ago. It’s a lot less: - Move this a few px to the right. -Make this button a little greener. - Sprinkle a little JS to submit this form. - Translate this design to HTML and CSS. It’s a lot more: - Decrease the initial page load! - Oh, you know JS? Can you help debug this lambda function written in NodeJS? - SSG vs CSR vs SSR. - Who’s on-call to investigate the code pipeline being broken?! - Move this a few px to the right 😉. LinkedIn hates videos but I like 'em. If you're interested in React Server Components (RSCs) check this out 👇	VIDEO	Brian	Jenney	11,957	4,643	148	19	4	0.014301	null	2024-07-12 06:51:47	https://www.linkedin.com/feed/update/urn:li:activity:7217526060370808832
urn:li:activity:7217157136299040768	4 developers I mentor or graduated from Parsity recently got hired. Now the real work begins: - Exploring a new codebase - Finding areas to make impact - Learning the engineering culture and the boatload of jargon (CI/CD, TDD, SDLC, story points, sprints) - Figuring out JIRA and the team's flavor of agile - Using git… but like, for real this time - Doing on-call 👹 I’m beginning to think this is the area where developers need the most support. The job search is stressful for sure but it makes up such a small portion of the developer life-cycle. You won’t be spending your days optimizing algorithms or manipulating palindromes. The part after the interview is when the real work begins. If you’re a recently hired developer, what are some areas where you wish you had more knowledge?	TEXT	Brian	Jenney	17,080	17,080	113	19	1	0.007787	null	2024-07-11 06:25:49	https://www.linkedin.com/feed/update/urn:li:activity:7217157136299040768
urn:li:activity:7216525896097124352	What you thought the interview was going to be: - traverse this tree - link this list... but backwards! - optimize Djikstra - buy and sell these stocks! What you got: - why do you want to work here? - tell me about a time when... - how many duplicates in this string? - any questions for me? Tomorrow I want to go over some strategies to do before/after/during the interview for non-FAANG companies. This is based on my experience doing over 100 interviews, bombing too many to count, getting on site to your most loved (or most hated) companies and speaking with over 500 developers across the globe. I hope you find it useful and I'm not even selling anything! Will record and send in my newsletter which you can find at Parsity[dot]io 😎	EVENT	Brian	Jenney	10,001	10,001	43	5	3	0.005099	null	2024-07-09 12:37:30	https://www.linkedin.com/feed/update/urn:li:activity:7216525896097124352
urn:li:activity:7216065652346769408	My tech interview 10 years ago: - Why do you want to work here? - Y u no have CS degree? - LeetCode easy or coding trivia - In person lunch to make sure you’re not crazy - 💰 My most recent tech interviews: - Pair programming with screen share - Automated code challenge (LeetCode medium+) - Take home assignment that takes way too long - Tell me about a technically complex project you did recently… - Design some wildly complex system neither of us know how to build 🙄 - Let’s have 12 rounds spread out over 2 months because we don’t trust ourselves - 😅 Interviews are a game and they are winnable. What’s great about tech interviews is that they’re standardized for the most part. The small startup in SF will use a similar format to the tech company in Austin. Use this to your advantage and make sure you know your audience, research by any means necessary and maybe just cheat if all else fails. Just kidding… or am I? I sat down with the interview champion, Bhupinder Singh to get his takes on how to beat the interview, creating portfolios for bootcamp grads that don't suck and standing out as an early career developer. You can listen here https://lnkd.in/gCPnQw-H	TEXT	Brian	Jenney	24,677	24,677	77	12	1	0.003647	null	2024-07-08 06:08:39	https://www.linkedin.com/feed/update/urn:li:activity:7216065652346769408
urn:li:activity:7214995890095153152	Unit tests are a waste of time. Instead of taking minutes to write a test you can just: - write your code - manually replicate all the scenarios you want to test - pray for the best and have your QA team ensure it all works Now that it works, don't touch it! 😅 𝗪𝗵𝗲𝗻 𝗱𝗼𝗻𝗲 𝗰𝗼𝗿𝗿𝗲𝗰𝘁𝗹𝘆: - tests enable refactoring with confidence - confirm edge cases - document the ACTUAL functionality (I know your docs suck) 🤫 Oddly enough, most bootcamps skip any mention of unit testing even though most dev teams write loads of tests. Follow along with the super short video below to write your first unit test with Jest and learn the basics of testing.	VIDEO	Brian	Jenney	12,413	4,783	158	17	12	0.015065	null	2024-07-05 07:17:48	https://www.linkedin.com/feed/update/urn:li:activity:7214995890095153152
urn:li:activity:7213532867325308928	This is me at 29. Drunk, overweight and criminal. Now, I'm 40. Sober, 25 pounds lighter and a hell of a lot happier. Here's a breakdown of what I learned along the way: 𝗠𝗼𝗱𝗲𝗿𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗮 𝗺𝘆𝘁𝗵. - Getting sober, getting in shape and learning to code took more effort than I imagined. Way more. Sometimes you can work smarter and sometimes you just need to work harder. 𝗥𝗼𝘂𝘁𝗶𝗻𝗲𝘀 𝗮𝗿𝗲𝗻’𝘁 𝗯𝗼𝗿𝗶𝗻𝗴 - 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗸𝗲𝘆 𝘁𝗼 𝗳𝗿𝗲𝗲𝗱𝗼𝗺. - I wake up and do the same damn thing most days. My routine is my rock in a chaotic world. It’s how I make time when there is none. 𝗕𝗮𝗱 𝗹𝘂𝗰𝗸 𝗶𝘀 𝗰𝗼𝗻𝘁𝗮𝗴𝗶𝗼𝘂𝘀. 𝗦𝗼 𝗶𝘀 𝗴𝗼𝗼𝗱 𝗹𝘂𝗰𝗸. - I stay away from negative people, social media accounts and news. Pessimists are rampant and they’re often right. Optimists are happy and often successful.	IMAGE	Brian	Jenney	26,094	26,094	249	47	0	0.011344	null	2024-07-01 06:25:56	https://www.linkedin.com/feed/update/urn:li:activity:7213532867325308928
urn:li:activity:7212465424255344641	Stuck on what to build for your next side project? Here’s the process I’ve been using for years to learn everything from Typescript to AWS Lambdas: 1. 𝗣𝗶𝗰𝗸 𝗮𝗻 𝗔𝗣𝗜 - this is important, you need some external data or functionality in order to build something interesting or you’ll be mostly stuck with TODO or clone apps - 𝗨𝘀𝗲 𝗣𝗼𝘀𝘁𝗺𝗮𝗻 or some other http client to test the API and make sure it’s worthwhile - If the API is not free, 𝗰𝗼𝗻𝘀𝗶𝗱𝗲𝗿 𝗵𝗼𝘄 𝘆𝗼𝘂 𝗺𝗶𝗴𝗵𝘁 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗰𝗮𝗰𝗵𝗶𝗻𝗴 to limit requests 2. 𝗦𝗰𝗮𝗳𝗳𝗼𝗹𝗱 𝗼𝘂𝘁 𝘁𝗵𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 of the app - what is the first page a user lands on? What happens when they click a button? Where is data stored? 3. Begin building using the new technology/language you want to learn 𝗬𝗼𝘂 𝘄𝗶𝗹𝗹 𝗴𝗲𝘁 𝘀𝘁𝘂𝗰𝗸. This is kinda what you want. Google, ChatGPT and Stack Overflow through roadblocks. This will be a messy affair but you will learn a ton.	TEXT	Brian	Jenney	11,903	11,903	92	16	4	0.009409	null	2024-06-28 07:42:38	https://www.linkedin.com/feed/update/urn:li:activity:7212465424255344641
urn:li:activity:7212190269708861441	Help! I have a podcast where I talk about learning to code, career development and technical advice for early career developers. Here's the thing: it's been a decade since I first learned to code. Right now, I'm struggling with running a business and my career direction as a technical person in people management. These are exciting problems to solve but they're much different than what I assume can benefit my audience. If you're reading this, chances are you're my target demographic and you might even be good looking to boot! 𝗣𝗹𝗲𝗮𝘀𝗲 𝗹𝗲𝗮𝘃𝗲 𝗮 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗜 𝘀𝗵𝗼𝘂𝗹𝗱 𝗮𝗻𝘀𝘄𝗲𝗿 𝗼𝗻 𝘁𝗵𝗲 𝘀𝗵𝗼𝘄 𝗮𝗻𝗱 𝗶𝗳 𝗜 𝗰𝗵𝗼𝗼𝘀𝗲 𝗶𝘁 - 𝗜'𝗹𝗹 𝘀𝗵𝗼𝘂𝘁 𝘆𝗼𝘂 𝗼𝘂𝘁! (if you wanna remain anonymous just use a 😎 emoji)	IMAGE	Brian	Jenney	4,602	4,602	37	11	0	0.01043	null	2024-06-27 13:29:16	https://www.linkedin.com/feed/update/urn:li:activity:7212190269708861441
urn:li:activity:7211726722436595712	6 services I've used to improve my skills as a software engineer. Anything out there I missed?	VIDEO	Brian	Jenney	9,673	3,219	96	7	10	0.011682	null	2024-06-26 06:47:18	https://www.linkedin.com/feed/update/urn:li:activity:7211726722436595712
urn:li:activity:7211393789599305728	5 of my biggest regrets about my coding career(so far): 1. 𝗦𝘁𝗶𝗰𝗸𝗶𝗻𝗴 𝘁𝗼 𝗝𝗦 𝗳𝗼𝗿 𝘁𝗼𝗼 𝗹𝗼𝗻𝗴. It’s easy to get started with and a highly employable language. Learning Rust has opened my eyes to how easy I’ve had it working with such a high level language. 2. 𝗕𝗲𝗶𝗻𝗴 𝘁𝗼𝗼 𝗴𝗼𝗼𝗱 𝗳𝗼𝗿 𝗖𝗦𝗦. I took some kind of sick pride in not being very skilled at CSS. If you’re working on the front end - you need to have some respect for it. Users expect and depend on accessible, decent-looking sites. 3. 𝗟𝗲𝘁𝘁𝗶𝗻𝗴 𝗺𝘆 𝘄𝗼𝗿𝗸 𝘀𝗽𝗲𝗮𝗸 𝗳𝗼𝗿 𝗶𝘁𝘀𝗲𝗹𝗳. Naive at best. This was really an excuse to cover up the fact I was scared and insecure to speak up or share ideas. When I started speaking, my career really accelerated. 4. 𝗡𝗼𝘁 𝘁𝗮𝗸𝗶𝗻𝗴 𝗼𝗽𝘁𝗶𝗰𝘀 𝘀𝗲𝗿𝗶𝗼𝘂𝘀𝗹𝘆. No one would call me a fashion icon. 𝗜 𝘄𝗲𝗮𝗿 𝘀𝗶𝗹𝗹𝘆 𝗻𝗲𝗼𝗻 𝘀𝘄𝗲𝗮𝘁𝘀𝗵𝗶𝗿𝘁𝘀 and don’t take myself too seriously. This works well in developer circles but 𝘁𝗵𝗲 𝗷𝗼𝗸𝗲 𝗱𝗼𝗲𝘀𝗻’𝘁 𝘁𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗲 𝘄𝗲𝗹𝗹 𝘁𝗼 𝗽𝗲𝗼𝗽𝗹𝗲 𝗼𝘂𝘁𝘀𝗶𝗱𝗲 𝘁𝗲𝗰𝗵. Every book I’ve read on the subject of impressing others gives this advice: 𝗱𝗿𝗲𝘀𝘀 𝗮 𝗹𝗶𝘁𝘁𝗹𝗲 𝗻𝗶𝗰𝗲𝗿 𝘁𝗵𝗮𝗻 𝘁𝗵𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗴𝗿𝗼𝘂𝗽 to give an air of authority. I’m trying this right now - will let you know how it goes. 5. 𝗕𝗲𝗶𝗻𝗴 𝗮 𝗰𝗼𝗱𝗲𝗿. Writing code is cool. Understanding business problems and finding ways to make businesses more money through code is cooler. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗶𝘀 𝘄𝗼𝘂𝗹𝗱’𝘃𝗲 𝘀𝗮𝘃𝗲𝗱 𝗺𝗲 𝗳𝗿𝗼𝗺 𝗮 𝗳𝗲𝘄 𝗳𝗮𝗶𝗹𝗲𝗱 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗲𝘀 and given me more direction on where to spend my energy as a manager and coder. I’ll have many more regrets in the future but that’s what makes life interesting right? Right? 😅	TEXT	Brian	Jenney	15,010	15,010	171	22	1	0.012925	null	2024-06-25 08:44:20	https://www.linkedin.com/feed/update/urn:li:activity:7211393789599305728
urn:li:activity:7211002063919403008	Everyone is telling you to just do freelance as a web dev. If only it were that simple. I've done quite a lot of contract work over the years without ever using UpWork, Fiverr or any freelance site. A few students at Parsity have supplemented their own experience with freelance jobs. When I ask them about their approach, I see a lot similarities with what has worked for me: 1. 𝗦𝘁𝗮𝗿𝘁 𝗹𝗼𝗰𝗮𝗹. Find a friend, business or organization that needs a site. If you can't think of one, 𝗱𝗼 𝗮 𝗚𝗼𝗼𝗴𝗹𝗲 𝘀𝗲𝗮𝗿𝗰𝗵 𝗳𝗼𝗿 𝗯𝗿𝗶𝗰𝗸 𝗮𝗻𝗱 𝗺𝗼𝗿𝘁𝗮𝗿 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗲𝘀 like child care centers, dentists or podiatrists and check out their sites. If they don't exist or if they suck - 𝗰𝗮𝗹𝗹 𝘁𝗵𝗲𝗺 𝗮𝗻𝗱 𝗺𝗮𝗸𝗲 𝘁𝗵𝗲𝗺 𝗮𝗻 𝗼𝗳𝗳𝗲𝗿. 2. 𝗦𝗲𝗹𝗹 𝘁𝗵𝗲 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻, 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘁𝗲𝗰𝗵. Businesses like money. 𝗛𝗼𝘄 𝗰𝗮𝗻 𝘆𝗼𝘂 𝘂𝘀𝗲 𝘆𝗼𝘂𝗿 𝘀𝗸𝗶𝗹𝗹𝘀 𝗮𝘀 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝘁𝗼 𝗯𝗿𝗶𝗻𝗴 𝘁𝗵𝗲𝗺 𝗺𝗼𝗿𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀? Will a new site do that? Can you improve the layout or content? Can you add functionality like appointment booking or payment processing? 3. 𝗚𝗲𝘁 𝗽𝗮𝗶𝗱 𝗶𝗻 𝗿𝗲𝗳𝗲𝗿𝗿𝗮𝗹𝘀. When you're starting off, it might be hard to gain trust or have the confidence to charge 1k for a 3 -5 page site. 𝗕𝘂𝗶𝗹𝗱 𝗳𝗼𝗿 𝗳𝗿𝗲𝗲 𝗶𝗻 𝗲𝘅𝗰𝗵𝗮𝗻𝗴𝗲 𝗳𝗼𝗿 𝗮 𝘀𝗶𝗻𝗰𝗲𝗿𝗲 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻. Then never work for free again. One summer, as a 37 year old senior software engineer, I did 100 cold calls for my buddy's business so I could learn sales. It was draining, uncomfortable and I dreaded it. I learned a ton. If you don't have experience, you got to get it somehow.	TEXT	Brian	Jenney	11,692	11,692	109	21	8	0.011803	null	2024-06-24 06:47:45	https://www.linkedin.com/feed/update/urn:li:activity:7211002063919403008
urn:li:activity:7210330249199255554	Outside of FAANG interviews, I have NEVER been asked to traverse a tree or reverse a linked list. I did however once get asked to create a snake game with HTML, CSS and JS. I'm not sure how related it was to the role but it was pretty fun. 😅 Because I like you and you're probably a nerd if you're reading this - I've created a partially done version of the snake game for you to complete. It's missing functionality within the the TODOs in the comments. If you figure out the problem and post it - please tag me! https://lnkd.in/gbvu3gV6	IMAGE	Brian	Jenney	13,147	13,147	69	23	1	0.007074	null	2024-06-22 10:18:12	https://www.linkedin.com/feed/update/urn:li:activity:7210330249199255554
urn:li:activity:7209629445219913729	I'm not teaching my kids how to code. Not because I think that AI will take all the jobs or that the industry is too volatile. I think the exact opposite actually. The reason I'm not teaching them to code is simply because they have other interests. I enjoy this career and highly recommend it. I also don't have a lot to compare it to. 𝗢𝘃𝗲𝗿 𝗮 𝗱𝗲𝗰𝗮𝗱𝗲 𝗮𝗴𝗼 𝗺𝘆 𝗹𝗶𝗳𝗲 𝘄𝗮𝘀 𝗶𝗻 𝗮 𝘁𝗮𝗶𝗹𝘀𝗽𝗶𝗻. I was addicted, unhappy and barely getting by. It feels like a lifetime has passed since then. My oldest son just graduated high school and I thought about the advice I'd give him if he DID want to pursue a career in software. It's not much different than the advice I've told him about pursuing a design career: 1. 𝗙𝗶𝗻𝗱 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝘄𝗵𝗼 𝗵𝗮𝘀 "𝗺𝗮𝗱𝗲 𝗶𝘁" 𝗮𝗻𝗱 𝗴𝗲𝘁 𝘁𝗵𝗲𝗶𝗿 𝗮𝗱𝘃𝗶𝗰𝗲/𝗺𝗲𝗻𝘁𝗼𝗿𝘀𝗵𝗶𝗽. Pay them or work for free so you're both invested. 2. 𝗗𝗼 𝘀𝗼𝗺𝗲 𝗳𝗿𝗲𝗲 𝘄𝗼𝗿𝗸 for someone else and get recommendations. 3. 𝗙𝗶𝗻𝗱 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗵𝗼 𝗮𝗿𝗲 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼 𝗱𝗼 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗮𝗿𝗲 doing and steal what works for them. 4. 𝗦𝗵𝗮𝗿𝗲 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂'𝗿𝗲 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗼𝗻 in public to attract people who can offer guidance or opportunity. 5. 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗮𝗿𝘁 𝗼𝗳 𝘀𝗲𝗹𝗹𝗶𝗻𝗴 𝗮𝗻𝗱 𝗵𝗼𝘄 𝘁𝗼 𝘀𝗽𝗲𝗮𝗸 𝗹𝗶𝗸𝗲 𝗮𝗻 𝗮𝘂𝘁𝗵𝗼𝗿𝗶𝘁𝘆. Read books on this stuff, it's learnable and can only help no matter what you do. I break down the advice I'd give him or anyone looking to break into software in this episode here: https://lnkd.in/g-2g4qEe and I hope it's helpful.	IMAGE	Brian	Jenney	24,987	24,987	186	23	1	0.008404	null	2024-06-20 11:53:28	https://www.linkedin.com/feed/update/urn:li:activity:7209629445219913729
urn:li:activity:7209270665051271168	You won't get better at React/JS/TS/whatevs from watching someone else type. You might get better by doing this however 👇	VIDEO	Brian	Jenney	8,444	2,788	95	9	3	0.012672	null	2024-06-19 12:07:48	https://www.linkedin.com/feed/update/urn:li:activity:7209270665051271168
urn:li:activity:7208912746719903744	The job search can feel unrewarding, draining and shake what little confidence you have in yourself. It’s a game of both skill and chance. You can be absolutely qualified and still “fail”. Rejection is rarely personal, it’s an inevitable consequence of many factors: - 𝗥𝗲𝘀𝘂𝗺𝗲 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗶𝘀 𝘀𝘂𝗯𝗷𝗲𝗰𝘁𝗶𝘃𝗲 (ask 5 people to look at your resume and get 5 different opinions) - Some 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗵𝗶𝗿𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗮𝗹 𝗰𝗮𝗻𝗱𝗶𝗱𝗮𝘁𝗲𝘀 but open roles to the public with 0 intention of hiring - 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗰𝗮𝗻 𝗯𝗲 𝗯𝗶𝗮𝘀𝗲𝗱 in favor of a specific answer even when presented with working (or even better) alternatives So what does this mean? - Expect failure and learn from it. - Try your hardest not to take it personally. Whatever you do, please do not stop playing the game. You only have to win once.	TEXT	Brian	Jenney	7,751	7,751	88	6	1	0.012256	null	2024-06-18 12:36:18	https://www.linkedin.com/feed/update/urn:li:activity:7208912746719903744
urn:li:activity:7208499870192603139	I bombed the interview so hard, I considered just walking out. In my second round at the Google onsite 7 years ago, my interviewer was visibly frustrated. I was bumbling through a tree traversal problem using a for loop 🙄. "𝘛𝘩𝘪𝘴 𝘪𝘴 𝘸𝘩𝘺 𝘸𝘦 𝘥𝘰𝘯'𝘵 𝘶𝘴𝘶𝘢𝘭𝘭𝘺 𝘩𝘪𝘳𝘦 𝘴𝘦𝘭𝘧-𝘵𝘢𝘶𝘨𝘩𝘵 𝘥𝘦𝘷𝘴", he said before he took over and showed me how he would've approached the problem. Let me be clear: this guy was an ass hat of the highest degree. He also exposed a major gap in my coding knowledge. I went on to spend lots of money on programs, books and courses to learn data structures and algorithms. This helped me pass a ton more interviews but also increased my confidence. 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴 𝘁𝗵𝗼𝘂𝗴𝗵: 99% of the technical interview advice you read is for the top 1% of companies. I just left the interview circuit and have spoken with 500 developers over the last 18 months. I also completed around 100 interviews over the last 10 years. Your next interview is much more likely to revolve around building a React component, talking about your past experiences and coding challenges that will involve arrays or strings rather than trees. I talk about how to prepare for the interviews for the 99% of companies outside FAANG here: https://lnkd.in/gRqHXib6	TEXT	Brian	Jenney	2,873,799	2,873,801	1,228	123	14	0.000475	null	2024-06-17 09:04:56	https://www.linkedin.com/feed/update/urn:li:activity:7208499870192603139
urn:li:activity:7207387406784733184	When I learned about this debugging "trick" it changed the way I investigated issues in my JS code. It's odd that I see so few people using this method but hopefully it makes your life a little easier as you crank out bugs.	VIDEO	Brian	Jenney	5,705	2,055	63	15	0	0.013672	null	2024-06-14 07:24:24	https://www.linkedin.com/feed/update/urn:li:activity:7207387406784733184
urn:li:activity:7207029362993295363	You want to build an amazing side project but you don’t know where to start. ❌ TODO app? ❌ Clone of that other app that you use? ❌ Tutorial project? When I’m not sure what I want to build, I do this: - 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗱𝗮𝘁𝗮 - what API can you use which may have some interesting information? - 𝗨𝘀𝗲 𝗮 𝘁𝗼𝗼𝗹 𝗹𝗶𝗸𝗲 𝗣𝗼𝘀𝘁𝗺𝗮𝗻 𝘁𝗼 𝗲𝗻𝘀𝘂𝗿𝗲 𝘁𝗵𝗲 𝗔𝗣𝗜 𝗶𝘀 𝘄𝗼𝗿𝘁𝗵𝘄𝗵𝗶𝗹𝗲 and accessible - 𝗪𝗵𝗮𝘁 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 𝗰𝗮𝗻 𝘆𝗼𝘂 𝗰𝗼𝗻𝘀𝘁𝗿𝘂𝗰𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝘁𝗵𝗲 𝗔𝗣𝗜? For example, a real time stock API could be used to trigger an alert to a user when it dips below a certain threshold - Figure out the 𝗺𝗶𝗻𝗶𝗺𝗮𝗹 𝗮𝗺𝗼𝘂𝗻𝘁 𝗼𝗳 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 - 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝘂𝘀𝗲𝗿 𝗳𝗹𝗼𝘄? What happens when a user goes to your app? What is the feature they interact with and how is the data surfaced? - Pick a combination of new and familiar technologies - Get stuck, read the docs and 𝗯𝘂𝗶𝗹𝗱 𝘆𝗼𝘂𝗿 𝘄𝗮𝘆 𝗼𝘂𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗵𝗼𝗹𝗲 𝘆𝗼𝘂’𝘃𝗲 𝗱𝘂𝗴 😅 - Gain more practical knowledge than a 100 hour course could ever offer you	TEXT	Brian	Jenney	11,299	11,299	132	22	6	0.014161	null	2024-06-13 07:41:40	https://www.linkedin.com/feed/update/urn:li:activity:7207029362993295363
urn:li:activity:7206328329593888769	I got paid a total of 0 dollars from doing 500 calls with software developers over the last 18 months. It was a great investment. I learned about what many of you are struggling with, met some amazing people, got some of you unstuck and a few of you even became customers of mine. As much as I’d like to continue these calls, I know there’s a better way to reach more people and I just don’t know how to do it yet. What do you suggest?	IMAGE	Brian	Jenney	21,423	21,423	76	27	0	0.004808	null	2024-06-11 09:16:00	https://www.linkedin.com/feed/update/urn:li:activity:7206328329593888769
urn:li:activity:7205954993273643009	The problem with 99% of the technical interview advice you read is that it applies to the top 1% of companies out there. I spoke with over 500 developers in the last couple years and now own an online coding school, Parsity where we’ve rolled out mock interviews which reflect the reality of the non-tech job market. 𝗛𝗲𝗿𝗲’𝘀 𝟰 𝘁𝘆𝗽𝗲𝘀 𝗼𝗳 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗜 𝘀𝗲𝗲 𝗼𝘃𝗲𝗿-𝗿𝗲𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗲𝗱 𝗳𝗼𝗿 𝘄𝗲𝗯 𝗱𝗲𝘃 𝗿𝗼𝗹𝗲𝘀: - 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 😅 - code challenges using 2 pointers, sliding window and array manipulation I’ve also met developers who accepted offers after no technical screening at all! This has happened to me at least twice. While you’re pounding LeetCode, don’t forget to have some answers in your back pocket for questions like “𝘵𝘦𝘭𝘭 𝘮𝘦 𝘢𝘣𝘰𝘶𝘵 𝘺𝘰𝘶𝘳𝘴𝘦𝘭𝘧?” or “𝘸𝘩𝘺 𝘥𝘰 𝘺𝘰𝘶 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘩𝘦𝘳𝘦?” Also - when in doubt, just say "𝘐'𝘥 𝘶𝘴𝘦 𝘢 𝘩𝘢𝘴𝘩 𝘮𝘢𝘱 𝘵𝘰 𝘴𝘱𝘦𝘦𝘥 𝘶𝘱 𝘵𝘩𝘦 𝘳𝘶𝘯 𝘵𝘪𝘮𝘦!" You'll probably be right 47% of the time 🤷. Good luck out there.	TEXT	Brian	Jenney	17,726	17,726	95	21	3	0.006713	null	2024-06-10 08:32:30	https://www.linkedin.com/feed/update/urn:li:activity:7205954993273643009
urn:li:activity:7204539407033335811	Grinding LeetCode !== Learning DSA Most of your interviews won't involve trees, recursion or a whiteboard. You should still learn these things. Here's how I went from zero to 🌲 in O(n). I write to developers once per week about career, coding and sucking less at software: https://lnkd.in/gmEZY7K8	VIDEO	Brian	Jenney	29,603	13,249	211	14	9	0.007905	null	2024-06-06 10:47:28	https://www.linkedin.com/feed/update/urn:li:activity:7204539407033335811
urn:li:activity:7204494058562437123	The interview started before you made it to the interview. You turn on the camera to get prepared for the technical screening. You spend 15 minutes on “tell me about yourself” and the interviewer is too polite to cut you off. 𝗡𝗼𝘄 𝘁𝗵𝗲 𝗥𝗘𝗔𝗟 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗯𝗲𝗴𝗶𝗻𝘀. - You studied how to detect palindromes and common DSA. - The problem is to create a React component 😐 - You didn’t set up VS Code so you bumble around and run 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙 to get something to begin. - In the remaining 30 minutes you struggle with your system settings to disable Co-Pilot and write some decent code but can’t quite get the last piece of the puzzle. - With 5 minutes left, the interviewer invites you to ask any questions but you don't have one... 😬 𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱: - 𝗔𝘀𝗸 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗽𝗿𝗲𝗽𝗮𝗿𝗲 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 and what kind of problem you will be asked - 𝗨𝘀𝗲 𝗖𝗼𝗱𝗲𝗣𝗲𝗻 𝗼𝗿 𝗖𝗼𝗱𝗲𝗦𝗮𝗻𝗱𝗯𝗼𝘅 to quickly scaffold an environment - 𝗞𝗲𝗲𝗽 𝘁𝗵𝗲 𝗰𝗵𝗶𝘁-𝗰𝗵𝗮𝘁 𝘁𝗼 𝗮 𝗺𝗶𝗻𝗶𝗺𝘂𝗺 during a tech screen to get to the real problem - 𝗛𝗮𝘃𝗲 𝗮 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝗼𝗿 𝟮 prepared to ask when it’s over - Do some pushups or a walk around the block to 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝘀𝗼𝗺𝗲 𝗻𝗲𝗿𝘃𝗼𝘂𝘀 𝗲𝗻𝗲𝗿𝗴𝘆. Good luck. I write to who want to accelerate their careers once per week here: https://lnkd.in/gmEZY7K8	TEXT	Brian	Jenney	8,610	8,610	76	8	2	0.009988	null	2024-06-06 07:47:16	https://www.linkedin.com/feed/update/urn:li:activity:7204494058562437123
urn:li:activity:7203811513592168450	There is a limit to the return on your technical ability. I don't think every developer needs to be a mini-influencer but learning how to communicate your ideas is a suspiciously underrated skill in tech. Public speaking goes from a nice-to-have to a must-have the higher up the engineering ladder you climb. You don't have to wait to start practicing this skill. I break down 3 tactics I used to go from shy, quiet developer to a less-shy, vocal developer.	ARTICLE	Brian	Jenney	3,251	3,251	25	5	1	0.009536	null	2024-06-04 10:35:05	https://www.linkedin.com/feed/update/urn:li:activity:7203811513592168450
urn:li:activity:7203780857063510018	After nearly 4 years at Clorox, I was laid off. The same month I was laid off, I secured an offer at a new company. Here's 3 lessons from getting laid off and hired in the same month: 1. 𝗕𝗲𝗵𝗮𝘃𝗶𝗼𝗿𝗮𝗹 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗮𝗿𝗲 𝗲𝗾𝘂𝗮𝗹𝗹𝘆 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗮𝘀 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀: Between coding challenges and take home assignments, I prepared a list of technical stories from my work experience, to answer the most common behavioral questions that I've been asked over and over again. 2. 𝗦𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗶𝘀 𝗮 𝗺𝘆𝘁𝗵. Our entire org got axed at a big, stable, non-tech company. There is no where to hide nowadays. Tech is not the only industry affected by layoffs and economic instability. 3. 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 ≠ 𝗿𝗲𝗮𝗹𝗶𝘁𝘆. Most of my opportunities came from outside LinkedIn. Some of my co-workers were hired shortly after being laid off and they never use Linkedin. I cannot speak for everyone. What I can say is that with 10 years in the tech market, I had access to a network to help me access opportunities, that's the power of building a network you can tap into. At the end of the day, the pessimists are often right but the optimists are often successful. There are a lot of other lessons I’ve learned over the last 10 years working in software and I’ll be sharing some of the major takeaways at an upcoming webinar hosted by Code Career Mastery . RSVP here 👉 https://bit.ly/44XRLKN Hope to see you there.	TEXT	Brian	Jenney	49,587	49,587	221	26	4	0.005062	null	2024-06-04 08:33:16	https://www.linkedin.com/feed/update/urn:li:activity:7203780857063510018
urn:li:activity:7203392450386624512	🙄 As much as we like to dunk on recruiters, they can be your best resource on the job hunt. I interviewed David Roberts, a software developer turned recruiter turned career coach. He schooled me on why most of us, especially bootcamp grads, are going about LinkedIn, GitHub profiles and job searching in the wrong way. David breaks down how to stand out as a developer on the job market, thoughts on “free work” and learning how to “sell” yourself. You can check it out here: https://lnkd.in/gpzTfxMQ	IMAGE	Brian	Jenney	18,237	18,237	119	23	8	0.008225	null	2024-06-03 06:49:52	https://www.linkedin.com/feed/update/urn:li:activity:7203392450386624512
urn:li:activity:7202333831591284737	You don’t have a problem learning to code. You have a time management issue. Instead of spending marathon sessions where you cram on the weekend, try this: - 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝘇𝗲 - use a decision matrix to identify the most important task you can do - 𝗣𝗹𝗮𝗻 - tackle the most important thing in the morning - 𝗦𝗮𝗰𝗿𝗶𝗳𝗶𝗰𝗲 - open your phone and check your activity - something’s gotta give - 𝗦𝗽𝗿𝗶𝗻𝘁 - humans aren’t robots… yet. Take short pauses to reflect and correct your course 30 mins a day > 6 hours on your day off consistency > intensity	IMAGE	Brian	Jenney	5,534	5,534	56	13	0	0.012468	null	2024-05-31 08:43:18	https://www.linkedin.com/feed/update/urn:li:activity:7202333831591284737
urn:li:activity:7201982845081329665	I break down the 4 lessons I learned about starting a 5 figure side business as a software developer on this week's episode of Develop Yourself Podcast (link in bio). Most people trying to start their own business focus on: - landing page - offer creation - website - email sequences - social media When they skipped an important step: - have a skill or product to solve a problem I've started more than a few failed businesses and finally had some success in the last couple years. This business is mostly on maintenance mode since I've taken over ownership of Parsity (as the chart shows) but I think there are some lessons you might find helpful if you're thinking of trying on your entrepreneurship hat.	TEXT	Brian	Jenney	2,476	2,476	26	8	0	0.013732	null	2024-05-30 09:28:36	https://www.linkedin.com/feed/update/urn:li:activity:7201982845081329665
urn:li:activity:7201615514253602816	My poor Git skills didn't really bite me until 3 years into my career. I had just been hired as a developer for a cool tech startup. I volunteered to handle a code release, just like I've recommended in previous posts. The lead developer was off that night and told me his process to merge a small change from one branch to production. Simple, I thought. He scribbled his Git work flow on a whiteboard in a small office while I tried to hide my anxiety. It was so much different than any flow I'd used. 𝗜 𝘄𝗮𝘀 𝗰𝗼𝗻𝗳𝘂𝘀𝗲𝗱 𝗯𝘂𝘁 𝗱𝗶𝗱𝗻'𝘁 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗮𝗱𝗺𝗶𝘁 𝗶𝘁. I wrote down the process step by step in my notebook as if it was some secret spell. That night I merged something into production successfully. One problem: It wasn't the right code 😬. My manager saved me that morning and we reverted my changes and merged the correct code. I was painfully embarrassed. I also knew it was time for me to actually understand how to use Git. Here are a few things which helped me get Git before I got got... 🧐 - use 𝚘𝚑𝚖𝚢𝚣𝚜𝚑 to 𝗺𝗮𝗸𝗲 𝗺𝘆 𝘁𝗲𝗿𝗺𝗶𝗻𝗮𝗹 𝗺𝗼𝗿𝗲 𝗚𝗶𝘁-𝗳𝗿𝗶𝗲𝗻𝗱𝗹𝘆 - 𝗮𝗱𝗱 𝗮𝗹𝗶𝗮𝘀 𝗰𝗼𝗺𝗺𝗮𝗻𝗱𝘀 so I could type things like 𝚐𝚌𝚘 instead of 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 - learn how to 𝗶𝗻𝘃𝗲𝘀𝘁𝗶𝗴𝗮𝘁𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 within a branch with 𝚐𝚒𝚝 𝚕𝚘𝚐 - 𝗯𝗶𝗻𝗮𝗿𝘆 𝘀𝗲𝗮𝗿𝗰𝗵 𝗺𝘆 𝗰𝗼𝗺𝗺𝗶𝘁𝘀 to see where I introduced a bug using 𝚐𝚒𝚝 𝚋𝚒𝚜𝚎𝚌𝚝 - 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗳𝗿𝗼𝗺 𝗮 𝘀𝗶𝗻𝗴𝗹𝗲 𝗳𝗶𝗹𝗲 on a different branch 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 <𝚋𝚛𝚊𝚗𝚌𝚑> -- 𝚙𝚊𝚝𝚑/𝚝𝚘/𝚏𝚒𝚕𝚎 - understand how to 𝗿𝗲𝘃𝗲𝗿𝘁 𝗮 𝗿𝗲𝘃𝗲𝗿𝘁 𝚐𝚒𝚝 𝚛𝚎𝚟𝚎𝚛𝚝 <𝚌𝚘𝚖𝚖𝚒𝚝-𝚑𝚊𝚜𝚑-𝚏𝚛𝚘𝚖-𝚘𝚛𝚒𝚐𝚒𝚗𝚊𝚕-𝚛𝚎𝚟𝚎𝚛𝚝> - 𝗼𝗻𝗹𝘆 𝗺𝗲𝗿𝗴𝗲 𝗰𝗲𝗿𝘁𝗮𝗶𝗻 𝗰𝗼𝗺𝗺𝗶𝘁𝘀 into a branch with 𝚌𝚑𝚎𝚛𝚛𝚢-𝚙𝚒𝚌𝚔 My major flaw is that I was too concerned with memorizing a particular set of commands to achieve something. There are at 𝚗 different ways to get the same outcome with Git. I now like to start with a simple question: "𝘞𝘩𝘢𝘵 𝘢𝘮 𝘐 𝘵𝘳𝘺𝘪𝘯𝘨 𝘵𝘰 𝘥𝘰?" and work backwards from there.	TEXT	Brian	Jenney	14,639	14,639	161	23	3	0.012774	null	2024-05-29 09:08:58	https://www.linkedin.com/feed/update/urn:li:activity:7201615514253602816
urn:li:activity:7200895246665146368	Could there be a worse time to learn to code? I was 2 months sober, working a full time job while doing ride share on the side and had 2 kids at home. I had negative time. 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘁𝗼 𝗰𝗼𝗱𝗲 𝘁𝗮𝘂𝗴𝗵𝘁 𝗺𝗲 𝘁𝗵𝗲 𝟮𝗻𝗱 𝗺𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘀𝗸𝗶𝗹𝗹 𝗜 𝘄𝗼𝘂𝗹𝗱 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗯𝗲𝗰𝗼𝗺𝗲 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿: time management. It really just boiled down to: 1. 𝗣𝗹𝗮𝗻 𝗼𝘂𝘁 𝘄𝗵𝗮𝘁 𝘁𝗼 𝗱𝗼 (𝘦𝘹: 𝘵𝘰𝘮𝘰𝘳𝘳𝘰𝘸 - 𝘧𝘪𝘯𝘪𝘴𝘩 𝘴𝘦𝘤𝘵𝘪𝘰𝘯 1 𝘰𝘧 Colt Steele'𝘴 𝘜𝘥𝘦𝘮𝘺 𝘤𝘰𝘶𝘳𝘴𝘦) 2. No cold plunge. No meditation. No daily affirmation. 𝗪𝗼𝗿𝗸 𝗳𝗶𝗿𝘀𝘁 𝘁𝗵𝗶𝗻𝗴 before my kids yell at me for pancakes. 3. 𝗠𝗮𝗸𝗲 𝗮 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗺𝗮𝘁𝗿𝗶𝘅 to see what is the single most important thing I can do. (𝘦𝘹: 𝘤𝘳𝘦𝘢𝘵𝘦 4 𝘴𝘲𝘶𝘢𝘳𝘦𝘴 𝘰𝘯 𝘢 𝘱𝘢𝘱𝘦𝘳. 𝙄𝙢𝙥𝙤𝙧𝙩𝙖𝙣𝙩/𝙪𝙧𝙜𝙚𝙣𝙩, 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵/𝘯𝘰𝘯-𝘶𝘳𝘨𝘦𝘯𝘵, 𝘯𝘰𝘵 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵/𝘯𝘰𝘵-𝘶𝘳𝘨𝘦𝘯𝘵, 𝘯𝘰𝘵 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵/𝘶𝘳𝘨𝘦𝘯𝘵) 4. 𝗠𝗮𝗸𝗲 𝗮 𝘀𝗮𝗰𝗿𝗶𝗳𝗶𝗰𝗲. I spent hours a day watching tv. I gave up binge-watching when I learned to code. For you, maybe you have to cut down on sports or harassing strangers online or whatever. Happy Memorial Day 🫡 🇺🇸	TEXT	Brian	Jenney	8,137	8,137	78	18	0	0.011798	null	2024-05-27 09:26:52	https://www.linkedin.com/feed/update/urn:li:activity:7200895246665146368
urn:li:activity:7199448204629716995	You’re right, whiteboard interviews are unfair, biased and don't resemble the kind of work you do on a daily basis. Now what? Do you limit yourself to companies that don’t ask these types of questions? Sure. I tried this for a while myself. 𝗬𝗼𝘂 𝗰𝗼𝘂𝗹𝗱 𝗮𝗹𝘀𝗼 𝗹𝗲𝗮𝗿𝗻 𝘀𝗼𝗺𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗰𝗼𝗺𝗺𝗼𝗻 𝗱𝗮𝘁𝗮 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝘀 𝗮𝗻𝗱 𝗮𝗹𝗴𝗼𝗿𝗶𝘁𝗵𝗺𝘀 𝗮𝘁 𝘁𝗵𝗲 𝗨𝗻𝗶𝘃𝗲𝗿𝘀𝗶𝘁𝘆 𝗼𝗳 𝗬𝗼𝘂𝗧𝘂𝗯𝗲. Or if you’re a masochist, a book perhaps. As a developer you ARE going to encounter these types of interviews. Why not give yourself a shot at actually passing them? Want to get started? - trees/tries - linked lists - graphs - stacks/queues - binary search - merge sort - quick sort 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝘁𝗵𝗲𝘀𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝘀 𝗮𝗻𝗱 𝗮𝗹𝗴𝗼𝗿𝗶𝘁𝗵𝗺𝘀 𝗳𝗿𝗼𝗺 𝘀𝗰𝗿𝗮𝘁𝗰𝗵. Find the Big O time for the most common operations (eg. what is the time complexity for searching a BST? How about inserting into a linked list?). Great, now you can still turn down these white board interviews. But because you want to, not because you have to.	TEXT	Brian	Jenney	10,876	10,876	26	7	1	0.003126	null	2024-05-23 09:36:51	https://www.linkedin.com/feed/update/urn:li:activity:7199448204629716995
urn:li:activity:7199080917921902594	Eat / code / sleep is not a process for progress, it’s a recipe for burnout. I’ve seen some of you trying out this method and I’ve yet to see it work. Hell, I tried it myself. It led to: - anxiety - less enthusiasm for my work - decreased quality of thought Counter-intuitively, the more I tried to cram in material or optimize my schedule, the less progress I was making. It was frustrating. For me, having a non-negotiable work out routine forced me to detach from work. Few things can interrupt my workout besides a sick kid or a critical bug at work. This is where I clear my mind and often where I come up with my best ideas. Getting in shape was honestly a side effect of this routine and perhaps the best “hack” I’ve discovered for keeping me sane in a fairly stressful occupation.	TEXT	Brian	Jenney	4,645	4,645	48	5	2	0.011841	null	2024-05-22 09:17:23	https://www.linkedin.com/feed/update/urn:li:activity:7199080917921902594
urn:li:activity:7196913986578100224	I got laid off at the end of March. I just verbally accepted an offer yesterday. Here are some themes I noticed throughout my job searches, including this one: • 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗿𝗲𝗰𝗿𝘂𝗶𝘁𝗲𝗿𝘀 𝗶𝘀 𝗸𝗲𝘆. All my interviews came from recruiters - basically none from cold applying. • 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗲𝗮𝘀𝘆 𝗮𝗽𝗽𝗹𝘆 𝗶𝘀 𝗹𝗶𝗸𝗲 𝗽𝗹𝗮𝘆𝗶𝗻𝗴 𝘁𝗵𝗲 𝗹𝗼𝘁𝘁𝗼. It's unlikely to work but you can only win if you play. • 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝘄𝗲𝗿𝗲 𝗮 𝗺𝗶𝘅 𝗼𝗳 𝗰𝗼𝗱𝗲 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 𝗮𝗻𝗱 𝘀𝘁𝗼𝗿𝗶𝗲𝘀 to prove I knew my stuff. Very little DSA. 𝘛𝘩𝘦𝘴𝘦 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘴 𝘢𝘭𝘸𝘢𝘺𝘴 𝘤𝘰𝘮𝘦 𝘶𝘱: - Tell me about an Interesting project you worked on and your role. - How would you handle conflict/deadlines? - Tell me about a process/improvement you led. • 𝗚𝗹𝗮𝘀𝘀𝗱𝗼𝗼𝗿, 𝗥𝗲𝗱𝗱𝗶𝘁 𝗮𝗻𝗱 𝗕𝗹𝗶𝗻𝗱 can really improve your chances of nailing an interview (𝘳𝘦𝘴𝘦𝘢𝘳𝘤𝘩 𝘱𝘳𝘦𝘷𝘪𝘰𝘶𝘴 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘴) • Writing down the 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝘃𝗮𝗹𝘂𝗲𝘀 𝗮𝗻𝗱 𝗶𝗻𝘀𝗲𝗿𝘁𝗶𝗻𝗴 𝘁𝗵𝗲𝗺 𝗶𝗻𝘁𝗼 𝘁𝗵𝗲 𝗰𝗼𝗻𝘃𝗼 is helpful • Doing 𝗺𝗼𝗰𝗸 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗵𝗲𝗹𝗽𝗲𝗱 𝗺𝗲 𝗴𝗲𝘁 𝗼𝘃𝗲𝗿 𝗺𝘆 𝗻𝗲𝗿𝘃𝗲𝘀 (𝘐 𝘭𝘪𝘬𝘦 𝘗𝘳𝘢𝘮𝘱[𝘥𝘰𝘵]𝘤𝘰𝘮 - 𝘵𝘩𝘦𝘺 𝘴𝘩𝘰𝘶𝘭𝘥 𝘩𝘰𝘯𝘦𝘴𝘵𝘭𝘺 𝘴𝘱𝘰𝘯𝘴𝘰𝘳 𝘮𝘦 𝘢𝘵 𝘵𝘩𝘪𝘴 𝘱𝘰𝘪𝘯𝘵) Yes, I realize I have 25k+ followers and nearly a decade of experience. This makes my path different than yours. 𝗠𝘆 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝗵𝗮𝘀𝗻'𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱 𝗺𝘂𝗰𝗵 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝘆𝗲𝗮𝗿𝘀. The big difference is that my interviews now focus less on coding skills than they used to but I did crush a CodeSignal or 2 😎. In case you're wondering - NO I was not part of any tech layoff. This was a marketing dept layoff and the reason I did not write about it is because I'm kinda sick of the layoff talk 🙄. Oh yeah - thank you to my previous corporate overlords. Learned a ton and met really great people. I can only pray that my efforts incrementally increased shareholder value 🫡	TEXT	Brian	Jenney	68,761	68,761	424	46	15	0.007053	null	2024-05-16 09:46:46	https://www.linkedin.com/feed/update/urn:li:activity:7196913986578100224
urn:li:activity:7196535871054008321	I don’t hate tutorials, I just don't like how most of you are using them. You’re probably making a lot of the same mistakes I did: - Passive watching - Falling down every rabbit hole - No practical application You watch a 10 hour video, sit down to code and realize you have no f*ckin clue what to do. You hate to see it and I’ve been there. I use this method: - 𝗟𝗲𝗮𝗿𝗻 𝗷𝘂𝘀𝘁 𝗲𝗻𝗼𝘂𝗴𝗵 from your tutorial to begin writing some code - 𝗕𝘂𝗺𝗯𝗹𝗲 𝘆𝗼𝘂𝗿 𝘄𝗮𝘆 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 to get something you can interact with - Reach the limit of your technical depth and 𝗴𝗲𝘁 𝘀𝘁𝘂𝗰𝗸 - 𝗦𝘁𝗼𝗽 𝗰𝗼𝗱𝗶𝗻𝗴 𝗮𝗻𝗱 𝗿𝗲-𝘃𝗶𝘀𝗶𝘁 𝘁𝗵𝗲 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 and build up some more knowledge for the next piece of your app Repeat.	TEXT	Brian	Jenney	13,754	13,754	80	22	0	0.007416	null	2024-05-15 08:44:16	https://www.linkedin.com/feed/update/urn:li:activity:7196535871054008321
urn:li:activity:7196183023761989632	4 little letters almost got me fired. LGTM. Looks good to me. Later that day, I got a cryptic Slack message from the lead developer. "𝘉𝘳𝘪𝘢𝘯, 𝘸𝘦 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘤𝘩𝘢𝘵" 😬 💗 📈 Turns out the code I had barely reviewed blew up and was going to delay the feature from being released. Whoops. I was embarrassed and a little surprised - I mean, it wasn’t like 𝗜 wrote the code. Either way, he was right. 𝗜 𝗵𝗮𝗱 𝗳𝗮𝗶𝗹𝗲𝗱 𝘁𝗼 𝗱𝗼 𝘁𝗵𝗲 𝗯𝗮𝗿𝗲 𝗺𝗶𝗻𝗶𝗺𝘂𝗺. I resolved to become the best damn code reviewer on the team that day. A year later, during my annual review, my manager told me that my peers were complimenting my reviews. I had prevented errors from slipping through and suggested solutions which led to more maintainable code. 𝗜 𝗯𝗮𝘀𝗶𝗰𝗮𝗹𝗹𝘆 𝗷𝘂𝘀𝘁 𝗰𝗼𝗽𝗶𝗲𝗱 𝘄𝗵𝗮𝘁 𝗼𝘂𝗿 𝗹𝗲𝗮𝗱 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝘄𝗮𝘀 𝗱𝗼𝗶𝗻𝗴: 1. Block off time in the morning to do the review 2. Understand the work being done by reading the ticket associated with the PR 3. Run code locally before looking at the code 4. Read the code and ask questions or suggest improvements 5. Use Loom or a screen share to discuss details or schedule a pair session if needed This was a slow and often tedious process. 𝗜 𝗰𝗮𝗻 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝘀𝗲𝗲 𝗺𝗮𝗻𝘆 𝗼𝗳 𝘆𝗼𝘂 𝗿𝗼𝗹𝗹𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗲𝘆𝗲𝘀. 𝘊𝘐/𝘊𝘋! 𝘗𝘢𝘪𝘳 𝘱𝘳𝘰𝘨𝘳𝘢𝘮! 𝘚𝘮𝘢𝘭𝘭 𝘤𝘰𝘮𝘮𝘪𝘵𝘴! Yes. Correct. Also - I still stand by this process.	TEXT	Brian	Jenney	834,650	834,650	2,289	128	57	0.002964	null	2024-05-14 09:22:11	https://www.linkedin.com/feed/update/urn:li:activity:7196183023761989632
urn:li:activity:7195816831251623937	𝘏𝘰𝘸 𝘮𝘰𝘴𝘵 𝘴𝘶𝘤𝘤𝘦𝘴𝘴𝘧𝘶𝘭 𝘣𝘰𝘰𝘵𝘤𝘢𝘮𝘱 𝘨𝘳𝘢𝘥𝘴 𝘰𝘱𝘦𝘳𝘢𝘵𝘦: - Makes coding and learning a routine - Applies consistently and broadly - Has 1 or 2 complex side projects - Re-calibrates their approach when needed - Has faith that opportunity will present itself 𝘞𝘩𝘺 𝘮𝘰𝘴𝘵 𝘣𝘰𝘰𝘵𝘤𝘢𝘮𝘱 𝘨𝘳𝘢𝘥𝘴 𝘧𝘢𝘪𝘭: - Applies to only junior roles - Tutorial - Tutorial - Tutorial - Relies on motivation instead of routine - Doesn’t get hired in 3 months - 𝘎𝘪𝘷𝘦𝘴 𝘶𝘱	TEXT	Brian	Jenney	7,989	7,989	71	23	0	0.011766	null	2024-05-13 09:07:04	https://www.linkedin.com/feed/update/urn:li:activity:7195816831251623937
urn:li:activity:7194369764574580736	Here's how I'm actually doing my job search: 𝗦𝗲𝗮𝗿𝗰𝗵𝗶𝗻𝗴: - 10% LinkedIn easy apply (you gotta play the lotto) - Hired a resume writer and updated my LI profile with keywords - Apply directly through the company site after finding them on Otta or Wellfound - DM recruiters and hiring managers for positions I really want 𝗦𝘁𝘂𝗱𝘆𝗶𝗻𝗴: - Use Pramp[dot]com for interview practice (LI hates links) - Read Alex Xu books on Sys Design - AlgoExpert for DSA practice or my own app (JavascriptProsApp[dot]com) - Create scripts for behavioral questions (why freestyle it?) 𝗨𝗽-𝗦𝗸𝗶𝗹𝗹𝗶𝗻𝗴: - Build sh*t using technology I should know better like Docker, TypeScript, AWS and a little Rust just in case TLDR - a combination of mass applying, targeted applying and interview prep for non-FAANG roles. So far so good. It also doesn't hurt having 25k followers and 10 years experience so I'm not pretending that this flow will work for everyone. Hope that's helpful.	TEXT	Brian	Jenney	14,228	14,228	103	24	1	0.008996	null	2024-05-09 09:16:56	https://www.linkedin.com/feed/update/urn:li:activity:7194369764574580736
urn:li:activity:7194042345250512896	Unit tests are a waste of time. Instead of taking minutes to write a test you can just: - write your code - manually replicate all the scenarios you want to test - pray for the best and have your QA team ensure it all works Now that it works, don't touch it! 😅 When done correctly: - tests enable refactoring with confidence - confirm edge cases - document the ACTUAL functionality (I know your docs suck) 🤫 Oddly enough, most bootcamps skip any mention of unit testing even though most dev teams write loads of tests. Not Parsity tho 😉 Because you're probably smart and maybe even good looking - I have a repo for you to get your hands dirty with the basics of Jest and Unit Testing. 𝘚𝘶𝘱𝘦𝘳 𝘴𝘦𝘤𝘳𝘦𝘵 𝘶𝘯𝘪𝘵 𝘵𝘦𝘴𝘵𝘪𝘯𝘨 𝘳𝘦𝘱𝘰 𝘧𝘰𝘳 𝘣𝘦𝘵𝘵𝘦𝘳 𝘵𝘩𝘢𝘯 𝘢𝘷𝘦𝘳𝘢𝘨𝘦 𝘭𝘰𝘰𝘬𝘪𝘯𝘨 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴 👇 https://lnkd.in/dh_bVgz9	TEXT	Brian	Jenney	28,162	28,162	78	16	3	0.003444	null	2024-05-08 11:35:53	https://www.linkedin.com/feed/update/urn:li:activity:7194042345250512896
urn:li:activity:7193282825939308546	𝘊𝘰𝘥𝘦 𝘴𝘩𝘰𝘶𝘭𝘥 𝘢𝘭𝘸𝘢𝘺𝘴 𝘧𝘰𝘭𝘭𝘰𝘸 𝘋𝘙𝘠 𝘱𝘳𝘪𝘯𝘤𝘪𝘱𝘭𝘦𝘴! Except, maybe your abstraction is more clever than useful in this case. 𝘛𝘋𝘋 𝘰𝘳 𝘥𝘪𝘦! Or you know, TaDD (test after development is done). Or, perhaps manual QA can be enough. 𝘛𝘺𝘱𝘦𝘚𝘤𝘳𝘪𝘱𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘯𝘭𝘺 𝘤𝘩𝘰𝘪𝘤𝘦 𝘧𝘰𝘳 𝘴𝘦𝘳𝘪𝘰𝘶𝘴 𝘑𝘚 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴! But maybe it’s overkill for this simple UI app. Or just use JSDoc annotations. Be careful falling into dogmatic, knee-jerk responses when it comes to writing software. One thing I’ve learned is that there are exceptions to the rules we accept as coding law. *** I sat down with your favorite TypeScript Wizard Ryan Talbert and learned what he really thinks about JavaScript, TypeScript and his wild origin story. You can check it out in the comments 👇	TEXT	Brian	Jenney	17,197	17,197	71	18	1	0.005233	null	2024-05-06 09:17:50	https://www.linkedin.com/feed/update/urn:li:activity:7193282825939308546
urn:li:activity:7191835658225647616	He created a full stack app that worked pretty well. It even looked nice. But when I asked how it worked… Oof. 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗰𝗮𝘀𝗲 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗮𝗯𝘂𝘀𝗲. Too many people fall into the trap of looking at a tutorial, following along with the instructor and typing what they type. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗼𝗳𝗳: a shiny new app. 𝗧𝗵𝗲 𝗰𝗼𝘀𝘁: a false sense of mastery It’s an enticing trap and it may even fool someone into hiring you. 90% of my side projects have never had users or been deployed. I made janky apps and sites to learn new concepts, frameworks and even join a startup as a mid-level developer in a completely new tech stack. Every side project doesn’t need to be a masterpiece. Leverage them to learn what you won’t at work or what you would like to work on next. 𝘐𝘧 𝘺𝘰𝘶 𝘸𝘢𝘯𝘵 𝘮𝘺 𝘴𝘵𝘦𝘱 𝘣𝘺 𝘴𝘵𝘦𝘱 𝘨𝘶𝘪𝘥𝘦 𝘰𝘯 𝘤𝘳𝘦𝘢𝘵𝘪𝘯𝘨 𝘢 𝘴𝘰𝘭𝘪𝘥 𝘴𝘪𝘥𝘦 𝘱𝘳𝘰𝘫𝘦𝘤𝘵 𝘺𝘰𝘶 𝘤𝘢𝘯 𝘨𝘳𝘢𝘣 𝘪𝘵 𝘩𝘦𝘳𝘦: https://lnkd.in/gEzeRC9F 𝘛𝘪𝘳𝘦𝘥 𝘰𝘧 𝘵𝘶𝘵𝘰𝘳𝘪𝘢𝘭𝘴? 𝘊𝘩𝘦𝘤𝘬 𝘵𝘩𝘪𝘴 𝘰𝘶𝘵: https://lnkd.in/gpqEgqny	TEXT	Brian	Jenney	20,836	20,836	106	24	0	0.006239	null	2024-05-02 09:27:18	https://www.linkedin.com/feed/update/urn:li:activity:7191835658225647616
urn:li:activity:7191099996136443904	You’re having trouble coming up with solutions to problems as a software developer because you’re re-inventing the wheel. As a junior developer, there are zero problems you will encounter that haven’t been solved a dozen times over. There are tried and true approaches for that feature you’re working on. But you don’t know what you don’t know. Here’s where I’d start: - 𝗹𝗼𝗼𝗸 𝘂𝗽 𝗺𝗲𝘁𝗮-𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 - the general design patterns that dominate the field - 𝗳𝗮𝗺𝗶𝗹𝗶𝗮𝗿𝗶𝘇𝗲 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 𝘄𝗶𝘁𝗵 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲-𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 - like the module pattern in JS - 𝗿𝗲𝗮𝗱 𝘂𝗽 𝗼𝗻 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 like presenter/container and HOCs for ReactJS You’ll begin to notice that much of the code you write either fits into a larger pattern or implements smaller patterns. You’ll be a more confident and efficient developer because of it. 𝘞𝘩𝘢𝘵 𝘢𝘳𝘦 𝘴𝘰𝘮𝘦 𝘤𝘰𝘮𝘮𝘰𝘯 𝘱𝘢𝘵𝘵𝘦𝘳𝘯𝘴 𝘺𝘰𝘶 𝘩𝘢𝘷𝘦 𝘦𝘯𝘤𝘰𝘶𝘯𝘵𝘦𝘳𝘦𝘥 𝘵𝘩𝘢𝘵 𝘸𝘰𝘶𝘭𝘥’𝘷𝘦 𝘴𝘢𝘷𝘦𝘥 𝘵𝘩𝘦 𝘺𝘰𝘶𝘯𝘨𝘦𝘳 𝘺𝘰𝘶?	TEXT	Brian	Jenney	4,201	4,201	47	2	2	0.01214	null	2024-04-30 08:44:03	https://www.linkedin.com/feed/update/urn:li:activity:7191099996136443904
urn:li:activity:7190738316160319489	A few months ago, I wrote about a developer who bombed a mock interview because he tried to use a ReactJS API during a vanilla JS challenge. I suggested he learn the fundamentals of JS before touching React. Now, I’m not so sure. 𝗛𝗼𝘄 𝗺𝘂𝗰𝗵 𝗝𝗦 𝗱𝗼 𝘆𝗼𝘂 𝗿𝗲𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗸𝗻𝗼𝘄 𝗻𝗼𝘄𝗮𝗱𝗮𝘆𝘀? Most roles for JS developers depend on a strong knowledge of the layer above JS. Companies want ReactJS, NextJS and Angular developers (the other 5 are looking for Vue developers 😉). Is it still worth having a strong grasp on: - prototypal inheritance - closure - type coercion - scope/hoisting I realize you still need some clue about these concepts but perhaps much less than I previously thought. Is there anything so wrong with being a framework developer? It appears to be a lucrative career path. Genuinely curious.	TEXT	Brian	Jenney	11,695	11,695	60	37	0	0.008294	null	2024-04-29 08:46:51	https://www.linkedin.com/feed/update/urn:li:activity:7190738316160319489
urn:li:activity:7189657446359953409	I'm not that smart but I know 2 things pretty well: 1. Coding 2. Getting in shape I've talked enough about coding. Here are 3.5 tips to help you get in shape, lose weight and spite your ex. Or get healthy. Whatever. I got into the best shape of my life at 37 using these methods: 1. 𝗪𝗲𝗶𝗴𝗵 𝗼𝘂𝘁 𝘆𝗼𝘂𝗿 𝗲𝗳𝗳𝗶𝗻' 𝗳𝗼𝗼𝗱. That cup of rice was never a cup. Track you calorie intake with MyFitnessPal and make sure you aren't eating double the calories you think you are. 2. 𝗡𝗼𝘁𝗵𝗶𝗻𝗴 𝗶𝘀 𝗼𝗳𝗳 𝗹𝗶𝗺𝗶𝘁𝘀 𝘕𝘰 𝘤𝘢𝘳𝘣𝘴! 𝘊𝘢𝘯'𝘵 𝘦𝘢𝘵 𝘢𝘧𝘵𝘦𝘳 6 𝘗𝘔. 𝘌𝘢𝘵 𝘰𝘯𝘭𝘺 𝘨𝘳𝘢𝘴𝘴-𝘧𝘦𝘥 𝘴𝘲𝘶𝘪𝘳𝘳𝘦𝘭𝘴! Eff all that. Eat what you want (within reason) and just be in a caloric deficit. Basically, eat a couple hundred fewer calories than you need to maintain your weight. You can figure out your maintenance calories from step 1 or try out a TDEE calculator. 3. 𝗙𝗮𝗶𝗹 𝘆𝗼𝘂𝗿 𝘄𝗮𝘆 𝘁𝗼 𝗴𝗿𝗼𝘄𝘁𝗵 Lift until your muscle fails to lift anymore. Over 15 reps? Add weight. Under 10 reps? Remove weight. No gym? Do 100 burpees every other day and 300 squats twice a week. You're gonna see your muscles grow. 3.5 𝗦𝘁𝗼𝗽 𝗰𝗼𝗺𝗽𝗮𝗿𝗶𝗻𝗴 Your body will grow within its limits. Your genetics play a part in how your body will look but losing weight is a matter of calories going in and calories going out. Don't over-complicate it.	TEXT	Brian	Jenney	32,730	32,730	117	38	0	0.004736	null	2024-04-26 09:11:52	https://www.linkedin.com/feed/update/urn:li:activity:7189657446359953409
urn:li:activity:7189291701511835648	No 90 day plan. No manager feedback. You think you're doing well but the team is silently frustrated. Your notice to leave the team comes out of the blue... to you at least. Your manager isn't some sadistic bastard. In most cases at least. The reason they didn't confront you or offer feedback is because they are human. They just want to focus on their work and avoid conflict. It's not right, but it's reality. On day 1, you should set some practical milestones with your team lead or manager. 𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝘀𝘂𝗰𝗰𝗲𝘀𝘀 𝗳𝗼𝗿 𝘆𝗼𝘂 𝗹𝗼𝗼𝗸 𝗹𝗶𝗸𝗲 in the first month or two on the job? 𝗜𝗳 𝘁𝗵𝗲𝘆 𝗱𝗼𝗻'𝘁 𝗴𝗶𝘃𝗲 𝘆𝗼𝘂 𝗮 𝗽𝗹𝗮𝗻, 𝗺𝗮𝗸𝗲 𝗼𝗻𝗲 yourself and present it to them. For a junior developer it might look like this: 𝗗𝗮𝘆𝘀 𝟭 - 𝟯𝟬: Get all repos running locally on your machine and understand code review and deployment processes. Get at least 2 small features into production. 𝗗𝗮𝘆𝘀 𝟯𝟬 - 𝟲𝟬: Participate in an on-call rotation and learn process for critical incidents. Understand the full software development lifecycle. Be able to fix small bugs with little help. 𝗗𝗮𝘆𝘀 𝟲𝟬 - 𝟵𝟬: Take on a mid-level difficulty feature and deploy to production. Contribute to technical discussions. Once you're aligned on what success looks like, it's no longer a guessing game and you have proof that you are where you should be or have an idea about where you need to improve.	TEXT	Brian	Jenney	6,249	6,249	64	0	1	0.010402	null	2024-04-25 08:58:32	https://www.linkedin.com/feed/update/urn:li:activity:7189291701511835648
urn:li:activity:7188938151007068160	“𝘐𝘵’𝘴 𝘩𝘢𝘳𝘥 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘺𝘰𝘶 𝘴𝘪𝘯𝘤𝘦 𝘺𝘰𝘶 𝘥𝘰𝘯’𝘵 𝘳𝘦𝘢𝘭𝘭𝘺 𝘬𝘯𝘰𝘸 𝘵𝘩𝘦 𝘣𝘢𝘴𝘪𝘤𝘴 𝘰𝘧 𝘑𝘢𝘷𝘢𝘚𝘤𝘳𝘪𝘱𝘵”. A co-worker told me this early in my career at a small start up. It stung to hear. He was also right. I resolved to suck less at JS. I learned the basics including promises, closure, async/await, 𝚝𝚑𝚒𝚜 and design patterns. I went through all the Kyle Simpson books. I made janky apps to internalize the information. I gained knowledge and confidence. Luckily Ryan Talbert can save you some of the pain I felt and accelerate your knowledge with JS with his recently published book you can check out below. I bought this book and have found it really useful. I wish it was around when I first started writing JS and ReactJS professionally. This is not a sponsored post btw. I just like this book and figured you might too.	ARTICLE	Brian	Jenney	5,177	5,177	59	10	1	0.013521	null	2024-04-24 09:33:39	https://www.linkedin.com/feed/update/urn:li:activity:7188938151007068160
urn:li:activity:7188568858964770817	Nothing is quite as embarrassing as code you wrote blowing up in production and someone asking you “𝘩𝘦𝘺 𝘩𝘰𝘸’𝘴 𝘵𝘩𝘪𝘴 𝘴𝘶𝘱𝘱𝘰𝘴𝘦𝘥 𝘵𝘰 𝘸𝘰𝘳𝘬?” and you respond “𝘐 𝘥𝘰𝘯’𝘵 𝘬𝘯𝘰𝘸, 𝘮𝘺 𝘱𝘦𝘵 𝘳𝘰𝘣𝘰𝘵 𝘸𝘳𝘰𝘵𝘦 𝘪𝘵” 😬 This happened to me. I ripped off some code for my first project at work that crashed shortly after the release. I couldn’t explain how it worked - only that it was supposed to. 😬 ^ 10 I still copy and paste code from AI tools or Stack Overflow. Now, I make sure that I understand and refactor the code to make it my own for when it inevitably needs to change. 𝗜𝗳 𝘆𝗼𝘂’𝗿𝗲 𝗯𝗹𝗶𝗻𝗱𝗹𝘆 𝗰𝗼𝗽𝘆/𝗽𝗮𝘀𝘁𝗶𝗻𝗴 𝗰𝗼𝗱𝗲 from AI tools or Stack Overflow that you can not explain then 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝘁𝗼 𝘀𝗲𝗲𝗸 𝗵𝗲𝗹𝗽 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗰𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻. The disease is also the cure: Your AI overlord can explain its code and if you’re in the beginning stages of your dev career then you should re-write what you’ve been given to make it your own. Add a test or 2 to prove it works (link in comments cuz I like you) Hopefully this saves you a little pain in the future.	TEXT	Brian	Jenney	3,710	3,710	36	6	2	0.01186	null	2024-04-23 09:06:13	https://www.linkedin.com/feed/update/urn:li:activity:7188568858964770817
urn:li:activity:7188204548505702401	Vanessa Vun did everything wrong and still got hired: - 𝗺𝗮𝘀𝘀 𝗮𝗽𝗽𝗹𝗶𝗲𝗱 using the pray and spray approach - went the 𝘀𝗲𝗹𝗳-𝘁𝗮𝘂𝗴𝗵𝘁 route with the 𝗠𝗘𝗥𝗡 stack (I mean who still uses JS amirite 🤷) - did not stay 30 years old 🤦🏻‍♀️ Despite all this, she’s now a software engineer. Crazy, I know. It’s almost as if there’s more than 1 way to skin a cat, or land a job in software or do things. I had the pleasure of speaking with Vanessa last week and she breaks down how she went from clinical lab scientist to software engineer in her 30’s using a practical approach. If you're not following her, I mean I would.	TEXT	Brian	Jenney	6,940	6,940	80	10	3	0.013401	null	2024-04-22 08:58:34	https://www.linkedin.com/feed/update/urn:li:activity:7188204548505702401
urn:li:activity:7187096693249568768	I’ve gained quite a lot more followers on here so I figure it’s time to out myself again: 12 years ago I was addicted to drinking and drugs and living a criminal lifestyle. After an intervention, I promised to quit, unsure if I would actually be able to do it for more than a week (10 years later and I’m going strong 💪) I noticed I had a lot of time on my hands now with none of my terrible outlets available. I found Codecademy.com and wrote my first line of code. I was hooked (notice a theme here?) I fell ass backwards into a full-stack role after building janky websites for a year. Switched companies 4 times, took on contracts, taught at bootcamps and bought a ton of courses. I Made lots of embarrassing mistakes. Kept building stuff. Sucked less each year. I’ll be honest - I don’t like sharing much about my checkered past. It’s a distant memory at this point but I also know a lot of people reading this may be going through their own struggles. Maybe it’s strong drugs… maybe it’s video games. Obviously you have to want to change. You need desire and most importantly, direction. Here’s what worked for me: - exercising daily - finding a replacement relapse when triggered (e.g. I eat a ton of sweets when I want to do… other stuff) - find a hobby to fill in the time (for me it was coding, for you maybe reading or puzzles) - schedule events on days you would normally do stupid things (I watched a ton of awful movies on Thursday and Friday nights in movie theaters to pass the time) - tell everyone you quit - you’ll feel a lot more embarrassed if you fail and therefore incentivized to succeed I sincerely hope that helps.	TEXT	Brian	Jenney	12,227	12,227	173	17	2	0.015703	null	2024-04-19 07:36:21	https://www.linkedin.com/feed/update/urn:li:activity:7187096693249568768
urn:li:activity:7186033201201479682	Turns out that the scariest thing about Devin AI isn't the fact it will be replacing dev jobs anytime (too) soon. The scary thing is that we collectively fell for it. A YouTuber just revealed the truth behind the Devin AI demo that scared developers and kicked off a new wave of fear and hype around AI. 𝗢𝗻𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: turns out that the demo was edited, exaggerated and deceptive. Devin fished for a simple contract project, added some bugs and took hours to do a task that a much more senior developer completed in about 30 minutes. 𝘔𝘢𝘺𝘣𝘦 𝘋𝘦𝘷𝘪𝘯 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘪𝘴 𝘮𝘰𝘳𝘦 𝘭𝘪𝘬𝘦 𝘢 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘵𝘩𝘢𝘯 𝘐 𝘵𝘩𝘰𝘶𝘨𝘩𝘵? 🤔 Also, maybe, just maybe - we should be a tad more skeptical of outrageous claims and read past the headline before spreading the kind of fear-bait which the internet loves. PS - I still think Devin is pretty damn cool and the marketing team probably achieved their goals with this one. I'm sure we're at least 6 months away from the AI takeover 😉	TEXT	Brian	Jenney	5,703	5,703	41	21	2	0.011222	null	2024-04-16 09:10:25	https://www.linkedin.com/feed/update/urn:li:activity:7186033201201479682
urn:li:activity:7185672375873482752	Look, no one can tell you how long it’s going to take to get hired. One thing I’ve learned from working with dozens of developers last year and having literally hundreds of conversations with many of you here is that 𝘁𝗵𝗲𝗿𝗲 𝗶𝘀 𝗻𝗼 𝘀𝗶𝗻𝗴𝗹𝗲 𝗽𝗮𝘁𝗵 𝘁𝗼𝘄𝗮𝗿𝗱𝘀 𝘁𝗵𝗮𝘁 𝗳𝗶𝗿𝘀𝘁 𝗷𝗼𝗯. My favorite myths: 𝗜𝘁’𝘀 𝗡𝗢𝗧 𝗮 𝗻𝘂𝗺𝗯𝗲𝗿𝘀 𝗴𝗮𝗺𝗲… well, except that sometimes it kind of is. One of my mentees has a wife who sent his resume to tons of companies. He rarely uses LI and has had more interviews than others who have more experience. 𝗬𝗼𝘂 𝗠𝗨𝗦𝗧 𝗹𝗲𝗮𝗿𝗻 𝗶𝗻 𝗽𝘂𝗯𝗹𝗶𝗰. Nothing wrong with that. It takes courage and it’s certainly a strategy I’ve seen work. I’ve also never done it and most of the mentees I work with who have been recently hired haven’t either. 𝗜𝗳 𝘆𝗼𝘂 𝗹𝗲𝗮𝗿𝗻 [𝘅] 𝘆𝗼𝘂 𝘄𝗶𝗹𝗹 𝗯𝗲 𝗺𝗼𝗿𝗲 𝗵𝗶𝗿𝗲-𝗮𝗯𝗹𝗲. This is how Swiss-Army knife developers are born. They start with JS. Then Python. Next, Go. How bout Rust? These are all great languages but just piling on technologies isn’t a recipe for being more hire-able. The most successful mentees I’ve worked with are persistent, practically optimistic, work on side projects and adjust their strategy when something is not working.	TEXT	Brian	Jenney	35,355	35,355	61	4	2	0.001895	null	2024-04-15 09:16:37	https://www.linkedin.com/feed/update/urn:li:activity:7185672375873482752
urn:li:activity:7184956566079451136	This is the kind of project I love to see. Pranav Bindra took a suggestion I made on my podcast and ran with it to create something useful by leveraging AI that might help some of you nerds on the job hunt. Well done 👏	SHARE	Brian	Jenney	3,975	3,975	45	2	0	0.011824	null	2024-04-13 09:52:15	https://www.linkedin.com/feed/update/urn:li:activity:7184956566079451136
urn:li:activity:7184588391479398400	Nearly a decade ago I started my first day as a developer. I knew HTML, CSS, Jquery and a little AngularJS. The tech stack at the job included C#, SQL, DB2 and Apex. 😅 The night before the first day, I was barely able to sleep. 𝗪𝗼𝘂𝗹𝗱 𝗜 𝗯𝗲 𝗳𝗼𝘂𝗻𝗱 𝗼𝘂𝘁 𝗮𝘀 𝗮 𝗳𝗮𝗸𝗲 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗮𝗻𝗱 𝗳𝗶𝗿𝗲𝗱 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆? Would they give me a task I couldn’t figure out? 𝗛𝗼𝘄 𝗹𝗼𝗻𝗴 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲𝘆 𝗿𝗲𝗮𝗹𝗶𝘇𝗲𝗱 𝘁𝗵𝗲𝘆 𝗺𝗮𝗱𝗲 𝗮𝗻 𝗲𝗿𝗿𝗼𝗿 𝗶𝗻 𝘁𝗵𝗲𝗶𝗿 𝗵𝗶𝗿𝗶𝗻𝗴 𝗽𝗿𝗼𝗰𝗲𝘀𝘀? 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: - 𝗺𝗮𝗸𝗲 𝗮 𝟯𝟬/𝟲𝟬/𝟵𝟬 𝗱𝗮𝘆 𝗽𝗹𝗮𝗻 which usually includes delivering a small feature - immediately 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲𝗯𝗮𝘀𝗲 and identify areas I just don’t understand - 𝗮𝘀𝗸 𝗮 𝗯𝘂𝗻𝗰𝗵 𝗼𝗳 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘄𝗵𝗶𝗹𝗲 𝗜’𝗺 𝘀𝘁𝗶𝗹𝗹 𝗻𝗲𝘄 enough that no one will judge me - take notes - realize I’m here to 𝗱𝗼 𝗺𝗼𝗿𝗲 𝘄𝗮𝘁𝗰𝗵𝗶𝗻𝗴 𝘁𝗵𝗮𝗻 𝗱𝗼𝗶𝗻𝗴 during my first month So if you just got hired, congrats! I also know it can be just as stressful as the interview process. Maybe worse. What’s your tips for people just starting a new dev position?	TEXT	Brian	Jenney	22,482	22,482	150	21	3	0.00774	null	2024-04-12 09:29:15	https://www.linkedin.com/feed/update/urn:li:activity:7184588391479398400
urn:li:activity:7183497722325336065	Quintessential junior dev move: Wasting hours solving a problem a co-worker could’ve helped you figure out in minutes. No, this is not a long term solution to becoming an effective developer. Also: You are ultimately judged on the work you complete. When you bump your head against your technical depth, acknowledge it and ask for help. But for Jeebus sake please don’t just say “I can’t figure out [𝘹]” Try this: - I’m having an issue with [𝘵𝘩𝘪𝘴 𝘴𝘱𝘦𝘤𝘪𝘧𝘪𝘤 𝘱𝘳𝘰𝘣𝘭𝘦𝘮] - I’ve tried [𝘺] but it’s not working in the way I expect which is [𝘵𝘩𝘪𝘴 𝘸𝘢𝘺] - [𝘔𝘢𝘺𝘣𝘦 𝘢𝘥𝘥 𝘢 𝘤𝘰𝘥𝘦 𝘴𝘢𝘮𝘱𝘭𝘦, 𝘣𝘶𝘨 𝘵𝘳𝘢𝘤𝘦 𝘰𝘳 𝘥𝘰𝘤𝘶𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯] - Is anyone available to take a look with me sometime today or point me in the right direction? Don’t let your ego get in the way of progress.	TEXT	Brian	Jenney	81,240	81,240	360	35	15	0.005047	null	2024-04-09 09:15:19	https://www.linkedin.com/feed/update/urn:li:activity:7183497722325336065
urn:li:activity:7183143532130435072	There’s too much to learn. - A new framework to replace the old one that you just learned. - Obscure algorithms from dudes with too many letters in their last name. - Everyone is switching to AI/ML now? Should you learn Python? While you can’t JUST stick to the basics, if you chase every shiny new technology you will become a Swiss Army Knife developer. You can do a little of everything… poorly. Instead, identify mega vs micro trends in software development: - Recent mega trends include K8s, NextJS, Serverless and TypeScript. - Micro trends might include tRPC, edge computing and PWA. - Use side projects to gain experience with technologies that make up mega trends and keep your skills relevant. Gamble a bit with the micro trends. If you’re lucky, some of them will become mega trends and you’ll be first in line to take advantage.	TEXT	Brian	Jenney	8,957	8,957	70	9	3	0.009155	null	2024-04-08 09:47:54	https://www.linkedin.com/feed/update/urn:li:activity:7183143532130435072
urn:li:activity:7182417009874288640	Podcast is surpassing 10k downloads a month. My boring advice is getting some traction. I've interviewed some amazing people who are much smarter than me. Who should I beg to come on the show to talk about code stuff and self-improvement stuff? If you're learning to code - what do you want to hear about?	IMAGE	Brian	Jenney	8,756	8,756	109	27	0	0.015532	null	2024-04-06 09:40:57	https://www.linkedin.com/feed/update/urn:li:activity:7182417009874288640
urn:li:activity:7182046620186730496	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 Acquire.com and WellFound to see what small startups and 1 person businesses are building for inspiration. 2. 𝗗𝗼𝗻’𝘁 𝗯𝘂𝗶𝗹𝗱 𝗮 𝗵𝗼𝘂𝘀𝗲. 𝗔𝗱𝗱 𝗮 𝗯𝗿𝗶𝗰𝗸. Check out the feature requests or reviews for an app you’re already 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	24,921	24,921	166	14	15	0.007825	null	2024-04-05 09:09:10	https://www.linkedin.com/feed/update/urn:li:activity:7182046620186730496
urn:li:activity:7181294435895320577	Friendly reminder that you don’t need to start your own business or have a side hustle if you don’t want to. I’ve been hustling since I was 10 years old. - car washes - painting houses - selling mixtapes - crime 🤫 As an adult, my side projects give me energy and purpose. Coding is my hobby and profession. It doesn’t have to be yours though. Despite what you’ve read and perhaps against my own advice, there is nothing wrong with going to work and then closing your laptop. I’ve met some amazing developers who don’t touch code on the weekends.	TEXT	Brian	Jenney	11,653	11,653	93	12	1	0.009096	null	2024-04-03 07:20:15	https://www.linkedin.com/feed/update/urn:li:activity:7181294435895320577
urn:li:activity:7180605456711663616	We get it, networking is important. But what the hell does that mean? Especially on a platform like LinkedIn? Well, I can certainly tell you what it’s not: - DMs to strangers asking them to look at your resume or for a job (𝘴𝘦𝘳𝘪𝘰𝘶𝘴𝘭𝘺, 𝘵𝘳𝘺 𝘢 𝘲𝘶𝘪𝘤𝘬 𝘤𝘰𝘮𝘱𝘭𝘪𝘮𝘦𝘯𝘵 𝘣𝘦𝘧𝘰𝘳𝘦 𝘨𝘦𝘵𝘵𝘪𝘯𝘨 𝘳𝘪𝘨𝘩𝘵 𝘵𝘰 𝘵𝘩𝘦 𝘢𝘴𝘬) - Posts romanticizing a string of rejections (𝘦.𝘨. 𝘑𝘶𝘴𝘵 𝘣𝘰𝘮𝘣𝘦𝘥 𝘮𝘺 101𝘵𝘩 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸. 𝘞𝘩𝘰 𝘤𝘢𝘯 𝘳𝘦𝘧𝘦𝘳 𝘮𝘦 𝘵𝘰 𝘣𝘰𝘮𝘣 𝘵𝘩𝘦 102𝘳𝘥) - Messages to connections you’ve never spoken to asking for referrals 🥲 So what do you do? - Genuine engagement with other people by commenting on their posts (𝘢𝘨𝘳𝘦𝘦?) - DMs where you give first (𝘢 𝘭𝘪𝘯𝘬 𝘵𝘰 𝘢 𝘩𝘦𝘭𝘱𝘧𝘶𝘭 𝘢𝘳𝘵𝘪𝘤𝘭𝘦 𝘧𝘰𝘳 𝘦𝘹𝘢𝘮𝘱𝘭𝘦) - Posts that share what you’re learning (𝘢𝘯𝘥 𝘴𝘵𝘳𝘶𝘨𝘨𝘭𝘪𝘯𝘨 𝘸𝘪𝘵𝘩)	TEXT	Brian	Jenney	8,489	8,489	87	23	4	0.013429	null	2024-04-01 09:42:30	https://www.linkedin.com/feed/update/urn:li:activity:7180605456711663616
urn:li:activity:7179497939101233153	What is the 1 thing that separates developers who get hired vs those who don’t? I’ve thought about this a lot, especially as I’m now the owner of a coding bootcamp. I’ve seen too many success stories (and failures) from unlikely people. - The guy who could barely complete a for-loop? Hired before the bootcamp ended. - The woman with a CS degree? Nearly a year and 100’s of applications for her to get a break. There is very little rhyme, reason or “hack” I can confidently suggest. Except this: 𝗚𝗿𝗶𝘁 𝗮𝗻𝗱 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 𝗪𝗜𝗟𝗟 𝗴𝗲𝘁 𝘆𝗼𝘂 𝘁𝗼 𝘁𝗵𝗲 𝗳𝗶𝗻𝗶𝘀𝗵 𝗹𝗶𝗻e. The surest way towards failure is to quit. Most people will choose this route. 𝗗𝗼𝗻’𝘁 𝗹𝗲𝘁 𝘆𝗼𝘂𝗿 𝘀𝗸𝗶𝗹𝗹𝘀 𝗮𝘁𝗿𝗼𝗽𝗵𝘆. Build stuff or do LeetCode or Odin Project. Do something where your hands are on a keyboard making code do stuff. 𝗡𝗼𝘁 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀? Maybe work on that. 𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗮𝗻𝗱 𝗳𝗮𝗶𝗹𝗶𝗻𝗴? Good. Work on that. Good luck out there!	TEXT	Brian	Jenney	59,005	59,005	162	26	3	0.003237	null	2024-03-29 08:21:37	https://www.linkedin.com/feed/update/urn:li:activity:7179497939101233153
urn:li:activity:7178782008100233218	Honestly, a lot of software development is just writing: - JIRA tickets - System design documents - README docs - Presentations - Emails to the guy in marketing about why the button isn't working - Explaining why that NPM package is breaking the build over Slack or Teams - Medium articles on why TypeScript sucks or why Rust is faster than language [x] 🙄 We work with humans just as much as we work on code.	TEXT	Brian	Jenney	39,337	39,337	352	32	9	0.009991	null	2024-03-27 08:56:46	https://www.linkedin.com/feed/update/urn:li:activity:7178782008100233218
urn:li:activity:7178421446963081216	❌ 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 - meetings to prepare for other meetings - on-call shifts - writing documentation - maintaining legacy code - demo days - researching poorly documented 3rd party APIs - translating technical limitations to non-coders Coding is my hobby and profession. At the end of the day, 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. What'd I miss here?	TEXT	Brian	Jenney	19,543	19,543	156	28	4	0.00962	null	2024-03-26 09:04:01	https://www.linkedin.com/feed/update/urn:li:activity:7178421446963081216
urn:li:activity:7178062436967571458	My biggest networking hack has been hosting a podcast. I've met some of your favorite LinkedIn influencers (hit me up btw 😉) and people in software who are miles ahead of me. One problem though: These super stars have already "made it". Most of my audience is in that messy stage between learning to code and getting hired. Who is telling that story? If you're waiting until you've "made it" then we've missed the most important part of your journey. This week, I sat down with a current Parsity student Levy Dowell to discuss - how he juggles work, life and studying - why exercise and coding are more related than you think - what he wishes he knew before starting a program - some advice for those deciding between the self-taught and bootcamp route Link in comments.	TEXT	Brian	Jenney	4,746	4,746	54	10	0	0.013485	null	2024-03-25 09:17:26	https://www.linkedin.com/feed/update/urn:li:activity:7178062436967571458
urn:li:activity:7176611482468581376	Stability is a myth. Which is one of the reasons I'm glad I'm grateful for the community I've made both on LinkedIn and at work. [insert mass-layoff speech here, thank corporate overlords 🙇] With a little more time on my hands, I’m excited to partner with 🌻 Anna Miller and 🚀 Nate Hobi to be part of Code Career Mastery a 6-month mentorship for mid-level SWE to help them make their next big move while introducing more curriculum to Parsity to help developers with technical interviews and AFTER they get hired. I’m excited for this partnership because I believe in being in the driver's seat of your career. Tech moves fast and the market can be unforgiving. Becoming a partner allows me to offer additional resources for SWE who looking for their next move - whether it be more money, better team culture, your next technical challenge or an opportunity to move into a more senior role. I've helped more than a few of you out there to land a new role, next role or pass an interview. Now I want to do more. I’ll also be a guest speaker, sharing on the topic of Building Influence as a SWE. See you there 👋🏼	TEXT	Brian	Jenney	7,872	7,872	72	10	3	0.010798	null	2024-03-21 09:11:52	https://www.linkedin.com/feed/update/urn:li:activity:7176611482468581376
urn:li:activity:7176256882255306753	Something odd I’ve noticed about low performing software engineers: They work really hard. I would know. I’ve been one. The irony is that working harder is rarely the solution. Here’s why I was not making progress despite putting in long hours: 𝗟𝗮𝗰𝗸 𝗼𝗳 𝗙𝗼𝗰𝘂𝘀: Hard work without direction led to wasted effort. I needed to understand what the priorities were and work on tasks that brought the most value or learning leverage. 𝗙𝗲𝗮𝗿 𝗼𝗳 𝗔𝘀𝗸𝗶𝗻𝗴 𝗳𝗼𝗿 𝗛𝗲𝗹𝗽: Many devs, myself included, have been guilty of this. You think asking for help is a sign of weakness, but in reality, it's more efficient than getting rate-limited on Chat Gippity or staring at a blank screen. 𝗡𝗼𝘁 𝗜𝗻𝘃𝗲𝘀𝘁𝗶𝗻𝗴 𝗶𝗻 𝗦𝗸𝗶𝗹𝗹 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: Tech changes fast. If you're not learning, you're falling behind. Putting in the hours at work on the same tasks over and over has diminishing returns. Invest time in up-skilling. If you find yourself in a cycle of hard work but low performance, take a step back and evaluate. You might just find that a slight change in approach can lead to significant improvements.	TEXT	Brian	Jenney	23,939	23,939	137	26	2	0.006893	null	2024-03-20 09:42:49	https://www.linkedin.com/feed/update/urn:li:activity:7176256882255306753
urn:li:activity:7175882257335791616	You cannot cheat time in the saddle. Too many of the developers I speak to want to play it safe. I tried this too. Goes something like this: ✅ Take on work you know exactly how to handle ✅ "LGTM" on another code review ✅ Stay silent in meetings ❌ Wonder why you don't get promoted Here’s the thing: you’re going to make mistakes. I cannot promise your experience will be like mine. I’ve blown up production a few times. I deleted the column without a back up. I pretended to understand and f*cked things up. I learned a lot, got yelled at a few times and embarrassed too many times to count. Now I can share my takeaways with mentees and team mates (minus the yelling). I’m not saying to be careless, I’m just saying you will have to get used to the idea of failure if you want to grow.	TEXT	Brian	Jenney	6,882	6,882	68	20	2	0.013078	null	2024-03-19 08:54:11	https://www.linkedin.com/feed/update/urn:li:activity:7175882257335791616
urn:li:activity:7175540449934245888	White board interviews are biased, outdated and you will never use any DSA in "real life" as a developer. Right? Except: - 𝘀𝗼𝗺𝗲𝘁𝗶𝗺𝗲𝘀 𝗶𝘁'𝘀 𝗲𝗮𝘀𝗶𝗲𝗿 𝘁𝗼 𝘂𝘀𝗲 𝗿𝗲𝗰𝘂𝗿𝘀𝗶𝗼𝗻 than an iterative solution - 𝘁𝗿𝗲𝗲𝘀 𝗮𝗿𝗲 𝗲𝘃𝗲𝗿𝘆𝘄𝗵𝗲𝗿𝗲 from the database you're using to the DOM you're butchering - 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝘀𝗼𝗺𝗲 𝗯𝗮𝘀𝗶𝗰 𝗕𝗶𝗴 𝗢 might prevent you from writing that triple nested loop that crashes when you finally get some users Why limit yourself to companies that don't ask DSA? 𝗬𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗽𝗼𝘂𝗻𝗱 𝟱𝟬𝟬 𝗟𝗲𝗲𝘁𝗖𝗼𝗱𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝗲𝗶𝘁𝗵𝗲𝗿. - build some basic structures from scratch - ask Chat GPT what their practical usage might be - learn a handful of algos which dominate software and then when to apply them	TEXT	Brian	Jenney	5,919	5,919	55	17	0	0.012164	null	2024-03-18 10:15:58	https://www.linkedin.com/feed/update/urn:li:activity:7175540449934245888
urn:li:activity:7174442191157702656	2 minutes into the interview and I already knew I failed. I politely told my interviewer, "𝘐 𝘥𝘰𝘯'𝘵 𝘵𝘩𝘪𝘯𝘬 𝘪𝘵'𝘴 𝘸𝘰𝘳𝘵𝘩 𝘮𝘰𝘷𝘪𝘯𝘨 𝘧𝘰𝘳𝘸𝘢𝘳𝘥 𝘢𝘯𝘥 𝘐 𝘥𝘰𝘯'𝘵 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘸𝘢𝘴𝘵𝘦 𝘺𝘰𝘶𝘳 𝘵𝘪𝘮𝘦" He was a bit shocked and even encouraged me to try. So I did. The problem required recursion. I had no freaking clue where to start. So I quit on the spot. 😢 I made an oath that day to learn how to leverage recursion for silly-ass toy problems in interviews. This time... it was personal. Honestly, they don't have to be intimidating and I'm going to show you a recipe I use to construct the majority of recursive solutions along with a practical example that is NOT fibonacci.	VIDEO	Brian	Jenney	11,658	3,798	131	19	5	0.013296	null	2024-03-15 09:31:53	https://www.linkedin.com/feed/update/urn:li:activity:7174442191157702656
urn:li:activity:7173715129526546437	As a junior developer, most advice will probably work for you. You just haven’t stuck with it long enough to see any results. Or worse - you’re consistent and STILL don’t see any results. You may have a different problem. 𝗬𝗼𝘂 𝗺𝗮𝘆 𝗻𝗲𝗲𝗱 𝗺𝗼𝗿𝗲 𝘃𝗼𝗹𝘂𝗺𝗲. Lemme explain: Around 10 years ago I got sober and started working out. I saw zero results from my diet and exercise routine despite being consistent. It was deflating but I’m also a stubborn SOB. I broke down and paid for an online coach and 𝗜 𝗴𝗼𝘁 𝗯𝗲𝘁𝘁𝗲𝗿 𝗿𝗲𝘀𝘂𝗹𝘁𝘀 𝗶𝗻 𝟵𝟬 𝗱𝗮𝘆𝘀 𝘁𝗵𝗮𝗻 𝗜 𝗵𝗮𝗱 𝗶𝗻 𝘁𝗵𝗲 𝗽𝗿𝗲𝘃𝗶𝗼𝘂𝘀 𝟳 𝘆𝗲𝗮𝗿𝘀. What changed? He cut my calorie intake and increased my workout intensity by a factor of wtf. I went from 30 mins a day of bumbling around in the gym to doing sets of a 100 burpees at a time. My body responded. Apply this approach to your job search or learning to code or getting in shape. Consistency > Intensity but < Consistency + Intensity	TEXT	Brian	Jenney	14,063	14,063	77	12	6	0.006755	null	2024-03-13 09:22:48	https://www.linkedin.com/feed/update/urn:li:activity:7173715129526546437
urn:li:activity:7173381981760577537	A decade of brutal code reviews did not prepare me for the hate I've received on TikTok, IG and Reddit for my coding opinions. If you’re looking for civil discourse or to learn anything useful, I might 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: - The Coding Career Handbook https://lnkd.in/geszM2C2 - The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change https://lnkd.in/gzUzmKx2 - Kyle Simpson’s YDKJS series https://lnkd.in/gzAnyJHv - The Art of Refactoring https://lnkd.in/gmNYnS9s - The Phoenix Project https://lnkd.in/gF4Vp2Ux	UNKNOWN	Brian	Jenney	33,096	33,096	117	24	4	0.004381	null	2024-03-12 11:27:56	https://www.linkedin.com/feed/update/urn:li:activity:7173381981760577537
urn:li:activity:7172972628540960769	I've bombed more interviews than I've beaten. Here's a few mistakes I've made over the years: - Only studying DSA (data structures and algorithms) - Not asking ahead of time what questions will be asked - Not researching on the company - Not setting up my dev environment Dicky Kitchen Jr is a dude I met through IG who is on his coding journey and suggested we do a mock interview. He agreed to be my v̶i̶c̶t̶i̶m̶ participant. We treated it like a real deal technical screening and based on what I've learned from my own experiences, interviewing others for multiple companies and speaking with hundreds of you out there - 𝗜 𝘁𝗵𝗶𝗻𝗸 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗽𝗿𝗲𝘁𝘁𝘆 𝗿𝗲𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗮𝘁𝗶𝘃𝗲 𝗼𝗳 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝘄𝗶𝗹𝗹 𝗲𝗻𝗰𝗼𝘂𝗻𝘁𝗲𝗿. Because you're probably awesome and I like you, I want to give you some material to help you prepare and beat your next interview. Check it out here: https://lnkd.in/dvq9yG9N	UNKNOWN	Brian	Jenney	28,593	28,593	82	5	2	0.003113	null	2024-03-11 08:50:31	https://www.linkedin.com/feed/update/urn:li:activity:7172972628540960769
urn:li:activity:7171906368021381120	When you turn 40 in tech, you really only have 2 options: 1. Start a newsletter 2. Start a podcast I did both 😅. Honestly, when I took over Parsity, it came with a podcast. At first I was nervous about it. I have mostly hidden behind a screen, typing bro-etry on LI. Since I’ve started, it’s become one of my favorite mediums for sharing what I’ve learned and I’ve met so many great people because of it. This week, I got a chance to speak on a few different podcasts on opposite ends of the dev career spectrum: - For early career devs - Eric Winkelspecht who hosts 𝘚𝘦𝘭𝘧 𝘛𝘢𝘶𝘨𝘩𝘵 𝘋𝘦𝘷𝘴 - For early career managers - Nick Cosentino who hosts 𝘋𝘶𝘥𝘦, 𝘞𝘩𝘦𝘳𝘦'𝘴 𝘔𝘺 𝘊𝘰𝘥𝘦 Next week, I’ll be dropping a couple episodes I know will help many of you on the interview grind along with some free resources to study for the non-DSA interview. Shout out to m̶y̶ ̶v̶i̶c̶t̶i̶m̶ Dicky Kitchen Jr who did this intense mock interview with me! 𝗜’𝗱 𝗹𝗼𝘃𝗲 𝘁𝗼 𝗵𝗲𝗮𝗿 𝘆𝗼𝘂𝗿 𝗶𝗱𝗲𝗮𝘀 𝗳𝗼𝗿 𝘄𝗵𝗼 𝗜 𝘀𝗵𝗼𝘂𝗹𝗱 𝘁𝗿𝘆 𝘁𝗼 𝘀𝗽𝗲𝗮𝗸 𝘁𝗼 𝗻𝗲𝘅𝘁 𝗮𝗻𝗱 𝘁𝗼𝗽𝗶𝗰𝘀 𝘁𝗵𝗮𝘁 𝘄𝗶𝗹𝗹 𝗵𝗲𝗹𝗽 𝘁𝗵𝗼𝘀𝗲 𝗷𝘂𝘀𝘁 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗶𝗻 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲.	UNKNOWN	Brian	Jenney	8,879	8,879	74	16	1	0.010249	null	2024-03-08 08:51:41	https://www.linkedin.com/feed/update/urn:li:activity:7171906368021381120
urn:li:activity:7171189894717927426	No one’s going to look at your portfolio. You should still be building projects. The real value of that Weather App, Movie Finder or Chat Bot isn’t that it’s unique or styled like a pro. The real value is that it teaches you how to build and deploy an application. It gives you something to talk about when they ask you to “𝘛𝘦𝘭𝘭 𝘮𝘦 𝘢𝘣𝘰𝘶𝘵 𝘢𝘯 𝘪𝘯𝘵𝘦𝘳𝘦𝘴𝘵𝘪𝘯𝘨 𝘱𝘳𝘰𝘫𝘦𝘤𝘵 𝘺𝘰𝘶’𝘷𝘦 𝘸𝘰𝘳𝘬𝘦𝘥 𝘰𝘯” So before you get caught up in the shade of green you’re going to use for that nav bar, consider what you really want to learn. I might suggest: - 𝗔𝗪𝗦 (dynamo DB, Lambdas, S3) - 𝗩𝗲𝗿𝗰𝗲𝗹 (edge functions, streaming) - 𝗔𝗜 (integrate Dall-E or OpenAI) - 𝗔𝘂𝘁𝗵 (OAuth, Okta, roll-your-own with roles) Think what will make a good story and work backwards from there.	UNKNOWN	Brian	Jenney	19,677	19,677	159	27	7	0.009808	null	2024-03-06 09:21:06	https://www.linkedin.com/feed/update/urn:li:activity:7171189894717927426
urn:li:activity:7170836675756052480	These things will ruin you as a software developer: - Being too smart for frameworks 🙄 - Avoiding data structures and algorithms - Refusing to ask for help - Online debates about why someone is dumb for using a certain stack/language Avoid as many of these as possible.	UNKNOWN	Brian	Jenney	10,332	10,332	105	21	3	0.012485	null	2024-03-05 10:13:43	https://www.linkedin.com/feed/update/urn:li:activity:7170836675756052480
urn:li:activity:7170432341604069376	According to Reddit, YouTube and too many influencers online: - AI is the end of developers - No one can get hired Give up, hide in a bunker and maybe do drop-shipping. Or invest in Crypto. I am over the fear-mongering online regarding AI and the job market for developers. The reality: - It's tough to get the first job and the market is weird for everyone right now - AI is NOT taking your coding job for the foreseeable future Let's explore how you should be using AI and WHEN to incorporate it into your workflow as a developer. https://lnkd.in/gZaeADBA 👆 𝙏𝙝𝙚𝙧𝙚'𝙨 𝙖𝙡𝙨𝙤 𝙖 𝙉𝙤𝙙𝙚/𝙀𝙭𝙥𝙧𝙚𝙨𝙨 𝘼𝙄 𝙨𝙩𝙖𝙧𝙩𝙚𝙧 𝙥𝙧𝙤𝙟𝙚𝙘𝙩 𝙞𝙣 𝙩𝙝𝙚 𝙨𝙝𝙤𝙬 𝙣𝙤𝙩𝙚𝙨 𝙞𝙛 𝙩𝙝𝙖𝙩'𝙨 𝙮𝙤𝙪𝙧 𝙩𝙝𝙞𝙣𝙜	IMAGE	Brian	Jenney	3,116	3,116	34	5	0	0.012516	null	2024-03-04 07:48:31	https://www.linkedin.com/feed/update/urn:li:activity:7170432341604069376
urn:li:activity:7169383727167459328	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. 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. I break down why you should be writing them and how to get started this podcast - 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗴𝗿𝗮𝗯 𝘁𝗵𝗲 𝗨𝗻𝗶𝘁 𝗧𝗲𝘀𝘁 𝗚𝘂𝗶𝗱𝗲 𝗶𝗻 𝘁𝗵𝗲 𝘀𝗵𝗼𝘄 𝗻𝗼𝘁𝗲𝘀 𝗵𝗲𝗿𝗲 👉 https://lnkd.in/ghn_kr63	UNKNOWN	Brian	Jenney	5,962	5,962	54	9	0	0.010567	null	2024-03-01 10:12:56	https://www.linkedin.com/feed/update/urn:li:activity:7169383727167459328
urn:li:activity:7169014305760247808	This quote from Vercel's AI night is no doubt going to ruffle some feathers. I would agree... except, I'd probably include us JS devs too 😅. Every company has basically been mandated to incorporate AI. We've seen some pretty ham-fisted approaches but also some amazing benefits. As a developer, I use Co-Pilot and ChatGippity daily. It's the new normal. Knowing how to work with and leverage current APIs/models will set you apart from prompt engineers. For this reason, you should probably spend 10 bucks for some tokens on the Open AI dev platform and experiment with integrating it into your next side project. I'm excited to incorporate more AI/NextJS/Typescript into Parsity's curriculum and since I'm feeling nice, I even have an 𝗔𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗿 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘄𝗵𝗶𝗰𝗵 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲𝘀 𝗢𝗽𝗲𝗻𝗔𝗜 𝗮𝗻𝗱 𝗡𝗼𝗱𝗲/𝗘𝘅𝗽𝗿𝗲𝘀𝘀 𝘁𝗼 𝗴𝗲𝘁 𝘆𝗼𝘂𝗿 𝗵𝗮𝗻𝗱𝘀 𝗱𝗶𝗿𝘁𝘆 👇 Check it out here => https://lnkd.in/gxajBHtz 🤖	IMAGE	Brian	Jenney	9,335	9,335	101	13	7	0.012962	null	2024-02-29 09:16:29	https://www.linkedin.com/feed/update/urn:li:activity:7169014305760247808
urn:li:activity:7168682708649410560	Eat code sleep is not a process for progress, it’s a recipe for burnout. I’ve seen some of you trying out this method and I’ve yet to see it work. Hell, I tried it myself. It led to: - anxiety - less enthusiasm for my work - decreased quality of thought Counter-intuitively, the more I tried to cram in material or optimize my schedule, the less progress I was making. It was frustrating. For me, having a non-negotiable workout routine forced me to detach from work. Few things can interrupt my workout besides a sick kid or a critical bug at work. This is where I clear my mind and where I come up with my best ideas. Getting in shape was honestly a side effect of this routine and perhaps the best “hack” I’ve discovered for keeping me sane during stressful periods.	UNKNOWN	Brian	Jenney	4,466	4,466	50	8	2	0.013435	null	2024-02-28 11:24:55	https://www.linkedin.com/feed/update/urn:li:activity:7168682708649410560
urn:li:activity:7168286513049419776	I don’t have a problem with tutorials. I do have a problem with the way most of you are using them however. You’re probably making a lot of the same mistakes I did: - Passive watching - Falling down every rabbit hole - Confusing completion with understanding - No practical application 𝗬𝗼𝘂 𝘄𝗮𝘁𝗰𝗵 𝗮 𝟭𝟬 𝗵𝗼𝘂𝗿 𝘃𝗶𝗱𝗲𝗼, 𝘀𝗶𝘁 𝗱𝗼𝘄𝗻 𝘁𝗼 𝗰𝗼𝗱𝗲 𝗮𝗻𝗱 𝗿𝗲𝗮𝗹𝗶𝘇𝗲 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝗻𝗼 𝗳*𝗰𝗸𝗶𝗻 𝗰𝗹𝘂𝗲 𝘄𝗵𝗮𝘁 𝘁𝗼 𝗱𝗼. You hate to see it and I’ve been there. I use this method: - 𝗟𝗲𝗮𝗿𝗻 𝗷𝘂𝘀𝘁 𝗲𝗻𝗼𝘂𝗴𝗵 from your tutorial to begin writing some code - Bumble your way through to 𝗯𝘂𝗶𝗹𝗱 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗶𝗻𝘁𝗲𝗿𝗮𝗰𝘁 𝘄𝗶𝘁𝗵 - 𝗥𝗲𝗮𝗰𝗵 𝘁𝗵𝗲 𝗹𝗶𝗺𝗶𝘁 𝗼𝗳 𝘆𝗼𝘂𝗿 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗱𝗲𝗽𝘁𝗵 and get stuck - Stop coding and re-visit the tutorial and 𝗯𝘂𝗶𝗹𝗱 𝘂𝗽 𝘀𝗼𝗺𝗲 𝗺𝗼𝗿𝗲 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 for the next piece of your app Repeat.	UNKNOWN	Brian	Jenney	15,636	15,636	134	21	7	0.010361	null	2024-02-27 09:27:49	https://www.linkedin.com/feed/update/urn:li:activity:7168286513049419776
urn:li:activity:7167894230202343424	I asked former Parsity grad Ryan Passer an interesting question: "𝘋𝘰 𝘺𝘰𝘶 𝘩𝘢𝘷𝘦 𝘵𝘰 𝘭𝘪𝘬𝘦 𝘤𝘰𝘥𝘪𝘯𝘨 𝘵𝘰 𝘣𝘦 𝘴𝘶𝘤𝘤𝘦𝘴𝘴𝘧𝘶𝘭 𝘢𝘵 𝘪𝘵?" I can tell you that I have not met a developer who I admired who did not find some joy in their work. 𝗔 𝗹𝗶𝘁𝘁𝗹𝗲 𝗼𝘃𝗲𝗿 𝟳𝟬% 𝗼𝗳 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹 𝗰𝗼𝗱𝗲𝗿𝘀 𝗮𝗹𝘀𝗼 𝘄𝗿𝗶𝘁𝗲 𝗰𝗼𝗱𝗲 𝗳𝗼𝗿 𝗮 𝗵𝗼𝗯𝗯𝘆 according to Stack Overflow's yearly developer survey 🤷. In this episode, Ryan Passer shares his opinions and advice for up and coming developers including: - his journey from marketer to Parsity to full stack software engineer - his unusual (𝘣𝘶𝘵 𝘯𝘰𝘵 𝘳𝘦𝘢𝘭𝘭𝘺) interview experience - 𝗸𝗲𝗲𝗽𝗶𝗻𝗴 𝗺𝗼𝘁𝗶𝘃𝗮𝘁𝗲𝗱 while learning to code - side projects - hot takes on technology trends - 𝘄𝗵𝘆 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗯𝗲 𝗮 𝗳𝘂𝗹𝗹 𝘀𝘁𝗮𝗰𝗸 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 in today's market 𝙇𝙞𝙨𝙩𝙚𝙣 𝙝𝙚𝙧𝙚 👉 https://lnkd.in/gNbar8AD	UNKNOWN	Brian	Jenney	2,852	2,852	33	4	0	0.012973	null	2024-02-26 07:15:29	https://www.linkedin.com/feed/update/urn:li:activity:7167894230202343424
urn:li:activity:7167205568791662592	Before taking over ownership of Parsity I had a pretty cool project/product that is now gifted to all Parsity grads. 𝗜𝘁'𝘀 𝗻𝗼𝘁 𝗮 𝗰𝗼𝘂𝗿𝘀𝗲. I don't really know what to call it honestly. Someone described it as a "field guide for software developers". Basically, I thought about all the generic issues that web developers will likely deal with and created projects to reflect those challenges. - Troubleshooting GitHub actions pipelines - Fixing a Lambda on AWS - Migrating APIs - Improving Core Web Vitals - Diving into a new codebase - Creating an NPM library Check it out! There are some free and not-so-free challenges on there javascriptprosapp.com	UNKNOWN	Brian	Jenney	6,180	6,180	56	8	4	0.011003	null	2024-02-24 09:40:22	https://www.linkedin.com/feed/update/urn:li:activity:7167205568791662592
urn:li:activity:7166832230269407232	Sometimes I feel like a fake engineering manager but that’s ok. Before this, I was a fake senior software engineer and before that I was pretending to be a developer. At each new stage, there’s a little voice in my head reminding me why I shouldn’t be in my position. I peruse LinkedIn and compare myself to others. Terrible habit. I know it will happen again and I’m prepared. Here’s how I get over that little voice in my head: - 𝗳𝗶𝗻𝗱 𝗮𝗻 𝗮𝘃𝗮𝘁𝗮𝗿 - who do I want to be like? - what do they know that I don’t? - 𝗰𝗿𝗲𝗮𝘁𝗲 𝗮 𝗰𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁 with the items from the previous step - 𝗳𝗶𝗻𝗱 𝗺𝗲𝗻𝘁𝗼𝗿𝘀 𝗼𝗿 𝗯𝗼𝗼𝗸𝘀 or both to bring me closer to the avatar - 𝗰𝗵𝗲𝗰𝗸 𝗶𝘁𝗲𝗺𝘀 𝗼𝗳𝗳 𝘁𝗵𝗲 𝗹𝗶𝘀t and prove to myself that I’m where I need to be Rinse and repeat for each promotion, new company or new role. I break down some non-fluffy advice here: https://lnkd.in/gt6AJcUx	UNKNOWN	Brian	Jenney	9,378	9,378	69	16	3	0.009384	null	2024-02-23 09:09:39	https://www.linkedin.com/feed/update/urn:li:activity:7166832230269407232
urn:li:activity:7166107221989294080	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. Now, as an engineering manager, my job is a lot of coding but it’s also a lot of speaking. To get over my fear I did a few things: 1. Write down questions to ask during meetings 2. Volunteer for a lunch and learn 3. Explain my code over a video using Loom (I made so many 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.	UNKNOWN	Brian	Jenney	27,675	27,675	161	41	4	0.007444	null	2024-02-21 09:09:01	https://www.linkedin.com/feed/update/urn:li:activity:7166107221989294080
urn:li:activity:7165378462139052032	Turn off the tutorial. Open the code editor. You’re going to learn a hell of a lot more from: - getting stuck - reading the documentation - realizing the docs suck - getting rate limited on Chat GPT - throwing everything at the wall - finally figuring it out - feeling like a genius… for a few minutes as opposed to: - typing what another person has typed John Crickett would probably agree. I sat down with the code challenge King to talk about: • how he'd be learning to code if he was starting over • how he got into tech • his approach to social media • how he blew up on multiple platforms • AI and jobs Check it out here: https://lnkd.in/gDqsPWXv	VIDEO	Brian	Jenney	14,517	14,517	71	10	8	0.006131	null	2024-02-19 08:40:28	https://www.linkedin.com/feed/update/urn:li:activity:7165378462139052032
urn:li:activity:7164301478705266690	LinkedIn or Twitter fame is a silly goal if you’re building in public to land a role. The real power of learning in public is: - demonstrating technical depth - showcasing your work - learning how to articulate your thoughts on technical subjects As owner of Parsity I've encouraged more students to use LinkedIn, not to become mini-influencers but to get used to explaining the concepts they're learning and make connections outside of our program. I know it's not comfortable or easy and most won't do it. That's ok. I get it and there's more than 1 way to skin a cat (the cat being getting hired 🤔 🐈). A few students I see writing on a regular basis include: Stephen Swaringin Spencer Willis Check 'em out. Also - if you have writer's block, grab my LinkedIn templates to get your noggin' joggin' 👉 https://lnkd.in/gQiYrQd9	UNKNOWN	Brian	Jenney	11,740	11,740	66	13	2	0.006899	null	2024-02-16 08:56:26	https://www.linkedin.com/feed/update/urn:li:activity:7164301478705266690
urn:li:activity:7163579750081376256	So apparently, there is a tutorial out there teaching people how to use Git. One big issue - the example they show includes opening a PR against everyone's favorite NodeJS framework: Express.js I got quite a bit of hate when 𝗜 𝘀𝘂𝗴𝗴𝗲𝘀𝘁𝗲𝗱 𝘆𝗼𝘂 𝗗𝗢𝗡'𝗧 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗲 𝘁𝗼 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲. I stand by my statement. With this important nuance: 𝗬𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗛𝗔𝗩𝗘 𝘁𝗼 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗲 𝘁𝗼 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲 as a way to stand out. If you actually want to contribute - then you should. You can also: - clone down a project - run it locally - try to extend or break a small feature - learn a lot and never open a PR Garbage PRs that serve no purpose will do nothing but harm your reputation and if they mistakenly get merged, imagine how many nerds will cry that day. Lose/Lose.	IMAGE	Brian	Jenney	10,891	10,891	46	8	1	0.00505	null	2024-02-14 09:13:25	https://www.linkedin.com/feed/update/urn:li:activity:7163579750081376256
urn:li:activity:7162902637632311297	Hosting the Develop Yourself Podcast was honestly never my intention. You see, I inherited this podcast once I took over Parsity. It's become one of the most enjoyable parts of my week. I've met engineering leaders including one of my favorite authors and people who I follow on social media that I respect. 𝗧𝗵𝗲 𝗽𝗼𝗶𝗻𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗽𝗼𝗱𝗰𝗮𝘀𝘁 𝗶𝘀 𝘁𝗼 𝗵𝗲𝗹𝗽 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗮𝗻𝗱 𝗰𝗮𝗿𝗲𝗲𝗿 𝗰𝗵𝗮𝗻𝗴𝗲𝗿𝘀 𝗹𝗲𝗮𝗿𝗻 𝗺𝗼𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲𝗶𝗿 𝗰𝗿𝗮𝗳𝘁 𝗮𝗻𝗱 𝗳𝗶𝗻𝗱 𝗮 𝗾𝘂𝗶𝗰𝗸𝗲𝗿 𝗽𝗮𝘁𝗵 𝗳𝗿𝗼𝗺 𝟬 -> 𝗵𝗶𝗿𝗲𝗱 𝗮𝗻𝗱 𝗳𝗿𝗼𝗺 𝗵𝗶𝗿𝗲𝗱 -> 𝗻𝗲𝘅𝘁 𝗰𝗮𝗿𝗲𝗲𝗿 𝗹𝗲𝘃𝗲𝗹. Some of my favorite guests are people earlier in their career since they have recently lived through that difficult stage that many of you are currently experiencing. This week I spoke with Nathan Drake, former Parsity grad and learn how he got hired, dipped his toe into entrepreneurship and takeaways from the job search after graduating a bootcamp. 𝘞𝘢𝘪𝘵 𝘵𝘪𝘭 𝘺𝘰𝘶 𝘴𝘦𝘦 𝘸𝘩𝘰 𝘐 𝘨𝘰𝘵 𝘧𝘰𝘳 𝘯𝘦𝘹𝘵 𝘸𝘦𝘦𝘬... 😉	UNKNOWN	Brian	Jenney	2,812	2,812	27	1	1	0.010313	null	2024-02-12 12:23:11	https://www.linkedin.com/feed/update/urn:li:activity:7162902637632311297
urn:li:activity:7162840158529081345	I don't want to paint a picture of the job market for developers as roses and rainbows right now. It's tough to get hired. It's always been difficult to get that first job. Also: - A few former mentees just landed their first job 🍾 - A couple acquaintances are taking on job number 2 🤫 I'm sick of the nonstop fear-peddling. It's just not helpful. There are things we can control and things we cannot. If it's any consolation - everyone is finding it difficult to find a job. Not just devs. 📈 Continue to work on what you know makes sense for you and maybe unfollow the people that are pumping your head full of negativity. Some people I follow that help early career developers with landing a job are: 🌻 Anna Miller Rod H. Danan David Roberts.	UNKNOWN	Brian	Jenney	29,697	29,697	164	23	5	0.006465	null	2024-02-12 08:47:51	https://www.linkedin.com/feed/update/urn:li:activity:7162840158529081345
urn:li:activity:7161403703181156352	Coding interview hacks that have nothing do with coding: 1. 𝗖𝗵𝗲𝗰𝗸 𝗚𝗹𝗮𝘀𝘀𝗱𝗼𝗼𝗿 𝗼𝗿 𝗧𝗲𝗮𝗺𝗕𝗹𝗶𝗻𝗱 for previous questions from interviews 2. 𝗦𝘁𝗮𝗹𝗸 𝘆𝗼𝘂𝗿 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝗲𝗿𝘀 𝗼𝗻 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 - not like in a creepy way though. Are they involved in some communities that you’re part of? Maybe slip that into the convo (again, non-creepy please) 3. 𝗝𝘂𝘀𝘁 𝘀𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝘂𝗽 𝗮𝘀𝗸 what the interview will be… This week I’ve spoken with a few developers, including a Parsity student who is getting ready for an interview. Their recruiter didn’t tell them what kind though 😅. There’s too much to study and too much at stake to risk. You HAVE to ask. Just say this: “𝘛𝘰 𝘮𝘢𝘬𝘦 𝘴𝘶𝘳𝘦 𝘐’𝘮 𝘸𝘦𝘭𝘭 𝘱𝘳𝘦𝘱𝘢𝘳𝘦𝘥 𝘧𝘰𝘳 𝘵𝘩𝘦 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸, 𝘤𝘢𝘯 𝘺𝘰𝘶 𝘭𝘦𝘵 𝘮𝘦 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘵𝘩𝘪𝘴 𝘸𝘪𝘭𝘭 𝘦𝘯𝘵𝘢𝘪𝘭? 𝘞𝘪𝘭𝘭 𝘵𝘩𝘪𝘴 𝘣𝘦 𝘢 𝘵𝘦𝘤𝘩𝘯𝘪𝘤𝘢𝘭 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸, 𝘢 𝘤𝘰𝘥𝘪𝘯𝘨 𝘤𝘩𝘢𝘭𝘭𝘦𝘯𝘨𝘦 𝘰𝘳 𝘤𝘰𝘯𝘷𝘦𝘳𝘴𝘢𝘵𝘪𝘰𝘯𝘢𝘭?” Good luck out there 🤲	UNKNOWN	Brian	Jenney	23,481	23,481	102	25	6	0.005664	null	2024-02-08 09:19:51	https://www.linkedin.com/feed/update/urn:li:activity:7161403703181156352
urn:li:activity:7161084195484688387	There's nothing wrong with being average. As an average developer you will: - get work done in a timely manner - write maintainable code - get promoted every once in a while For many of you, being average is your current goal and that's fine. BUT, if you want to be a super star on a team, there's 1 trait I've noticed in developers I admire and it's been true for every team where I've worked. I break down this trait and how I've copied it to become a slightly above average developer.	ARTICLE	Brian	Jenney	11,323	11,323	81	4	1	0.007595	null	2024-02-07 12:13:44	https://www.linkedin.com/feed/update/urn:li:activity:7161084195484688387
urn:li:activity:7160709484774903808	I’ve gone from struggling junior developer to struggling engineering manager over the last 10 years and that little voice in my head has been present for the entire time. “𝘛𝘩𝘦𝘺’𝘳𝘦 𝘨𝘰𝘯𝘯𝘢 𝘧𝘪𝘯𝘥 𝘺𝘰𝘶 𝘰𝘶𝘵” It’s lot quieter than when I started but it's never left. I’ve come to accept it and seen its patterns. Promotion? - Voice gets louder. Accomplishment? - Voice gets quieter. New job? - Deafeningly loud. Solve an LC hard in 30 minutes? - 🤐 The feeling that you’re just not quite good enough may in fact be true. Be objective. Write out your weaknesses. Write out your strengths. Where is the gap between who you want to be and who you are currently and what will it take to get there?	UNKNOWN	Brian	Jenney	30,239	30,239	231	16	4	0.008301	null	2024-02-06 11:23:56	https://www.linkedin.com/feed/update/urn:li:activity:7160709484774903808
urn:li:activity:7160315837994696705	The dirty secret about a lot of the "tech" influencers you're taking advice from: Many have never written code for a living and yet they'll tell you how bad or good the market is, why JS sucks and why I'm an idiot for saying you should learn HTML and CSS.... seriously. I have a lot of opinions on how you should get that first job, what to learn and why you should be creating side projects. 𝗔 𝘀𝗶𝗻𝗴𝗹𝗲 𝗲𝘃𝗲𝗻𝘁 𝗹𝗮𝘀𝘁 𝘆𝗲𝗮𝗿 𝗴𝗮𝘃𝗲 𝗺𝗲 𝗮 𝘂𝗻𝗶𝗾𝘂𝗲 𝗽𝗲𝗿𝘀𝗽𝗲𝗰𝘁𝗶𝘃𝗲 𝗼𝗻 𝘁𝗵𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗹𝗮𝗻𝗱𝘀𝗰𝗮𝗽𝗲: Kyle Simpson reposted me and nearly a thousand followers flocked to my page. Hundreds began scheduling free 15 minute chats with me and I was totally un-prepared 😅. [𝘊𝘩𝘦𝘤𝘬 𝘰𝘶𝘵 𝘩𝘪𝘴 𝘱𝘰𝘥𝘤𝘢𝘴𝘵 𝘸𝘪𝘵𝘩 𝘮𝘦 - 𝘪𝘵'𝘴 𝘰𝘯𝘦 𝘰𝘧 𝘮𝘺 𝘧𝘢𝘷𝘰𝘳𝘪𝘵𝘦 𝘰𝘯𝘦𝘴 𝘴𝘰 𝘧𝘢𝘳] 𝗦𝗼 𝗳𝗮𝗿 𝗜'𝘃𝗲 𝘀𝗽𝗼𝗸𝗲𝗻 𝘁𝗼 𝗮 𝗹𝗶𝘁𝘁𝗹𝗲 𝗼𝘃𝗲𝗿 𝟱𝟬𝟬 𝗼𝗳 𝘆𝗼𝘂. The guy who got out of prison who's learning to code to the senior at Amazon that feels like he's been lucky his whole career and too many bootcamp grads to count. I share the themes in these conversations and the advice I've given to the most recurring questions like: 1. What to build for a side project? 2. Why does my LinkedIn suck? 3. Feeling like an impostor and a practical approach to quiet that voice down 𝗟𝗶𝘀𝘁𝗲𝗻 𝗵𝗲𝗿𝗲: https://lnkd.in/dEV2dW9U	UNKNOWN	Brian	Jenney	12,613	12,613	59	18	1	0.006184	null	2024-02-05 09:45:11	https://www.linkedin.com/feed/update/urn:li:activity:7160315837994696705
urn:li:activity:7159223589039132673	Here's the awful debugging process I used to use: 1. Add a console log in the code 2. Add more logs 3. Add more logs 4. Add more logs 5. Refresh 100 times 6. Cry a little For debugging FE apps, a 𝚍𝚎𝚋𝚞𝚐𝚐𝚎𝚛 statement can save you a lot of headache. Pause execution and walk through the code line by line or step into a function to see what's happening. Also logging with 𝚌𝚘𝚗𝚜𝚘𝚕𝚎.𝚕𝚘𝚐({𝚜𝚘𝚖𝚎𝚅𝚊𝚛})can at least make it a bit easier to see what you're inspecting. 𝗙𝗼𝗿 𝗡𝗼𝗱𝗲/𝗘𝘅𝗽𝗿𝗲𝘀𝘀 𝗮𝗽𝗽𝘀 𝗵𝗼𝘄𝗲𝘃𝗲𝗿, 𝘁𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗹𝗶𝘁𝘁𝗹𝗲 𝗺𝗼𝗿𝗲 𝘀𝗲𝘁 𝘂𝗽 𝗶𝗻𝘃𝗼𝗹𝘃𝗲𝗱. If you're using VS Code (cuz of course you are) you can set breakpoints in the code and run in debug mode to pause like you would in the browser. I walk through it in the video below.	VIDEO	Brian	Jenney	12,769	12,769	100	10	9	0.009319	null	2024-02-02 09:19:25	https://www.linkedin.com/feed/update/urn:li:activity:7159223589039132673
urn:li:activity:7158871892253171712	5 Biggest mistakes of my coding career? 1. Not learning the fundamentals before diving into frameworks 2. Refusing to admit when I didn’t know something 3. Only taking on tasks I knew I could finish 4. Not understanding how engineering relates to business goals 5. Staying silent 🤐 That last one hurt me the most. I thought I was playing it safe by taking on easy tickets. I nodded my head during estimation sessions and gave bland status updates. I never shared my ideas during meetings. I just wanted to blend in. It was the most dangerous thing I could’ve done. They say the tallest blade of grass is the first to get cut. Yeah, I guess. It’s also the one growing the fastest. Companies need average developers more than they’d like to admit. But, if career trajectory and increased hire-ability is your goal, then playing it safe is your greatest threat.	UNKNOWN	Brian	Jenney	17,441	17,441	148	13	4	0.00946	null	2024-02-01 09:36:14	https://www.linkedin.com/feed/update/urn:li:activity:7158871892253171712
urn:li:activity:7158141676874604544	Some of my most hated advice for junior developers or bootcamp grads is to "𝘫𝘶𝘴𝘵 𝘤𝘰𝘯𝘵𝘳𝘪𝘣𝘶𝘵𝘦 𝘵𝘰 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦". 𝗪𝗶𝗹𝗹 𝗶𝘁 𝗺𝗮𝗸𝗲 𝘆𝗼𝘂 𝘀𝘁𝗮𝗻𝗱 𝗼𝘂𝘁? 𝘔𝘢𝘺𝘣𝘦. (I think a lot of you over-estimate just how involved your average software developer is in the coding community). 𝗪𝗶𝗹𝗹 𝘆𝗼𝘂 𝗽𝘂𝗹𝗹 𝘆𝗼𝘂𝗿 𝗵𝗮𝗶𝗿 𝗼𝘂𝘁 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼 𝗳𝗶𝗴𝘂𝗿𝗲 𝗼𝘂𝘁 𝗵𝗼𝘄 𝘁𝗼 𝗴𝗲𝘁 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗲𝗿𝗴𝗲𝗱 𝘁𝗼 𝗮𝗻𝘆 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘁𝗵𝗮𝘁 𝘄𝗼𝘂𝗹𝗱 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗶𝗺𝗽𝗿𝗲𝘀𝘀 𝗽𝗲𝗼𝗽𝗹𝗲? Absolutely. 𝗔𝗿𝗲 𝘁𝗵𝗲𝘆 𝘀𝘁𝗶𝗹𝗹 𝘄𝗼𝗿𝘁𝗵 𝗲𝘅𝗽𝗹𝗼𝗿𝗶𝗻𝗴? For sure. Open source is a beautiful thing. We stand on the shoulders of tech giants... for free. It's crazy that software like React, NextJS, Serverless and the 1.3 million NPM packages you need to scaffold a simple front end app are available on the web 😅. That being said, it's not a great place for junior devs to start: - overwhelming complexity - high bar for entry - lack of guidance Instead, try this - clone down a popular project - try to get it working locally - extend some functionality - hit a debugger statement that you’ve added This gives you the benefit of exploring open source and what it’s like to interact with a production-grade codebase instead of fishing around the 420 open issues only to fix a typo in the README 😅 or overwhelm the maintainers with more code to dig through (for free).	UNKNOWN	Brian	Jenney	13,403	13,403	111	14	2	0.009475	null	2024-01-30 09:29:01	https://www.linkedin.com/feed/update/urn:li:activity:7158141676874604544
urn:li:activity:7157767546614517760	So much coding “content” boils down to some dude in a laptop typing fast af in the dark with a hood on his head. Or maybe some bald dude with a blue background telling you about JS… so cringe. As I was scrolling and trolling on IG, I was shocked to see someone actually breaking down tough concepts like the event loop, closure and hoisting. Ya’ know, practical stuff that actually might help you learn. No hot takes. No click bait. Just helpful JS stuff. David Rogers sat down with me and breaks down how he learned to code without a bootcamp, landed his first job and the difficulties of working in tech. If your timeline is full of fear-mongers, anxiety-pushers and big bald heads, give him a follow maybe.	IMAGE	Brian	Jenney	3,906	3,906	45	9	1	0.014081	null	2024-01-29 08:35:40	https://www.linkedin.com/feed/update/urn:li:activity:7157767546614517760
urn:li:activity:7156677967807406080	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. 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	UNKNOWN	Brian	Jenney	27,940	27,940	142	30	2	0.006228	null	2024-01-26 08:12:33	https://www.linkedin.com/feed/update/urn:li:activity:7156677967807406080
urn:li:activity:7156327042853048321	We've seen enough highlight reels from last year. Here were my biggest blunders in 2023: 1. 𝗖𝗼𝗱𝗶𝗻𝗴 𝘄𝗮𝘆 𝘁𝗼𝗼 𝗺𝘂𝗰𝗵 𝗮𝘀 𝗮 𝗺𝗮𝗻𝗮𝗴𝗲𝗿. I fell into my comfort zone instead of improving our processes and expanding my knowledge of our other systems. 2. 𝗡𝗼𝘁 𝗽𝗹𝗮𝘆𝗶𝗻𝗴 𝗽𝗼𝗹𝗶𝘁𝗶𝗰𝘀. Like it or not, presentations and publicizing your teams' work are important. 3. 𝗙𝗼𝗰𝘂𝘀𝗶𝗻𝗴 𝗼𝗻 𝘁𝗵𝗲 𝘄𝗿𝗼𝗻𝗴 𝗺𝗲𝘁𝗿𝗶𝗰𝘀. I chased likes for too long on social media. They don't equal cash or genuine engagement. At work I focused on arbitrary Lighthouse scores which didn't move the needle for the business. There were many more 😅 but these stuck out to me as areas where I need to improve going forward. Let’s see what I break in 2024!	UNKNOWN	Brian	Jenney	3,636	3,636	29	1	0	0.008251	null	2024-01-25 08:55:38	https://www.linkedin.com/feed/update/urn:li:activity:7156327042853048321
urn:li:activity:7155956086628306945	I had 500 15 minute conversations with developers from all over the world in the last 18 months. Here are my takeaways: - 𝗶𝗺𝗽𝗼𝘀𝘁𝗼𝗿 𝘀𝘆𝗻𝗱𝗿𝗼𝗺𝗲 𝗶𝘀 𝗽𝗿𝗲𝘃𝗮𝗹𝗲𝗻𝘁 𝗮𝗻𝗱 𝗿𝗮𝗺𝗽𝗮𝗻𝘁 at all levels (shocker) - most junior developers need to optimize their resumes to show 𝗶𝗺𝗽𝗮𝗰𝘁 𝗼𝘃𝗲𝗿 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 - 𝗽𝗶𝗰𝗸𝗶𝗻𝗴 𝗮 𝗴𝗼𝗼𝗱 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰t is something most developers want to do but don’t know where to start (just follow John Crickett and steal his projects or maybe Odin Project) - 𝗻𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴, 𝗰𝗼𝗹𝗱 𝗮𝗽𝗽𝗹𝘆𝗶𝗻𝗴 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗶𝗻 𝗽𝘂𝗯𝗹𝗶𝗰 𝗔𝗟𝗟 𝘄𝗼𝗿𝗸 - the trick is sticking to one long enough to see results - 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗮𝗻𝗱 𝗫 𝗵𝗮𝘃𝗲 𝗮𝘄𝗲𝘀𝗼𝗺𝗲 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝗶𝗲𝘀 despite what anyone says to the contrary I was personally shocked to hear just how many of us don’t feel good or smart enough. I do believe that some self-assessment is healthy and useful. I also believe that working remotely with cloudy expectations creates an environment for negative assessments to fester. 𝗜𝗳 𝗶𝘁’𝘀 𝗮𝗻𝘆 𝗰𝗼𝗻𝘀𝗼𝗹𝗮𝘁𝗶𝗼𝗻, 𝗸𝗻𝗼𝘄 𝘁𝗵𝗮𝘁 𝗯𝗮𝘀𝗶𝗰𝗮𝗹𝗹𝘆 𝗲𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝗜’𝘃𝗲 𝘀𝗽𝗼𝗸𝗲𝗻 𝘁𝗼, 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝘀𝗲𝗻𝗶𝗼𝗿 𝗮𝘁 𝗔𝗺𝗮𝘇𝗼𝗻 𝘁𝗼 𝘁𝗵𝗲 𝗷𝘂𝗻𝗶𝗼𝗿 𝘄𝗵𝗼 𝗷𝘂𝘀𝘁 𝗴𝗼𝘁 𝗵𝗶𝗿𝗲𝗱 𝗳𝗲𝗲𝗹𝘀 𝗹𝗶𝗸𝗲 𝘁𝗵𝗲𝗿𝗲 𝗶𝘀 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲𝗶𝗿 𝘁𝗼𝗼𝗹 𝗯𝗲𝗹𝘁.	IMAGE	Brian	Jenney	10,642	10,642	119	21	0	0.013155	null	2024-01-24 08:17:01	https://www.linkedin.com/feed/update/urn:li:activity:7155956086628306945
urn:li:activity:7155601374536187904	Write code for long enough and you’ll see every sacred cow get slaughtered: 𝗧𝗗𝗗 𝗼𝗿 𝗗𝗶𝗲! - except there are teams that have <1 test and deliver safely (manual QA anyone?) 𝗧𝘆𝗽𝗲𝘀𝗰𝗿𝗶𝗽𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗢𝗡𝗟𝗬 𝗰𝗵𝗼𝗶𝗰𝗲 𝗳𝗼𝗿 𝗺𝗼𝗱𝗲𝗿𝗻 𝘄𝗲𝗯 𝗮𝗽𝗽𝘀 - unless maybe your team prefers JSDoc. Or better yet, you don’t want or need types to solve a problem you didn’t even know you had. 𝗣𝗮𝗶𝗿 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗳𝗼𝗿 𝗯𝗲𝘁𝘁𝗲𝗿 𝗰𝗼𝗱𝗲 𝗾𝘂𝗮𝗹𝗶𝘁𝘆! - but sometimes, it can be a slow and lop-sided affair where you just watch someone else type 𝗖𝗜/𝗖𝗗 𝗶𝘀 𝗮 𝗺𝘂𝘀𝘁! - except when your project involves highly complex or safety-critical systems where manual reviews are essential. CI/CD might introduce more risks than benefits. 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗳𝗼𝗿 𝘀𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆! - unless you're dealing with a small application where the overhead of managing 420 of services just doesn’t make sense. I was naive and arrogant enough at one point to assume there was THE way to do something based on some article or bald dude with a blue background on LI. Hate those types amirite? I still think there are patterns that tend to work better than others and in the absence of time or to decrease risk - it’s best to pick a tried and true approach. 𝗧𝗵𝗮𝘁 𝗯𝗲𝗶𝗻𝗴 𝘀𝗮𝗶𝗱, 𝗶𝗳 𝘆𝗼𝘂 𝗰𝗮𝗻’𝘁 𝗮𝗿𝗴𝘂𝗲 𝗳𝗼𝗿 𝗯𝗼𝘁𝗵 𝘀𝗶𝗱𝗲𝘀 𝗼𝗳 𝗮𝗻 𝗮𝗿𝗴𝘂𝗺𝗲𝗻𝘁, 𝘆𝗼𝘂 𝗺𝗮𝘆 𝗻𝗼𝘁 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗶𝘁 𝘄𝗲𝗹𝗹 𝗲𝗻𝗼𝘂𝗴𝗵 𝘁𝗼 𝗮𝗿𝗴𝘂𝗲 𝗳𝗼𝗿 𝗲𝗶𝘁𝗵𝗲𝗿.	UNKNOWN	Brian	Jenney	13,483	13,483	93	50	6	0.011051	null	2024-01-23 09:18:27	https://www.linkedin.com/feed/update/urn:li:activity:7155601374536187904

Subsets and Splits

No community queries yet

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