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:7028372991092682752	I’ve gone from struggling junior developer to struggling engineering manager over the last 8 years and that little voice in my head has been present that entire time. “𝘛𝘩𝘦𝘺’𝘳𝘦 𝘨𝘰𝘯𝘯𝘢 𝘧𝘪𝘯𝘥 𝘺𝘰𝘶 𝘰𝘶𝘵” It’s lot quieter than when I started but it never left. I’ve come to accept it and see its patterns. - Promotion? Voice gets louder. - Accomplishment? Voice gets quieter. - New job? Deafeningly loud 😬 - Solve an LC hard in 30 minutes? 🤐 😎 The feeling that you’re just not quite good enough may in fact be true. I try to be objective. I write out my weaknesses. Write out my strengths. Where is the gap between who I want to be and who I am currently and what will it take for me to get there?	UNKNOWN	Brian	Jenney	4,527	4,527	59	12	1	0.015905	null	2023-02-06 07:28:52	https://www.linkedin.com/feed/update/urn:li:activity:7028372991092682752
urn:li:activity:7027316085376843777	Yesterday a mentee I've been working with got a verbal offer for a QA position. Coincidentally, yesterday, I wrote a post about another mentee who also successfully transitioned to a QA role. Maybe I'm just psychic... 🤔 Anyways, he hasn't even graduated his bootcamp and here he is with an offer. 🤯 I'm not at all advocating that everyone switch to QA or that it's the right choice. But it is 𝘈 choice and one that has worked for others. This weekend I'll be breaking down these success stories and sharing a challenge to help you learn Cypress.io, an end-to-end (e2e) testing framework using your most loved (or hated) language - Javascript. Link in comments 😉.	IMAGE	Brian	Jenney	4,817	4,817	54	3	0	0.011833	null	2023-02-03 09:21:23	https://www.linkedin.com/feed/update/urn:li:activity:7027316085376843777
urn:li:activity:7026925884964032512	The job market for developers doesn’t suck. It’s just less piping hot. So yes, getting that first role is difficult, arduous and more luck is involved than many would like to admit. A mentee of mine had that same issue last year and I suggested we pivot into searching for QA roles. Here’s what he did: - 𝘚𝘵𝘶𝘥𝘺 𝘊𝘺𝘱𝘳𝘦𝘴𝘴 𝘢𝘯𝘥 𝘚𝘦𝘭𝘦𝘯𝘪𝘶𝘮 - 𝘗𝘳𝘢𝘤𝘵𝘪𝘤𝘦 𝘸𝘳𝘪𝘵𝘪𝘯𝘨 𝘢𝘶𝘵𝘰𝘮𝘢𝘵𝘦𝘥 𝘵𝘦𝘴𝘵𝘴 𝘢𝘵 https://lnkd.in/gaq774ga - 𝘜𝘱𝘥𝘢𝘵𝘦 𝘩𝘪𝘴 𝘳𝘦𝘴𝘶𝘮𝘦 𝘵𝘰 𝘳𝘦𝘧𝘭𝘦𝘤𝘵 𝘳𝘦𝘭𝘦𝘷𝘢𝘯𝘵 𝘘𝘈 𝘱𝘳𝘰𝘫𝘦𝘤𝘵𝘴 𝘧𝘳𝘰𝘮 𝘵𝘩𝘦 𝘱𝘳𝘦𝘷𝘪𝘰𝘶𝘴 𝘴𝘵𝘦𝘱 - 𝘈𝘱𝘱𝘭𝘺 𝘢 𝘭𝘰𝘵 He landed a role at a tech company shortly after as a QA automation engineer where he will write code for end to end test suites. There’s more to the tech-o-sphere than ReactJS. There’s DevOps, QA, product, data, sales... Don’t limit yourself to what your bootcamp taught you.	UNKNOWN	Brian	Jenney	21,896	21,896	208	14	5	0.010367	null	2023-02-02 07:01:14	https://www.linkedin.com/feed/update/urn:li:activity:7026925884964032512
urn:li:activity:7026559963669958656	Nearly a decade ago I started my first day as a developer. I knew HTML, CSS, Jquery and a little AngularJS... very little. The night before the first day, I was barely able to sleep. Would I be found out as a fake developer and fired immediately? Would they give me a task I couldn’t figure out? How long before they realized they made an error in their hiring process? Well, I never got “found out” and took on more than a few tasks I couldn’t figure out. I still have these fears each time I start a new position. Here are some ways I get over my anxiety: - make a 30/60/90 day plan which usually includes delivering a small feature - immediately explore the codebase and identify areas I just don’t understand - ask a bunch of questions while I’m still new enough that no one will judge me 😅 - take notes - realize I’m here to do more observing than anything during my first month So if you just got hired, congrats! I also know it can be just as stressful as the interview process. What’s some tips you have for people just starting a new dev position?	UNKNOWN	Brian	Jenney	8,810	8,810	131	16	0	0.016686	null	2023-02-01 07:49:54	https://www.linkedin.com/feed/update/urn:li:activity:7026559963669958656
urn:li:activity:7026199049628254208	Ok, we’ve seen enough good code on this damn site. It's hard to know what good code is if you can't identify bad code. Below is some janky ass code for you to refactor. Here's the thing though - it does in fact work with the expected arguments. Could it be improved? Hell yeah it can. I’m curious, what’s the most unforgivable mistake I’ve made here and how would you fix it?	IMAGE	Brian	Jenney	33,206	33,206	74	66	6	0.004397	null	2023-01-31 07:15:04	https://www.linkedin.com/feed/update/urn:li:activity:7026199049628254208
urn:li:activity:7025835385209446400	250 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, coding is fun but 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 (you better have signed up, seriously wtf). 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	5,796	5,796	57	12	0	0.011905	null	2023-01-30 07:12:58	https://www.linkedin.com/feed/update/urn:li:activity:7025835385209446400
urn:li:activity:7024409899027632128	Stuck on what to build for your next side project? Here’s the process I’ve been using for years to learn everything from Typescript to AWS Lambdas: 1. 𝗣𝗶𝗰𝗸 𝗮𝗻 𝗔𝗣𝗜 - this is important, you need some external data or functionality in order to build something interesting or you’ll be mostly stuck with TODO or clone apps a. 𝘜𝘴𝘦 𝘗𝘰𝘴𝘵𝘮𝘢𝘯 or some other http client to test the API and make sure it’s worthwhile b. If the API is not free, consider how you might 𝘭𝘦𝘷𝘦𝘳𝘢𝘨𝘦 𝘤𝘢𝘤𝘩𝘪𝘯𝘨 𝘵𝘰 𝘭𝘪𝘮𝘪𝘵 𝘳𝘦𝘲𝘶𝘦𝘴𝘵𝘴 2. 𝗦𝗰𝗮𝗳𝗳𝗼𝗹𝗱 𝗼𝘂𝘁 𝘁𝗵𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗮𝗽𝗽 - what is the first page a user lands on? What happens when they click a button? Where is data stored? 3. 𝗕𝗲𝗴𝗶𝗻 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 using the new technology/language you want to learn You will get stuck. This is kinda what you want. Google, ChatGPT and Stack Overflow through roadblocks. This will be a messy affair but you will learn a ton.	UNKNOWN	Brian	Jenney	5,884	5,884	69	12	2	0.014106	null	2023-01-26 08:22:42	https://www.linkedin.com/feed/update/urn:li:activity:7024409899027632128
urn:li:activity:7024187553276715008	So how does it feel to be the worst developer on a team? Not so great. It's also an experience that was pivotal in my career as a software developer.	ARTICLE	Brian	Jenney	2,767	2,767	49	5	1	0.019877	null	2023-01-25 18:20:25	https://www.linkedin.com/feed/update/urn:li:activity:7024187553276715008
urn:li:activity:7024025016161751040	𝘛𝘋𝘋 𝘰𝘳 𝘥𝘪𝘦! Or you know, TaDD (test after development is done). Or, perhaps manual QA is the correct choice. 𝘊𝘰𝘥𝘦 𝘴𝘩𝘰𝘶𝘭𝘥 𝘢𝘭𝘸𝘢𝘺𝘴 𝘧𝘰𝘭𝘭𝘰𝘸 𝘋𝘙𝘠 𝘱𝘳𝘪𝘯𝘤𝘪𝘱𝘭𝘦𝘴! Except, maybe the abstraction is more clever than useful in this case. 𝘛𝘺𝘱𝘦𝘚𝘤𝘳𝘪𝘱𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘯𝘭𝘺 𝘤𝘩𝘰𝘪𝘤𝘦 𝘧𝘰𝘳 𝘴𝘦𝘳𝘪𝘰𝘶𝘴 𝘑𝘚 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴! But maybe it’s overkill for this simple UI app. 𝘈𝘨𝘪𝘭𝘦 𝘪𝘴 𝘩𝘰𝘸 𝘳𝘦𝘢𝘭 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘵𝘦𝘢𝘮𝘴 𝘸𝘰𝘳𝘬. We have an aggressive deadline we cannot miss. Perhaps waterfall will work here. Be careful falling into dogmatic, knee-jerk responses when it comes to writing software. One thing I’ve learned is that there are often exceptions to the rules we accept as coding law. What's a code commandment you've broken?	UNKNOWN	Brian	Jenney	3,080	3,080	24	4	1	0.009416	null	2023-01-25 06:57:31	https://www.linkedin.com/feed/update/urn:li:activity:7024025016161751040
urn:li:activity:7023665386994761728	The developer who failed 100 interviews. At first I didn’t believe him. I mean, 100? There’s no way. Then we did a mock interview. Oof. Here’s the thing - he was a very personable dude. Polite, well-spoken and confident. During the interview though, he didn’t come off as such. His answers were short to the point I could see how they could be perceived as rude. He cut me off a few times as I asked a question or tried to explain a concept. When asked about a project he had worked on, he gave a cursory overview of a trivial feature and didn’t offer much detail. He used some internal names for the app which didn’t make sense to me. After the interview, I brought some of these issues to his attention. We dug into his former role and the work he did. It was interesting. He had worked on challenging technical problems across the stack. So why in the hell wasn’t he mentioning this in the interview? He was genuinely surprised with my perception and feedback. 100 interviews deep and here he was getting this hot-take for the first time. Companies will rarely give feedback to candidates and I know that’s “unfair.” It’s also reality. Legal reasons. Awkwardness. Time constraints. Pick one. Many of us are overly focus on the technical aspect of interviews. I mean, we’re software developers. Don’t underestimate the human aspect.	UNKNOWN	Brian	Jenney	10,097	10,097	125	22	2	0.014757	null	2023-01-24 07:35:25	https://www.linkedin.com/feed/update/urn:li:activity:7023665386994761728
urn:li:activity:7023302875975995392	How do I get better at Javascript? Build stuff. Not specific enough? Try this: Here are the subjects I struggled the most with and how I learned them through practice: - Promises - implement Promise.all - Closure - create a function that returns another function that can only be called 1 time - This - implement bind and call from scratch - Recursion - make a function that searches a deeply nested object for a value 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.	UNKNOWN	Brian	Jenney	11,541	11,541	147	14	0	0.01395	null	2023-01-23 07:25:18	https://www.linkedin.com/feed/update/urn:li:activity:7023302875975995392
urn:li:activity:7022237846707007488	Am I... average? In reality, many amazing teams are made up of mostly "average" developers. Not teams of ninjas/rockstars/wizards/elves 🧝‍♂️ As an average developer there’s still a lot of room to make 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. 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	9,429	9,429	78	22	0	0.010606	null	2023-01-20 08:45:34	https://www.linkedin.com/feed/update/urn:li:activity:7022237846707007488
urn:li:activity:7021848156548071424	I had a mentee who struggled to get hired after 6 months of mass applying. I suggested he consider QA roles. We studied Cypress.io and Selenium . He was hired within a couple of months at a well-known company as a QA Automation Engineer. Full-Stack and Frontend are not the only entryways into a career in software development.	UNKNOWN	Brian	Jenney	20,709	20,709	211	36	6	0.012217	null	2023-01-19 06:48:41	https://www.linkedin.com/feed/update/urn:li:activity:7021848156548071424
urn:li:activity:7021156664162586624	I’ve successfully networked my way into 0 of my last 4 jobs as a developer. I built exactly 0 projects in public. I’ve also worked with 20 developers this year. They’ve overwhelmingly had the same experience. The boring truth: - They applied a lot. - They worked with recruiters to get interviews. They kept their skills sharp with side projects and mentorship. I know, I know. Everyone must build in public and network their way to their first role. I don’t doubt this works for a lot of people. I’ve seen it work. It’s just not the only way.	UNKNOWN	Brian	Jenney	12,509	12,509	157	28	1	0.014869	null	2023-01-17 09:51:16	https://www.linkedin.com/feed/update/urn:li:activity:7021156664162586624
urn:li:activity:7020786124197412865	Concepts and technologies JS developers consistently struggle with: Redux Webpack Closure Promises Recursion I have material on each of these subjects in my course library but there’s 1 challenge that students have found more difficult than solving the actual technical problems: 𝘌𝘹𝘱𝘭𝘢𝘪𝘯𝘪𝘯𝘨 𝘵𝘩𝘦𝘴𝘦 𝘤𝘰𝘯𝘤𝘦𝘱𝘵𝘴 𝘰𝘯 𝘷𝘪𝘥𝘦𝘰. It’s tough. It’s awkward. It’s also the best way to ensure you actually understand the concept. Making this material was pretty eye opening for me honestly. I had to refresh and re-learn a lot of things I thought I knew. You certainly don’t need to buy my course to do this (you should though 😉) and I encourage you to try this challenge: Use Loom (or whatever) to record yourself explaining one of the concepts above to a technical audience. Maybe post it on LI. Maybe cringe at hearing your own voice. I don’t know - but I guarantee you’re going to get some much needed practice with technical communication. If you are a brave soul, tag me when you do post 😉.	UNKNOWN	Brian	Jenney	4,664	4,664	44	12	0	0.012007	null	2023-01-16 08:21:15	https://www.linkedin.com/feed/update/urn:li:activity:7020786124197412865
urn:li:activity:7019766958812270592	My tech stack for preventing skill rot as a developer: - CodeCrafters - AlgoExpert - LeetCode Every year I set aside some money for keeping my coding skills up to par and these 3 are worth it IMO (no affiliation btw 😉) . While AlgoExpert and Leetcode are very helpful for interview practice. CodeCrafters takes an interesting approach to learning with challenges that mimic real world problems in software development.	UNKNOWN	Brian	Jenney	13,808	13,808	145	17	5	0.012094	null	2023-01-13 13:01:39	https://www.linkedin.com/feed/update/urn:li:activity:7019766958812270592
urn:li:activity:7019703130938322944	The blueprint to take you from junior developer to senior developer: 𝘑𝘶𝘯𝘪𝘰𝘳: - Double down on fundamentals - Make things work and then make them efficient - Learn the tools of your trade (code editor, git, Jira) - Become familiar with the frameworks/libraries which dominate your field but focus on the one you’re currently working with - Learn your immediate codebase (the one you’re working on daily) - Don’t be afraid to ask for help 𝘔𝘪𝘥-𝘓𝘦𝘷𝘦𝘭: - Make things work and make the solutions reusable - Work on mastering one area of your stack - Learn the art of communication and practice speaking at work - Learn to give constructive feedback and receive it - Understand the code deployment process - Be familiar with other areas of the codebase and systems you interact with - Don’t be afraid to ask for help 𝘚𝘦𝘯𝘪𝘰𝘳: - Create patterns your team can leverage - Mentor others - Make things work, make them scalable and measure their performance - Find places to create efficiencies from code development through deployment - Help create an environment where others can learn and give feedback - Don’t be afraid to ask for help	UNKNOWN	Brian	Jenney	13,725	13,725	149	6	10	0.012022	null	2023-01-13 08:54:10	https://www.linkedin.com/feed/update/urn:li:activity:7019703130938322944
urn:li:activity:7018950128208142336	Just hired 2 junior developers and onboarded them to our team. They’re amazing and have exceeded our expectations. Here’s what makes them stand out: - 𝙩𝙝𝙚𝙮 𝙖𝙧𝙚 𝙥𝙧𝙤𝙖𝙘𝙩𝙞𝙫𝙚 - they seek out tickets to complete and pair with others without being asked - 𝙩𝙝𝙚𝙮 𝙬𝙧𝙞𝙩𝙚 𝙩𝙝𝙤𝙧𝙤𝙪𝙜𝙝 𝙋𝙍𝙨 - I immediately noted the screenshots and before and after pics for a recent PR that taught me about a feature I was not familiar with. Less than a month on the job and they were already teaching me something - 𝙩𝙝𝙚𝙮 𝙜𝙤𝙩 𝙜𝙪𝙩𝙨 - our team is at the tail end of a project with some mission critical issues to fix. They volunteered to take on these tickets which was a bit of a surprise and also relief for the team When I think about previous hires who stood out, they basically did these same things. It only took me about 3 years to figure that out 😅.	UNKNOWN	Brian	Jenney	37,284	37,284	548	31	4	0.015637	null	2023-01-11 07:03:18	https://www.linkedin.com/feed/update/urn:li:activity:7018950128208142336
urn:li:activity:7018585780314918912	I spent the first couple years as a developer basically saying nothing. I just stayed in the background nodding my head. 5 points for that ticket to move a button? Sounds good. Massive, complex feature due next week eh? Any questions? Nope! This strategy didn’t work out well for me. I was forgettable. So I forced myself to start contributing to discussions. I started by asking questions. 1 question per meeting. As I grew in seniority, I realized there was a not-so-silent expectation that I would participate in and lead more discussions and proposals. I had to talk… a lot. Here are some communication hacks I’ve learned from studying others: - 𝘴𝘱𝘦𝘢𝘬 𝘴𝘭𝘰𝘸𝘦𝘳 than you naturally do - your tone should 𝘨𝘰 𝘧𝘳𝘰𝘮 𝘩𝘪𝘨𝘩 𝘵𝘰 𝘭𝘰𝘸 in order to sound more confident (try it out) - 𝘯𝘦𝘷𝘦𝘳 𝘳𝘦𝘢𝘥 𝘸𝘰𝘳𝘥 𝘧𝘰𝘳 𝘸𝘰𝘳𝘥 off a slide during a presentation - 𝘶𝘴𝘦 𝘺𝘰𝘶𝘳 𝘩𝘢𝘯𝘥𝘴 for emphasis and to keep people engaged during a presentation (point to stuff) - 𝘥𝘰𝘯’𝘵 𝘶𝘴𝘦 𝘵𝘦𝘤𝘩𝘯𝘪𝘤𝘢𝘭 𝘫𝘢𝘳𝘨𝘰𝘯 and aim for the simplest way to explain something (people will silently be thanking you and most are too embarrassed to admit they don’t understand something) Lastly, the best hack I’ve discovered to help me with me communication is speaking into a camera using Loom. I challenge my mentees to do this as well. It’s a great habit you can apply immediately at work, especially on distributed, remote teams. Send a video explaining what you’ve done and why instead of 10 chats via slack or even worse, an email chain. Any communication/speaking tips I should add?	UNKNOWN	Brian	Jenney	7,602	7,602	86	27	3	0.015259	null	2023-01-10 06:47:42	https://www.linkedin.com/feed/update/urn:li:activity:7018585780314918912
urn:li:activity:7018227574757625856	When I tell you to be optimistic I don’t mean it as fluff. I don’t mean things will be easy or that they will inevitably get better. I mean to look at the current obstacles in your way and realize they are not insurmountable. It’s easy to be cynical. Yes, it is difficult to get that first job. Yes, it is difficult being a software engineer despite what Tik Tok shows you. Yes, interviews are dumb and unfair. Now what? - skills will always be valuable - so build stuff - not getting ANY interviews? Have someone look at your resume and LI - not passing a single interview? Write down the areas where you are weak and attack them Now, stay optimistic. Realize that with the proper skills and preparation you WILL be ready when (not if) luck presents itself.	UNKNOWN	Brian	Jenney	3,599	3,599	40	14	0	0.015004	null	2023-01-09 07:21:25	https://www.linkedin.com/feed/update/urn:li:activity:7018227574757625856
urn:li:activity:7017173550901936128	These concepts and topics blew my mind as a JS developer and maybe they’ll help you level up too: - generator functions - web workers - web components - currying - decorators Anything you’d add?	UNKNOWN	Brian	Jenney	6,309	6,309	41	6	1	0.007608	null	2023-01-06 09:16:06	https://www.linkedin.com/feed/update/urn:li:activity:7017173550901936128
urn:li:activity:7016785355802628097	Another ticket moves across the board. The button is now 30px more to the right. It’s another shade of green. The design team is happy and so is your manager. You on the other hand, begin to wonder “Am I growing as a developer?” Ultimately, you and not your job will be responsible for your technical growth. You can certainly seek out challenging assignments when they’re available but that’s not always possible. So what do you do then? One of the many benefits of being a developer is that you can create the problems you want to solve. - Interested in Lambdas? Spin one up using AWS - Curious about web sockets? Create a chat-app - Don’t write tests at work? Try Cypress and Jest on a side project - Sadomasochist? Start learning AngularJS You don't need permission to build whatever your heart desires.	UNKNOWN	Brian	Jenney	5,872	5,872	72	19	2	0.015838	null	2023-01-05 07:20:14	https://www.linkedin.com/feed/update/urn:li:activity:7016785355802628097
urn:li:activity:7016055020668272640	3 API projects to teach you stuff and maybe even get you paid 1. 𝗧𝗶𝗺𝗲-𝘀𝗲𝗿𝗶𝗲𝘀 𝗳𝗿𝗼𝗺 𝗮 𝗖𝗦𝗩 - a user sends a csv file with historical data and some information about how to aggregate the data and the endpoint returns formatted JSON data 2. 𝗦𝗰𝗿𝗮𝗽𝗲𝗿 𝘁𝗵𝗮𝘁 𝗴𝗮𝘁𝗵𝗲𝗿𝘀 𝗷𝗼𝗯 𝗽𝗼𝘀𝘁𝗶𝗻𝗴𝘀 with less than [x] applicants 3. Endpoint that runs a 𝗡𝗮𝗶𝘃𝗲-𝗕𝗮𝘆𝗲𝘀 𝗽𝗿𝗲𝗱𝗶𝗰𝘁𝗶𝗼𝗻 𝗺𝗼𝗱𝗲𝗹 based on [x] years worth of NBA stats to predict the outcome of a game between 2 teams Anything you'd add?	UNKNOWN	Brian	Jenney	6,307	6,307	66	16	1	0.01316	null	2023-01-03 07:08:49	https://www.linkedin.com/feed/update/urn:li:activity:7016055020668272640
urn:li:activity:7015696871335616512	I see you over there, eyeing another Udemy course on DSA. I have a few myself 😉. While you’re optimizing your approach to a DFS solution and exploring the many varieties of trees, don’t forget that as a JS developer you’re going to be working a hell of a lot more with arrays and objects than graphs, trees and tries. A solid grasp of - map - filter - reduce - reverse look up maps - transforming data from one shape to another Will take you a lot further on the job than solving toy problems. Ok now back to my Udemy course.	UNKNOWN	Brian	Jenney	5,496	5,496	73	15	0	0.016012	null	2023-01-02 07:57:37	https://www.linkedin.com/feed/update/urn:li:activity:7015696871335616512
urn:li:activity:7014643869938040832	If there's one thing I hope you leave behind in 2022, it's using 122 console logs to debug your NodeJS/Express apps. Maybe exercise more too. Anyways back to your lame debugging methods. Here's what I used to do: - slam API with requests from Postman - get closer to issue (or at least think I was) - add more logs - wait, it's not even hitting that function - more logs - more requests - f*ck got rate-limited from 3rd party API I didn't realize we were using Don't do that. If you're using VS Code check out this video which shows you how to set breakpoints in a Node/Express app using VSCode. Grab the source code for the project you see below which includes tests, file upload capability and some challenges 😎	VIDEO	Brian	Jenney	6,490	6,490	62	15	0	0.011864	null	2022-12-30 09:46:25	https://www.linkedin.com/feed/update/urn:li:activity:7014643869938040832
urn:li:activity:7014268220207497216	You don't HAVE to build in public. A good side project never has to see the light of day. Ideally, a solid side project will: 1. Teach you something 2. Increase your confidence 3. Create a path for self-teaching 4. Wean you off "watch and type" tutorials The most impactful side project I built was a web app to handle real-estate transactions. It taught me ReactJS, NodeJS and AWS and a hell of a lot about real estate. It also failed. We never got it off the ground and had little interest from investors. I spent nearly 3 years working on this “side project”. I don’t regret it one bit. I took those exact same skills to the next company and gained a lot of confidence in technologies I was interested in learning. I got a crash course in real estate. I met some amazing people who are now working on other incredible projects. I know the popular advice is to “build in public” and I’ve seen that strategy work for a lot of developers - so try it out if that’s your thing. 𝘈𝘭𝘴𝘰 - 𝘤𝘰𝘯𝘴𝘪𝘥𝘦𝘳 𝘵𝘩𝘪𝘴: the majority of developers aren’t actually on LinkedIn or actively posting. Anecdotally, I’ve worked for half a dozen companies and barely any of my co-workers ever spent much time here. They were incredibly employable however. They didn’t build anything in public. They did the boring work of applying, getting rejected (yes, even the smartest ones) and studying. #juniordeveloper #buildinginpublic	UNKNOWN	Brian	Jenney	3,840	3,840	46	18	0	0.016667	#juniordeveloper ,#buildinginpublic	2022-12-29 09:20:48	https://www.linkedin.com/feed/update/urn:li:activity:7014268220207497216
urn:li:activity:7013894655352201216	I'm always encouraging you to create a side project. I know how much they've helped me over the years to switch tech stacks, learn things outside of work and even create a couple failed startups. Right now, my side project is creating a series of challenges to increase the skills and confidence for JS developers. Yesterday, I scaffolded a Remix app for the first time in a repo designed to introduce you to e2e testing using Cypress. I thought, "Holy sweet Jimminy Crickets this thing is ugly." I mean, it's not a design challenge but I figured I should add some style... but I also don't really enjoy writing CSS 😅 🤫 TailwindCSS to the rescue. Honestly, I just copied and pasted some boilerplate code I ripped off the internet for the styling and updated my tests to pass and voila! Literally 5 mins to go from refrigerator art to... art.	SLIDE_SHOW	Brian	Jenney	1,567	1,567	16	1	0	0.010849	null	2022-12-28 08:09:43	https://www.linkedin.com/feed/update/urn:li:activity:7013894655352201216
urn:li:activity:7013885291354619904	So I still deal with impostor syndrome. I know what you might want to hear or have already heard: It just gets better and you're fine the way you are. Think positively or wait it out and eventually you will feel less impostor-y. 🌈 🦄 🥰 Except, that didn't really work out for me and I will never give you advice that I wouldn't follow. For me, impostor syndrome signals a disparity in the skills I think a person in my position should have and my current capabilities. What I've done to identify this gap is list out the skills/traits I feel like I'm supposed to have. Often times the list is not as daunting as I imagined. I start working on this list, little by little. I understand the areas that will make me feel more "worthy" of my position and attack them. Now I have "proof" that I am where I'm supposed to be. In my experience, it's rare that others perceive us as impostors. People are too caught up in their own world to really care about you 😉. The insecurity that often accompanies change is indeed in your head but that doesn't mean you should ignore it. Identify, attack, move on and repeat? I know a lot of you feel like this and I’m curious to know how you’ve dealt with it 🤔	UNKNOWN	Brian	Jenney	2,822	2,822	28	12	0	0.014174	null	2022-12-28 08:09:43	https://www.linkedin.com/feed/update/urn:li:activity:7013885291354619904
urn:li:activity:7013527307478843392	I've had the pleasure of working with a little over a dozen developers in the last 6 months who have landed their first role or their next role. Junior devs, mid-level, senior and lead. Maybe CTO next 😉. I've also worked with a dozen others who are still searching and are equally as talented as the others who found success earlier. So what gives? I wish I could tell you the formula for landing that first role but I have not unlocked that cheat code yet. I don't think anyone has. My main takeaway is that you cannot control when or how luck decides to strike. Your best bet is to be prepared when it does. - 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝘀𝘁𝗿𝗼𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗳𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻 in your primary language - 𝗯𝘂𝗶𝗹𝗱 𝗶𝗻 𝗽𝘂𝗯𝗹𝗶𝗰 (if that's your thing) - 𝘣𝘶𝘵 𝘥𝘦𝘧𝘪𝘯𝘪𝘵𝘦𝘭𝘺 𝘣𝘶𝘪𝘭𝘥! - 𝗹𝗲𝗮𝗿𝗻 𝗯𝗮𝘀𝗶𝗰 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗱𝗲𝘀𝗶𝗴𝗻 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 (𝘚𝘖𝘓𝘐𝘋, 𝘖𝘖𝘗) - 𝗹𝗲𝗮𝗿𝗻 𝗱𝗲𝘀𝗶𝗴𝗻 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝘆𝗼𝘂’𝗿𝗲 𝘂𝘀𝗶𝗻𝗴 (𝘦𝘨: 𝘩𝘰𝘰𝘬𝘴 𝘧𝘰𝘳 𝘙𝘦𝘢𝘤𝘵) - 𝗱𝗼 𝗽𝗼𝘀𝘁-𝗺𝗼𝗿𝘁𝗲𝗺𝘀 𝗮𝗳𝘁𝗲𝗿 𝗿𝗲𝗷𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗲𝘀 (𝘸𝘩𝘺 𝘥𝘪𝘥 𝘺𝘰𝘶 𝘧𝘢𝘪𝘭? 𝘸𝘩𝘺 𝘥𝘪𝘥 𝘺𝘰𝘶 𝘴𝘶𝘤𝘤𝘦𝘦𝘥?) There’s no point stacking interviews or increasing your surface area for luck if you don’t have the skills to actually hit your target.	UNKNOWN	Brian	Jenney	3,288	3,288	41	7	0	0.014599	null	2022-12-27 08:13:04	https://www.linkedin.com/feed/update/urn:li:activity:7013527307478843392
urn:li:activity:7013166621301112832	In 2013 I bought one of those HTML5 programming books for dummies. I was determined to learn to code by the end of Summer. I read the entire flipping book. Cover to cover. Then, I promptly sat down in front of my laptop after downloading Sublime text editor and realized I had no goddamned clue how to code shit. Learning to code wasn’t like any studying I had previously done. I know you’re probably thinking, “A whole book on HTML5? How Sway? LOL” Shut your pie hole - I barely knew anything back then. Thankfully, I am a stubborn bastard and decided to go to a meetup with other developers who showed me how to get code from my noggin into my text editor and open it up in a web browser. Magic. - I stopped reading and started building janky apps on CodePen. - I added Jquery. Astonishing. - I got hired at a job where I had to learn C#. - Bought another book… for dummies. I hadn’t quite learned yet. Never said I was the brightest bulb on the tree. Just the stubbornest. After creating some useless API endpoints using C#, I knew enough to be dangerous. Ok, I saw a pattern here. I actually really enjoy books on coding and find a lot of value in them… at this stage. Now I’m an engineering manager still building janky apps in my spare time and building less janky apps in my professional time. Want to get better as a developer? Build shit.	UNKNOWN	Brian	Jenney	4,599	4,599	63	7	2	0.015656	null	2022-12-26 07:51:31	https://www.linkedin.com/feed/update/urn:li:activity:7013166621301112832
urn:li:activity:7012454877192749056	Another mentee of mine got hired. The funny thing is we barely covered any technical material during our meetings. I'm beginning to realize a lot of developers just need encouragement, a clear direction for what to study and a good kick in the ass to go for what they want. Learning about closures doesn't hurt either 😉	UNKNOWN	Brian	Jenney	9,765	9,765	147	11	0	0.01618	null	2022-12-24 08:34:49	https://www.linkedin.com/feed/update/urn:li:activity:7012454877192749056
urn:li:activity:7011759714803888128	Maybe this wasn't such a good idea... Earlier this year I posted a link to schedule a 15 minute chat with me. 200+ of you took me up on my offer 😲 What was originally meant as a tactic to get more sales call for my mentorship services turned into something much more valuable than I could've ever expected. I've heard all your problems and identified the top 5 which I explore in this article with links to free resources I know will help you. Looking forward to the next 200. ✊	ARTICLE	Brian	Jenney	2,959	2,959	42	9	3	0.018249	null	2022-12-22 10:34:49	https://www.linkedin.com/feed/update/urn:li:activity:7011759714803888128
urn:li:activity:7011371149905326080	You don't need Redux. But you should still know how to use it. 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. You can still debate whether context, useReducer or whatever new state management library popped up this week is better than Redux… I mean, if that’s your thing who am I to judge... but you know I am 😉. Try learning these concepts/tools and I think you will get a better understanding and appreciation for Redux: - publisher/subscriber pattern - ducks architecture - pure functions - redux dev extension Oh, and if you want to get your hands dirty with Redux - grab my starter kit in the comments below.	UNKNOWN	Brian	Jenney	6,890	6,890	69	15	3	0.012627	null	2022-12-21 09:11:14	https://www.linkedin.com/feed/update/urn:li:activity:7011371149905326080
urn:li:activity:7011100204888195073	I know it's all the rage to have an existential crisis over ChatGPT but have you considered using it for more than just generating code like a little code monkey? I asked our robot overlord to review some code I'd written and it gave me some pretty spot-on feedback. I can see how this tool could be leveraged to create more dialogue during code reviews between devs who have different experience levels or are unfamiliar with a codebase. LGTM!	IMAGE	Brian	Jenney	8,150	8,150	72	15	4	0.011166	null	2022-12-20 15:09:35	https://www.linkedin.com/feed/update/urn:li:activity:7011100204888195073
urn:li:activity:7011042674573025280	What most aspiring developers do: - Build 99 small, trivial apps - Chase shiny frameworks - Follow “watch and type” tutorials - Marathon coding sessions on the weekend and nothing during the week - Look for junior developer jobs What you should do: - Build 1 or 2 interesting and complex apps and deploy them to the web - Double down on the fundamentals of your primary language and design patterns - Consistent daily coding (it’s a wonder what 1 hour a day will do) - Apply for jobs where you meet ~50% of the requirements	UNKNOWN	Brian	Jenney	6,734	6,734	97	10	4	0.016484	null	2022-12-20 11:13:53	https://www.linkedin.com/feed/update/urn:li:activity:7011042674573025280
urn:li:activity:7010610080341520384	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. Being too narrowly focused on the technical aspect of the job and 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, nodding my head during estimation sessions and giving bland status updates. I never shared my ideas during meetings. I wanted to blend in. It was probably 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. If career trajectory and increased hire-ability is your goal however, playing it safe is the biggest threat to your goals.	UNKNOWN	Brian	Jenney	7,859	7,859	89	18	0	0.013615	null	2022-12-19 06:37:54	https://www.linkedin.com/feed/update/urn:li:activity:7010610080341520384
urn:li:activity:7009544909904826368	You passed the interview! Now the real work begins. Bootcamps do a great job (for the most part) of getting developers hire-able. But what happens after you nail the interview? If you're a junior dev, self taught or went to a bootcamp, you probably struggle in the same areas that I did after getting hired: - Git - Writing good peer reviews - Estimating features - Writing unit tests - Debugging - Technical communication - Crippling impostor syndrome - Learning a new codebase Like too many of us, I learned these skills through trial and error. Over years! That doesn't mean it has to take you that long. While there is no substitute for time in the field, you can certainly follow accounts like Rahul Pandey and Alex Chiou to learn how to succeed as a software engineer and gain the non-coding skills you'll need to advance in your career. If YouTube is more your thing, I'd recommend 𝗧𝗵𝗲𝗼 𝗳𝗿𝗼𝗺 𝗣𝗶𝗻𝗴𝗟𝗮𝗯𝘀 (𝘑𝘚 𝘤𝘶𝘵𝘵𝘪𝘯𝘨 𝘦𝘥𝘨𝘦 𝘴𝘵𝘶𝘧𝘧 𝘢𝘯𝘥 𝘴𝘱𝘪𝘤𝘺 𝘳𝘢𝘯𝘵𝘴) and 𝗔 𝗟𝗶𝗳𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗲𝗱 (𝘨𝘦𝘯𝘦𝘳𝘢𝘭 𝘤𝘢𝘳𝘦𝘦𝘳 𝘢𝘥𝘷𝘪𝘤𝘦 𝘧𝘰𝘳 𝘮𝘪𝘥 𝘢𝘯𝘥 𝘴𝘦𝘯𝘪𝘰𝘳 𝘥𝘦𝘷𝘴).	UNKNOWN	Brian	Jenney	15,815	15,815	148	9	3	0.010117	null	2022-12-16 07:59:14	https://www.linkedin.com/feed/update/urn:li:activity:7009544909904826368
urn:li:activity:7009200431083962370	"The market is over-saturated, no one is hiring coders right now." - 𝘚𝘰𝘮𝘦 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳 𝘐 𝘸𝘢𝘴 𝘥𝘳𝘪𝘷𝘪𝘯𝘨 𝘪𝘯 𝘚𝘍 𝘸𝘩𝘪𝘭𝘦 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘧𝘰𝘳 𝘓𝘺𝘧𝘵 𝘪𝘯 2014 If you're listening to the cynics, eventually you'll believe them and their negative outlook will become your self-fulfilling prophecy.	UNKNOWN	Brian	Jenney	6,855	6,855	69	13	4	0.012546	null	2022-12-15 09:13:46	https://www.linkedin.com/feed/update/urn:li:activity:7009200431083962370
urn:li:activity:7008835271429419008	What you thought the front end interview would be: - traverse tree - search array - binar-ily - detect a palindrome - maps! use a map! What you got instead: - tell me about a time when... - build something that looks like this mock-up - tell me how this obscure feature in JS works - let's build a component while I watch... and judge! Check out this walkthrough of the 3 species of interviews you will encounter in the wild as a front end developer, based on the 100 or so interviews I've done or heard about from others over the last few years.	ARTICLE	Brian	Jenney	4,609	4,609	67	6	2	0.016273	null	2022-12-14 09:16:51	https://www.linkedin.com/feed/update/urn:li:activity:7008835271429419008
urn:li:activity:7008800130854268928	The job hunt is a numbers game! No - wait, it’s all about networking and coffee chats. Hold on a sec - you need to learn in public! That’s the trick. Honestly, I’ve seen people fail and succeed using all of these methods. There is no hack. It’s actually quite boring really: - Pick one thing and stick with it long enough to see results. Be consistent but not dumb - if something is not working, seek advice and change it.	UNKNOWN	Brian	Jenney	6,141	6,141	84	12	0	0.015633	null	2022-12-14 06:45:44	https://www.linkedin.com/feed/update/urn:li:activity:7008800130854268928
urn:li:activity:7008476745502773249	Every developer should have a side project that teaches them something outside of work. The problem? Most people don't know how to build a project that will stretch their limits. Here are 5 steps that might help you get started: 1. pick an API you are interested in 2. decide on a framework or language you’d like to learn for this project 3. create the MVP user flow by drawing out the features needed for the app (a piece of paper is is sufficient, no need to get fancy) 4. choose a cloud service provider for deployments - personally I’d use AWS since it’s what you’ll likely use in the “real world” 5. roughly 50% of your tech stack should be new to you and the other 50% should be familiar so you don’t get completely overwhelmed	UNKNOWN	Brian	Jenney	6,504	6,504	97	9	2	0.016605	null	2022-12-13 09:26:50	https://www.linkedin.com/feed/update/urn:li:activity:7008476745502773249
urn:li:activity:7008151811547168768	Yes, I do think ChatGPT will steal your coding job... if all you do is write code. Writing code is honestly the easy part... understanding all the biz requirements, constraints and how to deliver complex projects is at least a few months away for this AI 😅 *** Protect yourself from bots and check out some free material that will make you less replaceable: https://brianjenney.me	UNKNOWN	Brian	Jenney	5,646	5,646	55	8	1	0.011335	null	2022-12-12 11:56:24	https://www.linkedin.com/feed/update/urn:li:activity:7008151811547168768
urn:li:activity:7008074862338478080	In 2016 I was on the software developer hamster wheel program. 10 out of 10 would not recommend. Here’s how it goes: - Hear about a new technology - Buy small course or book and blindly follow along - Build trivial project - Hear about a new technology - 🐹 Now instead of being good in a few languages/technologies I was below average in several! Once I really doubled down on the fundamentals of Javascript and design patterns I felt more confident and the quality of my work improved. That doesn’t mean I don’t explore new tech - but I am a lot more picky with what I choose to learn.	UNKNOWN	Brian	Jenney	5,813	5,813	68	2	3	0.012558	null	2022-12-12 06:48:50	https://www.linkedin.com/feed/update/urn:li:activity:7008074862338478080
urn:li:activity:7007028599518097408	The most impactful line of code you can write as a Javascript developer? 𝚍𝚎𝚋𝚞𝚐𝚐𝚎𝚛 I'm consistently shocked by how many people either don't use this keyword or know it exists. It's a hell of a lot better than littering your code with 129 console logs. I'll walk you through this and some other debugging tips in the video below. *** 𝗜𝗳 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 𝗺𝗼𝗿𝗲 𝗝𝗦 𝗺𝗮𝘁𝗲𝗿𝗶𝗮𝗹 𝘁𝗵𝗮𝗻 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗵𝗮𝗻𝗱𝗹𝗲, 𝗴𝗿𝗮𝗯 𝗶𝘁 𝗵𝗲𝗿𝗲: https://brianjenney.me	VIDEO	Brian	Jenney	7,122	7,122	80	7	1	0.012356	null	2022-12-09 09:41:54	https://www.linkedin.com/feed/update/urn:li:activity:7007028599518097408
urn:li:activity:7006686111783673857	Need a break from the LeetCode grind? I've been having a lot of fun with #adventofcode. Perhaps the best feature of these problems is that they require you to sift through a lot of information to get to the meat of the problem which is closer to your average interview experience than being explicitly asked to implement some random algo. Check it out here: https://adventofcode.com/	UNKNOWN	Brian	Jenney	3,706	3,706	32	3	2	0.009984	#adventofcode.	2022-12-08 10:31:45	https://www.linkedin.com/feed/update/urn:li:activity:7006686111783673857
urn:li:activity:7006627280177287168	If you’re one of those people who is waiting until January 1st to make some big change in your life, that thing you know you should be doing… Well, I think that’s OK. I like going to the gym in January and seeing all the new people. I honestly hope they stick with it because I know how powerful exercise has been in my professional and personal life. There’s nothing wrong with setting a date to make a change. The hard part is sticking with it. I’ve quit alcohol, got in shape and learned to code using this pattern and maybe it will help you: - 𝘎𝘦𝘵 𝘢𝘤𝘤𝘰𝘶𝘯𝘵𝘢𝘣𝘭𝘦 - tell people what you are doing so failure is more embarrassing - Instead of focusing on the benefits of your new habit - 𝘵𝘩𝘪𝘯𝘬 𝘰𝘧 𝘵𝘩𝘦 𝘳𝘦𝘱𝘦𝘳𝘤𝘶𝘴𝘴𝘪𝘰𝘯𝘴 𝘰𝘧 𝘕𝘖𝘛 𝘥𝘰𝘪𝘯𝘨 𝘪𝘵 - 𝘔𝘢𝘬𝘦 𝘤𝘩𝘢𝘯𝘨𝘦 𝘦𝘢𝘴𝘺 - don't rely on will power alone - you will fail. For example, if you want to stop eating so much junk, don't keep any in your house - 𝘔𝘢𝘬𝘦 𝘪𝘵 𝘥𝘰𝘢𝘣𝘭𝘦 - you’re not gonna go from 0 - 100. Instead of studying for 2 hours a day, go for 30 minutes consistently This weekend I'm seriously considering sharing a very non-tech newsletter that I wrote to help a friend lose weight and get in shape. Tis' the season and all. Should I?	UNKNOWN	Brian	Jenney	2,639	2,639	28	4	0	0.012126	null	2022-12-08 06:40:36	https://www.linkedin.com/feed/update/urn:li:activity:7006627280177287168
urn:li:activity:7006266040724721664	Tutorial hell is miserable. So instead, I: - create small side projects using technology I'm interested in - read books - explore popular open source libraries to see how the pros write code Don’t get me wrong, I’ll still use tutorials. But I’m not going to rely on them alone. ** Tired of tutorial hell? Check out my not-another-course collection of material https://lnkd.in/gpqEgqny	UNKNOWN	Brian	Jenney	4,854	4,854	51	16	3	0.014421	null	2022-12-07 07:03:52	https://www.linkedin.com/feed/update/urn:li:activity:7006266040724721664
urn:li:activity:7005923085593784320	I had 193 15 minute conversations with developers from all over the world in the last 6 months. Here are my takeaways: - impostor syndrome is prevalent and rampant at all levels (shocker) - most junior developers need to optimize their LinkedIn profiles - picking a good side project is something most developers want to do but don’t know where to start - networking, cold applying and learning in public ALL work - the trick is sticking to one long enough to see results - this is an awesome community despite what anyone says to the contrary I was personally shocked to hear just how many of us don’t feel good or smart enough. I do believe that some self-assessment is healthy and useful. I also believe that working remotely and often with cloudy expectations creates an environment for negative assessments to fester. If it’s any consolation, know that basically everyone I’ve spoken to, from the senior at Amazon to the junior who just got hired feels like there is something missing from their tool belt. I’ll be consolidating these conversations and the advice I find myself repeating next week in an article that I hope you find useful. *** 𝘊𝘩𝘦𝘤𝘬 𝘰𝘶𝘵 𝘴𝘰𝘮𝘦 𝘧𝘳𝘦𝘦 𝘳𝘦𝘴𝘰𝘶𝘳𝘤𝘦𝘴 𝘵𝘰 𝘩𝘦𝘭𝘱 𝘺𝘰𝘶 𝘭𝘦𝘷𝘦𝘭 𝘶𝘱 𝘢𝘴 𝘢 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘩𝘦𝘳𝘦 https://brianjenney.me	UNKNOWN	Brian	Jenney	12,046	12,046	158	18	6	0.015109	null	2022-12-06 08:24:32	https://www.linkedin.com/feed/update/urn:li:activity:7005923085593784320
urn:li:activity:7005536624382017537	I’ve seen all your side projects. They fall into 1 of 3 categories: 1. Clone of popular app 2. Random thing generator 3. Chat app I’m not saying there’s anything at all wrong with these apps. I’ve seen some amazing (and not so amazing) variations of these. Here’s the real issue though: It’s hard to stand out from other bootcamp grads who have basically created the same app. So what can you do? Create your own side project. - Pick an API about something you’re interested in - Choose a language and framework you’re curious about - Ideally, try to solve a real world problem - Maybe a web scraper that aggregates jobs with less than [x] applicants from a popular site. Something that displays historical data? Whatever floats your damn boat. - Add some tests maybe - Deploy it Now you’ve learned some valuable skills and maybe even have something beautiful to show off. What are some good side projects you've seen or would suggest?	UNKNOWN	Brian	Jenney	20,933	20,933	206	49	8	0.012564	null	2022-12-05 06:49:13	https://www.linkedin.com/feed/update/urn:li:activity:7005536624382017537
urn:li:activity:7004509183903485952	Expecting formal mentorship at your next job as a developer? Got some bad news for ya’ buddy. Most companies simply don’t have a plan or budget to offer the kind of mentorship that will actually accelerate your career so they rely on: - Video tutorials from popular services which may be outdated or irrelevant to your goals - Conferences - Senior devs who just don't have the time or desire 𝘚𝘰 𝘸𝘩𝘢𝘵 𝘤𝘢𝘯 𝘺𝘰𝘶 𝘥𝘰? Here’s the harsh truth - you, not your company, are ultimately responsible for your growth as a developer. If paid mentorship isn’t something you’re into, you can try: - books - building an app using a few technologies you are interested in - doing small algo challenges on sites that start with Leet and end with Code What are some ways you’ve been able to stay sharp as a developer? *** 𝘐𝘧 𝘺𝘰𝘶 𝘸𝘢𝘯𝘵 𝘴𝘰𝘮𝘦 𝘤𝘩𝘢𝘭𝘭𝘦𝘯𝘨𝘪𝘯𝘨 𝘮𝘢𝘵𝘦𝘳𝘪𝘢𝘭 𝘵𝘰 𝘭𝘦𝘷𝘦𝘭 𝘺𝘰𝘶 𝘶𝘱 𝘢𝘴 𝘢 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘤𝘩𝘦𝘤𝘬 𝘰𝘶𝘵 https://brianjenney.me	UNKNOWN	Brian	Jenney	6,200	6,200	57	4	1	0.01	null	2022-12-02 10:56:41	https://www.linkedin.com/feed/update/urn:li:activity:7004509183903485952
urn:li:activity:7004509234096717824	Expecting formal mentorship at your next job as a developer? Got some bad news for ya’ buddy. Most companies simply don’t have a plan or budget to offer the kind of mentorship that will actually accelerate your career so they rely on: - Video tutorials from popular services which may be outdated or irrelevant to your goals - Conferences - Senior devs who just don't have the time or desire 𝘚𝘰 𝘸𝘩𝘢𝘵 𝘤𝘢𝘯 𝘺𝘰𝘶 𝘥𝘰? Here’s the harsh truth - you, not your company, are ultimately responsible for your growth as a developer. If paid mentorship isn’t something you’re into, you can try: - books - building an app using a few technologies you are interested in - doing small algo challenges on sites that start with Leet and end with Code What are some ways you’ve been able to stay sharp as a developer? *** 𝘐𝘧 𝘺𝘰𝘶 𝘸𝘢𝘯𝘵 𝘴𝘰𝘮𝘦 𝘤𝘩𝘢𝘭𝘭𝘦𝘯𝘨𝘪𝘯𝘨 𝘮𝘢𝘵𝘦𝘳𝘪𝘢𝘭 𝘵𝘰 𝘭𝘦𝘷𝘦𝘭 𝘺𝘰𝘶 𝘶𝘱 𝘢𝘴 𝘢 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘤𝘩𝘦𝘤𝘬 𝘰𝘶𝘵 https://brianjenney.me	UNKNOWN	Brian	Jenney	75	75	0	0	0	0	null	2022-12-02 10:56:41	https://www.linkedin.com/feed/update/urn:li:activity:7004509234096717824
urn:li:activity:7004206369989947392	First off, if someone actually asks you this question in a coding interview - wtf. That being said, recursion is difficult and confused the hell out of me for a long time. In the video below, I walk through my delicious recursive recipe and do a fairly tricky problem in real time. I hope this gets you a step or 2 closer to understanding recursion. *** 𝗖𝗵𝗲𝗰𝗸 𝗼𝘂𝘁 𝘀𝗼𝗺𝗲 𝗼𝘁𝗵𝗲𝗿 𝗳𝗿𝗲𝗲 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 𝘁𝗼 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂 𝗴𝗲𝘁 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗿𝗲𝗮𝗱𝘆 𝗵𝗲𝗿𝗲: https://brianjenney.me	VIDEO	Brian	Jenney	9,633	9,633	78	12	6	0.009966	null	2022-12-01 14:16:15	https://www.linkedin.com/feed/update/urn:li:activity:7004206369989947392
urn:li:activity:7004093654042648576	The end of the Leetcode grind? The funny thing is, most non-tech companies weren’t asking whiteboard-style questions in the first place. You’re a hell of a lot more likely to encounter a take home, pair programming or language-specific type of challenge on the interview circuit than dynamic programming. I still encourage you to familiarize yourself with common data structures and algorithms. Learning them has given me confidence and better problem solving ability and it may do the same for you. That being said, if you’re expecting your next interview to be filled with trees, graphs and palindromes… you might be right but I’d caution against ONLY studying DSA. If you are on the interview grind, what’s your experience? *** 𝗘𝘃𝗲𝗿𝘆 𝘄𝗲𝗲𝗸𝗲𝗻𝗱 𝗜 𝘀𝗵𝗮𝗿𝗲 𝗳𝗿𝗲𝗲 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 𝗮𝗻𝗱 𝘁𝗶𝗽𝘀 𝘁𝗼 𝗮𝗰𝗰𝗲𝗹𝗲𝗿𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝗱𝗲𝘃 𝗰𝗮𝗿𝗲𝗲𝗿 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻 𝘀𝘁𝘂𝗳𝗳: https://brianjenney.me	UNKNOWN	Brian	Jenney	13,949	13,949	79	32	1	0.008029	null	2022-12-01 07:14:34	https://www.linkedin.com/feed/update/urn:li:activity:7004093654042648576
urn:li:activity:7003731378777325568	You're rejecting yourself from more roles than you need to. Listen, if you have ~50% of the skills and are within 1-2 years of the experience "requirements" then you should absolutely be applying. If you actually met 100% of the requirements, you're overqualified.	UNKNOWN	Brian	Jenney	8,280	8,280	118	16	4	0.016667	null	2022-11-30 07:31:55	https://www.linkedin.com/feed/update/urn:li:activity:7003731378777325568
urn:li:activity:7003034982453583872	Here’s a story I hate to hear: Developer graduates from bootcamp, gets hired, then let go for performance reasons. It sucks. I’ve heard this story from more than a couple developers and my heart goes out to them. Is the bootcamp at fault for not preparing them for a difficult profession? Maybe the job should’ve offered more support? Were they just out of their league? If your bootcamp, school or YouTube instructors did not fully prepare you for the “real world” of software development, you may have to supplement your education. - Get a mentor - Build stuff - Work with your manager to get feedback Get specific: - What is it that you need to learn? - How will you learn it? - How long will it take? Clarity precedes success. *** I write more stuff here: https://brianjenney.me	UNKNOWN	Brian	Jenney	8,110	8,110	60	13	2	0.009248	null	2022-11-28 08:57:38	https://www.linkedin.com/feed/update/urn:li:activity:7003034982453583872
urn:li:activity:7001936234331746304	Ask enough stupid questions and you're gonna be pretty goddmn smart. The trick is to only ask those "stupid" questions once. 90% of the people in the room probably have the same question and are too embarrassed to ask. Most of them won't write the answer down. I spent the first 3 years of my career as a software developer basically saying nothing. I'd nod my head whether or not I understood something and had some spectacular blow-ups because of it. I made a resolution to expose my ignorance and ask questions. Something unexpected happened when I did that: - I became more engaged in the work - co-workers would DM me and thank me for asking questions they were too embarrassed to ask themselves - I got more leadership opportunities - I learned faster Now, as an engineering manager, I hope the new members on my team feel safe and confident to ask their own "stupid" questions. Not only for moral reasons but for a very practical one as well: It will shorten the time it takes for them to become proficient in our processes and codebases. Expose your ignorance to grow faster. #licreatoraccelerator ** This weekend I'll be going over ways junior developers can create impact, stand out and do more than not get fired. Check it out here https://brianjenney.me	UNKNOWN	Brian	Jenney	6,960	6,960	90	13	5	0.015517	#licreatoraccelerator	2022-11-25 08:01:32	https://www.linkedin.com/feed/update/urn:li:activity:7001936234331746304
urn:li:activity:7001246977187348480	I was teaching at a bootcamp on weekends about 5 years ago. A student came up to me after class and had a complaint about my teaching style: “𝘠𝘰𝘶’𝘳𝘦 𝘮𝘰𝘷𝘪𝘯𝘨 𝘸𝘢𝘺 𝘵𝘰𝘰 𝘧𝘢𝘴𝘵 𝘧𝘰𝘳 𝘱𝘦𝘰𝘱𝘭𝘦 𝘭𝘪𝘬𝘦 𝘮𝘦. 𝘐 𝘥𝘪𝘥𝘯’𝘵 𝘨𝘳𝘰𝘸 𝘶𝘱 𝘶𝘴𝘪𝘯𝘨 𝘤𝘰𝘮𝘱𝘶𝘵𝘦𝘳𝘴 𝘭𝘪𝘬𝘦 𝘺𝘰𝘶” He was right; I had been rushing the lesson and my mind was a bit foggy. I just had a daughter and was pulling 7 day work weeks because I like money and diapers. Also - I had fooled him. “𝘓𝘪𝘬𝘦 𝘺𝘰𝘶?” I wanted to tell him that I did not grow up with computers. In fact I didn’t own a computer until I was about 28. I had learned to code just a few years before teaching this class, right after getting sober. I was driving real software engineers around San Francisco working for Uber and Lyft after my regular job and coding in the morning before work and on weekends. I was average at best. It took all that work to just be an average developer. But I was happy. And here I was fooling this class and this guy into thinking I was some fancy-pants software engineer. Maybe I’m fooling you too. Maybe you think I’m some highfalutin manager type who has been coding since MySpace and giving you advice based on a book I read or what sounds good. I can only tell you what’s worked for me and hope it shortens your path from where you are to where you want to be. So take what I say with a grain of salt. Pick out what makes sense for you, question who’s giving you the info and then put down the phone and apply it. *** 𝘌𝘷𝘦𝘳𝘺 𝘚𝘢𝘵𝘶𝘳𝘥𝘢𝘺 𝘐 𝘨𝘪𝘷𝘦 𝘢𝘤𝘵𝘪𝘰𝘯𝘢𝘣𝘭𝘦, 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘢𝘭 𝘢𝘱𝘱𝘳𝘰𝘢𝘤𝘩𝘦𝘴 𝘵𝘰 𝘣𝘦𝘤𝘰𝘮𝘪𝘯𝘨 𝘢 𝘣𝘦𝘵𝘵𝘦𝘳 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳: http://brianjenney.me #licreatoraccelerator	UNKNOWN	Brian	Jenney	12,006	12,006	126	17	1	0.011994	#licreatoraccelerator	2022-11-23 10:26:09	https://www.linkedin.com/feed/update/urn:li:activity:7001246977187348480
urn:li:activity:7000838967898116096	He created a full stack app that worked pretty well. It even looked nice. But when I asked how it worked… Oof. 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗰𝗮𝘀𝗲 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗮𝗯𝘂𝘀𝗲. Too many people fall into the trap of looking at a tutorial, following along with the instructor and typing what they type. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗼𝗳𝗳: a shiny new app. 𝗧𝗵𝗲 𝗰𝗼𝘀𝘁: a false sense of mastery It’s an enticing trap and it may even fool someone into hiring you. More than 90% of my side projects have never had users or been deployed. I made janky apps and sites to learn new concepts, frameworks and even join a startup as a mid-level developer in a completely new tech stack. Every side project doesn’t need to be a masterpiece. Leverage them to learn what you won’t at work or what you would like to work on next. If you want my step by step guide on creating a solid side project you can grab it here https://lnkd.in/gQ94kA97 *** 𝘛𝘪𝘳𝘦𝘥 𝘰𝘧 𝘵𝘶𝘵𝘰𝘳𝘪𝘢𝘭𝘴? 𝘊𝘩𝘦𝘤𝘬 𝘵𝘩𝘪𝘴 𝘰𝘶𝘵: https://lnkd.in/gpqEgqny #licreatoraccelerator	UNKNOWN	Brian	Jenney	21,833	21,833	197	31	8	0.010809	#licreatoraccelerator	2022-11-22 07:39:45	https://www.linkedin.com/feed/update/urn:li:activity:7000838967898116096
urn:li:activity:7000839046121889792	He created a full stack app that worked pretty well. It even looked nice. But when I asked how it worked… Oof. 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗰𝗮𝘀𝗲 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗮𝗯𝘂𝘀𝗲. Too many people fall into the trap of looking at a tutorial, following along with the instructor and typing what they type. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗼𝗳𝗳: a shiny new app. 𝗧𝗵𝗲 𝗰𝗼𝘀𝘁: a false sense of mastery It’s an enticing trap and it may even fool someone into hiring you. More than 90% of my side projects have never had users or been deployed. I made janky apps and sites to learn new concepts, frameworks and even join a startup as a mid-level developer in a completely new tech stack. Every side project doesn’t need to be a masterpiece. Leverage them to learn what you won’t at work or what you would like to work on next. If you want my step by step guide on creating a solid side project you can grab it here https://lnkd.in/gQ94kA97 *** 𝘛𝘪𝘳𝘦𝘥 𝘰𝘧 𝘵𝘶𝘵𝘰𝘳𝘪𝘢𝘭𝘴? 𝘊𝘩𝘦𝘤𝘬 𝘵𝘩𝘪𝘴 𝘰𝘶𝘵: https://lnkd.in/gpqEgqny #licreatoraccelerator	UNKNOWN	Brian	Jenney	718	718	1	0	0	0.001393	#licreatoraccelerator	2022-11-22 07:39:45	https://www.linkedin.com/feed/update/urn:li:activity:7000839046121889792
urn:li:activity:7000492456039333888	I've had a few people I know recently lose their job. It sucks. They weren't working for some fly-by-night startups either. These were established companies. It's a reminder that stability is a myth. Whether you just found yourself job-less or know someone who is in that position, hopefully this article that Erik Andersen put together with others in the tech/career space will be helpful. https://lnkd.in/dYcZWX-m #licreatoraccelerator --- I help developers accelerate their career and learn through hands-on exercises https://brianjenney.me	UNKNOWN	Brian	Jenney	1,897	1,897	8	0	0	0.004217	#licreatoraccelerator	2022-11-21 08:41:54	https://www.linkedin.com/feed/update/urn:li:activity:7000492456039333888
urn:li:activity:6999417291843006464	Are you getting sh*t done? Or are you just busy being busy? This week I attended an audio event hosted by Rahul Pandey and Alex Chiou: "How To Get Stuff Done In Tech". I've certainly fallen into the trap of just being busy without actually feeling like I'm making forward progress. I would end the day, mentally drained from meetings, research and centering divs 😉 only to look back and wonder what the hell I'd really done. My 3 main takeaways from this event: 1. Clarity leads to action (𝘩𝘢𝘷𝘦 𝘢 𝘱𝘭𝘢𝘯 𝘢𝘯𝘥 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘺𝘰𝘶𝘳 𝘱𝘳𝘪𝘰𝘳𝘪𝘵𝘪𝘦𝘴 𝘢𝘳𝘦) 2. Make habits easy to follow (𝘮𝘢𝘬𝘦 𝘢 𝘮𝘰𝘳𝘯𝘪𝘯𝘨 𝘳𝘰𝘶𝘵𝘪𝘯𝘦 𝘺𝘰𝘶 𝘤𝘢𝘯 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘤𝘰𝘮𝘮𝘪𝘵 𝘵𝘰 - 𝘯𝘰𝘵 𝘵𝘩𝘦 𝘰𝘯𝘦 𝘵𝘩𝘢𝘵 𝘪𝘯𝘤𝘭𝘶𝘥𝘦𝘴 1 𝘩𝘰𝘶𝘳 𝘢𝘧𝘧𝘪𝘳𝘮𝘢𝘵𝘪𝘰𝘯𝘴 𝘢𝘯𝘥 500 𝘱𝘶𝘴𝘩𝘶𝘱𝘴) 3. Don't fall into the trap of the manager schedule (𝘤𝘶𝘵 𝘰𝘶𝘵 𝘮𝘦𝘦𝘵𝘪𝘯𝘨𝘴 𝘸𝘩𝘦𝘳𝘦 𝘺𝘰𝘶 𝘤𝘢𝘯) Busy !== productive but it's easy to confuse the two. If you're not already following Rahul Pandey and Alex Chiou you really should. There's a lot of great information out there for junior devs and those trying to break into the industry... but what about the rest of us? Engineering managers, middle and senior devs? Where's our bootcamp? These two have a lot of great content and an app that explores life after the interview that I've found incredibly useful. #linkedinaudioevent #licreatoraccelerator	UNKNOWN	Brian	Jenney	8,171	8,171	43	5	2	0.006119	#linkedinaudioevent ,#licreatoraccelerator	2022-11-18 09:15:24	https://www.linkedin.com/feed/update/urn:li:activity:6999417291843006464
urn:li:activity:6999400627676078080	Holy fishcakes, I see the same issues on every junior developer's LinkedIn profile: - less than 500 connections - mentioning "junior" or "aspiring" in the profile - confusing job history - top skills that aren't relevant The video here will give you some pointers on how to make yourself more discoverable on LI and maybe make your profile suck a little less. #licreatoraccelerator	VIDEO	Brian	Jenney	11,883	11,883	119	15	12	0.012286	#licreatoraccelerator	2022-11-18 08:13:45	https://www.linkedin.com/feed/update/urn:li:activity:6999400627676078080
urn:li:activity:6999046107385253889	One of my mentees has been struggling on the job search and requested a meeting with me at 6AM this morn. Ruh roh... I expected we might go over some quick interview prep for an upcoming on-site or discuss a recent experience. I was pleasantly surprised when he pulled up his screen and showed me an offer letter! About as good a way to start my morning as I could imagine. I met Ramandeep Singh a few months ago. He had just graduated from a bootcamp and was looking for a role as a developer. We worked on all the technical aspects of preparing for interviews: Javascript features and concepts, algorithms and ReactJS. In retrospect, more than anything, I offered him support during a very demanding string of interviews, rejections and self-doubt. I am thoroughly impressed. It takes a lot of dedication to remain consistent when things just aren't going your way. This is exactly why most people fail. That little voice in the back of their head tells them every reason they won't or can't get hired. F*ck that voice. This was a good reminder for me that technical skills are absolutely important to learn, but encouragement, empathy and support are equally needed. We're humans first. Congratulations Ramandeep Singh - incredibly well deserved!	UNKNOWN	Brian	Jenney	18,667	18,667	177	21	1	0.010661	null	2022-11-17 08:41:41	https://www.linkedin.com/feed/update/urn:li:activity:6999046107385253889
urn:li:activity:6998805535609278464	Getting interviews is hard. Interviewing is hard. Do you know what’s harder? The part after the interview. Starting a new position, learning a new codebase, getting your first feature, doing your first on call rotation. The interview is just the entry fee to an entirely new game. Check out 4 things you can do as a software engineer to stand out on your team that have little to do with coding. #licreatoraccelerator	ARTICLE	Brian	Jenney	4,104	4,104	48	6	1	0.013402	#licreatoraccelerator	2022-11-16 16:59:49	https://www.linkedin.com/feed/update/urn:li:activity:6998805535609278464
urn:li:activity:6998299586368872449	You can’t wish away impostor syndrome. If there’s one theme I’ve noticed in the 176 conversations I’ve had with many of you over the phone or hangouts during the last few months, it’s this: Developers largely feel they are less competent than other developers on their team, bootcamp or university. I’m no statistician, I’m barely an engineer, but I don’t think it’s possible this many developers are in the bottom 10% of their respective groups. So what gives? We think the person next to us is smarter than we are. They understand some concept just a little more than we do. They know the answer to the question we’re afraid to ask. I’m intrigued and a little sad that so many of us feel like this. I suspect a lack of communication coupled with remote work has made us feel more isolated than ever. Funny thing is, the senior engineer at Amazon is feeling a lot of the same insecurities as the junior who just graduated. So what do you do? - identify the gaps in your skill - resist the urge to procrastinate with endless tutorials - embrace the fact you can not learn everything and expose your ignorance - make a plan to earn your confidence by learning what intimidates you #licreatoraccelerator	UNKNOWN	Brian	Jenney	4,908	4,908	39	8	0	0.009576	#licreatoraccelerator	2022-11-15 07:15:03	https://www.linkedin.com/feed/update/urn:li:activity:6998299586368872449
urn:li:activity:6997958321613750273	A framework for a great side project: 1. Find an interesting (and free) API: 𝘪𝘯𝘴𝘵𝘦𝘢𝘥 𝘰𝘧 𝘢 𝘮𝘰𝘷𝘪𝘦 𝘥𝘢𝘵𝘢𝘣𝘢𝘴𝘦, 𝘵𝘳𝘺 𝘴𝘵𝘰𝘤𝘬𝘴 𝘰𝘳 𝘮𝘢𝘤𝘩𝘪𝘯𝘦 𝘭𝘦𝘢𝘳𝘯𝘪𝘯𝘨 𝘈𝘗𝘐𝘴 2. Pick 1 or 2 new technologies you want to learn and leverage your current knowledge for the rest of the dev work 3. Create the user flow: 𝘜𝘴𝘦 𝘍𝘪𝘨𝘮𝘢 𝘰𝘳 𝘊𝘢𝘯𝘷𝘢 𝘧𝘰𝘳 𝘮𝘰𝘤𝘬𝘶𝘱𝘴 4. Deploy it: 𝘊𝘰𝘯𝘴𝘪𝘥𝘦𝘳 𝘈𝘞𝘚 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 𝘵𝘩𝘢𝘵’𝘴 𝘸𝘩𝘢𝘵 𝘮𝘰𝘴𝘵 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘸𝘪𝘭𝘭 𝘶𝘴𝘦 𝘪𝘯 𝘵𝘩𝘦 “𝘳𝘦𝘢𝘭” 𝘸𝘰𝘳𝘭𝘥 #licreatoraccelerator	UNKNOWN	Brian	Jenney	6,959	6,959	83	13	4	0.01437	#licreatoraccelerator	2022-11-14 08:45:03	https://www.linkedin.com/feed/update/urn:li:activity:6997958321613750273
urn:li:activity:6997300149437833216	There are developers with less talent than you who are getting hired. I know the news sucks right now but hear me out: You are likely not competing for the same roles as the influx of highly paid engineers who just came into the market. So continue to work on your skills, keep applying to all those non-sexy companies and tech-adjacent roles and make connections online and IRL. Some will tell you getting that first role (or the next one) is a numbers game. Others will say it's all about connections. Neither is wrong. So try a combination and do what works for you. 𝗕𝗲 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁 𝗯𝘂𝘁 𝗻𝗼𝘁 𝗳𝗼𝗼𝗹𝗶𝘀𝗵: - 𝘪𝘧 𝘺𝘰𝘶 𝘴𝘦𝘯𝘥 𝘰𝘶𝘵 100 𝘢𝘱𝘱𝘴 𝘢𝘯𝘥 𝘯𝘰𝘵 1 𝘨𝘦𝘵𝘴 𝘢 𝘳𝘦𝘱𝘭𝘺 maybe consider looking into your resume or LI profile and asking for advice - 𝘧𝘢𝘪𝘭𝘦𝘥 𝘦𝘷𝘦𝘳𝘺 𝘤𝘰𝘥𝘪𝘯𝘨 𝘤𝘩𝘢𝘭𝘭𝘦𝘯𝘨𝘦 𝘴𝘱𝘦𝘤𝘵𝘢𝘤𝘶𝘭𝘢𝘳𝘭𝘺? Identify what concepts you need to study - 𝘤𝘢𝘯'𝘵 𝘨𝘦𝘵 𝘱𝘢𝘴𝘵 𝘵𝘩𝘦 𝘣𝘦𝘩𝘢𝘷𝘪𝘰𝘳𝘢𝘭 𝘴𝘤𝘳𝘦𝘦𝘯 𝘸𝘪𝘵𝘩 𝘳𝘦𝘤𝘳𝘶𝘪𝘵𝘦𝘳𝘴? Try a mock interview with a friend or mentor and see if you're coming off like an unsafe bet (or a creep 😅) I've had a couple mentees get hired this month. Some take weeks to find a role. Some take months. I've yet to find a "hack" to land a role. Do the boring stuff, fail, learn and re-calibrate. Just don't quit. If you do have some strategies for getting hired please share 'em 👇🏽	UNKNOWN	Brian	Jenney	21,117	21,117	240	24	9	0.012928	null	2022-11-12 12:56:40	https://www.linkedin.com/feed/update/urn:li:activity:6997300149437833216
urn:li:activity:6996861067150721024	Why are we writing tests again? Isn’t that what QA is for? Tests aren’t free, they take time and when done correctly they: - supplement documentation - allow for easier refactoring - verify edge cases which are difficult to trigger manually The problem most people have when it comes to writing tests is just getting started. Check out the video and the links below to code snippets you can use to write your first tests using Jest. ↙️ 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝘁𝗼 𝘁𝗲𝘀𝘁: https://lnkd.in/g8Pz7ivi 𝗧𝗲𝘀𝘁 𝗳𝗶𝗹𝗲𝘀: https://lnkd.in/ganZJQSw #licreatoraccelerator #jest #unittesting #javascript	VIDEO	Brian	Jenney	9,100	9,100	52	9	2	0.006923	#licreatoraccelerator ,#jest ,#unittesting ,#javascript	2022-11-11 07:54:16	https://www.linkedin.com/feed/update/urn:li:activity:6996861067150721024
urn:li:activity:6996304884715192320	Having code that works on your machine is great. Having it work and perform well on another person's machine is where the money is at. I predict site performance will be increasingly important as shoppers migrate further into e-commerce and new apps wreak havoc on our already weak attention spans. As a developer, you want to know how to diagnose and triage the most common culprits slowing down your site. #licreatoraccelerator	ARTICLE	Brian	Jenney	2,568	2,568	42	1	1	0.017134	#licreatoraccelerator	2022-11-09 19:13:22	https://www.linkedin.com/feed/update/urn:li:activity:6996304884715192320
urn:li:activity:6996119056256839682	Stop being so selfish. Honestly, didn’t expect my personal trainer, a tatted up ex-con to be one of the main reasons I started writing on LinkedIn. Both him and my VP at the time encouraged me to share more online and I was apprehensive. Like you, I’ve benefitted from reading others’ stories on here, made some great connections and learned a ton. Here I was, picking all these people’s brains and learning from the community but not giving back myself. He was right, I was being selfish. I let my own ego get in the way of sharing what I had learned and was learning, the mistakes I made and the advice that could’ve saved me months or years of frustration. Should I let people know about my past? How much? What would they think? 𝘞𝘩𝘰 𝘨𝘪𝘷𝘦𝘴 𝘢 𝘧*𝘤𝘬, he told me. 𝘚𝘵𝘰𝘱 𝘮𝘢𝘬𝘪𝘯𝘨 𝘪𝘵 𝘢𝘣𝘰𝘶𝘵 𝘺𝘰𝘶! Yeah, he’s a super intense dude. 😅 So I wrote a lot more. Exposed my past. Got more followers and started a mentorship service. It’s one of the best decisions I’ve made this year. I've spoken with hundreds of you offline, met some amazing people and expanded my business. I know there are people out there who will tell you all the reasons not to share your thoughts. - There are too many voices already - You barely know anything - Who are you to share? Give us the benefit of learning from your mistakes and successes. Open yourself up to criticism and support. Learn how to formulate your thoughts and share them. Don’t be selfish. #CreateOnLinkedIn #licreatoraccelerator	UNKNOWN	Brian	Jenney	7,378	7,378	64	16	0	0.010843	#licreatoraccelerator	2022-11-09 06:51:32	https://www.linkedin.com/feed/update/urn:li:activity:6996119056256839682
urn:li:activity:6995801925787037696	You can stop using Redux. That doesn’t mean your company will though. With around 8.2 million downloads just last week, there’s a pretty good chance you will be using it. So stop being scared of it. Yes, you can still debate whether context, useReducer or whatever new state management library popped up this week is better than Redux… I mean, if that’s your thing who am I to judge (I am judging you… silently). If Redux or its more approachable step-brother, react-redux, still confuses you I understand. For some reason, lots of apps like to split up their actions, types and reducers into many, many small files for the sake of… I dunno really. Try learning these concepts and I think you will get a better understanding of and appreciation for Redux: - 𝘱𝘶𝘣𝘭𝘪𝘴𝘩𝘦𝘳/𝘴𝘶𝘣𝘴𝘤𝘳𝘪𝘣𝘦𝘳 𝘱𝘢𝘵𝘵𝘦𝘳𝘯 - 𝘥𝘶𝘤𝘬𝘴 𝘢𝘳𝘤𝘩𝘪𝘵𝘦𝘤𝘵𝘶𝘳𝘦 - 𝘱𝘶𝘳𝘦 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯𝘴 And of course, tell me why Redux sux and which state management tool you're currently using. #licreatoraccelerator	UNKNOWN	Brian	Jenney	9,811	9,811	72	30	0	0.010396	#licreatoraccelerator	2022-11-08 09:46:41	https://www.linkedin.com/feed/update/urn:li:activity:6995801925787037696
urn:li:activity:6995447580897816577	I’ve solved more problems running around Lake Merritt in Oakland, CA than staring at my computer screen. I’ve been running this lake since I was 14 years old and became a member of Summer Search, a program for inner-city kids who needed a boost in life. At the time, they were sending me out of state to participate in a rigorous outdoors program and I needed to be in decent shape - so running it was. I stopped running for a little over a decade and then picked it back up in my 30’s when I began coding. During these runs I’d find solutions to problems that had alluded me during the week: - creating a complex Redux setup for a real time chart - solution for a race condition during the checkout step of an ecom app - the idea to start a mentorship business - how to create a shared state library for a series of front ends I began to count on my runs when I ran into difficult issues in life or at work. There’s some science to back this up: 𝗬𝗼𝘂𝗿 𝗯𝗿𝗮𝗶𝗻 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀, 𝗺𝗲𝗺𝗼𝗿𝘆 𝗮𝗻𝗱 𝗮𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻 𝘀𝗽𝗮𝗻 𝗯𝗲𝗰𝗼𝗺𝗲 𝘀𝘁𝗿𝗼𝗻𝗴𝗲𝗿 𝗱𝘂𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗳𝗼𝗿 𝗮 𝘀𝗵𝗼𝗿𝘁 𝘁𝗶𝗺𝗲 𝘀𝗽𝗮𝗻 𝗮𝗳𝘁𝗲𝗿 𝗮 𝗿𝘂𝗻. Exercise is one of the first things people sacrifice when work or life gets difficult but I doubled down on my routine at each stage of my career. I know it's my not-so-secret weapon. I’d run during lunch, early in the morning or whenever I could. So while you’re banging your head against the computer or screaming at your rubber duck trying to solve that error on line 420, maybe try a run or a walk. Anyone else solved life's problems on a long run? #summersearch #licreatoraccelerator #debugging #running	IMAGE	Brian	Jenney	5,205	5,205	61	14	0	0.014409	#summersearch ,#licreatoraccelerator ,#debugging ,#running	2022-11-07 10:24:39	https://www.linkedin.com/feed/update/urn:li:activity:6995447580897816577
urn:li:activity:6995392171528908800	You aren't paid for how many lines of code you write. You're paid for solving problems and the outsize impact those have on the business. So don't keep on taking tickets you’re sure you will complete that don’t provide value. Instead, look for projects and features that have high visibility and impact. Then, learn from your failures, document your successes and leverage your wins.	UNKNOWN	Brian	Jenney	4,314	4,314	57	10	4	0.016458	null	2022-11-07 06:34:26	https://www.linkedin.com/feed/update/urn:li:activity:6995392171528908800
urn:li:activity:6994689819943591936	I know stability is a myth but just how much volatility will we have to get used to? Some (well, at least one) of the latest rounds of tech layoffs seems particularly immoral. I'm sure there are reasons beyond my scope of understanding that can be used to justify upending the lives of thousands of people for "business" reasons... but I'm no economics professor. To me, it seems wrong on a basic human level. The one silver lining here is the amount of people offering career support, job leads and a sympathetic ear. The tech community continues to be an incredibly supportive (and snarky) group. There's a link in my bio where you can schedule a time to chat if you want to talk to a human.	UNKNOWN	Brian	Jenney	2,832	2,832	27	2	0	0.01024	null	2022-11-05 09:11:28	https://www.linkedin.com/feed/update/urn:li:activity:6994689819943591936
urn:li:activity:6994366488761577472	Bombed the interview? It’s not over yet. Ever had this happen to you: Interviewer asks question that you were right on the verge of solving but too many coffees put you in a jittery state, you panicked and forgot how to do something you’ve done before. Time’s up, video ends and you curse yourself and your terrible caffeine addiction. 𝘖𝘙 Now that the pressure is off you figure out the answer to the question and immediately contact the interviewer/recruiter with your solution and explanation of how your nerves interfered with your performance. I’ve successfully used this exact process and suggested it to others whom I mentor. Sometimes it works, sometimes it doesn’t. Worst case scenario, you’ve proven to yourself you can figure out the problem and maybe learn something. Best case, you move to the next round. Ever used this technique? If so, how'd it work for you? #licreatoraccelerator #codinginterview	UNKNOWN	Brian	Jenney	5,314	5,314	48	10	1	0.011103	#licreatoraccelerator ,#codinginterview	2022-11-04 11:40:06	https://www.linkedin.com/feed/update/urn:li:activity:6994366488761577472
urn:li:activity:6994333550850232320	There's one thing developers find especially difficult to do, regardless of their seniority: Estimation. It's unfortunate that this is often the metric we're judged by most harshly. It's great you're code quality and tests caught random edge cases but if the feature needed for a December 25th promotion isn't ready until Jan 1, I can guarantee your team won't be happy. While there's not much you can do to "fix" a bad estimate, you can certainly get a good idea of when you will actually finish a feature using a system I share in the video below. With this retroactive estimate, you can quickly flag at-risk work and make plans to cut scope or quality... or pull some marathon coding sessions 😬. My steps for "retroactive estimation": - 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝗮𝗻𝗱 𝘄𝗿𝗶𝘁𝗲 𝗱𝗼𝘄𝗻 𝗮𝗹𝗹 𝘁𝗵𝗲 𝗻𝗲𝗰𝗲𝘀𝘀𝗮𝗿𝘆 𝘁𝗮𝘀𝗸𝘀 (styling, tests, PR) - 𝗧𝗵𝗶𝗻𝗸 𝗼𝗳 𝘁𝗵𝗲 𝘄𝗼𝗿𝘀𝘁 𝗰𝗮𝘀𝗲 𝘀𝗰𝗲𝗻𝗮𝗿𝗶𝗼𝘀 for each task (maybe the PR takes 2 days to resolve) - 𝗣𝗮𝗱 𝘆𝗼𝘂𝗿 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲𝘀 to include meetings and other non-dev activities - 𝗖𝗵𝗲𝗰𝗸 𝘆𝗼𝘂𝗿 𝗹𝗶𝘀𝘁 𝗱𝗮𝗶𝗹𝘆 to see if you are in fact on track to deliver and 𝗿𝗲-𝗰𝗮𝗹𝗶𝗯𝗿𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲𝘀 𝗯𝗮𝘀𝗲𝗱 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 - 𝗥𝗮𝗶𝘀𝗲 𝘆𝗼𝘂𝗿 𝗵𝗮𝗻𝗱 as soon as you see a possibility that the feature will NOT make the cut - 𝗨𝘀𝗲 𝘁𝗵𝗶𝘀 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲 𝗻𝗲𝘅𝘁 𝘁𝗶𝗺𝗲 you see a similar feature to more accurately point it #licreatoraccelerator	VIDEO	Brian	Jenney	3,738	3,738	36	8	0	0.011771	#licreatoraccelerator	2022-11-04 09:38:58	https://www.linkedin.com/feed/update/urn:li:activity:6994333550850232320
urn:li:activity:6993936930736406528	No, I’m not teaching my kids to code. Personally, I love writing code, both as a hobby and profession but I think the following skills/traits will be increasingly important in a digital world: • writing • the ability to learn independently • data literacy • public speaking • flexibility • curiosity I’m currently using an AI powered tool, Github Co-Pilot, in my daily work to write code. Years ago I would have scoffed at this reality. With low code and no-code tools becoming more widely available and powerful, my prediction is that tech will continue to play an outsized role in our lives but the work will shift further away from implementing code to architecting systems and orchestrating communication between them. The people who can lead technical efforts, create engaging experiences and leverage data in a smart way will be more coveted than the software engineers who “only” write code. If my kids do want to learn to code though…. Javascript. #mytechprediction #licreatoraccelerator	UNKNOWN	Brian	Jenney	14,468	14,468	101	36	6	0.009884	#mytechprediction ,#licreatoraccelerator	2022-11-03 07:09:05	https://www.linkedin.com/feed/update/urn:li:activity:6993936930736406528
urn:li:activity:6993570438714966017	The job can 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 (𝘢𝘴𝘬 5 𝘱𝘦𝘰𝘱𝘭𝘦 𝘵𝘰 𝘭𝘰𝘰𝘬 𝘢𝘵 𝘺𝘰𝘶𝘳 𝘳𝘦𝘴𝘶𝘮𝘦 𝘢𝘯𝘥 𝘨𝘦𝘵 5 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘰𝘱𝘪𝘯𝘪𝘰𝘯𝘴) - 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 (𝘰𝘳 𝘦𝘷𝘦𝘯 𝘣𝘦𝘵𝘵𝘦𝘳) alternatives So what does this mean? - Expect failure and learn from it - Try your hardest not to take rejection personally - Whatever you do, please do not stop playing the game You only have to win once. #licreatoraccelerator #interview #codinginterview	UNKNOWN	Brian	Jenney	3,391	3,391	47	9	0	0.016514	#licreatoraccelerator ,#interview ,#codinginterview	2022-11-02 06:53:44	https://www.linkedin.com/feed/update/urn:li:activity:6993570438714966017
urn:li:activity:6993269592940843008	I don't care what anyone says, effectively debugging an application is an important skill. In the browser, we can rely on a 𝘥𝘦𝘣𝘶𝘨𝘨𝘦𝘳 to pause execution of our scripts and investigate our janky code line by line. What about Node/Express apps? Check out a feature a much smarter developer showed me years ago that I still use to figure out where I screwed up my API logic. #licreatoraccelerator #debugging #nodejs #expressjs	ARTICLE	Brian	Jenney	3,702	3,702	48	6	2	0.015127	#licreatoraccelerator ,#debugging ,#nodejs ,#expressjs	2022-11-01 11:05:32	https://www.linkedin.com/feed/update/urn:li:activity:6993269592940843008
urn:li:activity:6993231735333298177	You don’t have a problem learning to code. You have a time management issue. Too many people follow this pattern: Zero coding 80% of the week. Marathon coding sessions on their day off. I’ve yet to see this strategy work. It’s simply not sustainable. 1 hour a day beats 6 on a Sunday. Hell, 30 minutes a day will likely get you further than attempting to cram a new framework into a weekend. Consistency > Intensity.	UNKNOWN	Brian	Jenney	28,433	28,433	337	22	3	0.012732	null	2022-11-01 08:29:01	https://www.linkedin.com/feed/update/urn:li:activity:6993231735333298177
urn:li:activity:6992877697496416256	So there I was doing one of my daily 15 minute chats with a developer (link in bio 😉) and I found myself getting schooled. There’s a lot of advice out there about getting your first job as a developer: - Send a box of donuts to the hiring committee - DM every hiring manager in the tri-state area - Do a bunch of open source PRs (and get them ignored…) - Write a bot to apply to 1 company per second 24/7 - Lie 🤷🏻‍♀️ The guy I was speaking with had a simple approach to getting interviews that was working for him which didn’t involve any donuts or even lying: He was reaching out to his network of friends and acquaintances. Tech people. Non-tech people. Asking for referrals or leads and then following up on them. No bootcamp, no CS degree and here he was getting interviews. So while you’re adding a new shade of green to the banner on your resume or adding yet another language to your skillset, don’t forget to reach out to family, friends and acquaintances IRL. #licreatoraccelerator	UNKNOWN	Brian	Jenney	6,994	6,994	59	13	0	0.010295	#licreatoraccelerator	2022-10-31 09:02:44	https://www.linkedin.com/feed/update/urn:li:activity:6992877697496416256
urn:li:activity:6991784125988757504	My most hated interview trend? This one really boils my potato: The take home assignment that's supposed to take 2 hours but actually takes 8. I've worked with too many developers on the interview circuit who get derailed by these often massive assignments that can require a backend, front end and interfacing with some AWS service... "Should only take you a couple hours" 😑 They're largely unavoidable for juniors on the market. Here's some generic tips for dealing with these kinds of challenges: - write some goshdang tests. - add some freaking documentation - record a sweet video of you walking through the functionality (a short one bucko... like 2 mins tops) Few people will do this and it will make you stand out. Here's my method for writing lots of tests quickly using the truth-table method that I hope you find useful. #licreatoraccelerator #unittesting #reactjs	VIDEO	Brian	Jenney	35,845	35,845	327	32	16	0.010462	#licreatoraccelerator ,#unittesting ,#reactjs	2022-10-28 08:39:22	https://www.linkedin.com/feed/update/urn:li:activity:6991784125988757504
urn:li:activity:6991409511588642817	I got through the first couple years of my career not knowing Big O, recursion or data structures. It cost me. I wasn’t building trivial apps here, and this lack of fundamentals led to some embarrassing mistakes. There was the 100 line if-else statement… seriously. The triple-nested for loop with a computationally expensive function. The interview I bombed because I could barely pass a LeetCode easy. “𝘉𝘶𝘵 𝘐’𝘭𝘭 𝘯𝘦𝘷𝘦𝘳 𝘵𝘳𝘢𝘷𝘦𝘳𝘴𝘦 𝘢 𝘵𝘳𝘦𝘦 𝘢𝘵 𝘸𝘰𝘳𝘬, 𝘢𝘭𝘭 𝘐 𝘥𝘰 𝘪𝘴 𝘤𝘦𝘯𝘵𝘦𝘳 𝘥𝘪𝘷𝘴 𝘢𝘯𝘥 𝘤𝘰𝘭𝘰𝘳 𝘣𝘶𝘵𝘵𝘰𝘯𝘴” Really? So you’ve never used recursion or leveraged a library that has? Never considered what happens if your function input grows… by a lot? Ever thought, how can I decrease the look up time for the information in this massive array? Armed with an understanding of common design patterns, data structures and algorithms I wasn’t just able to pass more interviews, I felt more confident and wrote better code. Maybe you will too 😉… probably won’t help you with those centering those divs though. #licreatoraccelerator	UNKNOWN	Brian	Jenney	14,384	14,384	145	21	3	0.011749	#licreatoraccelerator	2022-10-27 07:57:30	https://www.linkedin.com/feed/update/urn:li:activity:6991409511588642817
urn:li:activity:6991037091182784512	There can only be 1 best coder on the team. As an average developer there’s still a lot of room to make 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	6,570	6,570	60	6	1	0.010198	null	2022-10-26 07:07:27	https://www.linkedin.com/feed/update/urn:li:activity:6991037091182784512
urn:li:activity:6990737879891140608	That nagging feeling that you're not good enough or that maybe this career isn't meant for you can be debilitating. It's not enough to just wait it out. For me it wasn't at least. I realized that just as much as I needed to improve technically, I also needed to gain confidence in order to contribute at a level that made me proud. I'm a firm believer that the antidote to stress is action and I hope the steps I outline here give you some actionable steps to quiet that negative voice in your head. #licreatoraccelerator	ARTICLE	Brian	Jenney	3,433	3,433	77	6	1	0.024468	#licreatoraccelerator	2022-10-25 11:29:43	https://www.linkedin.com/feed/update/urn:li:activity:6990737879891140608
urn:li:activity:6990670305492955136	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 work with and speak with a lot of developers at the beginning of their careers. Many of them struggle in the same areas that I did after getting hired: • Git flows and branching • Writing good peer reviews • Estimating features • Deployment processes • Writing unit tests • Debugging • Learning a new codebase 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? #licreatoraccelerator	UNKNOWN	Brian	Jenney	21,651	21,651	215	28	6	0.011501	#licreatoraccelerator	2022-10-25 06:58:34	https://www.linkedin.com/feed/update/urn:li:activity:6990670305492955136
urn:li:activity:6990318372999610369	If you’re hell-bent on learning data structures and algorithms please don’t JUST do 100 LeetCode problems. Try this instead: • learn common data structures like trees, graphs, linked lists, stacks and queues • write these structures from scratch • learn common techniques to sort and traverse data in these structures • focus on recursion and backtracking after learning trees (𝘐 𝘧𝘪𝘯𝘥 𝘵𝘩𝘢𝘵 𝘪𝘵 𝘮𝘢𝘥𝘦 𝘮𝘰𝘳𝘦 𝘴𝘦𝘯𝘴𝘦 𝘵𝘩𝘪𝘴 𝘸𝘢𝘺) • time yourself solving LC problems - shoot for 30 mins for medium problems and write the space and time complexity next to your solution • learn common approaches to optimize algorithms (𝘩𝘢𝘴𝘩𝘮𝘢𝘱𝘴, 𝘮𝘦𝘮𝘰𝘪𝘻𝘢𝘵𝘪𝘰𝘯...) Also - realize that just because MAANG exclusively asks DSA, the majority of your interviews as a front end developer will probably focus on a combination of behavioral and technical assessments including concepts like string manipulation, working with arrays and objects, JS trivia and building small components using ReactJS.	UNKNOWN	Brian	Jenney	35,856	35,856	357	10	27	0.010988	null	2022-10-24 07:31:50	https://www.linkedin.com/feed/update/urn:li:activity:6990318372999610369
urn:li:activity:6989306782317785088	Code peer reviews can be emotional. At worst, they become punitive, nerve-wracking and destructive. Used correctly however, they can be a way for you to increase your influence on a team, teach and learn from others. Here's a video of me walking through my code review process. #licreatoraccelerator #codereview #juniordeveloper	VIDEO	Brian	Jenney	3,774	3,774	32	0	0	0.008479	#licreatoraccelerator ,#codereview ,#juniordeveloper	2022-10-21 13:29:26	https://www.linkedin.com/feed/update/urn:li:activity:6989306782317785088
urn:li:activity:6989221990033235968	Before you learn Kubernetes or Python or whatever is collecting dust in your Udemy library, I want you to do me a small favor. If you’re a JS developer, make sure you can build a small application, free of any external framework. I have a small challenge I give to developers who I mentor 1 on 1. It seems simple on the surface and my hope is that they do in fact find it easy. Often times, it uncovers some gaps in their knowledge and gives us a good idea about where to begin focusing our attention. You can’t build a house on a shaky foundation. Check it out in the comments below and if you’ve completed this challenge, don’t drop any hints!	UNKNOWN	Brian	Jenney	7,945	7,945	61	11	1	0.009188	null	2022-10-21 06:53:21	https://www.linkedin.com/feed/update/urn:li:activity:6989221990033235968
urn:li:activity:6988805484258484224	Diving into an unfamiliar codebase? I’ve worked at 4 companies and had a dozen or so contract jobs as a developer over the years. Here’s how I navigate a new codebase: - get it working locally (𝘺𝘰𝘶 𝘳𝘦𝘢𝘭𝘭𝘺 𝘵𝘩𝘪𝘯𝘬 𝘵𝘩𝘪𝘴 𝘸𝘰𝘶𝘭𝘥 𝘣𝘦 𝘰𝘣𝘷𝘪𝘰𝘶𝘴 𝘣𝘶𝘵 𝘦𝘹𝘱𝘦𝘳𝘪𝘦𝘯𝘤𝘦 𝘩𝘢𝘴 𝘴𝘩𝘰𝘸𝘯 𝘮𝘦 𝘰𝘵𝘩𝘦𝘳𝘸𝘪𝘴𝘦) - look for patterns - for a UI app, how is the business logic handled as opposed to presentational logic? (𝘸𝘩𝘦𝘯 𝘺𝘰𝘶 𝘸𝘳𝘪𝘵𝘦 𝘤𝘰𝘥𝘦, 𝘴𝘵𝘢𝘺 𝘸𝘪𝘵𝘩𝘪𝘯 𝘢𝘯𝘥 𝘭𝘦𝘷𝘦𝘳𝘢𝘨𝘦 𝘵𝘩𝘰𝘴𝘦 𝘴𝘢𝘮𝘦 𝘱𝘢𝘵𝘵𝘦𝘳𝘯𝘴) - pick a feature and break it - expand the API response or trigger an auth error. Update a route to go to a page you just created (𝘵𝘩𝘪𝘴 𝘸𝘪𝘭𝘭 𝘦𝘪𝘵𝘩𝘦𝘳 𝘷𝘦𝘳𝘪𝘧𝘺 𝘰𝘳 𝘤𝘩𝘢𝘭𝘭𝘦𝘯𝘨𝘦 𝘺𝘰𝘶𝘳 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥𝘪𝘯𝘨 𝘰𝘧 𝘣𝘢𝘴𝘪𝘤 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯𝘢𝘭𝘪𝘵𝘺) - update a test - pick a part of the codebase that could use more testing and write a test (𝘵𝘩𝘪𝘴 𝘸𝘪𝘭𝘭 𝘭𝘪𝘬𝘦𝘭𝘺 𝘵𝘦𝘢𝘤𝘩 𝘺𝘰𝘶 𝘵𝘩𝘦 𝘮𝘰𝘴𝘵 𝘢𝘣𝘰𝘶𝘵 𝘩𝘰𝘸 𝘢 𝘤𝘦𝘳𝘵𝘢𝘪𝘯 𝘧𝘦𝘢𝘵𝘶𝘳𝘦 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘸𝘰𝘳𝘬𝘴) - read the f*** docs Anything you’d add?	UNKNOWN	Brian	Jenney	18,377	18,377	127	23	0	0.008162	null	2022-10-20 03:56:29	https://www.linkedin.com/feed/update/urn:li:activity:6988805484258484224
urn:li:activity:6988466986611593216	I have a lot of new followers so I figure it’s time to out myself again. You may know me as some dude on LinkedIn spouting about developer productivity and interviews… you’re not wrong. 10 years ago however, my life was unrecognizable. I struggled with addiction and lived mostly outside the law. A friend’s death coupled with the birth of my first son only increased my foolishness. It’s not an exaggeration to say I was headed for a jail cell or a grave. After an intervention I stopped cold turkey. I had time on my hands and landed my first real job as an adult. I was nearly 30. I needed something to fill the time between works and sleep. I discovered HTML and CSS and found my new addiction. I spent my nights and weekends on free sites like codecademy and going to meetups to learn how to use my Sublime text editor. Many janky websites later and with a lot of luck and support from strangers on line I landed my first role. Every time I share this slice of my life I get nervous. What will people think? I also know there are others like me and my story is not as unique as you’d think. I know a lot of others are feeling alone or are struggling with addiction or insecurity and I hope that you read this and feel less alone. I hope you understand that your history doesn’t dictate your future. I’m no doctor and I can only tell you what’s worked for me: - Finding a hobby - Exercising (discipline and dopamine) - Making my goals public (social pressure) - Taking myself out to movies on weekends (days I was likely to slip up) - Taking it one day at a time (sounds corny but my goal was just to make it through the day… it worked) My DMs are always open if you want to chat. Ok back to more coding content 😉. #licreatoraccelerator	UNKNOWN	Brian	Jenney	15,724	15,724	169	16	1	0.011829	#licreatoraccelerator	2022-10-19 05:22:51	https://www.linkedin.com/feed/update/urn:li:activity:6988466986611593216
urn:li:activity:6988122989317820417	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 fail. Get a bad interviewer? All that pre-work might go down the drain. Perhaps your interviewer asks an unreasonably difficult question or has different standards about what constitutes a reasonable solution? Or perhaps luck works in your favor. Maybe you study a particular question that you have memorized and get asked that question. Maybe the interview is not technical at all and just consists of small talk and personality fit. 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 interviewers are both a game of skill AND chance. Increase your surface area for luck by continuing to apply, researching on sites like Glassdoor and Blind and studying the most common interview questions. #licreatoraccelerator	UNKNOWN	Brian	Jenney	7,292	7,292	74	5	1	0.010971	#licreatoraccelerator	2022-10-18 06:30:49	https://www.linkedin.com/feed/update/urn:li:activity:6988122989317820417
urn:li:activity:6986746992970387456	Out of the 200 or so chats I've had with developers in the last few months, around half of them are with people who live outside the US. The most common question they have: How do I get a remote job? Admittedly, I don't know much about the logistics of getting hired as a remote worker living abroad but luckily Erik Andersen has written an article that I read which has some excellent tips.	ARTICLE	Brian	Jenney	8,429	8,429	45	10	1	0.006644	null	2022-10-14 11:27:45	https://www.linkedin.com/feed/update/urn:li:activity:6986746992970387456
urn:li:activity:6986723507996950528	Tutorial Hell is real place. I've been there. The master writes the code, you watch them and type what they type. It's like a paint by numbers exercise. You may even end up with a nice shiny app and feel like you have achieved some level of mastery. You go in to add a new feature and think to yourself, 𝘩𝘰𝘸 𝘪𝘯 𝘵𝘩𝘦 𝘩𝘦𝘭𝘭 𝘥𝘰𝘦𝘴 𝘵𝘩𝘪𝘯𝘨 𝘸𝘰𝘳𝘬? What you actually learned was how to type really well, but you have about the same understanding of React, Redux or NodeJS as when you started... 12 hours ago. Listen, I'll still buy a half dozen tutorials each year. I see a lot of value in them BUT I also see how they're abused. I'm a huge fan of learning by getting stuck, reading the docs, doing research and most importantly, putting hands on keyboards. If you're looking for a non-tutorial, a project that takes you 80% of the way to the finish line but needs your fixes to get things working - check out the link in the comments ⬇️ I have some GitHub repos with challenges to teach you Redux and introduce you to Node and Express that might frustrate the hell out of you... in a good way I hope 😉	UNKNOWN	Brian	Jenney	12,276	12,276	131	12	0	0.011649	null	2022-10-14 10:00:12	https://www.linkedin.com/feed/update/urn:li:activity:6986723507996950528
urn:li:activity:6986325858881863680	Happy path coding - the mark of the junior developer. Goes a little something like this: - function works ✅ - test cases pass ✅ - PR LGMT’ed ✅ - Blows up spectacularly in production 🚨 I’ve had this experience happen more than a few times because I didn’t consider edge cases. What happens when a deeply nested object from a 3rd party API doesn’t come back as expected? What if the user clicks like a mad-man on the submit button? How often should a request be re-tried before failing? Treat your users kindly but expect them to treat your app like raving lunatics with thumbs for fingers.	UNKNOWN	Brian	Jenney	5,741	5,741	70	8	2	0.013935	null	2022-10-13 07:49:17	https://www.linkedin.com/feed/update/urn:li:activity:6986325858881863680
urn:li:activity:6986038679303577600	Exhausted LinkedIn, AngelList and Indeed on your job search? A very impressive young man reached out to me last week for a chat and was kind enough to share his list of job sites with notes included. Some heroes wear capes. Some painstakingly review job sites, put them in a public file and share them free of charge. 🙏🏻 Hopefully you find it helpful. Shout out to Anirudh Kadian!	ARTICLE	Brian	Jenney	23,943	23,943	228	17	29	0.011444	null	2022-10-12 12:15:03	https://www.linkedin.com/feed/update/urn:li:activity:6986038679303577600
urn:li:activity:6985985291488518145	Don’t remember a single thing as a software engineer. Just Google everything. Really? I wrote a semi-viral post a few months ago about a developer who was unable to pass an interview because he did not have a basic grasp of modern Javascript. He did not know how to use map, filter or reduce. He was not junior. Listen, I look up a ton of things. There’s absolutely nothing wrong with leveraging the collective knowledge of the internet to create code. BUT, there are some things I would expect any JS developer with more than a year of experience to have committed to memory: - for loops - basic iteration methods like forEach, map, filter - function syntax (including arrow functions) - conditional statements (if/else) That interview experience years ago is one of the reasons I started mentoring as a service. I don’t want you to lower your expectations for yourself or walk into interviews under the false impression that you "can just look it up". Perhaps your team uses ES5. Maybe you build emails all day. Your interviewer/s don’t care. They have the same set of questions for you as the others. Having a strong foundation in JS and understanding the basics is key to passing most front end interviews. 𝙏𝙇𝘿𝙍: It’s ok to Google stuff. As a Javascript developer there are some things you will be expected to just have committed to memory like for loops and basic ES6 features. Unfair? I think not. Maybe you think otherwise. Reality? You better believe it.	UNKNOWN	Brian	Jenney	9,075	9,075	82	19	0	0.011129	null	2022-10-12 09:10:52	https://www.linkedin.com/feed/update/urn:li:activity:6985985291488518145
urn:li:activity:6985619659207168001	Nobody asks why enough. Why are we using framework X? Why have we chosen Y deployment strategy? Why are we writing unit tests? Why is Typescript overrated? 😉 Whether you’re working at an established company or a 10 person startup, a lot of your tech stack has been decided for you. It’s critical to your growth to question why these decisions were made rather than blindly following them. Oftentimes there are solid reasons for your team’s choices. Sometimes… not. It’s important to know either way. This way, when you are tasked with making large decisions you can think clearly about the tradeoffs and benefits rather than saying “because that’s what I used in the past.” Being curious is one of your greatest assets as a developer.	UNKNOWN	Brian	Jenney	4,408	4,408	43	7	0	0.011343	null	2022-10-11 08:20:32	https://www.linkedin.com/feed/update/urn:li:activity:6985619659207168001
urn:li:activity:6984201017504542720	As a junior dev you may be focused on getting a function to just work but soon you’ll be pulling your hair out over things like: - migrations - versioning strategies for libraries - code pipelines - deployments - breaking updates I’ve found tackling these kinds of problems to be really exciting… for the most part. The issue most juniors face is that outside of actually being presented with these problems, they may wait years before getting the opportunity to encounter them. Here’s the great thing about being a software engineer: You can present these problems to yourself. - Github actions can give you experience with pipelines - creating an NPM package is a great way to learn about versioning strategies - deploy an app to AWS on the free tier - update you long lost side project from React 15 to 18 or Node 12 to 18 and cry for a bit So yes, keep getting those functions to work. And when you have the time, think about what's on the periphery of the code you write and how to make things work there.	UNKNOWN	Brian	Jenney	3,652	3,652	25	1	1	0.007393	null	2022-10-07 10:36:05	https://www.linkedin.com/feed/update/urn:li:activity:6984201017504542720
urn:li:activity:6983836643581403136	I've spoken with about 2% of my audience over the last few months. That number may seem small but in reality that means I've done around 150 phone calls with people here on LI. Our convos are short and even though they are tech focused, they're often more about impostor syndrome, confidence and career trajectory. Also... closure 😅 I find myself repeating a lot of the same advice and while I really enjoy these conversations, I want to reach more people. Dagna Bieda and I are taking the conversations we've been having in 1 on 1's and behind closed doors to the public. Next week we'll be discussing burnout, the silent killer and ways we've found to handle the stress that comes with working in tech. https://lnkd.in/eA6zXyhw	UNKNOWN	Brian	Jenney	303	303	1	0	0	0.0033	null	2022-10-06 10:35:20	https://www.linkedin.com/feed/update/urn:li:activity:6983836643581403136

Subsets and Splits

No community queries yet

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