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:6983779848020271104	If you can learn how to code for free, then why do people upwards of 10k for a bootcamp or 50k for a college degree? I’ll be honest, I’ve met way too many developers over the years who are unwilling to spend a dime on their education. They go to YouTube university, fall down several rabbit holes and emerge on the other end with a host of unrelated skills. None of which make them more employable than they previously were. Of course, I’ve met some highly disciplined and ambitious people who actually beat the odds. What you’re paying for when you enroll in a bootcamp (or college) is not only the knowledge you acquire but: 1. A clear and concise path to learn a skill 2. Support 3. Community 4. Accountability You can also get in shape without a trainer. Perform basic car maintenance without a mechanic. Remodel your home from YouTube tutorials. It just depends on your needs, time constraints and tolerance for failure. Want a shorter, clearer path towards your goal? Find someone where you want to be and ask them what it takes to get there.	UNKNOWN	Brian	Jenney	17,510	17,510	163	31	2	0.011194	null	2022-10-06 07:50:25	https://www.linkedin.com/feed/update/urn:li:activity:6983779848020271104
urn:li:activity:6983421096867880960	How does it feel to be the worst developer on a team? Well, I had the unpleasant experience of holding this title when I worked at a small startup. I probably had more technical growth in the short time I was there than at any other company I’ve worked since. You’ve probably heard the advice “If you’re the smartest person in the room, it’s time to leave the room.” Easier said than done. The guilt and anxiety I felt on a daily basis was difficult to deal with. There I was, confronted with my own limitations and the realization that this wasn’t just all in my head. I could barely keep up with the tasks I was assigned and relied on lots of pairing sessions to get my work done. The company was small - only 3 engineers and they were the kind of developers who gave speeches at conferences and wrote the libraries that other devs use in their daily work. I could either quit or at least attempt to keep up with the other devs and contribute to the best of my ability. I made a resolution to suck less. - I asked the smarty-pants devs what books they suggested I read - I audited my Javascript knowledge and wrote out what I knew I had to learn to contribute to discussions - enrolled in a course to learn DSA and comp sci fundamentals - someone made a joke about Djikstra once… who the hell is that? I would find out I never became the 2nd worst developer at this company, but I grew my technical skills, confidence and threshold for failure. As uncomfortable as it was, I know see just how pivotal this experience was. So if you’re just starting out, or maybe on a new team and discovering just how little you know…good. Embrace the suck, expose your ignorance and be prepared to learn.	UNKNOWN	Brian	Jenney	27,280	27,280	348	43	8	0.014626	null	2022-10-05 06:49:32	https://www.linkedin.com/feed/update/urn:li:activity:6983421096867880960
urn:li:activity:6982711844561895424	⏰ The clock is ticking! ⏰ 1.5 hrs-ish left to our watercooler audio chat, where you can tune in and ask any questions that come to mind about Salary vs. Fulfillment in Tech. Brian Jenney and I are bringing back the fun in-office feel of a water cooler chat to all those who want to listen in to an interesting chit-chat. https://lnkd.in/g7WtKSNU #linkedinAudioEvent #Tech #salary #fulfillment #joinUsLive #watercooler #office #chitChat	UNKNOWN	Brian	Jenney	222	222	3	4	1	0.036036	#linkedinA,#salary ,#fulfillment ,#joinU,#watercooler ,#office ,#chitC	2022-10-03 08:00:20	https://www.linkedin.com/feed/update/urn:li:activity:6982711844561895424
urn:li:activity:6982692840900345856	Nearly a decade ago I started my first day as a developer. I knew HTML, CSS, Jquery and a little AngularJS. The night before the first day, I was barely able to sleep. I scoured the internet for any articles on what to expect… nothing. Remember, this was a generation ago in tech years. 𝘞𝘰𝘶𝘭𝘥 𝘐 𝘣𝘦 𝘧𝘰𝘶𝘯𝘥 𝘰𝘶𝘵 𝘢𝘴 𝘢 𝘧𝘢𝘬𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘢𝘯𝘥 𝘧𝘪𝘳𝘦𝘥 𝘪𝘮𝘮𝘦𝘥𝘪𝘢𝘵𝘦𝘭𝘺? 𝘞𝘰𝘶𝘭𝘥 𝘵𝘩𝘦𝘺 𝘨𝘪𝘷𝘦 𝘮𝘦 𝘢 𝘵𝘢𝘴𝘬 𝘐 𝘤𝘰𝘶𝘭𝘥𝘯’𝘵 𝘧𝘪𝘨𝘶𝘳𝘦 𝘰𝘶𝘵? 𝘏𝘰𝘸 𝘭𝘰𝘯𝘨 𝘣𝘦𝘧𝘰𝘳𝘦 𝘵𝘩𝘦𝘺 𝘳𝘦𝘢𝘭𝘪𝘻𝘦𝘥 𝘵𝘩𝘦𝘺 𝘮𝘢𝘥𝘦 𝘢𝘯 𝘦𝘳𝘳𝘰𝘳 𝘪𝘯 𝘵𝘩𝘦𝘪𝘳 𝘩𝘪𝘳𝘪𝘯𝘨 𝘱𝘳𝘰𝘤𝘦𝘴𝘴? Well, I never got “found out” and took on more than a few tasks I couldn’t figure out… yet. If you recently started a new position or are about to, you may be feeling a lot of the same emotions. I still do, honestly. 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. Perhaps more so. What’s your tips for people just starting a new dev position?	UNKNOWN	Brian	Jenney	6,793	6,793	107	16	3	0.018549	null	2022-10-03 06:53:53	https://www.linkedin.com/feed/update/urn:li:activity:6982692840900345856
urn:li:activity:6981597869908664321	You can LeetCode til your fingers bleed and still fail. Unfortunately, I’ve fumbled more than a couple interviews in the past because I was unable to tell a good story about my accomplishments. As you move past entry level roles, interviews will begin to center less around your immediate coding skills and more towards your experience, so have a good story or 2 in your back pocket. 𝘞𝘩𝘢𝘵 𝘥𝘪𝘥 𝘺𝘰𝘶 𝘸𝘰𝘳𝘬 𝘰𝘯? 𝘞𝘩𝘢𝘵 𝘸𝘢𝘴 𝘪𝘯𝘵𝘦𝘳𝘦𝘴𝘵𝘪𝘯𝘨 𝘢𝘣𝘰𝘶𝘵 𝘪𝘵? 𝘞𝘩𝘢𝘵 𝘪𝘮𝘱𝘢𝘤𝘵 𝘥𝘪𝘥 𝘪𝘵 𝘩𝘢𝘷𝘦? Give some context. You may know what the EggsAndBacon API is but no one else does. What were the challenges you encountered? How did you succeed or fail (and what did you learn?) Use the STAR method or jot down the beginning, middle and end of your story and a metric or 2 you can point to to drive home the impact it had. Having a good story in your mental reserve will prepare you for the next time you’re hit with the old “tell me about a technical project you’ve worked on…”	UNKNOWN	Brian	Jenney	28,125	28,125	194	15	2	0.007502	null	2022-09-30 06:01:13	https://www.linkedin.com/feed/update/urn:li:activity:6981597869908664321
urn:li:activity:6980516439661166593	Random technical interview tips that have nothing to do with coding: - have some water near you during an interview - make sure your battery life and charger are sufficient - clean up your messy ass room - arrive a few minutes early to bumble around with the video chat login - have your code editor ready (and turn off Github Co-pilot 😉) - take a short walk or do some pushups before the interview Any other non-technical tips you’d add?	UNKNOWN	Brian	Jenney	16,262	16,262	86	34	0	0.007379	null	2022-09-27 06:45:16	https://www.linkedin.com/feed/update/urn:li:activity:6980516439661166593
urn:li:activity:6980181249357205505	𝘊𝘰𝘥𝘦 𝘴𝘩𝘰𝘶𝘭𝘥 𝘢𝘭𝘸𝘢𝘺𝘴 𝘧𝘰𝘭𝘭𝘰𝘸 𝘵𝘩𝘦 𝘋𝘙𝘠 𝘱𝘳𝘪𝘯𝘤𝘪𝘱𝘭𝘦! - Except, maybe your abstraction is more clever than useful in some cases 𝘛𝘋𝘋 𝘰𝘳 𝘥𝘪𝘦! - What about TaDD (test after development is done)? Or, perhaps manual QA is the correct choice 𝘛𝘺𝘱𝘦𝘚𝘤𝘳𝘪𝘱𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘯𝘭𝘺 𝘤𝘩𝘰𝘪𝘤𝘦 𝘧𝘰𝘳 𝘴𝘦𝘳𝘪𝘰𝘶𝘴 𝘑𝘚 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴! - Maybe TS is overkill for this simple UI app 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. Any sacred cows I missed here?	UNKNOWN	Brian	Jenney	7,563	7,563	63	23	2	0.011636	null	2022-09-26 08:21:14	https://www.linkedin.com/feed/update/urn:li:activity:6980181249357205505
urn:li:activity:6979816535590662144	Like it or not, software development can involve just as much investigation as writing code. Sometimes more of the former than the latter. You will be debugging issues in production or your own code and digging through stack traces and source code you've never encountered. Luckily, Chrome Devtools has some pretty interesting updates that should help us all when we're chasing bugs down. https://lnkd.in/gCnti9YV I may have to update my debugging cheatsheet now 😅: https://lnkd.in/gN-umMj2	ARTICLE	Brian	Jenney	2,257	2,257	16	0	0	0.007089	null	2022-09-25 08:25:17	https://www.linkedin.com/feed/update/urn:li:activity:6979816535590662144
urn:li:activity:6979091203384303616	I suck at giving estimates. You probably do too. Does this sound familiar: You looked over the feature, confidently blurted out “1 𝘱𝘰𝘪𝘯𝘵!” and here you are 2 weeks later “almost done.” And you’ve been “𝘢𝘭𝘮𝘰𝘴𝘵 𝘥𝘰𝘯𝘦” for the last 5 days. “𝘈𝘭𝘮𝘰𝘴𝘵.” Don’t do what I did when I got stuck on a ticket earlier in my career: - struggle in silence - give misleading or useless updates during stand-ups - power through it on your time off What I should’ve done: - admitted when I reached my technical depth - gave updated estimates based on my progress - asked for targeted support This weekend I’ll go over my process for retroactive pointing which has helped me suck a lot less at estimating completion dates.	UNKNOWN	Brian	Jenney	3,931	3,931	45	3	1	0.012465	null	2022-09-23 08:03:20	https://www.linkedin.com/feed/update/urn:li:activity:6979091203384303616
urn:li:activity:6978706680171659266	My 4 step process for debugging sh*t: 1. Reproduce the bug consistently to determine the underlying issue. 2. Examine the source code to narrow down the suspects and check for any recent changes using Git blame. 3. Set breakpoints, debuggers and console logs to identify the issue and step through the offending code line by line. Maybe ping the developer who wrote this spaghetti... oh no, it was me! 4. Implement a fix, test it locally and have another engineer review the logic. Jumping the gun can result in introducing more bugs, so I like to have someone with a cooler head reviewing code I wrote in an emotional state 😅. 𝘉𝘰𝘯𝘶𝘴 𝘴𝘵𝘦𝘱: a unit test to ensure the issue does not repeat itself. Any debugging tips you’d add?	UNKNOWN	Brian	Jenney	5,939	5,939	50	18	0	0.01145	null	2022-09-22 06:37:20	https://www.linkedin.com/feed/update/urn:li:activity:6978706680171659266
urn:li:activity:6978336946523713536	Framework FOMO affects 8 out of every 10 front end developers. What is Framework FOMO? Goes a little something like this: New, shiny JS framework comes out. You - in the middle of bumbling around with the framework you are currently using - think to yourself “ooh, shiny framework, must try”. NextJS. Vue. Svelte. Polymer. Do this a few times and now you are no longer a sub par developer in your main framework, but MANY frameworks! Congrats? There is no “best” JS framework. Pick a popular one. Double down on the fundamentals and understand the problems it solves and how. Also… React.	UNKNOWN	Brian	Jenney	7,558	7,558	57	13	1	0.009394	null	2022-09-21 06:07:52	https://www.linkedin.com/feed/update/urn:li:activity:6978336946523713536
urn:li:activity:6977619558274646016	How most successful bootcamp grads operate: - Makes coding and learning a routine - Applies consistently and broadly - Has 1 or 2 complex side projects - Re-calibrates their approach when needed - Has faith that opportunity will present itself Why most bootcamp grads fail: - Relies on motivation instead of routine - Applies to only junior roles - Tutorial - Tutorial - Tutorial - Doesn’t get hired in 3 months - 𝘎𝘪𝘷𝘦𝘴 𝘶𝘱	UNKNOWN	Brian	Jenney	11,875	11,875	151	18	2	0.0144	null	2022-09-19 06:35:33	https://www.linkedin.com/feed/update/urn:li:activity:6977619558274646016
urn:li:activity:6976578943961219072	Turn off the tutorial. Open the code editor. You’re going to learn a hell of a lot more from: - getting stuck - reading the documentation - realizing the docs suck - scouring Stack Overflow - oh no - that’s an old comment - throwing everything at the wall - finally figuring it out - wanting to share excitement and realizing your non-coding friends don't care 😑 as opposed to: - typing what another person has typed	UNKNOWN	Brian	Jenney	18,905	18,905	317	29	7	0.018672	null	2022-09-16 09:40:02	https://www.linkedin.com/feed/update/urn:li:activity:6976578943961219072
urn:li:activity:6976208879936270336	Your next technical interview might not be so technical at all. What I’ve learned from working with nearly 20 front end developers in the last year on the interview grind, is that they often over-optimize for code-related questions and challenges at the expense of everything else. You also want to have answers for questions like: - tell me about a challenging project you’ve worked on - how do you resolve conflicts with team mates? - here’s a website we made, how can we improve it (𝘩𝘰𝘸 𝘥𝘰 𝘺𝘰𝘶 𝘮𝘦𝘢𝘴𝘶𝘳𝘦 𝘵𝘩𝘦 𝘱𝘦𝘳𝘧𝘰𝘳𝘮𝘢𝘯𝘤𝘦 𝘰𝘧 𝘢 𝘸𝘦𝘣𝘱𝘢𝘨𝘦 𝘣𝘢𝘴𝘪𝘤𝘢𝘭𝘭𝘺?) - how do you handle tight deadlines? - what’s your debugging process? - why do you want to work here? What’s a good (or terrible 😈), non-technical question you’ve been asked in an interview?	UNKNOWN	Brian	Jenney	5,040	5,040	46	13	2	0.012103	null	2022-09-15 09:19:51	https://www.linkedin.com/feed/update/urn:li:activity:6976208879936270336
urn:li:activity:6975807369800806400	Always be interviewing. It’s such a weird skill. You do it once every few years and wonder why you suck at it. So how often should you interview? I’d say roughly once every 6 months. This way you can identify your marketability, seniority and realistic salary range. This doesn't mean grinding LC year round. It does mean small daily deposits though. 1 problem a day is a good goal. It also doesn't mean you're switching companies every 6 months. The goal is to keep your interview skills sharp and give you a clearer idea of how you would perform in a high stakes situation... like, if you found yourself jobless. Perhaps you’re a junior at your current company but find yourself passing interviews for mid-level positions. Or maybe you’re wondering if you’re overpaid? Underpaid? Don’t guess. Prove yourself right or wrong. Either way, at least you know. Stability is gone. You will likely work at half a dozen or more companies in your adult life so why not give yourself a fighting chance at actually deciding where you go next.	UNKNOWN	Brian	Jenney	7,786	7,786	83	14	2	0.012715	null	2022-09-14 06:44:29	https://www.linkedin.com/feed/update/urn:li:activity:6975807369800806400
urn:li:activity:6975452526905085952	Some things you need to develop an opinion on as a front-end developer: - SSR vs CSR - Typescript vs Javascript - CSS - 𝘛𝘢𝘪𝘭𝘸𝘪𝘯𝘥𝘊𝘚𝘚? 𝘔𝘢𝘵𝘦𝘳𝘪𝘢𝘭 𝘜𝘐? 𝘚𝘵𝘺𝘭𝘦𝘥 𝘊𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵𝘴? 𝘗𝘭𝘢𝘪𝘯 𝘊𝘚𝘚? - Testing - 𝘛𝘋𝘋? 𝘜𝘯𝘪𝘵 𝘵𝘦𝘴𝘵𝘴? 𝘦2𝘦? 𝘈𝘭𝘭 𝘰𝘧 𝘵𝘩𝘦 𝘢𝘣𝘰𝘷𝘦? 𝘕𝘰𝘯𝘦 𝘰𝘧 𝘵𝘩𝘦 𝘢𝘣𝘰𝘷𝘦 😱 - Module bundlers - UI frameworks - 𝘙𝘦𝘢𝘤𝘵 𝘷𝘴 𝘈𝘯𝘨𝘶𝘭𝘢𝘳 𝘷𝘴 𝘝𝘶𝘦𝘑𝘚 𝘷𝘴 𝘕𝘰 𝘍𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬 What would you add?	UNKNOWN	Brian	Jenney	3,907	3,907	27	9	0	0.009214	null	2022-09-13 07:16:08	https://www.linkedin.com/feed/update/urn:li:activity:6975452526905085952
urn:li:activity:6975452579384217601	Some things you need to develop an opinion on as a front-end developer: - SSR vs CSR - Typescript vs Javascript - CSS - 𝘛𝘢𝘪𝘭𝘸𝘪𝘯𝘥𝘊𝘚𝘚? 𝘔𝘢𝘵𝘦𝘳𝘪𝘢𝘭 𝘜𝘐? 𝘚𝘵𝘺𝘭𝘦𝘥 𝘊𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵𝘴? 𝘗𝘭𝘢𝘪𝘯 𝘊𝘚𝘚? - Testing - 𝘛𝘋𝘋? 𝘜𝘯𝘪𝘵 𝘵𝘦𝘴𝘵𝘴? 𝘦2𝘦? 𝘈𝘭𝘭 𝘰𝘧 𝘵𝘩𝘦 𝘢𝘣𝘰𝘷𝘦? 𝘕𝘰𝘯𝘦 𝘰𝘧 𝘵𝘩𝘦 𝘢𝘣𝘰𝘷𝘦 😱 - Module bundlers - UI frameworks - 𝘙𝘦𝘢𝘤𝘵 𝘷𝘴 𝘈𝘯𝘨𝘶𝘭𝘢𝘳 𝘷𝘴 𝘝𝘶𝘦𝘑𝘚 𝘷𝘴 𝘕𝘰 𝘍𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬 What would you add?	UNKNOWN	Brian	Jenney	5,332	5,332	10	6	0	0.003001	null	2022-09-13 07:16:08	https://www.linkedin.com/feed/update/urn:li:activity:6975452579384217601
urn:li:activity:6975089397872439296	Quintessential junior dev move: Wasting hours solving a problem a co-worker could’ve helped you figure out in minutes. You are ultimately judged on the work you complete, not your ability to slog through problems in solitude. When you bump your head against your technical depth, acknowledge it and ask for help. But for Jeebus' sake please don’t just say “I can’t figure out [x]” Try this: - I’m having an issue with [this specific problem] - I’ve tried [y] but it’s not working in the way I expect which is [this way] - [Maybe add a screenshot or documentation] - Is anyone available to take a look with me sometime today or point me in the right direction? Don’t let your ego get in the way of progress.	UNKNOWN	Brian	Jenney	7,248	7,248	105	13	3	0.016694	null	2022-09-12 07:16:36	https://www.linkedin.com/feed/update/urn:li:activity:6975089397872439296
urn:li:activity:6974028060509536257	I worked at a company that had exactly 0 unit tests and another with 90% overall coverage. Which one do you think had more bugs? Counterintuitively, the company with 0 tests had less critical issues than the one with high coverage 🤔. Of course other factors were at play and I don’t necessarily think either strategy is wrong. Different teams require different approaches. My general rules for writing tests: - they should allow for easy/ruthless refactoring by validating core functionality - they should test scenarios which would be time consuming to test manually - critical areas should have high coverage - they should support, not substitute manual QA Tests are not a guarantee against bugs, but rather a first line of defense. At best they allow us to write code that behaves in a way we expect and actually increases velocity. At worst they just feel like another chore. Which method do you use for tests? e2e? TDD? TaDD (𝘛𝘦𝘴𝘵𝘪𝘯𝘨 𝘢𝘧𝘵𝘦𝘳 𝘋𝘦𝘷𝘦𝘭𝘰𝘱𝘮𝘦𝘯𝘵'𝘴 𝘋𝘰𝘯𝘦) or no tests 😎😅?	UNKNOWN	Brian	Jenney	6,696	6,696	45	44	0	0.013292	null	2022-09-09 08:59:21	https://www.linkedin.com/feed/update/urn:li:activity:6974028060509536257
urn:li:activity:6973665140554575872	We’ve all heard the story of the genius asshole or perhaps been exposed to one (maybe even here, on LinkedIn - who would’ve thought?). Here’s how the story goes: super duper smart senior dev produces great work. He also makes others feel dumb, writes snarky comments on code reviews and generally creates an atmosphere where you either agree with him or are a total fool. The bigger problem: - new ideas aren’t offered - especially from junior members - appetite for risk is decreased among the team - why try to implement a new pattern when it will just get ripped apart? - people who can leave, will - those who can’t - stay Congrats! Now the team is little less proficient and whole hell of a lot less desirable to work with. So perhaps you don’t mind assholes on a moral level, because ya know, you are one. In that case, perhaps the business reasons above will motivate you.	UNKNOWN	Brian	Jenney	3,344	3,344	33	5	0	0.011364	null	2022-09-08 08:59:41	https://www.linkedin.com/feed/update/urn:li:activity:6973665140554575872
urn:li:activity:6973635533893767169	Get paid to learn. That first dev job can seem nearly impossible to get and the fear-mongers online don’t help. Here’s one way I got experience when I had none: - offered to do a site for free for an acquaintance - worked out what features the client wanted and set a timeline for completion - iterated on feedback and communicated with client throughout the build - deployed site to the webs If I were doing this now, I’d follow up with: - get a recommendation from the client - leverage that recommendation to land paying clients on sites like Upwork or codementor.io OR simply use it to gain validation for potential employers Hope that’s helpful.	UNKNOWN	Brian	Jenney	2,281	2,281	23	5	0	0.012275	null	2022-09-08 06:39:05	https://www.linkedin.com/feed/update/urn:li:activity:6973635533893767169
urn:li:activity:6973297492201267200	How to become a senior developer in one easy step: 𝘍𝘪𝘯𝘥 𝘰𝘶𝘵 𝘸𝘩𝘢𝘵 𝘪𝘵 𝘵𝘢𝘬𝘦𝘴 𝘵𝘰 𝘣𝘦𝘤𝘰𝘮𝘦 𝘢 𝘴𝘦𝘯𝘪𝘰𝘳 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘢𝘵 𝘺𝘰𝘶𝘳 𝘤𝘶𝘳𝘳𝘦𝘯𝘵 𝘤𝘰𝘮𝘱𝘢𝘯𝘺 - 𝘢𝘯𝘥 𝘥𝘰 𝘵𝘩𝘰𝘴𝘦 𝘵𝘩𝘪𝘯𝘨𝘴 Honestly, it can vary… widely. Some teams use years of experience to determine seniority... 😬 Others use potentially subjective metrics like code quality, complexity of features and influence in the organization. Others - a blood sacrifice. Whatever metrics you are being judged on, it’s important to know them so you have a very clear path towards mid-level or senior or mega-ultra-hyperbole engineer. What are some metrics you’ve seen to determine seniority?	UNKNOWN	Brian	Jenney	5,940	5,940	42	5	0	0.007912	null	2022-09-07 08:58:40	https://www.linkedin.com/feed/update/urn:li:activity:6973297492201267200
urn:li:activity:6972915647521468416	A couple developers I mentor recently got hired. Now the real work begins. - Exploring a new codebase. - Finding areas to make impact. - Learning the engineering culture. - Using git… but like, foreal this time. I’m beginning to think the transition into the first dev role is where developers need the most support. The job search is stressful for sure but it makes up such a small portion of the developer life-cycle. You won’t be spending your days optimizing algorithms or manipulating palindromes. The part after the interview is when the real growth happens. If you’re a recently hired developer, what are some areas where you wish you had more knowledge?	UNKNOWN	Brian	Jenney	11,069	11,069	112	19	0	0.011835	null	2022-09-06 07:03:05	https://www.linkedin.com/feed/update/urn:li:activity:6972915647521468416
urn:li:activity:6971863207342718976	Ever finish a Udemy tutorial only to discover that you still don't know how to code the thing you just "learned"? Yeah, me too. There is no substitute for getting your hands dirty with code. You can spend another weekend passively watching videos, following paint by numbers tutorials or reading a book on object oriented design and wonder why things just aren't clicking for you. At some point, you need to put pen to paper. Moments ago, I sent out a Node/Express project to a few hundred developers who read my newsletter and now I want to share it with you (link in comments). This repo includes a README with a video walking you through some basic concepts and an overview of the app. Now, your turn: - add some new routes - update the unit tests - change it to use TypeScript - use a real DB instead of my janky solution Hope you find it helpful!	UNKNOWN	Brian	Jenney	6,844	6,844	45	19	0	0.009351	null	2022-09-03 09:40:12	https://www.linkedin.com/feed/update/urn:li:activity:6971863207342718976
urn:li:activity:6971473888593543168	If you’re tired of my rants, spicy advice and tips on how to suck less as a software engineer - check out the rants, spicy advice and tips from some of my favorite YouTube channels instead: https://lnkd.in/gyuZ66S2 - excellent breakdown of DSA https://lnkd.in/gyXXZiiX - for mid/senior level engineers interested in career advancement https://lnkd.in/gZUpnX8F - it’s kinda like you’re sitting with a really Senior Fullstack Dev/mad scientist Any channels out there you suggest?	ARTICLE	Brian	Jenney	1,845	1,845	10	6	0	0.008672	null	2022-09-02 07:50:17	https://www.linkedin.com/feed/update/urn:li:activity:6971473888593543168
urn:li:activity:6971131734729916418	Why do you need to know Vanilla JS? You’re probably writing JS within the bounds of a framework like ReactJS or Angular. So what’s the benefit? I’ve found that going back to the basics offers a lot of “Eureka” moments. It deepens my understanding of how these frameworks work and the benefits they offer. - now it makes sense why that 𝚞𝚜𝚎𝙴𝚏𝚏𝚎𝚌𝚝 is firing when an object is in the dependency array even though none of the kev-value pairs have changed - Redux becomes a little less magical (or confusing 😉) - it’s easier to debug 3rd party libraries written in Vanilla JS or write one myself Frameworks come and go… JS is forever! #javascript #frontenddeveloper #reactjs	UNKNOWN	Brian	Jenney	6,422	6,422	53	4	0	0.008876	#javascript ,#frontenddeveloper ,#reactjs	2022-09-01 09:18:25	https://www.linkedin.com/feed/update/urn:li:activity:6971131734729916418
urn:li:activity:6971131767705534464	Why do you need to know Vanilla JS? You’re probably writing JS within the bounds of a framework like ReactJS or Angular. So what’s the benefit? I’ve found that going back to the basics offers a lot of “Eureka” moments. It deepens my understanding of how these frameworks work and the benefits they offer. - now it makes sense why that 𝚞𝚜𝚎𝙴𝚏𝚏𝚎𝚌𝚝 is firing when an object is in the dependency array even though none of the kev-value pairs have changed - Redux becomes a little less magical (or confusing 😉) - it’s easier to debug 3rd party libraries written in Vanilla JS or write one myself Frameworks come and go… JS is forever! #javascript #frontenddeveloper #reactjs	UNKNOWN	Brian	Jenney	1,563	1,563	5	0	0	0.003199	#javascript ,#frontenddeveloper ,#reactjs	2022-09-01 09:18:25	https://www.linkedin.com/feed/update/urn:li:activity:6971131767705534464
urn:li:activity:6970771275182993409	Don’t fall into the trap of getting tickets “DONE”. Another trivial feature moves its way across the JIRA board. You do this several times over the course of the year and then wonder when your raise or promotion happens… it doesn’t. Listen, there is no simple blueprint to move you from junior → senior developer that you can apply to all software teams. Companies vary widely in the criteria they use to determine seniority and unfortunately you can be deserving and still not get it for reasons outside your control - budget issues for example. 𝘏𝘦𝘳𝘦 𝘪𝘴 𝘢 𝘨𝘦𝘯𝘦𝘳𝘢𝘭 𝘢𝘱𝘱𝘳𝘰𝘢𝘤𝘩 𝘵𝘰 𝘮𝘢𝘬𝘦 𝘢 𝘴𝘰𝘭𝘪𝘥 𝘤𝘢𝘴𝘦 𝘧𝘰𝘳 𝘱𝘳𝘰𝘮𝘰𝘵𝘪𝘰𝘯: - take on features that have high impact and visibility - keep a running brag document where you list achievements and the dates/ticket numbers and any related metrics - ask your manager what is required to reach the next step and explicitly identify what you are missing I don’t think anyone’s ever been fired for getting work across the line. And if you’re content doing that - more power to you. BUT, If you want the title that seems to be just outside your reach, you might want to think about how you can increase your impact.	UNKNOWN	Brian	Jenney	2,021	2,021	19	0	1	0.009896	null	2022-08-31 09:29:51	https://www.linkedin.com/feed/update/urn:li:activity:6970771275182993409
urn:li:activity:6970393772983472128	But I can just Google that. Well, you’re not wrong. I mean, yeah, a lot of being a software developer is Googling what we don’t know. Technology moves fast. We get stuck on a bug or feature. The collective knowledge of the internet gives us a way out. There is an extent to how much you should rely on the kindness of strangers however. If you’re a JS developer and cannot iterate over an array without the help of Stack Overflow - I’d challenge you to go back to the basics for a bit. The real issue with the copy-paste approach or composing software from snippets off the internet is that code inevitably breaks or needs to be extended. Bugs happen. New rules get created. What do you do if you lack the fundamentals or have over-relied on Google rather than your own problem solving skills? Googling is absolutely a skill and should not be discounted. Let’s not also discount our need to have some basic grasp of the language we use on a daily basis. Or am I just way off base here?	UNKNOWN	Brian	Jenney	13,468	13,468	112	23	2	0.010172	null	2022-08-30 08:18:13	https://www.linkedin.com/feed/update/urn:li:activity:6970393772983472128
urn:li:activity:6970022648646930432	They got it all wrong - the interview isn’t harder than the job - it just requires a completely different skill set. So while you’re grinding away at toy problems and optimizing solutions using hashmaps (natch) - don’t forget that the actual job of writing code will be challenging in a completely new way. So build stuff. Read code. Gain cursory knowledge of the software development lifecycle and deployment strategies. Write an awful test or 2 for that create-react-app project you abandoned. Put your LC easy solutions into a Github repo so the rest of us can steal them. The interview is the gateway to the job, not the job itself.	UNKNOWN	Brian	Jenney	14,419	14,419	85	7	1	0.00645	null	2022-08-29 07:36:31	https://www.linkedin.com/feed/update/urn:li:activity:6970022648646930432
urn:li:activity:6968971739254980608	The stuff your bootcamp didn’t teach you about being a software developer: - oncalls can be brutal - if something breaks, you will be the first to know - even if it’s 2AM on a Saturday - your day may be up to 50% meetings - I know they asked you to traverse a binary tree during the interview but you’re likely to get a lot of requests to change the color of a button - if you didn’t negotiate your salary - you lost money - you won’t be building anything from scratch - sometimes sh*tty code is good enough - PRs can be emotional… try to distance yourself from the code… also, don’t make people feel bad during PRs when it’s your turn - JIRA What’d I miss?	UNKNOWN	Brian	Jenney	59,701	59,701	575	81	11	0.011172	null	2022-08-26 09:56:16	https://www.linkedin.com/feed/update/urn:li:activity:6968971739254980608
urn:li:activity:6968583675189809152	Now that the bootcamp is over, how do you keep your coding muscles strong? Sure, you could knock out a random LC easy everyday. A dozen TODO apps. Learn yet another JS framework. OR You could invest your time in a side project. A big one. Something you’re not quite sure how to build exactly. Using around 50% familiar technologies and 50% new technologies you want to learn or are in demand and deploying your (secure) app using AWS will give you an experience which is closer to what you’ll experience in the wild. At worst you learn some valuable skills. At best you launch a useful app which generates monies. I’ve used my failed startup ideas to build side projects which helped me make the switch from AngularJS/C#/SQL to React/Node/Express and advance my career… no monies though… yet. My step by step process for building a solid side project is here:	ARTICLE	Brian	Jenney	6,602	6,602	48	9	2	0.008937	null	2022-08-25 08:08:54	https://www.linkedin.com/feed/update/urn:li:activity:6968583675189809152
urn:li:activity:6968247078766452738	Interviewing is an emotional game. I failed an interview recently, on a mock interview site, with no intention of actually interviewing in the future. It was just for practice. Basically as low stakes as possible. Still hurt. If you're dealing with rejection and need a little pick me up - check out the stories of amazing engineers here who were rejected and realize it happens to all of us:	ARTICLE	Brian	Jenney	32,171	32,171	249	18	8	0.008548	null	2022-08-24 10:05:18	https://www.linkedin.com/feed/update/urn:li:activity:6968247078766452738
urn:li:activity:6968204027234852864	Don’t take LinkedIn too seriously. There are a lot of people on here, with a lot of advice you should take with precaution. Hell, I’m one of them. I can’t tell you, with complete certainty, what will work for you. I do know what’s worked for me and others I’ve mentored and worked with. Will it work for you? Well, that’s my hope. I also don’t believe in telling people how things 𝘴𝘩𝘰𝘶𝘭𝘥 be. We live in an unforgiving reality. So yes, interviews suck. You will have to learn on your own. No one really cares about your sob story. You will be judged on things you may think are unfair - like your ability to traverse a binary tree. At the end of the day, I want you to succeed. It can be tough to wade through all the tips, tricks and advice on here. My rules for sifting through the mud and finding actual valuable nuggets of actionable advice: - 𝘪𝘴 𝘵𝘩𝘦 𝘱𝘦𝘳𝘴𝘰𝘯 𝘪𝘯 𝘢 𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯 𝘐 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘣𝘦 𝘪𝘯? - 𝘥𝘰𝘦𝘴 𝘵𝘩𝘪𝘴 𝘱𝘦𝘳𝘴𝘰𝘯 𝘴𝘦𝘦𝘮 𝘩𝘢𝘱𝘱𝘺? - 𝘥𝘰 𝘵𝘩𝘦𝘺 𝘩𝘢𝘷𝘦 𝘢 𝘸𝘰𝘳𝘬 𝘩𝘪𝘴𝘵𝘰𝘳𝘺 𝘸𝘩𝘪𝘤𝘩 𝘴𝘶𝘱𝘱𝘰𝘳𝘵𝘴 𝘵𝘩𝘦𝘪𝘳 𝘤𝘭𝘢𝘪𝘮𝘴? Hopefully this helps you navigate the LinkedIn maze. #juniordeveloper #coding #bootcamp	UNKNOWN	Brian	Jenney	4,588	4,588	52	3	1	0.012206	#juniordeveloper ,#coding ,#bootcamp	2022-08-24 07:26:10	https://www.linkedin.com/feed/update/urn:li:activity:6968204027234852864
urn:li:activity:6967908105808490496	Failed the Google on-site 2 times. Honestly, pretty happy about it overall. Google is an amazing company but it was never my dream. To top it off, when I first started writing code I couldn’t tell you what Big-O, merge sort or a binary tree was. I was just happy to nail those phone screens and get a free lunch on the campus 🤷🏽‍♂️. So how did I hustle my way onto the Google campus and sully their white boards? 𝘚𝘩𝘰𝘳𝘵 𝘢𝘯𝘴𝘸𝘦𝘳: - studying 𝘕𝘰𝘵 𝘴𝘰 𝘴𝘩𝘰𝘳𝘵 𝘢𝘯𝘴𝘸𝘦𝘳: - setting a timer when solving LC problems (30 mins max) - recording myself walking through solutions using Loom - writing the Big-O space and runtime complexity in comments - studying the basics of system design (caching, work queues, nosql/sql, CAP theorem - read Alex Xu's system design book) - compiled a few good stories to share that showed my skill as a developer (things I’d done which made an impact that I could prove via some metrics) I didn’t make it obviously, but I used a lot of what I studied to help me get offers at other companies, which in comparison, felt a hell of a lot easier than Google. If you’re studying for FAANG - what’s your process?	UNKNOWN	Brian	Jenney	9,780	9,780	66	17	1	0.008589	null	2022-08-23 11:30:21	https://www.linkedin.com/feed/update/urn:li:activity:6967908105808490496
urn:li:activity:6967476046875045888	Sometimes, “I don’t know” is the best answer. It’s also uncomfortable - so maybe try to talk through your ignorance out of fear of appearing… well, ignorant. It’s not fooling anyone. At best, it can be a laughable offense. At worst, it lessens trust. As a software engineer, you will likely come face to face with the limits of your knowledge on a regular basis. A new framework comes out. A pattern you used for years becomes antiquated. A term gets thrown around in a meeting you’ve never heard. 𝘠𝘰𝘶 𝘵𝘩𝘪𝘯𝘬 “𝘈𝘮 𝘐 𝘴𝘶𝘱𝘱𝘰𝘴𝘦𝘥 𝘵𝘰 𝘬𝘯𝘰𝘸 𝘵𝘩𝘪𝘴?” A wiser, almost better looking developer once told me - “expose your ignorance, it’s the only way you’ll learn.” This was after I nodded my head during a marathon pairing session going over a particularly complex unit testing setup. I had never written a single unit test up to this point. I was too embarrassed to admit I was out of my depth. Bring up those things you don’t understand. Ideally, in a public setting so others can benefit. I can nearly guarantee your team mates are silently thanking you.	UNKNOWN	Brian	Jenney	5,031	5,031	37	5	2	0.008746	null	2022-08-22 06:47:05	https://www.linkedin.com/feed/update/urn:li:activity:6967476046875045888
urn:li:activity:6966437049818103808	A couple months ago I shared a link to schedule a 15 minute chat with me in a post that got more attention than I anticipated. Nearly 100 calls later with developers from the US, India, Pakistan, the UK, Nigeria, Kenya and many other parts of the world, I’ve learned a lot about the landscape of web development and the interview experiences beginning developers face. Perhaps you’re as surprised as I am to know that the work we do, the rigorous interviews we face and the general feeling of not knowing enough are commonalities we share. These 100 calls have been overwhelmingly positive and have exposed me to some amazing stories, insights and people. Here’s some of the things I find myself repeating a lot: - get 500 connections on LinkedIn - it will make you more discoverable - don't limit yourself to junior roles and consider removing junior/aspiring from your title - do mock interviews on Pramp if you need practice (no affiliation... yet - holler at me Pramp!) - if you’re not getting any interviews don’t over-prepare for them - focus on getting them - don’t waste too much time learning - videos and tutorials can give you a false sense of mastery - build stuff! - take notes after each interview - what could you have done better? - JS stuff - closures and promises come up a lot - write unit tests for your take home project to stand out I see a LOT of easy to fix mistakes when checking out people’s LI profiles. Check out this list of steps to fix yours https://lnkd.in/gVHGwuqN Here’s to the next 100 calls 😅. #juniordeveloper #coding #javascript #javascriptdeveloper	ARTICLE	Brian	Jenney	8,982	8,982	84	27	4	0.012803	#juniordeveloper ,#coding ,#javascript ,#javascriptdeveloper	2022-08-19 10:23:05	https://www.linkedin.com/feed/update/urn:li:activity:6966437049818103808
urn:li:activity:6966063522086629376	Maybe you are an impostor. Perhaps that nagging feeling that you don’t quite know what you think you should is actually a signal. I know the standard advice is just “wait it out.” That didn’t work for me so well once I got promoted to senior developer. In my head there was a discrepancy between my expectations of a person in my role and the reality of my current knowledge. Heres what worked for me to tame that nagging voice in my head: - wrote down the skills I expected of a senior developer, using the engineers I worked with as examples - identified the skills I was missing - picked the skills I felt were the most important and would give me the most confidence - made a time-bound plan to learn these things - got more confident Hope that helps.	UNKNOWN	Brian	Jenney	10,866	10,866	95	8	6	0.010031	null	2022-08-18 09:11:53	https://www.linkedin.com/feed/update/urn:li:activity:6966063522086629376
urn:li:activity:6965683419548725248	You’re right, whiteboard interviews are unfair, biased and won’t likely resemble the kind of work you do on a daily basis. Now what? Do you simply limit yourself to companies that don’t ask these types of questions? Sure, you could. In fact there’s a list of companies that don't participate in whiteboard interviews https://lnkd.in/gUak6vrp You could also, you know, learn some of the most common data structures and algorithms at the University of YouTube. Or if you’re a masochist, a book perhaps. Want to get started? - trees/tries - linked lists - graphs - stacks/queues - binary search - merge sort - quick sort Implement these structures and algorithms from scratch. Find the Big O time for the most common operations (eg. what is the time complexity for searching a BST? How about inserting into a linked list?). Great, now you can still turn down these white board interviews. But because you want to, not because you have to.	ARTICLE	Brian	Jenney	2,876	2,876	17	7	1	0.008693	null	2022-08-17 08:12:34	https://www.linkedin.com/feed/update/urn:li:activity:6965683419548725248
urn:li:activity:6965339026832646144	Biggest (and most embarrassing) mistakes I’ve made as a developer so far...and the lessons learned: - The 100 line if/else statement used to determine if a customer was eligible for a refund - 𝘧𝘪𝘹𝘦𝘥 𝘵𝘰 𝘶𝘴𝘦 𝘵𝘢𝘣𝘭𝘦 𝘣𝘢𝘴𝘦𝘥 𝘭𝘰𝘨𝘪𝘤 - Not understanding how enums work and writing code that sent emails to every single user repeatedly - 𝘸𝘳𝘰𝘵𝘦 𝘵𝘦𝘴𝘵𝘴 𝘵𝘰 𝘤𝘢𝘵𝘤𝘩 𝘵𝘩𝘪𝘴 𝘴𝘪𝘭𝘭𝘺 𝘦𝘳𝘳𝘰𝘳 𝘢𝘯𝘥 𝘺𝘢 𝘬𝘯𝘰𝘸, 𝘳𝘦𝘢𝘥 𝘶𝘱 𝘰𝘯 𝘦𝘯𝘶𝘮𝘴 - Mistakenly deploying the stage branch on production during a hotfix - 𝘭𝘦𝘢𝘳𝘯𝘦𝘥 𝘵𝘰 𝘢𝘴𝘬 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘴 𝘢𝘣𝘰𝘶𝘵 𝘣𝘳𝘢𝘯𝘤𝘩𝘪𝘯𝘨 𝘳𝘢𝘵𝘩𝘦𝘳 𝘵𝘩𝘢𝘯 𝘫𝘶𝘴𝘵 𝘯𝘰𝘥𝘥𝘪𝘯𝘨 𝘮𝘺 𝘩𝘦𝘢𝘥 𝘸𝘩𝘦𝘯 𝘐 𝘥𝘪𝘥 𝘯𝘰𝘵 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥 - The infamous quadruple nested for loop that brought a real time ordering system to a crawl when traffic peaked - 𝘤𝘳𝘢𝘴𝘩 𝘤𝘰𝘶𝘳𝘴𝘦 𝘰𝘯 𝘉𝘪𝘨 𝘖 𝘯𝘰𝘵𝘢𝘵𝘪𝘰𝘯 - The PR that didn’t catch some glaring bugs which went into production - 𝘗𝘙𝘴 𝘢𝘳𝘦 𝘴𝘦𝘳𝘪𝘰𝘶𝘴 𝘣𝘶𝘴𝘪𝘯𝘦𝘴𝘴 𝘯𝘰𝘵 𝘳𝘶𝘣𝘣𝘦𝘳 𝘴𝘵𝘢𝘮𝘱𝘴 - Not speaking up or sharing my ideas for the first 3 years of my career - 𝘮𝘢𝘥𝘦 𝘢 𝘨𝘰𝘢𝘭 𝘵𝘰 𝘴𝘱𝘦𝘢𝘬 𝘮𝘰𝘳𝘦 𝘢𝘯𝘥 𝘧𝘦𝘭𝘵 𝘮𝘰𝘳𝘦 𝘦𝘯𝘨𝘢𝘨𝘦𝘥 𝘢𝘯𝘥 𝘩𝘢𝘱𝘱𝘺 𝘢𝘧𝘵𝘦𝘳 𝘵𝘢𝘬𝘪𝘯𝘨 𝘢𝘯 𝘢𝘤𝘵𝘪𝘷𝘦 𝘳𝘰𝘭𝘦 𝘰𝘯 𝘮𝘺 𝘵𝘦𝘢𝘮 I’m not writing this to encourage or romanticize shoddy coding or breaking things. Some of these oversights were more forgivable than others but they all taught me a lesson I might not have otherwise learned. I’d argue that if you’re not making ANY mistakes as a developer, you may be not be taking on enough risk or features that stretch your capabilities. What’s the biggest mistake you’ve made thus far?	UNKNOWN	Brian	Jenney	4,299	4,299	38	21	2	0.014189	null	2022-08-16 09:27:22	https://www.linkedin.com/feed/update/urn:li:activity:6965339026832646144
urn:li:activity:6964945325044228096	Will Github Copilot steal your job? I’ll tell you one thing it can’t (yet) do. Debug your buggy code. Debugging continues to be one of the most underrated and valuable skills you can add to your toolbelt as a software engineer. I leveraged a particularly gnarly critical bug fix to make my case for a promotion at one company. If there’s one universal expectation of senior developers, no matter the company, it’s that they jump in to triage the most critical of critical issues. Logging errors to the console often just isn’t enough. Node/Express apps are notoriously difficult to debug. If you are using VS Code, you can set breakpoints in the code, just like you might do in the browser, to pause execution and walk through your spaghetti code line by line. Check out how to do it step by step here: https://lnkd.in/gqE6hmVD	UNKNOWN	Brian	Jenney	2,564	2,564	15	9	0	0.00936	null	2022-08-15 07:17:59	https://www.linkedin.com/feed/update/urn:li:activity:6964945325044228096
urn:li:activity:6963876871511883777	I’ve gained quite a lot more followers on here so I figure it’s time to out myself again: 10 years ago I was addicted to drinking and drugs and living a criminal lifestyle. After an intervention, I promised to quit, unsure if I would actually be able to do it for more than a week. I noticed I had a lot of time on my hands now with none of my terrible outlets available. I found Codecademy and wrote my first line of code. I was hooked (notice a theme here?). I fell ass backwards into a full-stack role after building janky websites for a year. Switched companies 4 times, took on contracts, taught at bootcamps and bought a ton of courses. Made lots of embarrassing mistakes. Kept building stuff. Sucked less each year. I’ll be honest - I don’t like sharing much about my checkered past. It’s a distant memory at this point but I also know a lot of people reading this may be going through an addiction. Maybe it’s strong drugs… maybe it’s video games. Obviously you have to want to change. You need desire and most importantly, direction. Here’s what worked for me: - exercising daily (𝘥𝘰𝘱𝘢𝘮𝘪𝘯𝘦 𝘢𝘯𝘥 𝘤𝘰𝘯𝘧𝘪𝘥𝘦𝘯𝘤𝘦) - finding a replacement relapse when triggered (𝘐 𝘦𝘢𝘵 𝘢 𝘵𝘰𝘯 𝘰𝘧 𝘴𝘸𝘦𝘦𝘵𝘴 𝘸𝘩𝘦𝘯 𝘐 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘥𝘰… 𝘰𝘵𝘩𝘦𝘳 𝘴𝘵𝘶𝘧𝘧) - finding a hobby to fill in the time (𝘧𝘰𝘳 𝘮𝘦 𝘪𝘵 𝘸𝘢𝘴 𝘤𝘰𝘥𝘪𝘯𝘨, 𝘧𝘰𝘳 𝘺𝘰𝘶 𝘮𝘢𝘺𝘣𝘦 𝘳𝘦𝘢𝘥𝘪𝘯𝘨 𝘰𝘳 𝘱𝘶𝘻𝘻𝘭𝘦𝘴) - scheduling events on days I would normally do stupid things (𝘐 𝘸𝘢𝘵𝘤𝘩𝘦𝘥 𝘢 𝘵𝘰𝘯 𝘰𝘧 𝘢𝘸𝘧𝘶𝘭 𝘮𝘰𝘷𝘪𝘦𝘴 𝘰𝘯 𝘛𝘩𝘶𝘳𝘴𝘥𝘢𝘺 𝘢𝘯𝘥 𝘍𝘳𝘪𝘥𝘢𝘺 𝘯𝘪𝘨𝘩𝘵𝘴 𝘪𝘯 𝘮𝘰𝘷𝘪𝘦 𝘵𝘩𝘦𝘢𝘵𝘦𝘳𝘴 𝘵𝘰 𝘱𝘢𝘴𝘴 𝘵𝘩𝘦 𝘵𝘪𝘮𝘦) - telling everyone I quit (𝘺𝘰𝘶’𝘭𝘭 𝘧𝘦𝘦𝘭 𝘢 𝘭𝘰𝘵 𝘮𝘰𝘳𝘦 𝘦𝘮𝘣𝘢𝘳𝘳𝘢𝘴𝘴𝘦𝘥 𝘪𝘧 𝘺𝘰𝘶 𝘧𝘢𝘪𝘭 𝘢𝘯𝘥 𝘵𝘩𝘦𝘳𝘦𝘧𝘰𝘳𝘦 𝘪𝘯𝘤𝘦𝘯𝘵𝘪𝘷𝘪𝘻𝘦𝘥 𝘵𝘰 𝘴𝘶𝘤𝘤𝘦𝘦𝘥) I sincerely hope that helps.	UNKNOWN	Brian	Jenney	18,348	18,348	199	31	0	0.012535	null	2022-08-12 08:41:51	https://www.linkedin.com/feed/update/urn:li:activity:6963876871511883777
urn:li:activity:6963500115219140609	LinkedIn Sucks. It’s full of: - self aggrandizing sales people - toxic positivity - recruiters who only serve to ghost you - crying ceos - and other crying people apparently 🤔 (seriously, I feel bad for dude at this point) It’s also full of: - strangers willing to lend you a hand - quality content you can learn from - inspiring stories - opportunity LinkedIn, like most social media platforms, will do its best to feed you content it believes you will like. If your LI feed sucks, maybe follow some better people. Here's a list of people I follow and get a lot of value from: 𝘌𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨 𝘙𝘦𝘭𝘢𝘵𝘦𝘥 Adrian 🔵 Bogdan Jason Adam Kyle Simpson (duh) Alex Xu (system design) 𝘌𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨 𝘊𝘢𝘳𝘦𝘦𝘳 𝘈𝘥𝘷𝘪𝘤𝘦 Andy Wong (spicy yet hilarious) Alex Chiou && Rahul Pandey Erik Andersen 𝘐𝘯𝘴𝘱𝘪𝘳𝘢𝘵𝘪𝘰𝘯 𝘢𝘯𝘥 𝘉𝘳𝘢𝘯𝘥𝘪𝘯𝘨 Dan Koe Justin Welsh Definitely forgot some people but this list of authors teaches, entertains and inspires. If you want more pics of crying CEO's just keep scrolling LI for the next 2 - 3 days 😉.	UNKNOWN	Brian	Jenney	106,142	106,142	476	83	7	0.005332	null	2022-08-11 07:34:00	https://www.linkedin.com/feed/update/urn:li:activity:6963500115219140609
urn:li:activity:6963142107372912641	I had 95 brainstorm sessions with developers in the last 3 months. Some were FAANG employees and others had just graduated from bootcamps. Not more than 3 of them said they felt ready to: - interview - leave their current job - write that post - publish that article - ask for that promotion Stop waiting for the right time. You’re never going to feel ready. Do it anyways.	UNKNOWN	Brian	Jenney	3,565	3,565	42	7	0	0.013745	null	2022-08-10 07:46:58	https://www.linkedin.com/feed/update/urn:li:activity:6963142107372912641
urn:li:activity:6962780381527875584	My number 1 rule for creating a good side project? Build it as if you were going to sell it. In the last 8 years I’ve only had 3 side projects (not counting all the half finished projects from Udemy tutorials I followed… RIP) I unsuccessfully tried to turn each of these ideas into businesses. Each failed a little less miserably than the last. So what was the benefit? - successfully switched tech stacks to ReactJS and Node/Express (𝘸𝘩𝘪𝘤𝘩 𝘐 𝘩𝘢𝘥 𝘯𝘦𝘷𝘦𝘳 𝘶𝘴𝘦𝘥 𝘱𝘳𝘰𝘧𝘦𝘴𝘴𝘪𝘰𝘯𝘢𝘭𝘭𝘺) -met other talented developers and product people who worked with me on these projects (𝘴𝘰𝘮𝘦 𝘰𝘧 𝘸𝘩𝘰𝘮 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘸𝘦𝘯𝘵 𝘰𝘯 𝘵𝘰 𝘤𝘳𝘦𝘢𝘵𝘦 𝘴𝘶𝘤𝘤𝘦𝘴𝘴𝘧𝘶𝘭 𝘣𝘶𝘴𝘪𝘯𝘦𝘴𝘴𝘦𝘴) -learned enough devops to be dangerous and the basics of AWS (𝘭𝘢𝘮𝘣𝘥𝘢𝘴, 𝘦𝘤2, 𝘤𝘭𝘰𝘶𝘥𝘸𝘢𝘵𝘤𝘩…) -got my first taste of sales (𝘤𝘰𝘭𝘥 𝘤𝘢𝘭𝘭𝘪𝘯𝘨 𝘪𝘴 𝘱𝘦𝘳𝘩𝘢𝘱𝘴 𝘮𝘰𝘳𝘦 𝘯𝘦𝘳𝘷𝘦-𝘸𝘳𝘢𝘤𝘬𝘪𝘯𝘨 𝘵𝘩𝘢𝘯 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸𝘪𝘯𝘨) - finally understood CORS - but I forgot already… next side project I know there are a lot of early career devs reading this - what’s a side project you’d recommend for them to really spread their wings?	UNKNOWN	Brian	Jenney	6,487	6,487	56	11	0	0.010328	null	2022-08-09 07:50:52	https://www.linkedin.com/feed/update/urn:li:activity:6962780381527875584
urn:li:activity:6962406860205285376	The junior developer with 7 years experience. His resume looked impressive. The interview though… oof. How was it possible, this seasoned developer didn’t understand even the most basic JS concepts like: - array iteration methods (𝘮𝘢𝘱, 𝘧𝘪𝘭𝘵𝘦𝘳, 𝘳𝘦𝘥𝘶𝘤𝘦) - the difference between const and let - async/await pattern I was genuinely curious how he had survived this long as a front end developer. Turns out, most of his experience was at the same company, using a very dated tech stack. I now understood how he got to be senior. He was a senior at that particular company in that particular role. I’m sure he knew that codebase inside and out. For all intents and purposes however, he was very junior. I wanted to pull him to the side and tell him to study Javascript fundamentals, learn its modern syntax and do a side project using React or any modern framework so he would be a viable candidate. I regret not giving him that feedback so I’m sharing it here in the hopes you avoid a similar fate. Your current job and tech stack may not prepare you for the future. That is ultimately up to you.	UNKNOWN	Brian	Jenney	140,882	140,882	1,009	129	52	0.008447	null	2022-08-08 07:03:46	https://www.linkedin.com/feed/update/urn:li:activity:6962406860205285376
urn:li:activity:6961331812698640384	Preparing for front end interviews is easy. 1. Study JS trivia… including obscure stuff. Why does NaN ≠= NaN for example? 2. If the job says framework agnostic - study ReactJS (when they say front end they really meant ReactJS 😉) 3. Throw in some random algo prep as well - to be safe just do like 500 LeetCodes 4. Pray to Ecma International's TC39 committee for good measure (sacrifice recommended though not required) Easy right? Since I like you, I have a short list of some of the most common concepts you’re likely to encounter in the front end interview: https://lnkd.in/gW7QxXyT If you like that sort of material - check out my weekly newsletter. 1 freakin' tip each week to help you progress as a developer: https://lnkd.in/gTQC3KUh	ARTICLE	Brian	Jenney	11,263	11,263	70	7	9	0.007636	null	2022-08-05 08:10:57	https://www.linkedin.com/feed/update/urn:li:activity:6961331812698640384
urn:li:activity:6960957368738201600	Worst interview trend? The take home challenge that’s supposed to be an hour or 2 but really takes the whole day. As a junior developer without a lot of options, doing these challenges may be unavoidable. Writing sorta good code won’t do much to make you stand out either. You’d be shocked how far a unit test or 2 can go in making your project stand out and make the difference between an onsite interview and another rejection. One of the devs I mentored had this exact same experience. The company where he ultimately landed a job explicitly told him that the tests he added were one of the reasons he was invited to the final round. If your bootcamp did not cover unit testing (common theme) - check out my unit testing course in the comments section. It covers Jest, react-testing-library and generally how to approach beginner → non-trivial test cases in small ReactJS apps. Also, because I like you, here's a video I made a while ago to introduce you to Jest and write your first unit test. https://lnkd.in/g684tqyD And of course the react-testing-library docs: https://lnkd.in/guYxRdMb You say you don’t have time to write tests? I’d argue you don’t have time NOT to write tests.	UNKNOWN	Brian	Jenney	11,687	11,687	85	31	0	0.009926	null	2022-08-04 07:04:08	https://www.linkedin.com/feed/update/urn:li:activity:6960957368738201600
urn:li:activity:6960591911497715713	Some uncomfortable truths for software engineers: - You, not your company, is ultimately responsible for your growth as a developer - You may be really good at writing code but if you’re unpleasant to work with you will have a hard time getting promoted - Shipping code fast is almost always better than shipping code perfect - Say something in a meeting… anything. A bad idea to kick off a conversation is better than silence - If you don't negotiate your salary - you're probably leaving a lot of money on the table - It’s hard to sell refactoring efforts to the business… do it anyways, just don’t make it super obvious - Your first job will validate you - your second will get you paid - Switching jobs is the easiest way to increase your salary What would you add?	UNKNOWN	Brian	Jenney	22,359	22,359	194	36	8	0.010644	null	2022-08-03 06:56:10	https://www.linkedin.com/feed/update/urn:li:activity:6960591911497715713
urn:li:activity:6960292423121993728	#juniordeveloper, As I am searching for my next role, I go through a certain process when trying to find my next great role. Here it is: I apply to positions where I meet at least 65%ish of the job description (JD). If it is a junior or “entry-level” role I apply. There are two options that will occur once you apply, that I know of you either get to the next step or rejection. If I get the fun old rejection email, I just delete it and keep going. (I became desensitized to rejection emails because I am not the right flavor for every company, and I know that. I like Half Baked from Ben and Jerry’s doesn’t mean everyone will.) Oh yeah, I also send emails or LinkedIn messages to the recruiters/hiring managers. Some people don’t like it and others have really liked it. (ex. I have met people who said don’t DM them and I have met great people who have helped my growth.) If I’m not getting to the screening calls for at least 1/6 jobs I am applying for especially if I am meeting more than 75% of the JD. I would address my resume, the questions should be asked when looking at my resume such as: Am I portraying myself as a #developer/SWE? Am I discussing what I am capable of or what I can do? Is my resume grammatically correct? How does the format of my resume look? If I am getting to screening calls and not making the next round, then I would ask myself did I portray that I am capable of doing this job, and if am I asking the right questions. One of the many questions I have used as of late is, “From our call, my resume, and experience as a junior, would this team be accepting of a #juniorengineer?” If I make it to the technical screen. This is where I am being tested to see if I am able to prove I can program for this company. I could confidently say this, the technical screens I have not passed I have had a 100% SUCCESS rate of NOT making it to the next round. 😂 Whether ds&a, #javascript topics, trees, etc. It is tough to study for and know all these at least to me, at this point in my career, so I decided to spend more time working on javascript because understanding the basis is better than becoming great at ds&a when I did not know what closure, prototypical inheritance, promise, etc. My values are different on my journey than others so I can’t say what is important to each person. Thank you for this Brian. Upon getting passed these steps in the virtual on-site, which varies per company but ensuring that I am doing my best on the #technical round, and speaking to the product team, and hiring manager. If I don’t make it passed this area, I reach out and ask for feedback because I want to know where I came up short and how I can improve. If I make it passed all these SUCCESSFULLY, I would hope to get an offer. Always be your authentic self, it's tough to wear a mask all the time. After our call, I decided to post Louis! I also track my processes with https://lnkd.in/gAN6q2ui Thank you Teal for creating this great Software.	ARTICLE	Brian	Jenney	264	264	29	8	1	0.143939	#juniordeveloper,,#developer/,#juniorengineer?,#javascript ,#technical	2022-08-02 11:11:35	https://www.linkedin.com/feed/update/urn:li:activity:6960292423121993728
urn:li:activity:6960236288679542784	Your technical skills will get you hired. Your leadership skills and influence will get you promoted. How can you expand your influence on a software engineering team? - Write great peer reviews (𝘶𝘴𝘦 𝘵𝘩𝘦𝘴𝘦 𝘢𝘴 𝘢𝘯 𝘰𝘱𝘱𝘰𝘳𝘵𝘶𝘯𝘪𝘵𝘺 𝘵𝘰 𝘵𝘦𝘢𝘤𝘩 𝘢𝘯𝘥 𝘴𝘩𝘢𝘳𝘦 𝘬𝘯𝘰𝘸𝘭𝘦𝘥𝘨𝘦) - Onboard new members (𝘵𝘦𝘢𝘤𝘩𝘪𝘯𝘨 𝘰𝘵𝘩𝘦𝘳𝘴 𝘪𝘴 𝘱𝘳𝘰𝘣𝘢𝘣𝘭𝘺 𝘵𝘩𝘦 𝘣𝘦𝘴𝘵 𝘸𝘢𝘺 𝘵𝘰 𝘴𝘰𝘭𝘪𝘥𝘪𝘧𝘺 𝘺𝘰𝘶𝘳 𝘰𝘸𝘯 𝘬𝘯𝘰𝘸𝘭𝘦𝘥𝘨𝘦) - Introduce new processes that make work easier (𝘦𝘷𝘦𝘯 𝘴𝘮𝘢𝘭𝘭 𝘰𝘯𝘦𝘴 𝘭𝘪𝘬𝘦 𝘪𝘮𝘱𝘳𝘰𝘷𝘪𝘯𝘨 𝘵𝘩𝘦 𝘗𝘙 𝘱𝘳𝘰𝘤𝘦𝘴𝘴) - Solve critical issues (𝘳𝘢𝘪𝘴𝘦 𝘺𝘰𝘶𝘳 𝘩𝘢𝘯𝘥 𝘯𝘦𝘹𝘵 𝘵𝘪𝘮𝘦 𝘢 𝘣𝘶𝘨 𝘱𝘰𝘱𝘴 𝘶𝘱 𝘪𝘯 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘪𝘰𝘯) - Offer ideas and be open to discussion (𝘢 𝘣𝘢𝘥 𝘪𝘥𝘦𝘢 𝘪𝘯 𝘢 𝘴𝘪𝘭𝘦𝘯𝘵 𝘮𝘦𝘦𝘵𝘪𝘯𝘨 𝘤𝘢𝘯 𝘴𝘱𝘶𝘳 𝘢 𝘣𝘦𝘵𝘵𝘦𝘳 𝘪𝘥𝘦𝘢... 𝘴𝘢𝘺 𝘴𝘰𝘮𝘦𝘵𝘩𝘪𝘯𝘨 𝘸𝘩𝘦𝘯 𝘰𝘵𝘩𝘦𝘳𝘴 𝘴𝘢𝘺 𝘯𝘰𝘵𝘩𝘪𝘯𝘨) - Give others praise in public (𝘪𝘵'𝘴 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵 𝘵𝘩𝘪𝘯𝘨 𝘵𝘰 𝘥𝘰 𝘢𝘯𝘥 𝘸𝘪𝘭𝘭 𝘳𝘢𝘪𝘴𝘦 𝘵𝘦𝘢𝘮 𝘮𝘰𝘳𝘢𝘭𝘦) Obviously, having the technical skills needed to perform at an average → above average level in relation to your title is paramount. I mean, you need to know how to code. There is a lot more to being a mid-level or senior developer than coding alone, however. What are other ways you've seen to expand your influence and improve an engineering team?	UNKNOWN	Brian	Jenney	6,041	6,041	63	6	2	0.011753	null	2022-08-02 07:23:20	https://www.linkedin.com/feed/update/urn:li:activity:6960236288679542784
urn:li:activity:6959860412615970816	I was trying to BS my way through an interview when the interviewer cut me short. Thank God. “I don’t think really think this is a good use of our time.” He was right and honestly I was relieved. The job was for a NodeJS position and at the time I had never used it 🤫. I was new to tech and thought if I just strung together enough buzzwords I could get past this part of the interview. My benevolent interviewer saved us both some time and embarrassment and cut the interview short. He even gave me some pointers on how to learn NodeJS. Thanks random interviewer dude! So, what did I learn from this encounter? 𝘐𝘵’𝘴 𝘖𝘒 𝘵𝘰 𝘴𝘢𝘺 𝘺𝘰𝘶 𝘥𝘰𝘯’𝘵 𝘬𝘯𝘰𝘸… 𝘺𝘦𝘵. There is a limit to everyone’s technical depth. What will instill more confidence and trust between you and your team is when you can confidently admit you don’t quite know something and how you plan to learn it later.	UNKNOWN	Brian	Jenney	7,481	7,481	52	12	2	0.008822	null	2022-08-01 06:30:37	https://www.linkedin.com/feed/update/urn:li:activity:6959860412615970816
urn:li:activity:6958828417853140992	A mentee in my program had 10 interviews this week! I asked him: “Out of all these these interviews, how many trees did you have to traverse? How many linked lists did you reverse? How many graphs got Djikstra’d? He thought for a while… “Maybe 1” Experience has taught me that unless you are FAANG bound, studying only DSA for front end dev roles will leave you unprepared for the interview (not to mention the job). I was still a bit shocked though. Perhaps you are too. I’m not saying to burn your “Cracking the Coding Interview” book just yet. I am saying, be realistic and practical with how you are preparing. This Saturday I’ll be sharing 4 of the most common scenarios/questions you will encounter as a front end developer. You can grab them by signing up here: https://lnkd.in/gTQC3KUh	UNKNOWN	Brian	Jenney	8,271	8,271	52	19	0	0.008584	null	2022-07-29 10:11:42	https://www.linkedin.com/feed/update/urn:li:activity:6958828417853140992
urn:li:activity:6958427811560783872	The average number of interviews before getting a job offer is 2–3. I’m gonna bully you into interviewing until you give in. Seriously, I want you to realize that failing an interview… or 5 is the price of entry to a new career or a new role. I’m not asking you to get over the fear. I’m asking you to accept it and do it anyways. Not sold? Try this: 𝘚𝘤𝘩𝘦𝘥𝘶𝘭𝘦 𝘢𝘯 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸 𝘧𝘰𝘳 𝘢 𝘤𝘰𝘮𝘱𝘢𝘯𝘺 𝘺𝘰𝘶’𝘳𝘦 𝘯𝘰𝘵 𝘴𝘶𝘱𝘦𝘳 𝘦𝘹𝘤𝘪𝘵𝘦𝘥 𝘢𝘣𝘰𝘶𝘵 𝘢𝘯𝘥 𝘦𝘹𝘱𝘦𝘤𝘵 𝘵𝘰 𝘧𝘢𝘪𝘭. Seriously, count on failing. 𝘈𝘧𝘵𝘦𝘳 𝘺𝘰𝘶𝘳 𝘯𝘦𝘳𝘷𝘦𝘴 𝘩𝘢𝘷𝘦 𝘴𝘦𝘵𝘵𝘭𝘦𝘥, 𝘢𝘯𝘢𝘭𝘺𝘻𝘦 𝘵𝘩𝘦 𝘪𝘯𝘵𝘦𝘳𝘷𝘪𝘦𝘸. Were there questions you were asked that you feel you should know? A challenge you didn’t even know how to approach? Good. Learn that thing. Repeat a couple times without long breaks in between. 𝘞𝘦 𝘧𝘦𝘢𝘳 𝘵𝘩𝘦 𝘶𝘯𝘧𝘢𝘮𝘪𝘭𝘪𝘢𝘳. Make interviewing more familiar and less of a novelty. If you’re super neurotic like me and need a gentler introduction to interviewing, 𝘵𝘳𝘺 𝘢𝘯𝘴𝘸𝘦𝘳𝘪𝘯𝘨 𝘵𝘩𝘦 𝘧𝘰𝘭𝘭𝘰𝘸𝘪𝘯𝘨 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘴 𝘸𝘩𝘪𝘭𝘦 𝘳𝘦𝘤𝘰𝘳𝘥𝘪𝘯𝘨 𝘺𝘰𝘶𝘳𝘴𝘦𝘭𝘧 𝘶𝘴𝘪𝘯𝘨 𝘢 𝘵𝘰𝘰𝘭 𝘭𝘪𝘬𝘦 𝘓𝘰𝘰𝘮: - Explain closure - Explain promises to a non-technical audience - Explain HTTP verbs to a non-technical audience - Explain why React is so much better than Vue 😉 Good luck!	UNKNOWN	Brian	Jenney	8,388	8,388	73	22	0	0.011326	null	2022-07-28 07:43:02	https://www.linkedin.com/feed/update/urn:li:activity:6958427811560783872
urn:li:activity:6958056356805296128	There are 5 types of front-end interviews you’re going to encounter as a JS developer: - Build a component that fetches some data from an API and displays it - Extend the functionality from your take home app - JS trivia including closure, this, event loop, event queue and promises - Debug this broken app (usually React) and make some unit tests pass - Create some app/game without using a framework 😅 Anything I missed? #softwareengineering #coding #juniordeveloper #frontenddeveloper #javascript	UNKNOWN	Brian	Jenney	15,058	15,058	147	16	2	0.010958	#softwareengineering ,#coding ,#juniordeveloper ,#frontenddeveloper ,#javascript	2022-07-27 06:59:18	https://www.linkedin.com/feed/update/urn:li:activity:6958056356805296128
urn:li:activity:6957700485545918464	There’s more in common with getting in shape and learning to code than you might think. Both teach: Growth mindset - our body, like our mind is not fixed or limited. Humility - there is always somebody better than you. Learning a new programming language or lifting a larger weight will keep you humble. Delayed gratification - if you stick with either endeavor you will see long term benefits and fulfillment. No one is judging you (as much as you think) - people are focused on themselves, not you. We’re all looking in the actual mirror or the proverbial mirror at ourselves for the most part. Age limits don’t exist - despite what you may think - the gym, like the software industry is not controlled by 20 somethings and as long as you’re breathing, its a good time to get in shape or learn a new skill. For all you gym rat coders out there, what are some similarities I missed?	UNKNOWN	Brian	Jenney	7,651	7,651	71	19	2	0.012025	null	2022-07-26 07:25:57	https://www.linkedin.com/feed/update/urn:li:activity:6957700485545918464
urn:li:activity:6957320804585922560	Spicy advice: don’t highlight the fact you are a junior developer. Market yourself as a developer - drop “junior” or “aspiring” from your profile. Why would a potential employer need to know this? If anything, it gives them another mental hurdle to clear before even meeting you to assess your junior-ness. They think, hmmm, should I take a chance on this aspiring developer? Would you hire an aspiring doctor? A junior doctor perhaps? 🧐 Highlight your accomplishments, projects and what you have to offer… as a software developer. Thoughts? #softwaredeveloper #juniordeveloper #engineering #frontenddeveloper #bootcamp #techjobs	UNKNOWN	Brian	Jenney	18,371	18,371	147	42	8	0.010723	#softwaredeveloper ,#juniordeveloper ,#engineering ,#frontenddeveloper ,#bootcamp ,#techjobs	2022-07-25 06:16:08	https://www.linkedin.com/feed/update/urn:li:activity:6957320804585922560
urn:li:activity:6956625045288873984	Last week I sent out a challenge to a few hundred developers: Basically, create a form, with NO framework and have it handle some events and conditions. I give this same challenge to the developers I work with in my mentoring program. Some people fly through it while others struggle… a lot. It can be eye opening. The intention is to identify their core Javascript knowledge and simulate a pretty common interview scenario. No judgment, simply a way for me to know where we should begin focusing. If you find yourself struggling with this challenge, it’s likely a sign you should re-visit some JS fundamentals. A couple brave people submitted their answer and allowed me to share it. Manvi Jain is one of those brave souls (who was also brave enough to share her LinkedIn 😅). Here's her solution: https://lnkd.in/gYF96BdG If you’re interested - you can check out the challenge here: https://lnkd.in/gsWfuTBx	ARTICLE	Brian	Jenney	5,834	5,834	54	5	1	0.010285	null	2022-07-23 08:27:32	https://www.linkedin.com/feed/update/urn:li:activity:6956625045288873984
urn:li:activity:6956255332922785792	Could there be a worse time to learn to code? I’d been sober for a couple months, had a newborn and a small child to take care of and was doing ride share part time. It wasn’t like I was some computer whiz either. I didn’t own a computer through college or as an adult. I had just discovered Codecademy.com and was basically tinkering around trying to kill my boredom at work 🤫. After nearly a year of creating janky websites and learning enough Jquery to be dangerous, I was quite proud of myself. Maybe I can be an email developer, I thought. I was nowhere near ready to apply for a job but I had a mentor who pushed me. He actually sat me down and basically forced me to apply to companies. I got hired. In a full stack role, no less. I was also terrible. I didn’t even know what I didn’t know. I wrote a 100 line if/else statement. A quadruple nested for loop with some asynchronous actions…. I know. I know. I started the process of filling the gaps in my knowledge. I hired mentors. I left a trail of semi-finished Udemy videos in my wake. I asked embarrassing questions. I got incrementally better. Thank Bob I took that mentor’s advice and got started. Without that push, I'd probably still be spinning in circles, waiting for that perfect moment to apply... or worse, just gave up. Now I feel a lot more confident in my coding skills. Outside of work I mentor and speak with developers who deal with a lot of the same issues I faced. I've had about 100 conversations with devs from all over the world in the last 3 months. I honestly don’t think I’ve spoken with more than 3 of them who said they felt ready to: - interview - leave their current job - write that post - publish that article - ask for that promotion Stop waiting for the right time. You’re never going to feel ready. Do it anyways.	UNKNOWN	Brian	Jenney	6,352	6,352	78	16	4	0.015428	null	2022-07-22 07:53:15	https://www.linkedin.com/feed/update/urn:li:activity:6956255332922785792
urn:li:activity:6955904056154296321	Despite my best efforts, I can’t stop you front end devs from grinding the LeetCodes. I mean, I kinda get it. If nothing else, it will build your confidence and teach you some important fundamentals. Studying 100 representative problems just isn’t enough though. You need to be able to find patterns. When do you DFS rather than BFS? When should you use a linked list? Should this array be searched… binar-ily? Here is a non-exhaustive list of the concepts which will give you the power to solve nearly any damn LeetCode problem: Sorting and Searching Algos: - Binary search, merge sort, quick sort Trees (pre-req before recursion, or at least a good intro): - Binary Trees, N-ary trees, BFS, DFS, inorder, preorder, postorder Recursion: - Permutations, backtracking, combinations, factorials Graphs: - BFS, DFS, Adjacency List, Edge List, Edge Matrix Linked Lists (I guess…) Dynamic Programming: - Pray and think how can you use an array… Nearly all LeetCode-esque problems you come across leverage one or more of these data structures or concepts. Now it becomes a game of mix and match. Anything I missed?	UNKNOWN	Brian	Jenney	10,158	10,158	72	30	3	0.010337	null	2022-07-21 08:26:30	https://www.linkedin.com/feed/update/urn:li:activity:6955904056154296321
urn:li:activity:6955149189651591168	What most aspiring developers do: - Build 100 small trivial apps - Chase shiny frameworks - Follow paint by numbers tutorials - Marathon study/coding sessions - 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	33,660	33,660	326	41	14	0.011319	null	2022-07-19 06:34:13	https://www.linkedin.com/feed/update/urn:li:activity:6955149189651591168
urn:li:activity:6954779775349522432	Are you a framework developer? I was. For quite a while actually. So what does that mean exactly? Well, for me that meant that I lacked a lot of the core fundamentals needed to understand Javascript. The framework, AngularJS at the time, was an abstraction I didn’t just leverage but depended on to be useful. I didn’t know JS so much as I knew AngularJS (RIP). What changed? Well, once I moved companies, frameworks and teams, I quickly realized how little I knew. I went back to the drawing board, enrolled in a bootcamp while being employed as a developer and read books that my co-workers recommended. I built stuff and broke stuff. Now, I mentor other JS developers and one of the first assignments we do is an exercise to create a form that submits some data to a placeholder API. No framework allowed! I sent this challenge out to around 400 people on Saturday. Check it out here: https://lnkd.in/gsWfuTBx I can promise you will find this either: a. incredibly simple b. eye-openingly difficult to complete No judgement or shame here. I’m curious, which camp do you fall under? #javascript #frontenddevelopment #juniordeveloper #vanillajs	UNKNOWN	Brian	Jenney	12,403	12,403	77	15	4	0.00774	#javascript ,#frontenddevelopment ,#juniordeveloper ,#vanillajs	2022-07-18 06:14:15	https://www.linkedin.com/feed/update/urn:li:activity:6954779775349522432
urn:li:activity:6953716193186783232	How did our team adopt a culture of unit testing and go from 0 front end tests -> ~50% coverage? Slowly at first. Of course, there were some myths to expose: - We don’t have time - Our front end apps aren’t that complex - Isn’t that what QA is for? - Is it really worth it? After overcoming some of the initial apprehension, we saw the benefits: - We were empowered to refactor complex components without fear of breaking original functionality - Tests doubled as documentation for new developers - We were more confident in the quality of our code and releases - We could release code more frequently Some developers took to testing immediately while others weren’t sold. So we: - Set a testing threshold in our pipeline - Created videos and short tutorials on unit testing - Used code coverage tools to ensure we were testing what we thought If you’re new to unit testing and want to learn I’m excited to share a course I’ve created which includes source code, videos, articles and most importantly challenges to teach you unit testing and testing ReactJS components. It’s all the stuff I wish I had learned when I started and it will shorten your path to unit testing proficiency with real world applications. It’s 19.99 right now and if you happen to be in a difficult financial situation or from a country where $20 might be a significant expense, please DM me for a very super secret special discount code 😉. https://lnkd.in/gWbv4peB #reactjs #javascript #unittesting #unittest #juniordeveloper	ARTICLE	Brian	Jenney	2,449	2,449	18	3	2	0.009392	#reactjs ,#javascript ,#unittesting ,#unittest ,#juniordeveloper	2022-07-15 07:42:36	https://www.linkedin.com/feed/update/urn:li:activity:6953716193186783232
urn:li:activity:6953338613422055424	I don’t think there’s anything wrong with copying and pasting code from Stack Overflow. We all do it. I DO think there is something wrong if you copy and paste code which you don’t understand. It works! Yeah, but how? What happens when it breaks? Imagine a doctor, cutting a patient apart and inserting a foreign object. Patient wakes up, cured from what has been ailing them. '"Doctor, how did you cure me?" "Not really sure, kinda stuck something in there and it just worked - lol" "… 😧" "See ya in 6 months, let’s see how this turns out!"	UNKNOWN	Brian	Jenney	3,429	3,429	24	15	2	0.011957	null	2022-07-14 06:26:06	https://www.linkedin.com/feed/update/urn:li:activity:6953338613422055424
urn:li:activity:6953085302638850048	So recently I was working with a developer who is at the tail end of a 6 month long bootcamp. They were working on a full stack app using a pretty standard tech stack including AWS, Node/Express, MongoDB and ReactJS. We were digging into an issue with an API call. The arguments were sent in a shape that the API did not expect. Simple fix overall. There was just a small problem. They didn’t quite understand the syntax or general logic for adding key-value pairs to an object. I know you want to study ReactJS. NextJS. AWS. All the things that end in S. Before you dive too far into those things though, it’s probably worth auditing your basic JS knowledge and having a solid grip on: - loops - arrays - objects I actually have a small challenge I give to the developers I mentor to assess some of their basic JS knowledge. I’ll share a slimmed down version of it this Saturday in my newsletter if you're interested.	UNKNOWN	Brian	Jenney	19,388	19,388	177	38	2	0.011192	null	2022-07-13 13:48:51	https://www.linkedin.com/feed/update/urn:li:activity:6953085302638850048
urn:li:activity:6952983140780974080	When my code didn’t work Beginner me: - Blamed the user - Tried it on my machine… look it works - Blamed the previous dev - I don't usually use this language - I hate this framework Not so beginner me: - Ooh, I really messed up something #softwareengineer #juniordeveloper #javascript #techcareer	UNKNOWN	Brian	Jenney	5,658	5,658	47	6	0	0.009367	#softwareengineer ,#juniordeveloper ,#javascript ,#techcareer	2022-07-13 07:12:23	https://www.linkedin.com/feed/update/urn:li:activity:6952983140780974080
urn:li:activity:6952611952896458752	Only half of programming is coding. The other 90% is debugging. 🤔 Debugging JS code in the browser is fairly straightforward: Debuggers, console logs… hitting refresh and praying. Investigating bugs in a Node/ExpressJS presents a different set of challenges however since you can’t leverage the browser API. So you’re stuck with logging…. praying. Or are you? If you’re using VSCode (because of course you are) - check out this how-to-guide on debugging Node/Express projects I shared with 300 others: https://lnkd.in/gqE6hmVD Want 1 lesson, tip or piece of advice related to JavaScript delivered to your inbox every Saturday morning? Shoot me your email here: https://lnkd.in/gTQC3KUh #javascript #coding #software #nodejs #juniordeveloper	UNKNOWN	Brian	Jenney	9,329	9,329	68	12	1	0.008683	#javascript ,#coding ,#software ,#nodejs ,#juniordeveloper	2022-07-12 06:19:45	https://www.linkedin.com/feed/update/urn:li:activity:6952611952896458752
urn:li:activity:6952612012027785217	Only half of programming is coding. The other 90% is debugging. 🤔 Debugging JS code in the browser is fairly straightforward: Debuggers, console logs… hitting refresh and praying. Investigating bugs in a Node/ExpressJS presents a different set of challenges however since you can’t leverage the browser API. So you’re stuck with logging…. praying. Or are you? If you’re using VSCode (because of course you are) - check out this how-to-guide on debugging Node/Express projects I shared with 300 others: https://lnkd.in/gqE6hmVD Want 1 lesson, tip or piece of advice related to JavaScript delivered to your inbox every Saturday morning? Shoot me your email here: https://lnkd.in/gTQC3KUh #javascript #coding #software #nodejs #juniordeveloper	UNKNOWN	Brian	Jenney	3,889	3,889	9	0	0	0.002314	#javascript ,#coding ,#software ,#nodejs ,#juniordeveloper	2022-07-12 06:19:45	https://www.linkedin.com/feed/update/urn:li:activity:6952612012027785217
urn:li:activity:6952251499368378368	Me, somewhere shady in Oakland, CA as a teen. Spitting raps as my friend, the famous, inimitable Kali worked the boards. Software engineer? I didn’t even know what the hell they did back then. I wanted to be a rapper, and no, I will not share my rap moniker 😅. If I had known about coding back then would I have been interested? I dunno. I learned to code around 30 and it’s like a light bulb went off in my head. It was the most fulfilling hobby I had ever started. Even more than spitting profanity-laced raps. I speak to too many people who think life ends at 25. Or 30. Or 40. Am I too old to code, they ask? I sure hope not. There’s still time. When did you learn to code?	IMAGE	Brian	Jenney	7,104	7,104	90	34	0	0.017455	null	2022-07-11 06:30:42	https://www.linkedin.com/feed/update/urn:li:activity:6952251499368378368
urn:li:activity:6951196201304150016	Still using 128 console logs in your code to debug #javascript code? There’s a better way my friend: I’m actually a little shocked more developers aren’t aware of the debugger keyword or how to set breakpoints in their code. For me, this technique has saved me during some gnarly on-call shifts and helped me to diagnose and triage critical bugs. Here’s a video going over some debugging techniques I use that I hope you find useful: #frontenddeveloper #juniordeveloper #debugging	EXTERNAL_VIDEO	Brian	Jenney	5,942	5,942	61	16	4	0.013632	#javascript ,#frontenddeveloper ,#juniordeveloper ,#debugging	2022-07-08 08:51:06	https://www.linkedin.com/feed/update/urn:li:activity:6951196201304150016
urn:li:activity:6951196455604801538	Still using 128 console logs in your code to debug #javascript code? There’s a better way my friend: I’m actually a little shocked more developers aren’t aware of the debugger keyword or how to set breakpoints in their code. For me, this technique has saved me during some gnarly on-call shifts and helped me to diagnose and triage critical bugs. Here’s a video going over some debugging techniques I use that I hope you find useful: #frontenddeveloper #juniordeveloper #debugging	EXTERNAL_VIDEO	Brian	Jenney	139	139	1	1	0	0.014388	#javascript ,#frontenddeveloper ,#juniordeveloper ,#debugging	2022-07-08 08:51:06	https://www.linkedin.com/feed/update/urn:li:activity:6951196455604801538
urn:li:activity:6950438189044039680	At the end of an interview, inevitably, they ask - So, do you have any questions? The worst questions I’ve heard: - Nah. - When will I know if I got the job? - How did I do? Seriously. Here are my favorite 5 questions to ask at the end of an interview: - Can you walk me through your deployment process? - What is your team’s testing philosophy? - What is the on-call process? - What is your favorite part of working here? - What is one process you would change? These questions usually lead to interesting conversations, give me some insight into the engineering culture and a more honest take on what it’s like to actually work there. What’s your go to question?	UNKNOWN	Brian	Jenney	44,708	44,708	277	49	9	0.007493	null	2022-07-06 06:27:15	https://www.linkedin.com/feed/update/urn:li:activity:6950438189044039680
urn:li:activity:6950072176314118145	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 - Code editor shortcuts and commands - 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! I’ve always wanted to create a course to help first year developers survive and thrive after getting hired. Anything I missed on this list that you wished you had learned before starting your first role as a developer? #juniordeveloper #softwareengineer #javascript	UNKNOWN	Brian	Jenney	31,677	31,677	286	33	2	0.010134	#juniordeveloper ,#softwareengineer ,#javascript	2022-07-05 06:21:38	https://www.linkedin.com/feed/update/urn:li:activity:6950072176314118145
urn:li:activity:6948628861576257537	When I talk to junior developers, there are a couple concepts I consistently hear that confuse or intimidate the majority of them: 1. Redux 2. Webpack Each of these technologies took me a long time to wrap my head around. The learning curve is steep. I know there are a lot of alternatives to them too. Zustand, Snowpack, Recoil, Rollup, whatever framework just came out today... So why learn them? They are so widely used that you will almost certainly come across in your career.... especially if you are working on the front end. Don't be intimidated. Learn the main concepts, integrate them into a small app and get your hands dirty and you'll gain confidence and practical skills. #juniordeveloper #javascript #reduxjs #softwareengineer	UNKNOWN	Brian	Jenney	22,419	22,419	125	34	1	0.007137	#juniordeveloper ,#javascript ,#reduxjs ,#softwareengineer	2022-07-01 06:35:01	https://www.linkedin.com/feed/update/urn:li:activity:6948628861576257537
urn:li:activity:6948628910796419074	When I talk to junior developers, there are a couple concepts I consistently hear that confuse or intimidate the majority of them: 1. Redux 2. Webpack Each of these technologies took me a long time to wrap my head around. The learning curve is steep. I know there are a lot of alternatives to them too. Zustand, Snowpack, Recoil, Rollup, whatever framework just came out today... So why learn them? They are so widely used that you will almost certainly come across in your career.... especially if you are working on the front end. Don't be intimidated. Learn the main concepts, integrate them into a small app and get your hands dirty and you'll gain confidence and practical skills. #juniordeveloper #javascript #reduxjs #softwareengineer	UNKNOWN	Brian	Jenney	1,964	1,964	3	0	0	0.001527	#juniordeveloper ,#javascript ,#reduxjs ,#softwareengineer	2022-07-01 06:35:01	https://www.linkedin.com/feed/update/urn:li:activity:6948628910796419074
urn:li:activity:6948303324311937024	You ever bought a used car? If so, did you pay the exact price listed in the ad? Or did you haggle a bit? Was there an implicit expectation when the author of the ad wrote “OBO” (or best offer) that the final price would be lower than the asking? Think of salary negotiations the same way. With few exceptions, the initial offer has room for haggling. You just might not know that. There is no “OBO” in the description. It was silent.	UNKNOWN	Brian	Jenney	1,898	1,898	12	0	0	0.006322	null	2022-06-30 08:57:50	https://www.linkedin.com/feed/update/urn:li:activity:6948303324311937024
urn:li:activity:6947971984479703040	Ever sit down to pair with someone and they have zero control of their code editor? That was me for longer than I'd like to admit 😅 Years ago, one very senior developer politely asked me to get a better hang on using my code editor before we paired again. It was a bit embarrassing for me as I had been using VS Code for a few months before this incident. He seemed to fly around at light speed and use techniques I didn't even know existed. I wanted to be like him. He was kind enough to write a lot of these commands down for me and I've shared them here:	ARTICLE	Brian	Jenney	3,044	3,044	34	0	3	0.012155	null	2022-06-29 11:10:22	https://www.linkedin.com/feed/update/urn:li:activity:6947971984479703040
urn:li:activity:6947889633871478784	Maybe you’re afraid of posting on LinkedIn… honestly, me too sometimes. What will they think? Do I know enough? 1. Who cares 2. Yes, you do Give others that are just behind you the benefit of your experience. You may have some insight to shorten their path towards their goal or at least something they can relate to. At a basic level, we are humans, looking for connections, to be educated or entertained. Or both. Not concrete enough for you? Ok fine, check out this What to Post on LinkedIn Cheatsheet that I hope gets your gears turning	ARTICLE	Brian	Jenney	971	971	8	0	0	0.008239	null	2022-06-29 05:43:01	https://www.linkedin.com/feed/update/urn:li:activity:6947889633871478784
urn:li:activity:6947177075401261057	My interview tech stack for front end interviews: - Pramp.com for live practice with a human (FREE) - AlgoExpert's frontendexpert.io for practical JS problems - Alex Xu's books and more recently ByteByteGo for system design - Glassdoor and teamblind.com for company research - Blind 75 https://lnkd.in/guEs9s5V - My last minute cheat sheet for JS interviews https://lnkd.in/gN8rtJFm Good luck... and happy studying.	ARTICLE	Brian	Jenney	5,351	5,351	68	0	13	0.015137	null	2022-06-27 06:48:01	https://www.linkedin.com/feed/update/urn:li:activity:6947177075401261057
urn:li:activity:6946832408197427200	I get on here and write a lot about code and career advice to attract customers and hopefully offer some insight that may help you on your JS journey. I typically shy away from current topics or any political discourse but in case you were wondering or cared - I support a woman's rights to choose what she does with her body. - I support women who don't want to have abortions - I support women who want to have abortions - I support your right to have an opinion different than my own What I don't support is other people regulating a private matter and what a woman can and can't do with her body.	UNKNOWN	Brian	Jenney	3,277	3,277	27	0	0	0.008239	null	2022-06-26 07:38:37	https://www.linkedin.com/feed/update/urn:li:activity:6946832408197427200
urn:li:activity:6946104401946185728	Forget good advice. Ever had some really good criticism? Lord knows I have. And it’s not always fun… in fact it’s never fun. It can be embarrassing. Crushing. It can also be incredibly useful. A catalyst for growth. Here are the most impactful criticisms I’ve received over the years as a software engineer: - You don’t have a fundamental understanding of some core JS concepts - it makes it hard to work with you. - Speak up during meetings. You don’t say much. - This peer review missed some glaring bugs and is now holding up a major release. Let’s make sure that doesn’t happen again. - Think bigger. The organization is larger than our team. Could some of these criticisms been delivered in a nicer way? Sure. Am I glad they weren’t? Absolutely. We all want praise but what we really need oftentimes is critical feedback.	UNKNOWN	Brian	Jenney	2,211	2,211	17	5	0	0.00995	null	2022-06-24 07:19:21	https://www.linkedin.com/feed/update/urn:li:activity:6946104401946185728
urn:li:activity:6945346696256118784	I’ll be honest - I don’t think I’ve ever fully made it through a Udemy coding course. I’m not bashing Udemy either. I’ve gotten a lot out of these half-finished tutorials. In fact, I’ve intentionally not finished many of them. At worst, a Udemy course can be a paint-by-numbers exercise. They code, you watch and then copy. Turn off the video and open your editor and you realize you have no f*ckin clue how to replicate what you just learned. Here’s my method: - Watch the course until I understand just enough to get started and get the necessary source code - Extend the functionality of the paint by numbers exercise (for example for a CRUD app I might add a new endpoint or for a React app I may update the routing logic to add a new page) - Now, with my base app I will go completely off the rails and keep extending and adding little features - essentially using it as a starting point for a side project - As I get stuck, I will go back the course and look for any relevant information to get unstuck Going through the motions !== understanding.	UNKNOWN	Brian	Jenney	6,641	6,641	83	10	1	0.014154	null	2022-06-22 05:13:28	https://www.linkedin.com/feed/update/urn:li:activity:6945346696256118784
urn:li:activity:6944985944257159168	Habits > Goal setting. Try habit stacking. About 8 years ago I stopped drinking and realized I had a lot of time on my hands and a couple decades worth of bad habits. I started coding. About an hour or so a day before work. More on the weekends. Got hired. Realized I kinda sucked at writing code. Picked up reading as a habit. Nothing major, just 15 - 30 minutes a night before I went to sleep. Read lots of books on coding (and a lot of awful mystery novels). Asked for recommendations from co-workers I admired. Got kinda fat from not being poor. Made exercise a daily habit. Now here I am, in the midst of making writing on LI another habit. Ok, give me yours - what’s one habit you’re stacking this year?	UNKNOWN	Brian	Jenney	5,852	5,852	52	19	0	0.012133	null	2022-06-21 05:33:26	https://www.linkedin.com/feed/update/urn:li:activity:6944985944257159168
urn:li:activity:6944441029102100480	You’re not going to learn recursion from memorizing Fibonacci toy problems. Recursion is notoriously difficult for developers to understand and has tanked me in more than a few interviews. While doing the phone screen for Meta, years ago, I was given a challenge to take a string that contains only digits and an integer target, and return all possibilities to insert the operators '+', '-', and/or '*' between the digits in the string so that the resultant expression evaluates to the target value. Jeez, it’s confusing even writing that. I didn’t even attempt the problem. I politely admitted defeat and saved us from a very awkward interview. I spent a lot of money and time learning recursion after that debacle. Everyone will have a different model for recursion and making it “click”. Here’s me walking through a moderately difficult problem using recursion and thinking out loud in real time 👇 - hope that’s helpful.	EXTERNAL_VIDEO	Brian	Jenney	2,590	2,590	20	8	0	0.010811	null	2022-06-19 17:21:33	https://www.linkedin.com/feed/update/urn:li:activity:6944441029102100480
urn:li:activity:6943954226846846976	Instead of learning solutions of LeetCode questions, understand patterns! 🙂 For ex. If input array is sorted then - Binary search - Two pointers If asked for all permutations/subsets then - Backtracking If given a tree then - DFS - BFS If given a graph then - DFS - BFS If given a linked list then - Two pointers If recursion is banned then - Stack If must solve in-place then - Swap corresponding values - Store one or more different values in the same pointer If asked for maximum/minimum subarray/subset/options then - Dynamic programming If asked for top/least K items then - Heap If asked for common strings then - Map - Trie Else - Map/Set for O(1) time & O(n) space - Sort input for O(nlogn) time and O(1) space Thank you creator for this. 🙏	UNKNOWN	Brian	Jenney	148	148	4,113	200	159	30.216216	null	2022-06-18 09:05:14	https://www.linkedin.com/feed/update/urn:li:activity:6943954226846846976
urn:li:activity:6943560172212551680	Ex drug dealer. Ex convict. Ex cashier. I’ve met people from each group who now work as developers, scientists and in higher education. Funny thing is, you wouldn’t know from looking at their LinkedIn profile that they have amazing and often salacious stories. In fact they often go to great lengths to hide this part of their history. I understand. There are parts of my past that I’m not proud of. Long parts in fact. Just know that you are likely not unique. Whatever you’ve gone through does not exclude you from being a developer, a scientist, an ex-whatever.	UNKNOWN	Brian	Jenney	6,191	6,191	90	4	1	0.015345	null	2022-06-17 06:56:05	https://www.linkedin.com/feed/update/urn:li:activity:6943560172212551680
urn:li:activity:6943192562941775872	99% of bootcamp grads I see make these same mistakes: - Letting their GitHub contributions nosedive immediately after graduating - Waiting too long to interview or letting that first rejection stop their interview momentum - Not writing code on a daily basis Too much reliance on structured learning. Not enough consistency.	UNKNOWN	Brian	Jenney	39,883	39,883	400	45	17	0.011584	null	2022-06-16 06:31:43	https://www.linkedin.com/feed/update/urn:li:activity:6943192562941775872
urn:li:activity:6942826043846144000	Unit tests? We just don’t have the time. Now let’s manually test these 10 separate scenarios. Oh and these edge cases. Rats! Not quite right yet. I think we’re not checking the condition when a user is only partially logged in… or partially logged out…. partially. 🤔 Looks like we need to re-check all those scenarios again once you figure out that weird scenario. You see, we simply just don’t have time to write unit tests! If your team struggles to find time to write unit tests… it’s probably a sign you need to make time for unit tests. Want to learn unit testing but not sure where to start? Check out these videos 👇 Intro to Jest: https://lnkd.in/g684tqyD Testing Async Methods: https://lnkd.in/gfyTAnRz Testing Callbacks and Using Mocks: https://lnkd.in/gEdDXQcB Source Code: https://lnkd.in/ganZJQSw https://lnkd.in/g8Pz7ivi	EXTERNAL_VIDEO	Brian	Jenney	2,235	2,235	29	1	0	0.013423	null	2022-06-15 06:50:03	https://www.linkedin.com/feed/update/urn:li:activity:6942826043846144000
urn:li:activity:6942104667275370496	Spoke to around 20 developers this month who are having trouble with interviewing or feeling stuck in their career. From FAANG engineers to those just getting started. Here are 5 lessons I learned from these 20 calls: 1. Everyone suffers from impostor syndrome. Yes, even the FAANG engineers. 2. Closure comes up a lot in JS interviews so be prepared. 3. 100 Devs is an amazing FREE program and if you’re learning to code I’d check it out. 4. Not enough bootcamps teach unit testing. 5. No one really feels ready to interview. If you’re reading this, take it as a sign you should start anyway, learn from that experience and re-calibrate. Hope that's helpful.	UNKNOWN	Brian	Jenney	53,059	53,059	460	33	11	0.009499	null	2022-06-13 06:45:21	https://www.linkedin.com/feed/update/urn:li:activity:6942104667275370496
urn:li:activity:6940657639580200960	Writing code as a profession certainly isn’t all flexibility, big bags and unlimited vacation. The stress is real. At one company, we had a particularly stressful on-call rotation which included frequent 5AM PagerDuty alerts and more than a couple sleepless nights to fix critical issues. Ask any developer for a horror story about a bug they created and you won’t be disappointed. Personally, I’ve caused more than a few embarrassing bugs and fixed too many to count at this point. Making show-stopping bugs certainly isn’t relegated to junior developers either. Think about outages at Meta, AWS or whatever 3rd party service your company currently uses. When these apps go down, who do you think is dripping in sweat over their keyboards to fix it? This isn’t meant to discourage you but it certainly may explain (in part) why the salaries for this kind of work are higher than average. Anyone have a good on call horror story?	UNKNOWN	Brian	Jenney	2,241	2,241	22	0	1	0.010263	null	2022-06-09 06:43:43	https://www.linkedin.com/feed/update/urn:li:activity:6940657639580200960
urn:li:activity:6940293535397007360	What’s the biggest difference between the developers I’ve met who were hired and those who weren’t? I think about this pretty often and over the years I’ve worked with well over 100 developers while teaching at bootcamps or via 1 on 1 mentoring (link in my about section 😉). I was shocked to see some under-performers get hired quickly and those who were technically strong take a longer time. I’ve followed up with a lot of these same developers. The biggest difference? Some let the rejection get to them. They quit or they waited until they were “ready”. A lot of them are still waiting. The ones who succeeded learned from their failures and pushed past the fear and insecurity. They basically just didn’t stop.	UNKNOWN	Brian	Jenney	7,188	7,188	66	20	2	0.012243	null	2022-06-08 06:42:19	https://www.linkedin.com/feed/update/urn:li:activity:6940293535397007360
urn:li:activity:6939925410533031936	I can think of 2 straightforward ways to have your take-home-assessment project stand out: Write unit tests Write a solid README that includes a recording of you walking through the functionality (I personally like to use Loom) I am not a fan of the take home project-as-interview - they are too time consuming for the most part. If you’re going to spend a significant time on these projects, why not give yourself the best chance possible?	UNKNOWN	Brian	Jenney	2,448	2,448	23	7	0	0.012255	null	2022-06-07 06:09:21	https://www.linkedin.com/feed/update/urn:li:activity:6939925410533031936
urn:li:activity:6938231487758561280	Haven't we all felt like this? Am I the only one who doesn't know [x]? I can't speak about [y] - I might sound like a fool. [z] person probably knows this way better than I do. Besides his amazing books on JS - one of the most impactful takeaways from Kyle Simpson for me, has been to learn in public, admit when I don't know something and re-frame what it means to be an impostor. The term, and general feeling, of being an impostor is not unique and was especially detrimental to my career and perhaps yours as well.. how can you learn or grow if you're afraid to admit the gaps in your knowledge or wait until you've mastered something to share your thoughts on it? Once I learned to expose my ignorance and learn publicly, I saw a lot more growth as a software engineer. I'm still learning to be comfortable doing this honestly. At each new step, comes a new set of impostor-y feelings. He's made this manifesto and pledge (which you can sign) below which I'm really digging 👇🏽	ARTICLE	Brian	Jenney	716	716	5	0	0	0.006983	null	2022-06-02 13:54:52	https://www.linkedin.com/feed/update/urn:li:activity:6938231487758561280
urn:li:activity:6938130868976705537	One of the developers I mentor just landed his dream role! A not-so-suprising takeaway from his experience going through the interview process: Writing unit tests can make you stand out. For his take home project, he added unit tests to a ReactJS app as well as the backend. The interviewers mentioned the fact he included tests in his app. It impressed them, especially because so few people bother to do it. Oh, and in case you were wondering, for this full stack role and the half dozen others he applied for - 0 DSA!. Not 1. The opposite of some. For those that I mentor, we focus on JS fundamentals, design patterns, writing unit tests and technical communication… as well as DSA! It’s awesome to see someone I work with not only nail the interview but land a role at a company they truly wanted. Warms my cold heart. If you’re having trouble with your interview strategy or have yet to write your first unit test 😅 you should grab a few mins on my calendar (it’s in my about section) to chat about what’s holding you back.	UNKNOWN	Brian	Jenney	5,109	5,109	61	9	0	0.013701	null	2022-06-02 07:15:03	https://www.linkedin.com/feed/update/urn:li:activity:6938130868976705537
urn:li:activity:6937750629243138048	My biggest fear when interviewing? Maybe yours too. I walk into the room. White board just sitting there, looking all smug. Interviewer strolls in, carbonated water in hand. Asks question I have NO freaking clue how to answer. He sits there, bewildered. “You mean to tell me you don’t know [this thing you should know]?” Slams carbonated beverage on the table. Stands up. “You call yourself a developer?!” “You sir, are a charlatan!” Interviewer walks out. I silently erase my answer from the whiteboard. After around 100 interviews , I’ve learned there is no way to prepare for every question you can be asked. I’ve waved the white flag more than a few times. I’ve also never had the scenario above happen to me, despite having some pretty awful answers. This unfounded fear is something I’ve yet to fully overcome and I sincerely hope you don’t let made up scenarios like this prevent you from stepping into the ring. Am I just super neurotic or do you feel me?	UNKNOWN	Brian	Jenney	6,210	6,210	32	19	1	0.008374	null	2022-06-01 06:04:07	https://www.linkedin.com/feed/update/urn:li:activity:6937750629243138048
urn:li:activity:6937034502087065601	Recursion as a lazy guy in a movie theatre: Lazy guy wants to know how many rows are in front of him. He’s smart - but lazy. He knows that he is 1 row further back than the guy in front of him. A light bulb goes off. He asks the lazy guy in front of him how many rows are in front of him. This guy is also pretty lazy. He asks the guy in front of him - using the same logic as above (1 + the amount of rows in front of the guy in front of him). Eventually this game of telephone reaches a man in the second row. 1 guy in front of me he replies. This sets off a chain of lazy bastards relaying this information. Finally it reaches the second-laziest man at the top. “8 guys in front of me, see” (this is an old-time-y theatre) The initial requestor simply adds 1 to the number of people in front of the lazy man who is sitting in front of him. 9. He sits back, satisfied. The movie begins. Everyone has a different mental model for understanding recursion. Mine is a lazy man in a theatre. What’s yours?	UNKNOWN	Brian	Jenney	9,422	9,422	65	11	5	0.008597	null	2022-05-30 06:38:29	https://www.linkedin.com/feed/update/urn:li:activity:6937034502087065601
urn:li:activity:6936038412118351872	Will you use DS/A on the job? Probably not. Should you learn it anyway? Yeah. As a late bloomer coder from a very non-tech background (I didn't own a laptop until well into my mid 20's) - algos and data structures intimidated the hell out of me. I spent money, time and lots of effort to get proficient. What did I get out of it? Confidence, mostly. And a much better grasp on the underlying patterns and concepts which make up the software ecosystem, which in turn improved my code quality. But mostly... confidence. Anyways, don't let LeetCode scare you. Even though I rag on it a bit here and there - it's a great place to strengthen your coding skills (or improve you chances in the FAANG Hunger Games). Also - here's me walking through a DP problem using a common problem solving technique which I hope you find helpful. I know recursion and DP problems are often perceived as intimidating and they don't have to be. It's been a rough week. When life gets tough I do DP problems... cuz I'm a masochist.	EXTERNAL_VIDEO	Brian	Jenney	1,873	1,873	23	4	0	0.014415	null	2022-05-27 12:40:22	https://www.linkedin.com/feed/update/urn:li:activity:6936038412118351872
urn:li:activity:6935275704871792640	Today just feels weird. In a really awful way. I drop my kids off at school. At work, coding. As usual, I've retreated to my code hole. My little logical universe. A layer of insulation from a world which seems increasingly more volatile, unpredictable. Back to back massacres in different parts of the US just weeks apart. What's most concerning is how much our collective tolerance seems to have grown in response to these tragedies. Is there any limit? Any tragedy too great? What will be the catalyst to enact some actual, tangible change? I don't know how much more love or support we can send to parents and communities who have had their souls ripped from them in such cruel ways.	UNKNOWN	Brian	Jenney	2,353	2,353	17	4	0	0.008925	null	2022-05-25 10:09:39	https://www.linkedin.com/feed/update/urn:li:activity:6935275704871792640
urn:li:activity:6935222839948062721	How did I become a Senior Software Engineer? Well, I kinda just asked. I mean, I also got offered a role at another company at a senior level. I was at mid-level during this time. I spoke to my manager and let him know I would be leaving for greener pastures. Wait? What? Aren’t you happy here? Well, yeah, I replied. But, you know… 💰📈 Why didn’t you just ask? Uhhh, well… honestly never thought about it like that. I was kinda hoping it would just happen. It was lottery mentality thinking on my part. He was right. I should’ve made my goals clear. I could’ve spoken up. I was too nervous to admit that I wanted the senior title and didn’t really have a clue what was required. Be good at coding? Like really good? 🤷‍♀️ What I learned is that getting to senior wasn’t solely about technical skill… here at least (your mileage may vary). I needed to show mentorship capability, influence by making impactful technical decisions and of course have a track record of writing quality code. I really did enjoy where I worked and I ended up staying at that position. We created a roadmap to get me a senior title. I learned a valuable lesson about communication and what was required to get me to the next level as a software engineer in our organization from that experience. Getting from junior -> mid or from mid -> senior shouldn’t be a black box. Don’t make my mistake. Find out what it takes. Ask your manager. Ask for advice from other people in the position you’re after. Identify the gaps in your skills. Execute.	UNKNOWN	Brian	Jenney	9,922	9,922	105	11	1	0.011792	null	2022-05-25 06:39:35	https://www.linkedin.com/feed/update/urn:li:activity:6935222839948062721
urn:li:activity:6934854025058140161	The problem with learning ReactJS before Javascript: So here I was, doing a mock interview and the interviewee is attempting to implement the publish subscriber pattern. No framework. Just plain old JS. To their surprise, useState was not available within a Javascript object… oops. The majority of the interview was spent going over the basics of JS objects. Key-value pairs. Dot notation. Context. You know, table stakes JS stuff. I felt their pain. I started my Javascript career off with AngularJS and Jquery. I thought because I knew the framework, I knew JS. It took me years to return back to the fundamentals and really double down on the concepts that were holding me back. I’m not saying don’t learn frameworks. They are a very useful abstraction to create apps. Just don’t forget to build your house of knowledge on a solid foundation.	UNKNOWN	Brian	Jenney	463	463	4	0	0	0.008639	null	2022-05-24 06:14:02	https://www.linkedin.com/feed/update/urn:li:activity:6934854025058140161

Subsets and Splits

No community queries yet

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