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:7085620410423132162	A few areas where most devs struggle after they are hired: 1. Code quality 2. Git 3. Estimations It's not all about getting your code to run. Like it or not, you will be judged on whether or not you delivered working code on time. I'm not a fan of estimates. Humans naturally suck at them. When I mentor developers who were recently hired, I show them this tactic I've used to 𝗿𝗲𝘁𝗿𝗼𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲 their work and suck a bit less. Hope you find it useful.	VIDEO	Brian	Jenney	13,363	13,363	121	17	9	0.011001	null	2023-07-14 07:08:36	https://www.linkedin.com/feed/update/urn:li:activity:7085620410423132162
urn:li:activity:7084916877600165888	Don’t be fooled that I know a ton because I’m an engineering manager. I’m just faking it better than you. I talk a lot about the mistakes I’ve made in the past but I’m still learning and failing 10 years later. I may have been a Senior Software Engineer but when I became Engineering Manager I became junior again. My biggest mistakes in the last 12 months? - Not pulling in other departments and stakeholders before building a solution - which led to 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝘄𝗿𝗼𝗻𝗴 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻 and lots of hours of work to fix it. - 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗺𝗼𝗿𝗲 𝗰𝗼𝗱𝗲 𝘁𝗵𝗮𝗻 𝗜 𝘀𝗵𝗼𝘂𝗹𝗱 𝗵𝗮𝘃𝗲 because it’s where I feel comfortable. That time should have been spent improving processes for the team. - 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗜 𝘄𝗮𝘀 𝗮𝗯𝗼𝘃𝗲 𝗽𝗼𝗹𝗶𝘁𝗶𝗰𝘀. 𝙏𝙝𝙖𝙩 𝙡𝙖𝙨𝙩 𝙤𝙣𝙚 𝙞𝙨 𝙬𝙝𝙚𝙧𝙚 𝙄 𝙨𝙚𝙚 𝙖 𝙡𝙤𝙩 𝙤𝙛 𝙙𝙚𝙫𝙚𝙡𝙤𝙥𝙚𝙧𝙨 𝙛𝙖𝙞𝙡. “Politics” is really an umbrella term for anything outside of technical work but it’s incredibly important. Building relationships, giving presentations and creating visibility for my team are areas where I’ve made efforts to improve. I have no clue what the hell I’m doing sometimes, but I’m starting to figure it out. My biggest takeaways over the last 12 months? - 𝗔𝘀𝗸 𝗳𝗼𝗿 𝗵𝗲𝗹𝗽 𝗺𝗼𝗿𝗲 𝗼𝗳𝘁𝗲𝗻 and don’t assume intentions or motivations - 𝗣𝗿𝗼𝗺𝗼𝘁𝗲 𝗼𝘁𝗵𝗲𝗿𝘀 𝘁𝗼 𝗽𝗿𝗼𝗺𝗼𝘁𝗲 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳. Giving public thanks and shining the spotlight on my team members creates visibility without bragging (also - sometimes you gotta brag) - 𝗙𝗶𝘅 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀, don’t work around them - 𝗦𝗼𝗹𝘃𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝘁𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱 𝗳𝗶𝘅𝗶𝗻𝗴 not (just) because it seems fun or interesting We're all curious - what's a mistake you've made recently and how can others avoid it?	UNKNOWN	Brian	Jenney	6,922	6,922	95	10	0	0.015169	null	2023-07-12 09:30:12	https://www.linkedin.com/feed/update/urn:li:activity:7084916877600165888
urn:li:activity:7084554473120911360	Create React App is dead. NextJS is king. This is not a trivial change. NextJS introduces an entirely new paradigm and is full stack first. Let me introduce you to a host of new acronyms you will now need to be familiar with: - RSC - SSR - ISR - SSG - XPF 𝘐 𝘮𝘢𝘥𝘦 𝘰𝘯𝘦 𝘰𝘧 𝘵𝘩𝘰𝘴𝘦 𝘶𝘱 😮. As a full-stack JS developer, I like many of the things about NextJS like page-based routing, API routes, edge runtime and SEO friendliness. Excellent docs and high adoption means you won’t need to scramble to find answers to questions. Chat-GPT will be much less useful, however. NextJS 13 was released recently and as you may know, Chat-Gippity only knows its stuff up to 2021. Here’s what I’m doing to make sure I don’t fall too far behind: - Adding more challenges to my Not Another Course challenges (link in profile) that focus on NextJS - Watching YouTubers like Theo Browne go over complex concepts - Reading the NextJS docs - Building sh*t If there’s one thing the JS community likes more than new frameworks, it’s drama 😅. If you’re using NextJS 13 what do you love or hate?	UNKNOWN	Brian	Jenney	18,080	18,080	180	57	5	0.013385	null	2023-07-11 09:16:03	https://www.linkedin.com/feed/update/urn:li:activity:7084554473120911360
urn:li:activity:7084192059363885056	Congratulations! You landed your first software engineering role. Now an entirely new and much longer game begins. So where should you spend your focus now? I know several developers who were recently hired. Some from my own Not Another Course community and others from the 15-minute chats I do (link in profile). 𝗛𝗲𝗿𝗲’𝘀 𝘄𝗵𝗮𝘁 𝗜 𝘄𝗼𝘂𝗹𝗱 𝗱𝗼 𝗶𝗳 𝗜 𝘄𝗲𝗿𝗲 𝘁𝗵𝗲𝗺: - learn the code deployment process - ask to shadow the on-call engineer - read through previous code reviews from different developers to understand their code and feedback styles - create my own 30-day plan and have a goal to release code to production - understand the testing strategy (QA, unit tests or some combination?) - ask someone to help me navigate the observability tools - enjoy the ride 😎 If you were recently hired, what’s one thing you would suggest to incoming developers?	UNKNOWN	Brian	Jenney	9,335	9,335	101	16	1	0.012641	null	2023-07-10 08:57:01	https://www.linkedin.com/feed/update/urn:li:activity:7084192059363885056
urn:li:activity:7083109417751121920	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 video below to write your first unit test with Jest and learn the basics of testing.	VIDEO	Brian	Jenney	13,981	13,981	102	11	4	0.008369	null	2023-07-07 09:41:55	https://www.linkedin.com/feed/update/urn:li:activity:7083109417751121920
urn:li:activity:7082742507645648896	Top 6 services I used to broaden my skills as a software engineer: 1. AlgoExpert/FrontEndExpert - finally someone made a solid offering for the JS and ReactJS interview with practical exercises 2. CodeCrafters - I like this site so much. You build complex software that passes tests to see if it works. Addictive and inspired my own program (link in profile of course). 3. Kindle - I read books from smarter developers. I won’t give you a listicle here, there are plenty out there already. 4. Plato - when I became a manager I was overwhelmed. I needed mentorship and they provided some of the best I could’ve asked for. 5. ByteByteGo - system design is where it’s at. As coding can increasingly be handled by AI tools, it’s more important than ever to understand the bigger picture. 6. JoinTaro - there aren’t a lot of resources out there for mid and senior-level devs. Taro fills in the gap here with practical career advice that I steal from time to time 🤫. No one paid me to write this. I just use these tools and think they’re the bee's knees. Use em. Or don’t. Whatever. Anything out there I missed?	UNKNOWN	Brian	Jenney	15,529	15,529	148	22	4	0.011205	null	2023-07-06 09:31:55	https://www.linkedin.com/feed/update/urn:li:activity:7082742507645648896
urn:li:activity:7082372599736893441	Junior dev move 101: Wasting hours solving a problem a co-worker could’ve helped you figure out in minutes. You are ultimately judged on the work you complete, not your ability to slog through problems in solitude. When you bump your head against your technical depth, acknowledge it and ask for help. But for Jeebus' sake please don’t just say “I can’t figure out [x]” 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.	UNKNOWN	Brian	Jenney	12,358	12,358	207	21	1	0.018531	null	2023-07-05 08:25:26	https://www.linkedin.com/feed/update/urn:li:activity:7082372599736893441
urn:li:activity:7080555976503808000	Are you really a front end developer? Front end roughly translates to "JS developer" on many teams. This means you will be working on anything JS-related including backend services written with NodeJS. Debugging front end apps is trivial. Add a 𝚍𝚎𝚋𝚞𝚐𝚐𝚎𝚛 statement in the code and you can pause execution in the browser. Node/Express apps aren't so simple. There is a little more tooling to set up within VS Code to avoid using 108 console logs that I'll show you here. A much smarter developer showed me this trick years ago and it's been a life-saver when trying to debug critical incidents.	VIDEO	Brian	Jenney	4,432	4,432	159	16	5	0.040614	null	2023-06-30 08:35:17	https://www.linkedin.com/feed/update/urn:li:activity:7080555976503808000
urn:li:activity:7079843404561465344	As a junior developer, your problems are painfully common. That doesn't make them any less valid. After over 350 phone calls with developers from around the world I have some sympathy and more importantly, some 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝘁𝗵𝗲 𝘁𝗼𝗽 𝟯 𝗶𝘀𝘀𝘂𝗲𝘀 𝘆𝗼𝘂'𝗿𝗲 𝗳𝗮𝗰𝗶𝗻𝗴. Resources and links to docs included. 😎	ARTICLE	Brian	Jenney	4,866	4,866	59	4	2	0.013358	null	2023-06-28 08:30:37	https://www.linkedin.com/feed/update/urn:li:activity:7079843404561465344
urn:li:activity:7079473479372156929	Shocking and not so shocking takeaways from the 2023 Stack Overflow Developer Survey 1. 𝗝𝗮𝘃𝗮𝘀𝗰𝗿𝗶𝗽𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 programming language - take that haters 2. 𝗘𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝘂𝘀𝗲𝘀 𝗩𝗦 𝗖𝗼𝗱𝗲 - learn it like a pro. 3. 𝗡𝗲𝘅𝘁𝗝𝗦 𝘄𝗶𝗹𝗹 𝘀𝘂𝗿𝗽𝗮𝘀𝘀 𝗔𝗻𝗴𝘂𝗹𝗮𝗿 𝗶𝗻 𝗽𝗼𝗽𝘂𝗹𝗮𝗿𝗶𝘁𝘆. I’d bet the house on learning it. Same with Typescript. 4. Bootcamps love MERN - 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹𝘀 𝗹𝗼𝘃𝗲 𝗦𝗘𝗥𝗡. There’s never been a better time to learn SQL with offerings like Supabase that make it too easy to start. 5. 𝗠𝗼𝘀𝘁 𝗱𝗲𝘃𝘀 𝗮𝗿𝗲 𝗙𝗦. You probably should be too... more on that later. Lastly, don't let a survey from a bunch of SO power users dictate your career path but ignore some of these trends at your own risk 😅.	UNKNOWN	Brian	Jenney	24,619	24,619	218	24	8	0.010155	null	2023-06-27 08:51:11	https://www.linkedin.com/feed/update/urn:li:activity:7079473479372156929
urn:li:activity:7079111095717621763	You've applied to every company in the Tri-State area. 𝙉𝙤 𝙤𝙣𝙚 𝙞𝙨 𝙝𝙞𝙧𝙞𝙣𝙜. 𝙏𝙝𝙚 𝙢𝙖𝙧𝙠𝙚𝙩 𝙞𝙨 𝙨𝙖𝙩𝙪𝙧𝙖𝙩𝙚𝙙. 𝙔𝙤𝙪 𝙨𝙝𝙤𝙪𝙡𝙙 𝙟𝙪𝙨𝙩 𝙡𝙚𝙖𝙧𝙣 [𝙨𝙤𝙢𝙚 𝙣𝙚𝙬 𝙩𝙚𝙘𝙝𝙣𝙤𝙡𝙤𝙜𝙮] I've heard some version of all these frustrations for nearly 10 years. In fact, the ONLY time I stopped hearing these phrases was during the pandemic hiring spree. 𝗦𝗼𝗺𝗲 𝗵𝗮𝗿𝘀𝗵 𝘁𝗿𝘂𝘁𝗵𝘀: - Mass applying does work - I don't care what influencer tells you differently - Networking works too - Luck is a factor no one wants to admit - You can control your skills - not the timeline to get hired 𝗦𝗼𝗺𝗲 𝘀𝘁𝘂𝗳𝗳 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗳𝗶𝘅 𝗾𝘂𝗶𝗰𝗸𝗹𝘆: - Get 500 connections on LinkedIn to be more discoverable - Remove any mention of junior/aspiring/student from your profiles - Don't apply for only junior roles - let the market decide - Use strong language on your resume to stand out (𝙬𝙝𝙖𝙩 𝙮𝙤𝙪 𝙗𝙪𝙞𝙡𝙩, 𝙮𝙤𝙪𝙧 𝙧𝙤𝙡𝙚 𝙖𝙣𝙙 𝙬𝙝𝙖𝙩 𝙬𝙖𝙨 𝙩𝙝𝙚 𝙗𝙚𝙣𝙚𝙛𝙞𝙩) - Check your portfolio site in mobile view and make sure it looks decent 😅 If you were recently hired - what worked for you?	UNKNOWN	Brian	Jenney	9,752	9,752	123	23	5	0.015484	null	2023-06-26 09:26:08	https://www.linkedin.com/feed/update/urn:li:activity:7079111095717621763
urn:li:activity:7078016351084163072	Do I actually think you'll get a dynamic programming question at your next interview? I sure in the hell hope not 😅 If you do - I'll bet you a bucket of donuts it'll be something like: - refactor fibonacci to use DP - find the maximum/minimum sum in an array - find the number of paths in a maze Check out this bandicoot below as he explains an approach to a common DP problem 👇	VIDEO	Brian	Jenney	1,299	1,299	28	5	0	0.025404	null	2023-06-23 08:17:48	https://www.linkedin.com/feed/update/urn:li:activity:7078016351084163072
urn:li:activity:7077306686197088257	At some point, we told all new developers they had to become mini LinkedIn influencers. I disagree. Kinda. A few weeks ago I invited a former co-worker to speak to the Not Another Course community. She’s an amazing developer who I knew could offer some insight and practical advice for developers at the early stages of their careers. I was shocked to learn that she ended up working on our team from a post that caught the attention of our former VP. This led to an interview that she crushed. A mentee of mine had an even wilder story: He follows a popular YouTuber who he reached out to that ended up referring him for a role where he currently works. He hadn’t even graduated from his boot camp yet. These stories aren’t typical. They also can’t be ignored. Networking and learning in public work, despite my own biases. Do you know what else works? - Never writing a word on LinkedIn. - Making connections with people through comments on their posts. - Mass applying. - Going on Facebook and asking your high school friends and family if they know anyone who's hiring Pick a strategy you can actually follow and then do it. They all (can) work.	UNKNOWN	Brian	Jenney	4,777	4,777	70	13	1	0.017584	null	2023-06-21 08:39:21	https://www.linkedin.com/feed/update/urn:li:activity:7077306686197088257
urn:li:activity:7076944302446120961	The stuff your coding boot camp didn’t tell you about being a software developer: - On-calls can be brutal, with unexpected 2 AM weekend wake-ups on a Saturday - Your day may be up to 50% meetings - They asked you to traverse a binary tree during the interview. Your first task is to change a button's color - You didn’t negotiate your salary? You lost money - You won’t be building anything from scratch - Sometimes sh*tty code is good enough - JIRA - Git will either save or destroy hours of your day - so git good	UNKNOWN	Brian	Jenney	10,100	10,100	197	32	6	0.023267	null	2023-06-20 09:50:39	https://www.linkedin.com/feed/update/urn:li:activity:7076944302446120961
urn:li:activity:7075482197922623490	Very practically, the 2 easiest ways to stand out as a developer on a new team: 1. Write some documentation 2. Write a mother flipping test But your bootcamp didn’t teach you how to write a unit test. 😞 Lemme show you a short cut to get you started if you’re using ReactJS:	VIDEO	Brian	Jenney	13,350	13,350	142	13	2	0.01176	null	2023-06-16 07:59:09	https://www.linkedin.com/feed/update/urn:li:activity:7075482197922623490
urn:li:activity:7075132396357996544	I have a confession. Over the last year, I’ve done nearly 400 phone calls with developers from all around the world. The main topics we covered: 1. Getting hired 2. Preparing for interviews 3. Creating side projects And lots, I mean LOTS of tackling impostor syndrome. 𝗧𝗵𝗲𝘀𝗲 𝗰𝗮𝗹𝗹𝘀 𝘄𝗲𝗿𝗲 𝗳𝗿𝗲𝗲 𝗯𝘂𝘁 𝗜 𝗵𝗮𝗱 𝗮𝗻 𝘂𝗹𝘁𝗲𝗿𝗶𝗼𝗿 𝗺𝗼𝘁𝗶𝘃𝗲. First off, I sell courses to people. This originally started as a marketing tactic but less than 1% of the calls converted to customers. I kept it going. I was learning too much. I could feel the difference it made for people. I also remember all the feelings I had when I started learning to code and got my first job. 𝗗𝗼𝘂𝗯𝘁. 𝗙𝗲𝗮𝗿. 𝗔𝗻𝘅𝗶𝗲𝘁𝘆. 𝗛𝗼𝗽𝗲. Then I remember all the strangers on the internet or at meetups who helped me. Don’t get me wrong, I’m still selling stuff but that’s not the sole intention of these calls. If I can save you a few hours, days or even years from making the same mistakes I did then I’m happy to give you 15 minutes of my time. Also, when some of you strike it big I can come groveling to you for a consulting role in the future 😅. This weekend I’ll be sharing the lessons I’ve learned from speaking with so many of you (𝙨𝙞𝙜𝙣 𝙪𝙥 𝙖𝙩 𝙩𝙝𝙚 𝙨𝙞𝙩𝙚 𝙞𝙣 𝙗𝙞𝙤).	UNKNOWN	Brian	Jenney	7,502	7,502	73	13	0	0.011464	null	2023-06-15 08:35:14	https://www.linkedin.com/feed/update/urn:li:activity:7075132396357996544
urn:li:activity:7074407587634421761	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. What does success for you look like 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.	UNKNOWN	Brian	Jenney	16,130	16,130	111	19	6	0.008431	null	2023-06-13 09:14:50	https://www.linkedin.com/feed/update/urn:li:activity:7074407587634421761
urn:li:activity:7074045199793979392	How does it feel to be the worst developer on a team? Well, I had the unpleasant experience of holding this title when I worked at a small startup. I probably had more technical growth in the short time I was there than at any other company I’ve worked since. You’ve probably heard the advice “If you’re the smartest person in the room, it’s time to leave the room.” Easier said than done. The guilt and anxiety I felt daily were difficult to deal with. There I was, confronted with my limitations and the realization that this wasn’t just all in my head. I could barely keep up with the tasks I was assigned and relied on lots of pairing sessions to get my work done. The company was small - only 3 engineers and they were the kind of developers who gave speeches at conferences and wrote the libraries that other devs use in their daily work. I could either quit or at least attempt to keep up with the other devs and contribute to the best of my ability. I resolved to suck less. I asked the smarty-pants devs what books they suggested I read I audited my Javascript knowledge and wrote out what I knew I had to learn to contribute to discussions I enrolled in a course to learn DSA and comp sci fundamentals Someone made a joke about Djikstra once… who the hell is that? I would find out I never became the 2nd worst developer at this company, but I grew my technical skills, confidence and threshold for failure. As uncomfortable as it was, I now see just how pivotal this experience was. So if you’re just starting, or maybe on a new team and discovering just how little you know…good. Embrace the suck, expose your ignorance and be prepared to learn.	UNKNOWN	Brian	Jenney	11,144	11,144	179	27	3	0.018754	null	2023-06-12 10:00:25	https://www.linkedin.com/feed/update/urn:li:activity:7074045199793979392
urn:li:activity:7072617319927070720	Yes I'm an engineering manager. Yes, I still write code daily. Much less than I used to though. This week, I got to put back on my coding hat and work with my team at The Clorox Company for a hackathon where we built features for our sites to enhance personalization. - integrations with our CMS system to show dynamic content - location-based product recommendations - trending products via our search engine Today is the last day and the team is busy using Loom to record videos to demo their features. Nothing worse than having your project break apart on demo day 😅. Hackathons aren't just a fun getaway from "regular" work - they can provide some real business value. Ideally one of these projects is a winner for the business. At the very least we've discovered how to better leverage new and current tech and prove out ideas. #cloroxdtc	IMAGE	Brian	Jenney	10,945	10,945	138	14	1	0.013979	#cloroxdtc	2023-06-08 11:06:12	https://www.linkedin.com/feed/update/urn:li:activity:7072617319927070720
urn:li:activity:7072247454565330944	𝘞𝘩𝘢𝘵 𝘢𝘳𝘦 5 𝘑𝘚 𝘤𝘰𝘯𝘤𝘦𝘱𝘵𝘴 𝘺𝘰𝘶 𝘢𝘳𝘦 𝘮𝘢𝘬𝘪𝘯𝘨 𝘢 𝘮𝘪𝘴𝘵𝘢𝘬𝘦 𝘣𝘺 𝘕𝘖𝘛 𝘭𝘦𝘢𝘳𝘯𝘪𝘯𝘨? 𝘞𝘩𝘢𝘵 𝘎𝘪𝘵 𝘤𝘰𝘮𝘮𝘢𝘯𝘥𝘴 𝘸𝘪𝘭𝘭 𝘺𝘰𝘶 𝘧𝘪𝘯𝘥 𝘮𝘰𝘴𝘵 𝘶𝘴𝘦𝘧𝘶𝘭? 🤔 Every few days, Anirudh Kadian asked me some really interesting developer-related questions and has now compiled them into a slideshow that maybe you'll find useful, violently disagree with or chuckle at. Check 'em out.	UNKNOWN	Brian	Jenney	7,874	7,874	59	4	0	0.008001	null	2023-06-07 10:07:00	https://www.linkedin.com/feed/update/urn:li:activity:7072247454565330944
urn:li:activity:7071870862659829760	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 to look at your resume - Posts romanticizing a string of rejections - 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 (a link to a helpful article for example) - Posts that share what you’re learning (and struggling with) I've dropped a link to some templates to help you craft learning in public posts in the comments 😉	UNKNOWN	Brian	Jenney	7,495	7,495	83	22	1	0.014143	null	2023-06-06 09:40:14	https://www.linkedin.com/feed/update/urn:li:activity:7071870862659829760
urn:li:activity:7071508479231885313	LinkedIn Sucks. It’s full of: - toxic positivity - recruiters who ghost you - fear peddlers - cringy influencers with their big heads in blue backgrounds It’s also full of: - strangers willing to lend you a hand - quality content you can learn from - inspiring stories - opportunity LinkedIn, like most social media platforms, will do its best to feed you content it believes you will like. If your LI feed sucks, follow some better people. Here's a list of people I follow and get a lot of value from: Harley Ferguson - dev career advice for juniors -> senior John Crickett - side project king Erik Andersen - junior dev job whisperer Alex Chiou && Rahul Pandey - targeted, practical advice for devs looking to accelerate their careers Ryan Talbert - React and JS for career changers Richard Donovan - mindset and fitness for coders Anirudh Kadian - junior dev and entrepreneur with a lot of damn grit Eduardo Vedes ✨ - helps you learn to code Guille Ojeda - AWS and Cloud master Justin Welsh (Non-tech but certainly worth following for business and copy-writing)	UNKNOWN	Brian	Jenney	55,464	55,464	300	45	2	0.006256	null	2023-06-05 10:00:28	https://www.linkedin.com/feed/update/urn:li:activity:7071508479231885313
urn:li:activity:7070436781606793216	My most embarrassing interview? Well, once I ended an interview 10 minutes in when the interviewer asked me a problem I knew I could not solve. I figured I'd save us both some time and awkward chit chat if I just left. So I did. 😢 I vowed to never be in that position again. You see, I sucked at interviewing for years. It ruined my confidence and made me scared to take risks at work. Then I spent thousands of dollars and hundreds of hours learning DSA, system design and reading up on all the parts of JS that I skipped from being mostly self-taught. With my newfound confidence I did around 40 interviews over a year. - 20 mock interviews. - 3 FAANG final rounds. - A dozen non-FAANG. - Too many recruiter screens to count. 𝗥𝗲𝘀𝘂𝗹𝘁: Offer with an increase of ~30K and another one for ~50K. More importantly, a hell of a lot more confidence. If there's 1 single concept that I struggled with most, it was recursion. 𝗛𝗲𝗿𝗲'𝘀 𝗮 𝘃𝗶𝗱𝗲𝗼 𝗡𝗢𝗧 𝘂𝘀𝗶𝗻𝗴 𝗳*𝗰𝗸𝗶𝗻𝗴 𝗳𝗶𝗯𝗼𝗻𝗮𝗰𝗰𝗶 to walk you through some practical recursion. 𝙄'𝙢 𝙘𝙤𝙣𝙨𝙞𝙙𝙚𝙧𝙞𝙣𝙜 𝙙𝙤𝙞𝙣𝙜 𝙖𝙣 𝟴 𝙬𝙚𝙚𝙠 𝙘𝙧𝙖𝙨𝙝 𝙘𝙤𝙪𝙧𝙨𝙚 𝙤𝙣 𝙉𝙤𝙣-𝙁𝘼𝘼𝙉𝙂 𝙞𝙣𝙩𝙚𝙧𝙫𝙞𝙚𝙬𝙨 𝙩𝙖𝙞𝙡𝙤𝙧𝙚𝙙 𝙩𝙤𝙬𝙖𝙧𝙙𝙨 𝙅𝙎 𝙙𝙚𝙫𝙨. 𝘿𝙈 𝙞𝙛 𝙮𝙤𝙪 𝙬𝙖𝙣𝙩 𝙩𝙝𝙚 𝙙𝙚𝙩𝙖𝙞𝙡𝙨.	VIDEO	Brian	Jenney	14,264	14,264	124	12	3	0.009745	null	2023-06-02 10:00:58	https://www.linkedin.com/feed/update/urn:li:activity:7070436781606793216
urn:li:activity:7070058936183185408	I thought I was supposed to be happy. I got promoted to Senior Software Engineer. I had actually written this goal in my notebook 2 years prior. Once the initial excitement faded, I started to freak out. What would they expect from me now? The other seniors were much smarter than me. I still didn’t understand areas of the codebase that I thought I should. Was this a mistake? My brain went through every possible scenario that would lead to my failure or get me “exposed.” - I wouldn’t be able to figure out a critical issue and be fired. - A new senior member would code circles around me. - I’d get called on in a meeting to offer a solution and have no answer. Maybe you think like me 😅. I’ve had this feeling re-appear when I was promoted to Staff and then moved into management. I’ve come to accept it. New role = unknown. The unknown is scary. In the absence of experience, you imagine what MIGHT happen and how to best protect yourself from failure. One thing I started doing to tame the negative voice in my head is to use others’ knowledge to supplement my lack of experience. I hired mentors. I read books. I thought about the prototype of a person in my position and what they would do. How could I inherit their traits? (please tell me you JS devs caught that one) I hope you’re not as neurotic as me, but after speaking to a few hundred of you… I know that’s not the case.	UNKNOWN	Brian	Jenney	7,268	7,268	74	12	0	0.011833	null	2023-06-01 08:33:54	https://www.linkedin.com/feed/update/urn:li:activity:7070058936183185408
urn:li:activity:7069776177426534400	What you think your next interview will be like: "𝘚𝘰𝘭𝘷𝘦 𝘵𝘩𝘪𝘴 𝘰𝘣𝘴𝘤𝘶𝘳𝘦 𝘢𝘭𝘨𝘰 𝘪𝘯 𝘖(𝘯) 𝘵𝘪𝘮𝘦 𝘸𝘪𝘵𝘩 𝘢 𝘤𝘳𝘢𝘺𝘰𝘯 𝘢𝘯𝘥 𝘱𝘪𝘦𝘤𝘦 𝘰𝘧 𝘤𝘰𝘯𝘴𝘵𝘳𝘶𝘤𝘵𝘪𝘰𝘯 𝘱𝘢𝘱𝘦𝘳" What you're more likely to encounter: "𝘛𝘦𝘭𝘭 𝘮𝘦 𝘢𝘣𝘰𝘶𝘵 𝘢 𝘱𝘳𝘰𝘫𝘦𝘤𝘵 𝘺𝘰𝘶 𝘳𝘦𝘤𝘦𝘯𝘵𝘭𝘺 𝘸𝘰𝘳𝘬𝘦𝘥 𝘰𝘯 𝘣𝘦𝘧𝘰𝘳𝘦 𝘸𝘦 𝘤𝘳𝘦𝘢𝘵𝘦 𝘢 𝘙𝘦𝘢𝘤𝘵 𝘤𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵 𝘵𝘰𝘨𝘦𝘵𝘩𝘦𝘳" That doesn't mean you shouldn't study DSA. But for Bob's sake, please don't do 500 random Leet Code problems. I've outlined a study guide with suggestions for concepts and practice exercises which will take you further than memorizing the solutions to a bunch of LC easy's 😉.	ARTICLE	Brian	Jenney	5,726	5,726	55	6	3	0.011177	null	2023-05-31 14:25:53	https://www.linkedin.com/feed/update/urn:li:activity:7069776177426534400
urn:li:activity:7069334182702821376	5 Biggest mistakes of my coding career? 1. Not learning the fundamentals before diving into frameworks 2. Being afraid to admit when I didn’t know something 3. Only taking on tasks I knew I could finish 4. Not understanding how engineering fits into the company eco-system and business goals 5. Not speaking up 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 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	6,161	6,161	67	15	2	0.013634	null	2023-05-30 09:10:04	https://www.linkedin.com/feed/update/urn:li:activity:7069334182702821376
urn:li:activity:7067522208549519360	Your portfolio projects probably look like a lot of other projects out there: - TODO app. - Weather app. - Clone of [popular app] - Blog - Chat app Here’s the thing, 𝘁𝗵𝗲𝗿𝗲’𝘀 𝗻𝗼𝘁𝗵𝗶𝗻𝗴 𝗮𝘁 𝗮𝗹𝗹 𝘄𝗿𝗼𝗻𝗴 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲𝘀𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀. They can certainly teach you a lot. BUT - when digging through a stack of resumes for an open junior developer position, it is hard to stand out. If your goal is to stand out AND learn something try this: - 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝗮𝗻 𝗔𝗣𝗜 or a real-world problem you are familiar with -𝗦𝗸𝗲𝘁𝗰𝗵 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 using a tool like Excalidraw (a simple piece of paper will do) - 𝗪𝗿𝗶𝘁𝗲 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗹𝗶𝘀𝘁 𝗮𝗻𝗱 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲 how long each one will take and the order to create them - 𝗕𝘂𝗶𝗹𝗱, get stuck, read the docs, ask Chat Gippiter and repeat - 𝗗𝗲𝗽𝗹𝗼𝘆 on Vercel or AWS Now you have an interesting technical story and maybe even your next startup idea.	UNKNOWN	Brian	Jenney	25,338	25,338	262	25	16	0.011958	null	2023-05-25 09:02:43	https://www.linkedin.com/feed/update/urn:li:activity:7067522208549519360
urn:li:activity:7067159835598880769	Are you a “passionate developer”? Do you need to be? If you only got into coding for the money… I think that’s OK. The best developers I’ve met enjoy writing code and most of us do it for fun outside of work. That doesn’t mean YOU have to. There is an odd expectation that software engineers write code outside work hours and it isn’t uncommon to be asked in an interview about your side project or to take a look at your personal GitHub. Why? Do we ask doctors how many patients they’ve seen outside of office hours? Ever ask your plumber about his side project? Of course not. I still believe that in order to be a better-than-average author of code, you will need to find enjoyment in shipping code and squishing bugs. Tech moves fast. To keep up with trends and updates, you’ll likely need some intrinsic desire to do so… cuz your work certainly won’t be providing that time 😉. That being said, I don’t think you need to be a super passionate developer to be a good one. Am I off here? Do you need to genuinely love to code to move past junior code bot?	UNKNOWN	Brian	Jenney	9,637	9,637	107	27	2	0.014112	null	2023-05-24 09:36:28	https://www.linkedin.com/feed/update/urn:li:activity:7067159835598880769
urn:li:activity:7066797441869643776	“𝙄’𝙢 𝙜𝙤𝙞𝙣𝙜 𝙩𝙤 𝙜𝙚𝙩 𝙚𝙭𝙥𝙤𝙨𝙚𝙙,” I thought. As a junior developer, I was really anxious that one day my team would find out I was a hack. Then, one day, I did get “found out” 😬 I was working at a small startup with some incredible talent and when our star engineer left to pursue his own business, he gave me some candid feedback: “𝘐𝘵’𝘴 𝘥𝘪𝘧𝘧𝘪𝘤𝘶𝘭𝘵 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘺𝘰𝘶 𝘴𝘪𝘯𝘤𝘦 𝘺𝘰𝘶 𝘥𝘰𝘯’𝘵 𝘩𝘢𝘷𝘦 𝘢 𝘴𝘵𝘳𝘰𝘯𝘨 𝘨𝘳𝘢𝘴𝘱 𝘰𝘧 𝘴𝘰𝘮𝘦 𝘧𝘶𝘯𝘥𝘢𝘮𝘦𝘯𝘵𝘢𝘭 𝘑𝘢𝘷𝘢𝘴𝘤𝘳𝘪𝘱𝘵 𝘤𝘰𝘯𝘤𝘦𝘱𝘵𝘴 𝘭𝘪𝘬𝘦 𝘤𝘭𝘢𝘴𝘴𝘦𝘴 𝘰𝘳 𝘤𝘭𝘰𝘴𝘶𝘳𝘦. 𝘐 𝘵𝘩𝘪𝘯𝘬 𝘺𝘰𝘶 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘨𝘰 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘵𝘩𝘦 𝘣𝘢𝘴𝘪𝘤𝘴 𝘢𝘯𝘥 𝘭𝘦𝘢𝘳𝘯 𝘵𝘩𝘦𝘴𝘦 𝘵𝘩𝘪𝘯𝘨𝘴.” I was embarrassed. He was also correct. I wrote down his suggestions and made a plan to get more proficient with es6/7 and some of the concepts which had always confused me like promises, prototypal inheritance and decorators. It wasn’t even that difficult. I wondered why I hadn’t done this earlier. In fact it’s the method I still use and share with my mentees: 1. Open the code editor 2. Create a practical example leveraging the concept you’re learning 3. Record a video explaining the concept and your code For promises, you might create a promise using the promise constructor and invoke it using the async/await pattern and then refactor it to use promise chains. Make a video for yourself that you may never even watch. The video simply forces you to articulate what you’ve learned in plain English. Hope that’s helpful.	UNKNOWN	Brian	Jenney	6,119	6,119	91	13	2	0.017323	null	2023-05-23 08:48:20	https://www.linkedin.com/feed/update/urn:li:activity:7066797441869643776
urn:li:activity:7066435051688706048	Very predictable, boring advice that most developers don’t follow: - 𝗗𝗼𝗻’𝘁 𝗼𝘃𝗲𝗿-𝗿𝗲𝗹𝘆 𝗼𝗻 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹𝘀 - build something on your own, get stuck and read the f*cking docs - 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲 before diving into frameworks like React, Angular or Vue - 𝗞𝗲𝗲𝗽 𝘁𝗿𝗮𝗰𝗸 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗮𝗰𝗰𝗼𝗺𝗽𝗹𝗶𝘀𝗵𝗺𝗲𝗻𝘁𝘀. It’s nice to look back at your progress when you’re feeling down - 𝗬𝗼𝘂 𝗰𝗮𝗻’𝘁 𝗰𝗵𝗮𝘀𝗲 𝗲𝘃𝗲𝗿𝘆 𝗻𝗲𝘄 𝘁𝗲𝗰𝗵. Be aware of macro trends in your industry and micro trends in your niche. For example, a JS developer may need to have surface-level knowledge of Serverless and a deeper understanding of NextJS - 𝗦𝘁𝘂𝗱𝘆 𝗖𝗦 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀. They’re slower to change and give you a strong foundation for understanding concepts outside your core language and tech stack - 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝘆𝗼𝘂𝗿 𝗵𝗲𝗮𝗹𝘁𝗵 as much as your work - they are more related than you think What’d I miss?	UNKNOWN	Brian	Jenney	8,592	8,592	133	10	6	0.017342	null	2023-05-22 09:32:56	https://www.linkedin.com/feed/update/urn:li:activity:7066435051688706048
urn:li:activity:7065355444029976576	It's OK to build nothing this weekend. Eat, sleep, code 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 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. This weekend I'll be sharing the diet and workout routine which has taken me from a fluffy, anxiety-ridden coder to a much less fluffy, slightly-less-anxious engineering manager 😅 (link in bio and in comments at some point)	UNKNOWN	Brian	Jenney	6,025	6,025	66	18	2	0.014274	null	2023-05-19 10:11:09	https://www.linkedin.com/feed/update/urn:li:activity:7065355444029976576
urn:li:activity:7064988641869135874	You're hired! 3 months later... you're fired! This is a story I hate to hear and many times it's not avoidable. Poor management. CEO needs a new yacht. Asteroid destroys office. Hey sh*t happens. In this article we explore 2 developer career death traps and how to avoid them.	ARTICLE	Brian	Jenney	7,536	7,536	85	10	4	0.013137	null	2023-05-18 09:44:56	https://www.linkedin.com/feed/update/urn:li:activity:7064988641869135874
urn:li:activity:7064623106924896257	I mentor a lot of boot camp grads. They are universally obsessed with these 2 things: 1. Portfolio projects 2. DSA Here's the deal: - Most companies don't care about your portfolio project. If it's hidden behind a login... just forget about it. Build 1 or 2 really interesting things you can speak about with pride. - Yes study DSA. Nothing wrong with that. Just realize most companies aren't going to ask you these questions. Also, your job will require a completely different skill set. Finally... Double down on the fundamentals of your language and software design patterns. This is what will pay the most dividends and is a lesson I learned later than I should have.	UNKNOWN	Brian	Jenney	12,564	12,564	204	24	7	0.018704	null	2023-05-17 08:57:12	https://www.linkedin.com/feed/update/urn:li:activity:7064623106924896257
urn:li:activity:7064260728894947330	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: - find an avatar - who do I want to be like? - what do they know that I don’t? - create a checklist with the items from the previous step - find mentors or books or both to bring me closer to the avatar - check items off the list and prove to myself that I’m where I need to be Rinse and repeat for each promotion, new company or new role.	UNKNOWN	Brian	Jenney	7,398	7,398	106	21	1	0.017302	null	2023-05-16 09:21:37	https://www.linkedin.com/feed/update/urn:li:activity:7064260728894947330
urn:li:activity:7063898325724364800	You probably won't be the best coder on your team. Especially as a junior. So how do you stand out? As an average developer, there’s still a lot of room to make an impact outside being the highest technical authority. As a very non-rockstar coder, here are some things I’ve done over the years which helped me stand out: - start an engineering book club - volunteer for on-call - onboard junior members - create a PR template to streamline the code review process - offer to assist with others’ work - actually talk during pointing sessions and clarify tasks instead of just nodding my head Of course, getting work done in a timely manner and not significantly adding to the number of bugs in our backlog didn’t hurt either. I don’t think I’ve ever been the “best” coder on any team where I’ve worked. I’ve certainly been the worst in at least 1 company. Let me be clear, you cannot be technically incompetent, start a book club and expect to get recognized and promoted… BUT you also don’t need to wait until you understand JS on a Kyle Simpson level to offer your insight, suggest changes and speak up.	UNKNOWN	Brian	Jenney	5,337	5,337	71	10	0	0.015177	null	2023-05-15 09:43:09	https://www.linkedin.com/feed/update/urn:li:activity:7063898325724364800
urn:li:activity:7062805108643823616	The worst way to spend your weekend? Completing a take-home coding interview that was supposed to take 4 hours but 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.	VIDEO	Brian	Jenney	21,432	21,432	177	21	7	0.009565	null	2023-05-12 08:23:05	https://www.linkedin.com/feed/update/urn:li:activity:7062805108643823616
urn:li:activity:7062441243871477761	Top 5 pieces of advice to save your resume for all your junior devs, including 1 I bet you never considered 👇 1. Stop calling yourself a junior or aspiring. You are a developer. 2. Use strong language. “Led development on [x] feature which [improved some metric]” or “architected” sounds better than “worked with a team on [generic thing]” 3. Lead with your relevant experience. It can be confusing to look at a resume for a dev role and see nothing coding related. Put your projects/volunteer work/side projects at the top. 4. Don't get too cute with the format. Use a plain Word doc to be safe. 5. Add a Loom video with a very brief intro or walkthrough of a project. Like 1 minute max. Now, track the views this video gets. No views? Maybe change your resume. Many views but no calls? Maybe remove the video 😅 What else would you suggest?	UNKNOWN	Brian	Jenney	5,002	5,002	52	10	4	0.013195	null	2023-05-11 08:03:51	https://www.linkedin.com/feed/update/urn:li:activity:7062441243871477761
urn:li:activity:7062086393899995136	You can’t get hired because you have no experience. You have no experience because you can’t get hired. Let’s change that. Reach out to your cousin, aunt or that friend trying to launch their music career and offer to build a website. For free. Make them buy a domain. Or buy one for them - f*ck it. Sketch out the site and the main features and review them with your cousin, I mean the client. Build and deploy. Have them give you a testimonial. Now you have some viable experience, a real deal site to show off and have dipped your toe into freelance.	UNKNOWN	Brian	Jenney	39,578	39,578	401	35	12	0.011319	null	2023-05-10 08:58:42	https://www.linkedin.com/feed/update/urn:li:activity:7062086393899995136
urn:li:activity:7061707159692095490	The market for full stack developers is over-saturated. Learn dev-ops. Maybe C#. Java? PHP perhaps? Become a Chat-Gippity prompt engineer. Yes, that’s the ticket 🤔. I don’t think there’s anything wrong with learning another language or technology but if you change tech as the wind blows, you will quickly be a sub-par developer in many languages rather than a strong developer in 1 or 2. 𝘍𝘦𝘸 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘯𝘦𝘦𝘥 𝘢 𝘴𝘸𝘪𝘴𝘴-𝘢𝘳𝘮𝘺-𝘬𝘯𝘪𝘧𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳. However, IF you are a full stack developer who recently graduated and considering what to learn next (hint hint) I would put these 3 technologies at the top of my list: 1. TypeScript 2. NextJS 3. AWS (lambdas, S3 and IAM) Any others you'd suggest or wish you learned?	UNKNOWN	Brian	Jenney	11,562	11,562	130	41	3	0.015049	null	2023-05-09 07:55:29	https://www.linkedin.com/feed/update/urn:li:activity:7061707159692095490
urn:li:activity:7061362313768964096	3 members from my Not Another Course community just got hired. They’re talented, amazing people and well deserving. And they’re not much different than you. One had been looking for nearly a year for that first role. Another graduated from a program recently. They felt uncertain. Like it would never happen. That maybe they just weren’t good enough. When I think of all the mentees I’ve seen get hired either in my program or in the bootcamps where I’ve taught over the years, there are few hard and fast rules. - Most did NOT learn in public. - Some were not particularly talented. In fact, a few I thought were un-hireable proved me wrong 😅 - Some mass-applied. - A few networked their way to the first role. - Many of their interviews were barely technical. - Some ONLY got LeetCode problems. Your timeline will be unpredictable. Not even Chat-GPT can predict the future… yet. Be persistent, practically optimistic that opportunity will present itself, re-calibrate when you see things not working, maintain your skills and your own success will be inevitable.	UNKNOWN	Brian	Jenney	6,187	6,187	84	5	0	0.014385	null	2023-05-08 10:28:27	https://www.linkedin.com/feed/update/urn:li:activity:7061362313768964096
urn:li:activity:7059942985806872576	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? ❌ A thing that generates a random thing? When I’m not sure what I want to build, I do this: - 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗱𝗮𝘁𝗮 - what API can you use which may have some interesting information? - Use a tool like Postman to 𝗲𝗻𝘀𝘂𝗿𝗲 𝘁𝗵𝗲 𝗔𝗣𝗜 𝗶𝘀 𝘄𝗼𝗿𝘁𝗵𝘄𝗵𝗶𝗹𝗲 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 𝗰𝗼𝗺𝗯𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗼𝗳 𝗻𝗲𝘄 𝗮𝗻𝗱 𝗳𝗮𝗺𝗶𝗹𝗶𝗮𝗿 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗲𝘀 - 𝗚𝗲𝘁 𝘀𝘁𝘂𝗰𝗸, read the docs and build your way out of the hole you’ve dug 😅 Gain more practical knowledge than any 100 hour course could ever offer you.	UNKNOWN	Brian	Jenney	8,118	8,118	115	18	9	0.017492	null	2023-05-04 11:38:14	https://www.linkedin.com/feed/update/urn:li:activity:7059942985806872576
urn:li:activity:7059631200235130881	They told you don't need Redux. 𝘛𝘩𝘦𝘳𝘦'𝘴 𝘵𝘰𝘰 𝘮𝘶𝘤𝘩 𝘣𝘰𝘪𝘭𝘦𝘳𝘱𝘭𝘢𝘵𝘦! 𝘛𝘩𝘦𝘳𝘦 𝘢𝘳𝘦 𝘣𝘦𝘵𝘵𝘦𝘳 𝘴𝘰𝘭𝘶𝘵𝘪𝘰𝘯𝘴! My least favorite one: "𝘑𝘶𝘴𝘵 𝘶𝘴𝘦 𝘊𝘰𝘯𝘵𝘦𝘹𝘵! " With around 8.2 million downloads just last week, there’s a pretty high chance the next company you join will leverage this library. So stop being scared of it. Try learning these concepts/tools: - publisher/subscriber pattern - ducks architecture - FP principles And when you're ready to get your hands dirty with some Redux check out my e-com React App Challenge here https://lnkd.in/gqnbpDCH	UNKNOWN	Brian	Jenney	24,479	24,479	201	54	8	0.010744	null	2023-05-03 14:57:19	https://www.linkedin.com/feed/update/urn:li:activity:7059631200235130881
urn:li:activity:7059165914524504065	Some uncomfortable truths for software engineers: • 𝘠𝘰𝘶, not your company, 𝘢𝘳𝘦 𝘶𝘭𝘵𝘪𝘮𝘢𝘵𝘦𝘭𝘺 𝘳𝘦𝘴𝘱𝘰𝘯𝘴𝘪𝘣𝘭𝘦 𝘧𝘰𝘳 𝘺𝘰𝘶𝘳 𝘨𝘳𝘰𝘸𝘵𝘩 as a developer • You may be really good at writing code but 𝘪𝘧 𝘺𝘰𝘶’𝘳𝘦 𝘶𝘯𝘱𝘭𝘦𝘢𝘴𝘢𝘯𝘵 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘺𝘰𝘶 𝘸𝘪𝘭𝘭 𝘩𝘢𝘷𝘦 𝘢 𝘩𝘢𝘳𝘥 𝘵𝘪𝘮𝘦 𝘨𝘦𝘵𝘵𝘪𝘯𝘨 𝘱𝘳𝘰𝘮𝘰𝘵𝘦𝘥 • Shipping code fast is almost always better than shipping code perfect • 𝘚𝘢𝘺 𝘴𝘰𝘮𝘦𝘵𝘩𝘪𝘯𝘨 𝘪𝘯 𝘢 𝘮𝘦𝘦𝘵𝘪𝘯𝘨… anything. A bad idea to kick off a conversation is better than silence • Your first job will validate you - 𝘺𝘰𝘶𝘳 𝘴𝘦𝘤𝘰𝘯𝘥 𝘸𝘪𝘭𝘭 𝘨𝘦𝘵 𝘺𝘰𝘶 𝘱𝘢𝘪𝘥 What would you add?	UNKNOWN	Brian	Jenney	10,890	10,890	155	17	6	0.016345	null	2023-05-02 07:19:36	https://www.linkedin.com/feed/update/urn:li:activity:7059165914524504065
urn:li:activity:7058849684341096448	Of course you suck at interviewing. You do it once every 2 years and wonder why it’s so difficult. It’s a game with incredibly high stakes that most of us don’t practice until it’s time to play. This is a recipe for disaster. There’s enough information on LinkedIn about what you should and shouldn’t study but that’s only half the game of interviewing. 𝘠𝘰𝘶𝘳 𝘯𝘦𝘳𝘷𝘦𝘴 𝘢𝘳𝘦 𝘨𝘰𝘯𝘯𝘢 𝘨𝘦𝘵 𝘺𝘰𝘶. 𝗜 𝗯𝗼𝗺𝗯𝗲𝗱 𝗮 𝗺𝗼𝗰𝗸 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗹𝗮𝘀𝘁 𝘆𝗲𝗮𝗿 𝘁𝗵𝗮𝘁 𝗵𝗮𝗱 𝘁𝗵𝗲 𝗹𝗼𝘄𝗲𝘀𝘁 𝘀𝘁𝗮𝗸𝗲𝘀 𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲. I mean, it was literally a mock interview. - My heart raced. - I drank too much coffee before the meeting. - I didn’t have water nearby. - I froze up 😳 Don’t wait until the real game starts to get practice. There is simply no substitute for being judged, I mean interviewed, by another human. 𝗜𝗳 𝘆𝗼𝘂’𝗿𝗲 𝗮 𝗹𝗶𝘁𝘁𝗹𝗲 𝘀𝗵𝘆 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀: - Open up Leetcode or whatever tool you’re using to study problems - 𝗦𝗲𝘁 𝘁𝗵𝗲 𝘁𝗶𝗺𝗲𝗿 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗽𝗵𝗼𝗻𝗲 𝗳𝗼𝗿 𝟯𝟬 - 𝟰𝟱 𝗺𝗶𝗻𝘀 - Open up a video recording tool and 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝘆𝗼𝘂𝗿 𝘁𝗵𝗼𝘂𝗴𝗵𝘁 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 and code as you type - Watch it later and 𝗰𝗿𝗶𝗻𝗴𝗲 𝗮 𝗯𝗶𝘁 - Repeat until you 𝗰𝗿𝗶𝗻𝗴𝗲 𝗹𝗲𝘀𝘀	UNKNOWN	Brian	Jenney	8,698	8,698	113	25	2	0.016096	null	2023-05-01 11:09:26	https://www.linkedin.com/feed/update/urn:li:activity:7058849684341096448
urn:li:activity:7057707960898105344	Turns out I don't hate Typescript. I just had no clue how to use it beyond adding a type after a variable. 😬 Now that I'm exploring generics, unions and mapped types, I'm starting to see why you all like it so much.	UNKNOWN	Brian	Jenney	7,994	7,994	115	29	1	0.018139	null	2023-04-28 06:59:01	https://www.linkedin.com/feed/update/urn:li:activity:7057707960898105344
urn:li:activity:7057357474831491073	𝘊𝘰𝘥𝘦 𝘴𝘩𝘰𝘶𝘭𝘥 𝘢𝘭𝘸𝘢𝘺𝘴 𝘧𝘰𝘭𝘭𝘰𝘸 𝘋𝘙𝘠 𝘱𝘳𝘪𝘯𝘤𝘪𝘱𝘭𝘦𝘴! Except, maybe your abstraction is more clever than useful in this case. 𝘛𝘋𝘋 𝘰𝘳 𝘥𝘪𝘦! Or you know, TaDD (write 𝘁ests 𝗮fter 𝗱evelopment is 𝗱one). Or, perhaps manual QA is the correct choice. 𝘛𝘺𝘱𝘦𝘚𝘤𝘳𝘪𝘱𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘯𝘭𝘺 𝘤𝘩𝘰𝘪𝘤𝘦 𝘧𝘰𝘳 𝘴𝘦𝘳𝘪𝘰𝘶𝘴 𝘑𝘚 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴! But maybe it’s overkill for this simple UI app. 𝘗𝘏𝘗 𝘴𝘶𝘹! Maybe to you - but there are tons of developers still crafting amazing software with it. Be careful falling into dogmatic, knee-jerk responses when it comes to writing software. One thing I’ve learned is that there are always exceptions to the rules we accept as coding law. Any sacred cows I missed here?	UNKNOWN	Brian	Jenney	4,697	4,697	46	12	2	0.012774	null	2023-04-27 08:04:42	https://www.linkedin.com/feed/update/urn:li:activity:7057357474831491073
urn:li:activity:7057010976004481024	If you’re hell-bent on learning data structures and algorithms please don’t JUST do 500 random LeetCode problems... I mean, unless that's how you unwind after a day of coding (you sicko). Try this instead: - 𝗹𝗲𝗮𝗿𝗻 𝗰𝗼𝗺𝗺𝗼𝗻 𝗱𝗮𝘁𝗮 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝘀 like trees, graphs, linked lists, stacks and queues - code up these structures from scratch - 𝗹𝗲𝗮𝗿𝗻 𝗰𝗼𝗺𝗺𝗼𝗻 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀 to sort and traverse data in these structures and their practical application (when is a LL better than an array?) - focus on 𝗿𝗲𝗰𝘂𝗿𝘀𝗶𝗼𝗻 and backtracking 𝗔𝗙𝗧𝗘𝗥 learning 𝘁𝗿𝗲𝗲𝘀 (𝘐 𝘧𝘪𝘯𝘥 𝘵𝘩𝘢𝘵 𝘪𝘵 𝘮𝘢𝘥𝘦 𝘮𝘰𝘳𝘦 𝘴𝘦𝘯𝘴𝘦 𝘵𝘩𝘪𝘴 𝘸𝘢𝘺) - 𝘁𝗶𝗺𝗲 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 solving LC problems - shoot for 30 mins for medium problems and write the space and time complexity next to your solution then check it with Chat-GPT - learn 𝗰𝗼𝗺𝗺𝗼𝗻 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵𝗲𝘀 𝘁𝗼 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗲 algorithms (𝘩𝘢𝘴𝘩𝘮𝘢𝘱𝘴, 𝘵𝘢𝘪𝘭-𝘤𝘢𝘭𝘭𝘴, 𝘮𝘦𝘮𝘰𝘪𝘻𝘢𝘵𝘪𝘰𝘯...) Also - realize that just because MAANG exclusively asks DSA, the majority of your interviews as a Javascript developer will probably focus on a combination of behavioral and technical challenges including concepts like string manipulation, working with arrays and objects, JS trivia and building small components using ReactJS.	UNKNOWN	Brian	Jenney	17,177	17,177	153	15	13	0.010537	null	2023-04-26 08:38:36	https://www.linkedin.com/feed/update/urn:li:activity:7057010976004481024
urn:li:activity:7056632902171705345	Ok so maybe I was wrong. I often downplay the importance of networking on LinkedIn or learning in public, but I’m changing my tune. Last Friday, a former co-worker, Nicole Gooden spoke with me and members in my Not Another Course community (link in bio 😉) and shared how posting on LinkedIn helped her land that first role. She was learning in public, invited others to offer suggestions to the code she posted and a VP of technology did just that. This post led to a conversation which led to an interview which resulted in an offer. Crazy. But not really. I’ve been posting on LinkedIn consistently for a year which has led to more amazing connections and even some friendships that I never would have expected. I’ve personally mentored or spoke with many of you simply from putting myself out there. I am not a stellar engineer. I just have some opinions and advice that I’m confident will help you. So I share it. I still get nervous though. What will people think? Is this too cringe? Do I know enough to share? I know I’m not alone. Here’s what’s worked for me when I get paralyzed by “what-if” spiral thinking and maybe will help you as well: - 𝗪𝗿𝗶𝘁𝗲 𝗮𝗯𝗼𝘂𝘁 𝘆𝗼𝘂𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 - you are an expert on this subject - If you’ve benefitted from the wisdom of others, 𝗶𝘁’𝘀 𝘆𝗼𝘂𝗿 𝗱𝘂𝘁𝘆 𝘁𝗼 𝘀𝗵𝗮𝗿𝗲 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂’𝘃𝗲 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 - 𝗘𝘅𝗽𝗼𝘀𝗲 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 𝘁𝗼 𝗰𝗿𝗶𝘁𝗶𝗰𝗶𝘀𝗺 - it will help you grow. If it reveals jerks, then good. You now know where NOT to apply - 𝗡𝗼 𝗼𝗻𝗲 𝗶𝘀 𝗷𝘂𝗱𝗴𝗶𝗻𝗴 𝘆𝗼𝘂 nearly as much as you think We are all too concerned with our own lives to care much about what you’re posting. We read, chuckle (or cringe) and continue to scroll 🤷‍♀️. Worst case - you write something lame. Best case - you increase your surface area for luck and meet great people.	UNKNOWN	Brian	Jenney	8,075	8,075	114	28	0	0.017585	null	2023-04-25 08:11:36	https://www.linkedin.com/feed/update/urn:li:activity:7056632902171705345
urn:li:activity:7056287129760378880	Jacob Pixler went from audio engineer to software developer in a non-tech area after graduating a bootcamp. 𝘞𝘩𝘢𝘵 𝘩𝘦 𝘥𝘪𝘥𝘯'𝘵 𝘥𝘰: - cold apply - only apply for remote roles - target big companies I'll be honest, I was surprised and impressed by his results and search strategy. There is no single path towards that first role as a developer and the best approach is the one that works 😉. Check out Erik Andersen's interview with him here: https://lnkd.in/ghNwThnY	UNKNOWN	Brian	Jenney	5,457	5,457	35	4	1	0.00733	null	2023-04-24 09:56:07	https://www.linkedin.com/feed/update/urn:li:activity:7056287129760378880
urn:li:activity:7055241186533376000	I bet 50% of you are still using 420 console logs to debug your buggy code 🐞. There's a better way. Check out my debugging walkthrough below and let me know any tricks you've developed for investigating unexpected features 😅.	VIDEO	Brian	Jenney	50,869	50,869	331	25	20	0.007392	null	2023-04-21 11:30:53	https://www.linkedin.com/feed/update/urn:li:activity:7055241186533376000
urn:li:activity:7054869019115298816	Here’s the harsh truth about interviews that no one ever really addresses: Luck is a factor. You could be absolutely qualified for a position and study all the relevant material and still bomb. Perhaps your interviewer picks an unreasonably difficult question from their bag of LC problems. The previous interviewee got 2-sum while you got a traveling salesman problem. Maybe a candidate has recently been selected but they didn't call you in time to cancel... 🥲 𝘖𝘳 𝘱𝘦𝘳𝘩𝘢𝘱𝘴 𝘭𝘶𝘤𝘬 𝘸𝘰𝘳𝘬𝘴 𝘪𝘯 𝘺𝘰𝘶𝘳 𝘧𝘢𝘷𝘰𝘳. Maybe you study a particular question that you have memorized and get asked that exact same question. Maybe the interview is not technical at all and just consists of small talk and personality fit. "Oh you surf too? Hired!" 🏄‍♀️ So if you’ve recently bombed an interview or are beating yourself up because you see others achieving success on a timeline that doesn’t seem possible for you, realize that interviews are both a game of skill AND chance.	UNKNOWN	Brian	Jenney	6,665	6,665	106	15	2	0.018455	null	2023-04-20 11:40:52	https://www.linkedin.com/feed/update/urn:li:activity:7054869019115298816
urn:li:activity:7054454680046735360	300 conversation with developers later and I’m convinced that most of us need a sympathetic ear as much as we need career and coding advice. Here’s the thing: 𝗰𝗼𝗱𝗶𝗻𝗴 𝗶𝘀 𝗳𝘂𝗻. It can also be: - lonely - stressful - tedious - confusing Don’t wrap too much of your identity in the code you write. It can be a fickle beast. Sometimes I’m pretty damn good at slinging code. Sometimes I suck. So I hit the gym. Run around a lake. Read stuff. Write on here and in my newsletter (𝘺𝘰𝘶 𝘣𝘦𝘵𝘵𝘦𝘳 𝘩𝘢𝘷𝘦 𝘴𝘪𝘨𝘯𝘦𝘥 𝘶𝘱, 𝘴𝘦𝘳𝘪𝘰𝘶𝘴𝘭𝘺 𝘸𝘩𝘢𝘵 𝘵𝘩𝘦 𝘚𝘢𝘮 𝘏𝘪𝘭𝘭? 𝘓𝘪𝘯𝘬 𝘪𝘯 𝘣𝘪𝘰 😅). This way when one area drags me down, I use another to lift me up. Outside of coding, what are some hobbies you’ve picked up?	UNKNOWN	Brian	Jenney	7,095	7,095	78	35	1	0.016068	null	2023-04-19 07:40:30	https://www.linkedin.com/feed/update/urn:li:activity:7054454680046735360
urn:li:activity:7054105539470888961	Yes, I'm an engineering manager. Yes, I still have a side project. I am woefully late to the TypeScript party. I miss SQL. I want to use Vercel like a cool kid. Here's my side project tech stack so far: - NextJS - Supabase - TypeScript - TailWind This project will be publicly available with limited access. Members of my Not Another Course community (link in bio 😉)will have full access to help them navigate and sort through the massive number of challenges I have created for them. If you know me, you know I'm all about side projects. What technologies are you exploring for your side project?	UNKNOWN	Brian	Jenney	6,440	6,440	66	26	0	0.014286	null	2023-04-18 08:38:28	https://www.linkedin.com/feed/update/urn:li:activity:7054105539470888961
urn:li:activity:7053728822659067905	More developers should run toward critical incidents. It's not as risky as you think. - Likely worst case is you need to lean on your teammates to get it figured out. - Likely best case is you fix it, stand out and gain a lot of respect. Feels riskier to never raise your hand.	UNKNOWN	Brian	Jenney	4,417	4,417	48	7	0	0.012452	null	2023-04-17 07:50:53	https://www.linkedin.com/feed/update/urn:li:activity:7053728822659067905
urn:li:activity:7052659711992545281	Look, no one can tell you how long it’s going to take to get hired. One thing I’ve learned from working with over a dozen developers last year and having literally hundreds of conversations with many of you here is that there is no single path towards that first job. 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.	UNKNOWN	Brian	Jenney	2,929	2,929	27	6	0	0.011267	null	2023-04-14 09:14:11	https://www.linkedin.com/feed/update/urn:li:activity:7052659711992545281
urn:li:activity:7052308429553487872	How most successful bootcamp grads operate: - Makes coding and learning a routine - Applies consistently and broadly - Has 1 or 2 complex side projects - Re-calibrates their approach when things aren't working - Has faith that opportunity will present itself Why most bootcamp grads fail: - Relies on motivation instead of routine - Applies to only junior roles - Tutorial - Tutorial - Tutorial - Doesn’t get hired in 3 months - 𝘎𝘪𝘷𝘦𝘴 𝘶𝘱	UNKNOWN	Brian	Jenney	8,467	8,467	67	8	3	0.009212	null	2023-04-13 09:06:02	https://www.linkedin.com/feed/update/urn:li:activity:7052308429553487872
urn:li:activity:7051938107117481984	Congratulations! You got the job. Now here comes the hard part. Bootcamps do a great job (for the most part) of getting developers hire-able. But what happens after you nail the interview? I mentor and speak with a lot of developers at the beginning of their careers. They struggle in the same areas that I did after getting hired: - Git - Writing good peer reviews - Estimating features - Writing unit tests - Debugging - JIRA - Deployment processes Like too many of us, I learned these skills through trial and error. Over years! Anything I missed on this list that you wished you had learned before starting your first role as a developer?	UNKNOWN	Brian	Jenney	5,877	5,877	78	19	1	0.016675	null	2023-04-12 08:57:28	https://www.linkedin.com/feed/update/urn:li:activity:7051938107117481984
urn:li:activity:7051574178910539776	No I don't think ChatGPT will steal your job. Unless all you do is write code. A few months ago, our team was doing a large migration of a legacy codebase to a new platform. We had particularly complex nav bar to create and I suggested we leverage our AI overlord 🤲 to create it for us. That's when we realized we didn't JUST want a nav bar. We wanted a nav bar that connected to a 3rd party CMS. There were deeply nested values in the response object to safely check. The nav lived in a customized version of the framework we were using and made use of proprietary libraries to track user events. We have a custom component library we needed to use as well to match the mock ups. I'm not GPT hater. I subscribed to the service and pay for Co-Pilot as well. They're amazing tools for quickly writing tests, creating functions with minimal prompts and learning things like Typescript, Docker and Terraform... or generating ideas for my weekly newsletter 😉. Developers are more than button pushers. We write code but we also: - innovate - translate business requirements to code - investigate issues through multiple systems I'd say that's at least 6 months away for ChatGPT 😅.	UNKNOWN	Brian	Jenney	5,999	5,999	77	9	1	0.014502	null	2023-04-11 08:44:17	https://www.linkedin.com/feed/update/urn:li:activity:7051574178910539776
urn:li:activity:7051219290057830401	I met a developer who created a full stack app that worked pretty well. It even looked nice. But when I asked how it worked… Oof. 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗰𝗮𝘀𝗲 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗮𝗯𝘂𝘀𝗲. Too many developers 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. I know I'm not the only one to go through a tutorial, turn it off, open the code editor and realize I have no f*cking clue how to replicate what I just created. 😬 I'm no tutorial hater though. They have their time and place and I'll buy several more this year but I've learned the most when I take the training wheels off, get stuck and build something from scratch. It's the same approach I use with developers I mentor. 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/gQ94kA97 𝘛𝘪𝘳𝘦𝘥 𝘰𝘧 𝘵𝘶𝘵𝘰𝘳𝘪𝘢𝘭𝘴? 𝘊𝘩𝘦𝘤𝘬 𝘵𝘩𝘪𝘴 𝘰𝘶𝘵: https://lnkd.in/gQ_xZrxq	UNKNOWN	Brian	Jenney	28,680	28,680	200	30	14	0.008508	null	2023-04-10 09:03:26	https://www.linkedin.com/feed/update/urn:li:activity:7051219290057830401
urn:li:activity:7050138404327456769	I mentor a lot of boot camp grads. Many are pretty good at using ReactJS. Once I give them this challenge though, they tend to fall apart: 1. Create a simple form using HTML and CSS [𝗡𝗢 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀] 2. Add a button to submit the form once all fields are filled 3. After pressing submit, clear the form and display a message that disappears after [x] seconds Maybe you'll find this challenge easy. Good. Maybe it will expose some of the gaps in your HTML/CSS/JS knowledge. Good. Tomorrow I'll be sharing another Vanilla JS challenge in my weekly newsletter (link in bio 😉). Looking forward to seeing what people come up with.	UNKNOWN	Brian	Jenney	10,671	10,671	171	19	4	0.01818	null	2023-04-07 09:53:14	https://www.linkedin.com/feed/update/urn:li:activity:7050138404327456769
urn:li:activity:7049848243349815296	How do I get better at Javascript and ReactJS? Build stuff. Not specific enough? Try this: Here are the subjects I struggled with the most and how I learned them through practice: - 𝘗𝘳𝘰𝘮𝘪𝘴𝘦𝘴 - implement Promise.all or promisify a timeout - 𝘊𝘭𝘰𝘴𝘶𝘳𝘦 - create a function that returns another function that can only be called 1 time - 𝘛𝘩𝘪𝘴 - implement bind and call from scratch - 𝘙𝘦𝘤𝘶𝘳𝘴𝘪𝘰𝘯 - make a function that searches a deeply nested object for a value - 𝘞𝘦𝘣𝘱𝘢𝘤𝘬 - 𝚗𝚙𝚖 𝚎𝚓𝚎𝚌𝚝 create-react-app and analyze the bundle size - 𝘙𝘦𝘥𝘶𝘹 - understand pub/sub pattern and add Redux to a small app using Ducks architecture (look it up 😎) If you’re feeling brave, record a video going over the concept and share it with others so you can spread and reinforce your own knowledge. I actually compiled these same challenges and way more in something that resembles a course. You can check it out at my site in the link next to my big head 😉	UNKNOWN	Brian	Jenney	17,569	17,569	190	3	7	0.011384	null	2023-04-06 14:15:30	https://www.linkedin.com/feed/update/urn:li:activity:7049848243349815296
urn:li:activity:7049801204603752448	It's easy to write terrible React code. I would know, I've written quite a lot myself and seen even more from working with dozens of mentees at different companies. While there's no silver bullet for writing "good" code, there is certainly some low-hanging fruit which I see most junior developers could benefit from incorporating. I share 3 in this article for you to check out. Oh, and because I like you, I've included an interesting challenge where you will add a custom eslint configuration to a codebase that runs in a GitHub actions pipeline 😉.	ARTICLE	Brian	Jenney	5,604	5,604	78	5	1	0.014989	null	2023-04-06 11:25:33	https://www.linkedin.com/feed/update/urn:li:activity:7049801204603752448
urn:li:activity:7049025890852229123	Here’s some side projects I want to build. Try to beat me to it: - 𝘎𝘪𝘵𝘩𝘶𝘣 𝘢𝘯𝘥 𝘎𝘰𝘰𝘨𝘭𝘦 𝘈𝘯𝘢𝘭𝘺𝘵𝘪𝘤𝘴 𝘥𝘢𝘵𝘢 𝘤𝘰𝘮𝘱𝘢𝘳𝘪𝘴𝘰𝘯 𝘵𝘰𝘰𝘭 - compares releases of code with GA metrics to see if a recent release affected things like sessions. - 𝘊𝘚𝘚 𝘰𝘯 𝘥𝘦𝘮𝘢𝘯𝘥 - load a small script on a website that adds some rules to override current styles. The styles are composed via an admin portal and has version history. Useful for when you want to change the color of that button to green but don’t want to risk a deployment. - 𝘊𝘚𝘝 𝘵𝘰 𝘵𝘪𝘮𝘦𝘴𝘦𝘳𝘪𝘦𝘴 𝘤𝘩𝘢𝘳𝘵 - API which takes in a csv file with at least one date column. Returns the data as a historical timeline chart with comparisons of multiple columns. - 𝘗𝘦𝘳𝘴𝘰𝘯𝘢𝘭 𝘵𝘳𝘢𝘪𝘯𝘦𝘳 - TDEE calculator (look it up) which gives user a suggested calorie budget and meal plan based on some basic information as well as a workout routine and expected weight loss from following the plan. What are you building?	UNKNOWN	Brian	Jenney	4,539	4,539	38	9	1	0.010575	null	2023-04-04 07:49:08	https://www.linkedin.com/feed/update/urn:li:activity:7049025890852229123
urn:li:activity:7048670934496391168	The best way to learn promises, closures, bind, call, apply and 𝚝𝚑𝚒𝚜 is through practical exercise. Imagine trying to get in shape watching fitness videos on YouTube. You might understand what to do, but without action, the knowledge is worthless. So yes, read books, watch videos and buy that course. Then put it into action. Open up codepen or repl or your code editor and write your own example of the concept you learned. - Promisify a timeout. - Use closure to implement a curried function. - Use apply and call to invoke a function with a variable number of arguments. It doesn’t have to be pretty or even practical. It just has to lead you to those “aha” moments. This is where stuff starts to click.	UNKNOWN	Brian	Jenney	4,184	4,184	67	3	2	0.017208	null	2023-04-03 08:32:39	https://www.linkedin.com/feed/update/urn:li:activity:7048670934496391168
urn:li:activity:7047608021601976320	It's 2023 and I meet developers who are still: - not using any version control - deploying straight to production with no checks - avoiding writing tests and relying only on manual QA - not using linters - releasing code once a month Here's the thing: most of us want to change. So why don't we? Change is hard. We prefer the devil we know to the devil we don't. The best engineers I've worked with made change easy. They added a linter and fixed up all the files with syntax errors. Implemented a pattern that others could copy from. Made the first test and added a check in the pipeline. Created a process and docs that anyone could follow. You don't have to super senior staff hyperbole engineer to introduce changes. In fact, as a junior or new hire you may have a unique perspective. If something seems broken, inefficient or outdated come up with a solution. You'll stand out, your team will be a little better and you will gain trust and authority.	UNKNOWN	Brian	Jenney	5,807	5,807	66	15	2	0.014293	null	2023-03-31 10:19:40	https://www.linkedin.com/feed/update/urn:li:activity:7047608021601976320
urn:li:activity:7047224422251851776	Recipe for terrible 1 on 1’s: Manager: “Anything to discuss this week?” You: “Nah, I’m chilling” Manager: “Nice. Talk to ya next time 👍” 1 on 1’s can devolve into weekly status updates, which is why I think a lot of people like to skip them. If used correctly, they can be your chance to: - Share accomplishments - Discuss your career path - Find out what it will take to get to the next level - Get buy-in for process improvements. - Just catch up and chat like humans. At best, by skipping 1 on 1’s frequently, you get time back to work on that bug on line 136 and avoid some awkward small talk. At worst, it will stagnate your career or leave you wondering why you can’t seem to get promoted.	UNKNOWN	Brian	Jenney	7,687	7,687	46	15	0	0.007935	null	2023-03-30 08:38:47	https://www.linkedin.com/feed/update/urn:li:activity:7047224422251851776
urn:li:activity:7046839291066404864	My tech stack for side projects in 2018: - Create-React-App - Material-UI - Heroku - Enzyme - My own authentication system 😅 My tech stack for my next failed startup idea: - NextJS - TailwindCSS - AWS Amplify - Jest - Auth0 What are you building with this year?	UNKNOWN	Brian	Jenney	5,646	5,646	58	25	0	0.014701	null	2023-03-29 07:31:30	https://www.linkedin.com/feed/update/urn:li:activity:7046839291066404864
urn:li:activity:7046118753255768064	What you think front-end development is: - cute lil' button - sprinkle in some JS - ReactJS 😎 - dash of TailwindCSS - 𝘊𝘢𝘯 𝘺𝘰𝘶 𝘮𝘰𝘷𝘦 𝘵𝘩𝘪𝘴 𝘣𝘶𝘵𝘵𝘰𝘯 𝘰𝘷𝘦𝘳 2𝘱𝘹 𝘵𝘰 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵? What it really is: - Oh you know JS? Work on this Node/Express API 😉 - Rollup? Webpack? Snowpack? [x]pack? - New framework to solve old framework - SEO - How can I decrease bundle size? - 𝘊𝘢𝘯 𝘺𝘰𝘶 𝘮𝘰𝘷𝘦 𝘵𝘩𝘪𝘴 𝘣𝘶𝘵𝘵𝘰𝘯 𝘰𝘷𝘦𝘳 2𝘱𝘹 𝘵𝘰 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵?	UNKNOWN	Brian	Jenney	7,630	7,630	127	12	2	0.01848	null	2023-03-27 07:03:07	https://www.linkedin.com/feed/update/urn:li:activity:7046118753255768064
urn:li:activity:7045057029282938880	I've seen your resume. Apparently Chat-GPT has as well. I asked our AI overlord to write out a generic bootcamp grad resume and it did not disappoint. In the video below I walk through the generic advice I've shared with many of you over phone conversations. Of course, my advice is subjective and if you ask 10 different people for advice on your resume, you may get 13 different takes 🤔. Carry the 1... Anyways, hopefully this helps you avoid the dreaded NO pile on every hiring manager's desk.	VIDEO	Brian	Jenney	7,340	7,340	54	21	3	0.010627	null	2023-03-24 08:59:34	https://www.linkedin.com/feed/update/urn:li:activity:7045057029282938880
urn:li:activity:7044670002020458496	My top 3 products for preventing skill-rot as a developer: CodeCrafter offers advanced challenges through Github repos like replicating SQL or Docker. It's not your typical DSA material - it's one of the few resources where you are actually building something in your own coding environment. AlgoExpert While the DSA offering is great, in that it breaks up problems by category/concept, my favorite is the front end material. I have yet to see anything close to the problems they've created here. I've run into more than a few of their questions in interviews myself. ByteByteGo My prediction is that more coding interviews, even at the beginner level, will begin to focus on system design as coding tests become less trustworthy. ByteByteGo breaks down complex topics like distributed caching and common (and not so common) sys design questions. I'm not paid by any of these companies (but maybe I should be 🤔), I just think they have great products and you should consider them whether or not you're on the interview grind.	UNKNOWN	Brian	Jenney	9,475	9,475	93	9	2	0.010976	null	2023-03-23 07:42:12	https://www.linkedin.com/feed/update/urn:li:activity:7044670002020458496
urn:li:activity:7044664252296568832	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. I wanted to know what books 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 watched 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 the University of YouTube, you have the ability to learn from other amazing developers and copy what makes sense to you. A few professors who I’ve learned a lot from recently include - The Primeagen - Theo from Pinglabs - Blue Collar Coder Anyone else you’d suggest?	UNKNOWN	Brian	Jenney	5,163	5,163	54	14	0	0.013171	null	2023-03-23 06:56:27	https://www.linkedin.com/feed/update/urn:li:activity:7044664252296568832
urn:li:activity:7044307049358266368	Stop building clones of popular apps and start creating things you might actually find useful. I recently worked with a mentee on a side project that I want to steal. If you didn’t know, I’m into exercise and tracking calories but I also like to eat out sometimes. 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: it’s always a game of calorie math when I go to a chain restaurant with my kids. 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: pick a chain through the app and enter a calorie limit. The user is shown a list of items that fit their “budget” Simple.... kinda. I won’t give away some of the tricky maneuvers we had to pull to get the data for dozens of chain restaurants or potential ways to automate this task by location, but it was very fun to figure out and there’s more work to do. By the time Tasdeed Aziz finishes this project I think he’ll have something both interesting to speak about in an interview as well as a useful tool that others might want to use… like me 😉.	UNKNOWN	Brian	Jenney	6,383	6,383	79	11	2	0.014413	null	2023-03-22 07:42:22	https://www.linkedin.com/feed/update/urn:li:activity:7044307049358266368
urn:li:activity:7043970072788299777	I realized that I may have fooled some of you on here. You read my title, see my follower count and start to assume things. Just to be clear: - I still Google the difference between slice and splice - Get stuck on problems and wait too long to ask for help - Fail interviews - Realize how little I know and compare myself to others I’m kind of glad though. Wouldn’t it be boring to have it all figured out this early in the game?	UNKNOWN	Brian	Jenney	9,955	9,955	220	24	5	0.025013	null	2023-03-21 09:33:06	https://www.linkedin.com/feed/update/urn:li:activity:7043970072788299777
urn:li:activity:7043582777492983808	If I was a junior developer, pressed for time and studying for an upcoming interview, I’d do the following: 1. Go on Glassdoor and look up previous interview questions. 2. Stalk my interviewers on LI to see if we have anything in common I can bring up during the interview… without being too creepy 😉. 3. Research the company so when I’m inevitably asked “Why do you want to work here?” - I don’t choke. 4. Run a Lighthouse audit on their site if its public-facing and note any areas for improvement. 5. Pray.	UNKNOWN	Brian	Jenney	8,578	8,578	118	18	4	0.016321	null	2023-03-20 07:45:16	https://www.linkedin.com/feed/update/urn:li:activity:7043582777492983808
urn:li:activity:7042510798736211968	My biggest coding hack? Well, I used to be an addict. Maybe I still am? You see, over a decade ago, my life looked a lot more like a music video for a local rapper than an episode of Silicon Valley. Nearly 2 years after my son was born, I had an ultimatum: give up my ridiculous lifestyle or lose my family. I quit [a lot of stuff 😅] immediately with zero plan of how I was going to make it work or if I would succeed. I had lots of time to kill. I had no clue what normal people did for fun. I got introduced to HTML and CSS from a co-worker and my mind was blown. So this is how the internet works eh? How the hell did I not know this? Cue my new addiction. I approached coding with the same unhealthy mindset as I did with, uhhh, previous things. It took over my life. It worked well overall in that I made a transition that even my mother did not really believe was possible. But I don’t suggest it. Eat, sleep, code is a recipe for burnout, not success. Once I incorporated exercise, reading and other hobbies into my life, I was happier, less anxiety-ridden and more confident. I still have a ways to go though, honestly. Even now, I tend to go overboard with any new interest, and while that sounds like a superpower it can also be at the expense of those around me and my own health. Every once in a while, I share this embarrassing piece of my past in the hopes that a few readers will feel less alone who may be in a similar position. Just know that there are quite a few of us floating around out there and most just don’t post it online.	UNKNOWN	Brian	Jenney	6,408	6,408	113	13	2	0.019975	null	2023-03-17 08:29:44	https://www.linkedin.com/feed/update/urn:li:activity:7042510798736211968
urn:li:activity:7041796535830880256	Junior dev move 101: Wasting hours solving a problem a co-worker could’ve helped you figure out in minutes. Relying on your team mates to dig you out of holes is not a long-term strategy for becoming an effective developer. Also: You are ultimately judged on the work you complete. When you bump your head against your technical limit, acknowledge it and ask for help. But for Jeebus sake please don’t just say “𝘐 𝘤𝘢𝘯’𝘵 𝘧𝘪𝘨𝘶𝘳𝘦 𝘰𝘶𝘵 [𝘹]” Try this: - I’m having an issue with [this specific problem] - I’ve tried [y] but it’s not working in the way I expect which is [this way] - [Maybe add a screenshot or documentation] - 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.	UNKNOWN	Brian	Jenney	15,901	15,901	171	20	13	0.012829	null	2023-03-15 08:58:38	https://www.linkedin.com/feed/update/urn:li:activity:7041796535830880256
urn:li:activity:7041420462387593217	Are you a JavaScript developer or a ReactJS developer? If you’re a front end or full-stack developer, your job probably depends on you being a solid ReactJS developer. Unfortunately, those same skills don’t necessarily translate to being a proficient JavaScript developer. In fact, I was doing a mock interview a few months ago with a person who tried to use setState while doing a pub-sub implementation. Here’s the thing, we were using Vanilla JS. No frameworks or anything. I give a challenge to most of the mentees in my program and I’m going to share it with you. Nothing ground breaking. Create a form with a button that submits some data to an API and shows a success message on the screen for a couple seconds. Maybe you’ll find this easy. Good. Maybe this will be a reminder to practice your JS skills along with whatever framework you’re currently using. Also good. Check it out in comments below.	UNKNOWN	Brian	Jenney	8,553	8,553	86	14	0	0.011692	null	2023-03-14 08:01:30	https://www.linkedin.com/feed/update/urn:li:activity:7041420462387593217
urn:li:activity:7041059816093466624	As a junior developer, I was really anxious that one day my team would find out I was a hack. Then, one day, I actually did get “found out” 😬 I was working at a small startup with some incredible talent and when our star engineer left to pursue his own startup, he gave me some candid feedback: “𝘐𝘵’𝘴 𝘥𝘪𝘧𝘧𝘪𝘤𝘶𝘭𝘵 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘺𝘰𝘶 𝘴𝘪𝘯𝘤𝘦 𝘺𝘰𝘶 𝘥𝘰𝘯’𝘵 𝘩𝘢𝘷𝘦 𝘢 𝘴𝘵𝘳𝘰𝘯𝘨 𝘨𝘳𝘢𝘴𝘱 𝘰𝘧 𝘴𝘰𝘮𝘦 𝘧𝘶𝘯𝘥𝘢𝘮𝘦𝘯𝘵𝘢𝘭 𝘑𝘢𝘷𝘢𝘴𝘤𝘳𝘪𝘱𝘵 𝘤𝘰𝘯𝘤𝘦𝘱𝘵𝘴 𝘭𝘪𝘬𝘦 𝘤𝘭𝘢𝘴𝘴𝘦𝘴 𝘰𝘳 𝘤𝘭𝘰𝘴𝘶𝘳𝘦. 𝘐 𝘵𝘩𝘪𝘯𝘬 𝘺𝘰𝘶 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘨𝘰 𝘣𝘢𝘤𝘬 𝘵𝘰 𝘵𝘩𝘦 𝘣𝘢𝘴𝘪𝘤𝘴 𝘢𝘯𝘥 𝘭𝘦𝘢𝘳𝘯 𝘵𝘩𝘦𝘴𝘦 𝘵𝘩𝘪𝘯𝘨𝘴.” I was embarrassed. He was also correct. I wrote down his suggestions and made a plan to get more proficient with es6/7 and some of the concepts which had always confused me like promises, prototypal inheritance and decorators. It wasn’t even that difficult. I wondered why I hadn’t done this earlier. In fact it’s 𝘁𝗵𝗲 𝗺𝗲𝘁𝗵𝗼𝗱 𝗜 𝘀𝘁𝗶𝗹𝗹 𝘂𝘀𝗲 𝗮𝗻𝗱 𝘀𝗵𝗮𝗿𝗲 𝘄𝗶𝘁𝗵 𝗺𝘆 𝗺𝗲𝗻𝘁𝗲𝗲𝘀: 1. Open code editor 2. Create a practical example leveraging the concept I’m learning 3. Record a video explaining the concept and my code, write it down or both For promises, I might create a promise using the promise constructor and invoke it using the async/await pattern and then refactor it to use promise chains. If I think others might benefit from an epiphany I’ve had, then I’ll write an article. If not, I’ll make a video for myself that I may never even watch. The video simply forces me to articulate what I’ve learned in plain English. Hope that’s helpful.	UNKNOWN	Brian	Jenney	8,566	8,566	170	10	0	0.021013	null	2023-03-13 09:02:14	https://www.linkedin.com/feed/update/urn:li:activity:7041059816093466624
urn:li:activity:7040030360147005440	Your next technical interview might not be so technical at all. What I’ve learned from working with over 20 front end developers in the last 12 months on the interview grind, is that in addition to having canned answers for explaining closure, promises, and the difference between bind, call and apply, you want to have answers for questions like: - tell me about a challenging project you’ve worked on? - how do you resolve conflicts with team mates? - here’s a website we made, how can we improve it (how do you measure the performance of a webpage basically? psst... use Lighthouse) - how do you handle tight deadlines? - what’s your debugging process? - why do you want to work here? So while you're optimizing those tree traversals and palindrome toy problems, don't skip on the questions above. Any I missed?	UNKNOWN	Brian	Jenney	7,979	7,979	106	20	1	0.015917	null	2023-03-10 10:55:41	https://www.linkedin.com/feed/update/urn:li:activity:7040030360147005440
urn:li:activity:7039209851180261376	Most people think creating 100 small apps will teach them a lot about web development, but actually, creating 1 complex app will teach you more than those 100 trivial ones combined. My general rule of thumb for creating a “complex” app? Build it with the intention to sell. Solve a problem for yourself, your community or someone else. ❌ MVP How about MUP? Minimally Usable Product. Build the most basic version of this app and deploy it and maybe add a payment system like Stripe. Either you’ll walk away with a small business or an incredible learning experience you can speak about during an interview.	UNKNOWN	Brian	Jenney	12,461	12,461	204	26	8	0.0191	null	2023-03-08 05:26:17	https://www.linkedin.com/feed/update/urn:li:activity:7039209851180261376
urn:li:activity:7038851351824535552	A mentee asked me a very difficult question when we first started meeting. “Should I leave my job?” He liked his team and manager. The problem was he didn’t feel like he was growing as a developer. If he stayed, he likely would’ve been the best damn developer on this small team and had a pretty chill work day. Small UI fix here, squash a little bug there. Easy breezy. But what happens when you want to leave? Or have to? - I asked. The danger of staying complacent at a company or team where your skills are not growing is that technology moves fast and you will be very much at the mercy of the market when, not if, you find yourself looking for a new role. Stability is a myth. The decision was not easy but he began searching for new roles and not only nailed the interview but became a lead developer at a large organization. Imagine if he had just “played it safe.”	UNKNOWN	Brian	Jenney	6,690	6,690	86	12	1	0.014798	null	2023-03-07 04:47:13	https://www.linkedin.com/feed/update/urn:li:activity:7038851351824535552
urn:li:activity:7037454853765296128	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: - Resume quality is subjective (ask 5 people to look at your resume and get 5 different opinions) - Some companies hire internal candidates but open roles to the public - Engineering interviews can be biased 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.	UNKNOWN	Brian	Jenney	5,199	5,199	65	6	2	0.014041	null	2023-03-03 08:40:01	https://www.linkedin.com/feed/update/urn:li:activity:7037454853765296128
urn:li:activity:7037084970179321858	If I was a junior developer looking to increase my marketability, then before I went for that AWS cert, learned Python or Go, I’d expand my JS knowledge to include TypeScript. No matter how you feel about TypeScript, it’s impossible to ignore. The demand for developers who know TS is exploding and though I’ve tried my best to avoid using it on my front end apps, I’m currently using it for all my backend apps and adding a lot more material to my code challenges which incorporate TS. It’s by no means a silver bullet for those on the job hunt, but it’s probably the most practical tool to add to your belt as a front end developer. (By the way - I’m not a Typescript hater I’m just a serially late adopter… I used ReactJS for 2 years before I enjoyed it 🤷‍♂️)	UNKNOWN	Brian	Jenney	8,518	8,518	113	26	1	0.016436	null	2023-03-02 08:26:34	https://www.linkedin.com/feed/update/urn:li:activity:7037084970179321858
urn:li:activity:7036370906390167552	Before you take my advice or the suggestions of any influencer out there, ask yourself 3 things about this person: 1. Do I want to be anything like them career-wise? 2. Do they seem happy? 3. Does their work history support their claims? If the answer to all 3 is no, then maybe don’t take their advice.	UNKNOWN	Brian	Jenney	5,226	5,226	59	9	0	0.013012	null	2023-02-28 08:26:50	https://www.linkedin.com/feed/update/urn:li:activity:7036370906390167552
urn:li:activity:7036005613876711424	A young man made a Tik Tok about me recently. He did not like the cut of my jib. You see, I said something that ruffled his feathers quite a bit. It was this: “𝘠𝘰𝘶 𝘴𝘩𝘰𝘶𝘭𝘥 𝘭𝘦𝘢𝘳𝘯 𝘏𝘛𝘔𝘓 𝘢𝘯𝘥 𝘊𝘚𝘚 𝘣𝘦𝘧𝘰𝘳𝘦 𝘑𝘢𝘷𝘢𝘚𝘤𝘳𝘪𝘱𝘵” Not sure why or how this would controversial but yet, here we are. Last year I interviewed a dozen bootcamp grads and participated in about 50 other mock interviews through my own program and as a volunteer. I asked most of these candidates what I considered a softball question: ”Explain the difference between an id and class in CSS?” Around half of the grads could not. As a front end developer you may be using ReactJS, Angular or Vue (I’m sorry for you - be strong) but you better know how to wield some CSS and use HTML elements in a reasonable (and accessible) manner. Maybe this is my cue to get my old ass off Tik-Tok.	UNKNOWN	Brian	Jenney	9,699	9,699	113	43	1	0.016187	null	2023-02-27 09:27:26	https://www.linkedin.com/feed/update/urn:li:activity:7036005613876711424
urn:li:activity:7034932418000158720	I became an engineering manager last year and I've seen all your resumes. I have 3 piles in which I divide resumes for candidates. No pile. Maybe pile. Yes pile. Here's what's in each pile for junior developers. 🛑 𝘕𝘰 𝘱𝘪𝘭𝘦: Clearly, this person won't work. They have zero overlap in the skills we're looking for or a ton of errors on their resume. It's unclear from their resume what they are looking for. They have either no projects or work experience which is relevant. Maybe they clicked the easy-apply button and were playing spin the wheel. 🤷🏻‍♀️ 🤔 𝘔𝘢𝘺𝘣𝘦 𝘱𝘪𝘭𝘦: Where most generic resumes end up. They usually have an objective section that starts with "passionate developer..." Some relevant projects but little work experience. The projects are 1 of a few: Clone of [x] Chat app [thing] generator Not a "NO" but hard to say yes since they look like a lot of other candidates. 💪 𝘠𝘦𝘴 𝘱𝘪𝘭𝘦: Skills match our needs. Projects are interesting (or just different from the maybe pile) and they have some non-trivial accomplishments. I feel like I can imagine this person on this team making an impact. "Ooh, they did [something cool] on that team/project. I wonder if they can do that here for us?" Ask 10 different people what should be on your resume and you'll probably get 10 different answers. That being said. I've helped hire developers at every company where I've worked and looked at at least 200 resumes just this year alone from people who seem to have a lot of "luck" and those who never get to the interview. I'll be going over the patterns I've seen specifically for junior developers looking to avoid the Maybe and No piles this weekend here: https://lnkd.in/gVryxdVF	UNKNOWN	Brian	Jenney	11,889	11,889	123	22	14	0.013374	null	2023-02-24 09:29:05	https://www.linkedin.com/feed/update/urn:li:activity:7034932418000158720
urn:li:activity:7034552410454777859	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 - scouring Stack Overflow - wait, no one answered that question - trying chatGPT - throwing everything at the wall - finally figuring it out - wanting to share excitement and realizing your non-coding friends don't care 😑 as opposed to: - typing what another person has typed	UNKNOWN	Brian	Jenney	51,551	51,551	600	40	24	0.01288	null	2023-02-23 08:22:45	https://www.linkedin.com/feed/update/urn:li:activity:7034552410454777859
urn:li:activity:7034211263710683138	Look, no one can tell you how long it’s going to take to get hired. One thing I’ve learned from working with over a dozen developers last year and having literally hundreds of conversations with many of you here is that there is no single path towards that first job. 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.	UNKNOWN	Brian	Jenney	6,491	6,491	75	11	0	0.013249	null	2023-02-22 10:30:44	https://www.linkedin.com/feed/update/urn:li:activity:7034211263710683138
urn:li:activity:7033873383758979073	The stuff your bootcamp didn’t teach you about being a software developer: - on-calls can be brutal - if something breaks, you will be the first to know - even if it’s 2AM on a Saturday - your day may be up to 50% meetings - I know they asked you to traverse a binary tree during the interview but you’re likely to get a lot of requests to change the color of a button - if you didn’t negotiate your salary - you lost money - you won’t be building anything from scratch - sometimes sh*tty code is good enough - PRs can be emotional… try to distance yourself from the code - JIRA - Git strategy	UNKNOWN	Brian	Jenney	13,017	13,017	212	20	9	0.018514	null	2023-02-21 11:41:42	https://www.linkedin.com/feed/update/urn:li:activity:7033873383758979073
urn:li:activity:7033467712865533953	Recently, mentees in my program got a chance to meet Ben Denzer and learn about his journey from crane operator to engineering manager as a self-taught developer and his side project (you may have used this 😉) that is now a full blown business! Some takeaways from his chat with us: • learn TypeScript to stand out in a sea of junior devs • make sure your projects on your resume are mobile responsive • create side projects... duh Check out his chat with us here to learn how he changed his life and career and launched a business by teaching himself to code and some no-nonsense advice which may help you: https://lnkd.in/gxN8PKND	UNKNOWN	Brian	Jenney	3,477	3,477	28	11	1	0.011504	null	2023-02-20 08:58:17	https://www.linkedin.com/feed/update/urn:li:activity:7033467712865533953
urn:li:activity:7033467850681982976	Recently, mentees in my program got a chance to meet Ben Denzer and learn about his journey from crane operator to engineering manager as a self-taught developer and his side project (you may have used this 😉) that is now a full blown business! Some takeaways from his chat with us: • learn TypeScript to stand out in a sea of junior devs • make sure your projects on your resume are mobile responsive • create side projects... duh Check out his chat with us here to learn how he changed his life and career and launched a business by teaching himself to code and some no-nonsense advice which may help you: https://lnkd.in/gxN8PKND	UNKNOWN	Brian	Jenney	72	72	0	0	0	0	null	2023-02-20 08:58:17	https://www.linkedin.com/feed/update/urn:li:activity:7033467850681982976
urn:li:activity:7032401931645968384	I bet your coding bootcamp or course from the University of YouTube skipped this important skill you will need as a JS developer: Finding and squishing bugs. Only half of programming is coding. The other 90% is debugging... 🤔 Or something like that. Anyways, check out this video walking you through some debugging techniques I've stolen from smarter developers over the years.	VIDEO	Brian	Jenney	5,095	5,095	178	20	14	0.041609	null	2023-02-17 09:36:41	https://www.linkedin.com/feed/update/urn:li:activity:7032401931645968384
urn:li:activity:7032061882534416384	If you're a junior developer preparing for interviews - don't fall into the LeetCode rabbit hole. You're more likely to encounter: • JS trivia • String and Array manipulation problems • Frequency counters • Build a React component that fetches data • Tell me about a project you worked on Instead of: • Traverse this tree in O(n) 🧐	UNKNOWN	Brian	Jenney	31,618	31,618	386	26	12	0.01341	null	2023-02-16 11:34:27	https://www.linkedin.com/feed/update/urn:li:activity:7032061882534416384
urn:li:activity:7031998144401862656	The most dangerous stand-up status: “Worked on ticket 420 yesterday. Continuing on it today. No blockers” What that often really means: “𝘐’𝘮 𝘴𝘵𝘶𝘤𝘬 𝘢𝘯𝘥 𝘤𝘢𝘯’𝘵 𝘧𝘪𝘨𝘶𝘳𝘦 𝘵𝘩𝘪𝘴 𝘴𝘩𝘵 𝘰𝘶𝘵 𝘣𝘶𝘵 𝘐 𝘥𝘰𝘯’𝘵 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘢𝘥𝘮𝘪𝘵 𝘵𝘩𝘢𝘵” I was the king of these updates. Sometimes it worked out in my favor and I just figured sht out. The real issue is that these generic updates are misleading at best and can deteriorate trust at worst. When a sprint ends or a project is finally due and you have to ask for an extension, the team will be blind-sided. It took me a couple years and lot more courage to admit when I reached my technical depth. It’s gotten easier through repetition but I still find myself sometimes slipping into old habits. Ego, fear, hard-headedness… take your pick. I’d argue that if you are NOT bumping up against the limits of your technical capacity as a junior dev, it’s likely that you aren’t growing.	UNKNOWN	Brian	Jenney	18,752	18,752	150	15	2	0.008906	null	2023-02-16 07:03:44	https://www.linkedin.com/feed/update/urn:li:activity:7031998144401862656
urn:li:activity:7031631887282438145	People management is NOT the natural career progression for most software developers. Project management, however, is. The problem is that most of us just stumble across project management at some point or are thrust into it through a promotion. As a junior developer, you are concerned with your code and making sure it works. That’s a task in itself at this stage. Moving into mid and senior roles, there becomes a not-so-silent expectation that you are the shepherd of the codebase. You should have an overview of the general health of the codebase and the team. So how do you get practice at these earlier stages to prepare you for the big leagues? I recommend looking for opportunities to lead epics. An epic is a high-level story or concept that represents a large body of work and usually includes multiple user stories. Taking the lead doesn’t mean necessarily writing any code at all but rather organizing the stories in a logical order and keeping track of the pieces and overall delivery. This provides a good opportunity to dip your toe into project management and get a deeper understanding of the codebase.	UNKNOWN	Brian	Jenney	4,993	4,993	38	9	1	0.009613	null	2023-02-15 07:24:35	https://www.linkedin.com/feed/update/urn:li:activity:7031631887282438145
urn:li:activity:7030977564357644288	Top 5 ways to save your resume from landing in the NO pile, for all your junior devs: 1. Stop calling yourself "junior" or "aspiring". 𝗬𝗼𝘂 𝗮𝗿𝗲 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 or software engineer or whatever. 2. 𝗨𝘀𝗲 𝘀𝘁𝗿𝗼𝗻𝗴 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲. “Led development on [x] feature which [improved some metric]” or “architected” sounds better than “worked with a team on [generic thing]” 3. 𝗟𝗲𝗮𝗱 𝘄𝗶𝘁𝗵 𝘆𝗼𝘂𝗿 𝗿𝗲𝗹𝗲𝘃𝗮𝗻𝘁 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲. It can be confusing to look at resume for a dev role and see nothing coding related. Put your projects/volunteer work/side projects at the top. 4. That unique formatting you're using might get destroyed once your resume passes through some intake system. 𝗧𝗿𝘆 𝘂𝘀𝗶𝗻𝗴 𝗮 𝗽𝗹𝗮𝗶𝗻 𝗿𝗲𝘀𝘂𝗺𝗲. 5. Visit this freakin' site: https://lnkd.in/g4HQ6Stb What else would you suggest?	UNKNOWN	Brian	Jenney	7,516	7,516	65	6	2	0.009713	null	2023-02-13 11:19:55	https://www.linkedin.com/feed/update/urn:li:activity:7030977564357644288
urn:li:activity:7029848073149267968	2 minutes into the interview and I already knew I failed. I politely told my interviewer, "I don't think it's worth moving forward and I don't want to waste your time" He was a bit shocked and even encouraged me to try. So I did. The problem was a particularly complicated one that would require 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	3,053	3,053	148	18	5	0.05601	null	2023-02-10 09:02:52	https://www.linkedin.com/feed/update/urn:li:activity:7029848073149267968
urn:li:activity:7029493275149414400	Last week I wrote about a couple mentees of mine who had success in pivoting to QA roles directly from full stack bootcamps. One uses Selenium and one will be using Cypress.io to create e2e (end-to-end) tests. I like you... I think 🤔 Either way, I'm gonna share with you a challenge I've created for mentees in my community to introduce you to Cypress with a small RemixJS app that could use some additional tests which will be up to you to write. Check it out here: https://lnkd.in/dyHT3mHT	UNKNOWN	Brian	Jenney	2,795	2,795	22	5	0	0.00966	null	2023-02-09 08:58:08	https://www.linkedin.com/feed/update/urn:li:activity:7029493275149414400
urn:li:activity:7029098487933796352	Before you take my advice, let me be clear: I will only ever give you suggestions based on my own experience or what I’ve seen work for others. Will it work for you? Perhaps. As a junior or soon-to-be-developer, some generic advice can be helpful. Your problems are fairly generic at this stage and what you mostly need is direction. As a team lead or senior, more context is needed to deliver useful advice and you have to be pickier with what advice you accept. The reasons I post here are two-fold: 1. I have received considerable help from strangers online and I feel it’s only right to give back 2. I provide paid mentorship and courses to help developers be better at what they do and this is how people find me and make sure I'm not crazy I’ll continue to do free convos with developers and give you spicy, and not-so-spicy advice. I encourage you to take what makes sense and ignore what doesn’t.	UNKNOWN	Brian	Jenney	3,700	3,700	48	9	1	0.015676	null	2023-02-08 07:13:35	https://www.linkedin.com/feed/update/urn:li:activity:7029098487933796352
urn:li:activity:7028738272864468993	Your portfolio project probably looks a lot like other portfolio projects out there. TODO app Weather app Clone of [x] Blog Chat app Here’s the thing, there’s nothing at all wrong with these projects. They can certainly teach you a lot. BUT - when digging through a stack of resumes for an open junior developer position, it is hard to stand out. If your goal is to stand out AND learn something try this: - Start with an API or a real-world problem you are familiar with - Sketch out the features using a tool like Excalidraw - Build that sh*t - Deploy it on AWS like an adult Now you have an interesting technical story and maybe even your next startup idea. If you’re looking for some interesting API’s Anirudh Kadian has compiled a list of interesting AI flavored ones (this guy’s a true hero) 🙇🏽‍♂️ 👇 https://lnkd.in/gjCg5RKZ	UNKNOWN	Brian	Jenney	11,482	11,482	113	33	5	0.013151	null	2023-02-07 07:05:32	https://www.linkedin.com/feed/update/urn:li:activity:7028738272864468993

Subsets and Splits

No community queries yet

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