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:7155236339934773248	Let me save you 90 hours of watch time from the Udemy Course you bought at the beginning of the year. Between tutorial hell and your own side project is 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗽𝘂𝗿𝗴𝗮𝘁𝗼𝗿𝘆. The awkward phase when you’re not quite ready to create a complex side project but aren’t getting much out of following along with a video. Here’s how you limit your stay here: - 𝗗𝗼𝗻’𝘁 𝗲𝗾𝘂𝗮𝘁𝗲 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝘄𝗶𝘁𝗵 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗶𝗼𝗻 - there is no Gold Star for finishing a 100 hour course - Gain enough knowledge to be dangerous - 𝗘𝘅𝘁𝗲𝗻𝗱, 𝗯𝗿𝗲𝗮𝗸 𝗼𝗿 𝗿𝗲-𝘄𝗿𝗶𝘁𝗲 𝗮 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 from the tutorial - Write detailed comments about what is happening in the code and why Now you have a project that is similar to the tutorial but NOT exactly like it and you’ve removed the training wheels from your learning exercise. I break down a method I call the 𝗰𝗮𝘁𝗲𝗿𝗽𝗶𝗹𝗹𝗮𝗿 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆™️ to learn fast af in the comments.	UNKNOWN	Brian	Jenney	15,639	15,639	105	12	7	0.007929	null	2024-01-22 08:46:03	https://www.linkedin.com/feed/update/urn:li:activity:7155236339934773248
urn:li:activity:7153787160171560960	2 safe bets for what to learn in 2024 as a full stack software engineer: 1. NextJS/Vercel (𝘥𝘶𝘩) 2. Rust I’d go all in on Rust. 𝗠𝘆 𝗯𝗲𝘁 𝗶𝘀 𝘁𝗵𝗮𝘁 𝗶𝘁 𝗾𝘂𝗶𝗰𝗸𝗹𝘆 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝗮 𝗺𝗲𝗴𝗮-𝘁𝗿𝗲𝗻𝗱 in software development. Microsoft is re-writing core Windows libraries with it. AWS also announced that its SDK for Rust is now ready for production. Their are about 128 articles explaining the benefits of 𝗥𝘂𝘀𝘁 𝗳𝗼𝗿 𝘀𝗮𝘃𝗶𝗻𝗴 𝗼𝗻 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗰𝗼𝘀𝘁𝘀. As companies become more cost-conscious I’m betting we’ll see more adoption. Here’s the thing - Rust is a major departure from dev-centric programming languages like Python and JavaScript. 𝗧𝗵𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗰𝘂𝗿𝘃𝗲 𝗶𝘀 𝘀𝘁𝗲𝗲𝗽. 𝗠𝗮𝘆𝗯𝗲 𝘁𝗼𝗼 𝘀𝘁𝗲𝗲𝗽. I think this means opportunity for you. 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝘀𝘁𝘂𝗳𝗳 𝘄𝗵𝗶𝗹𝗲 𝗲𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝗶𝘀 𝗿𝘂𝘀𝗵𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗮 𝗽𝗿𝗼𝗺𝗽𝘁-𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿. Re-write your Node/Express API with Rust and deploy it as an AWS lambda, be at the start of the next mega-trend.	UNKNOWN	Brian	Jenney	63,237	63,237	208	48	11	0.004222	null	2024-01-18 08:56:12	https://www.linkedin.com/feed/update/urn:li:activity:7153787160171560960
urn:li:activity:7153423201056780289	Don't let the fear of looking dumb paralyze you. You'll be forever haunted by "𝘞𝘩𝘺 𝘥𝘪𝘥𝘯’𝘵 𝘐 𝘢𝘴𝘬 𝘵𝘩𝘢𝘵?" The most talented developers I’ve worked with are the first to admit when they don’t know something. Take it from me (𝘸𝘩𝘰’𝘴 𝘴𝘵𝘪𝘭𝘭 𝘳𝘦𝘤𝘰𝘷𝘦𝘳𝘪𝘯𝘨 𝘧𝘳𝘰𝘮 𝘵𝘩𝘪𝘴 𝘴𝘺𝘯𝘥𝘳𝘰𝘮𝘦): - People aren’t as smart as you think - Someone else wants to ask that question too, but they’re just as nervous - If you pretend to understand and don’t - you’ll be exposed sooner or later - Get comfortable being uncomfortable You don't need to know everything to be successful as a developer. You do need to get used to exposing your ignorance in a field that is as wide as it is deep.	UNKNOWN	Brian	Jenney	6,410	6,410	83	21	5	0.017005	null	2024-01-17 08:45:29	https://www.linkedin.com/feed/update/urn:li:activity:7153423201056780289
urn:li:activity:7153061093890813953	Your next technical interview might not be so technical at all. What I’ve learned from working with dozens of developers last year on the interview grind, is that in addition to having canned answers for explaining: - closure - promises - the difference between bind, call and apply 𝗬𝗼𝘂 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗵𝗮𝘃𝗲 𝗮𝗻𝘀𝘄𝗲𝗿𝘀 𝗳𝗼𝗿 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗹𝗶𝗸𝗲: - tell me about a challenging project you’ve worked on - how do you resolve conflicts with team mates? - here’s a website we made, how can we improve it (how do you measure the performance of a webpage basically?) - 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	11,279	11,279	92	19	4	0.010196	null	2024-01-16 08:54:37	https://www.linkedin.com/feed/update/urn:li:activity:7153061093890813953
urn:li:activity:7152688403967295488	“𝘊𝘢𝘳𝘦𝘦𝘳 𝘤𝘩𝘢𝘯𝘨𝘦 𝘪𝘴 𝘢 𝘤𝘰𝘮𝘱𝘭𝘦𝘵𝘦𝘭𝘺 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘨𝘢𝘮𝘦 𝘧𝘳𝘰𝘮 𝘭𝘦𝘢𝘳𝘯𝘪𝘯𝘨 𝘵𝘰 𝘤𝘰𝘥𝘦. 𝘓𝘦𝘢𝘳𝘯𝘪𝘯𝘨 𝘵𝘰 𝘤𝘰𝘥𝘦 𝘪𝘴 𝘵𝘩𝘦 𝘰𝘣𝘷𝘪𝘰𝘶𝘴 𝘱𝘢𝘳𝘵.𝘐𝘵'𝘴 𝘵𝘩𝘦 𝘵𝘪𝘤𝘬𝘦𝘵 𝘵𝘰 𝘵𝘩𝘦 𝘥𝘢𝘯𝘤𝘦.” - 𝘡𝘶𝘣𝘪𝘯 I sat down with Zubin Pratap, a former lawyer who switched careers into tech at 37 then got hired at Google and now mentors developers in addition to being a full time software engineer. Zubin breaks down: - the reality of switching careers and why the tech industry isn’t as unique as I thought - how he beat the Google interview - his controversial take on the education business - why you need to ruthlessly prune your social media following Link in comments.	VIDEO	Brian	Jenney	4,902	4,902	52	12	2	0.013464	null	2024-01-15 07:59:32	https://www.linkedin.com/feed/update/urn:li:activity:7152688403967295488
urn:li:activity:7151992660340232192	Terminal commands saved our internship program yesterday. Here's enough Vim to be dangerous: 𝗢𝗽𝗲𝗻 𝗮 𝗳𝗶𝗹𝗲: 𝚟𝚒𝚖 𝚏𝚒𝚕𝚎𝚗𝚊𝚖𝚎 𝗘𝘅𝗶𝘁 𝗩𝗶𝗺: Press Esc then type :𝚚 and press Enter (If you've made changes, add an exclamation mark to force quit without saving: :𝚚!) 𝗦𝗮𝘃𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀: Press Esc then type :𝚠 and press Enter 𝗦𝗮𝘃𝗲 𝗮𝗻𝗱 𝗲𝘅𝗶𝘁: Press Esc then type :𝚠𝚚 or 𝚉𝚉 and press Enter 𝚒: Enter insert mode to 𝘀𝘁𝗮𝗿𝘁 𝗲𝗱𝗶𝘁𝗶𝗻𝗴 𝘁𝗲𝘅𝘁 𝚡 𝗗𝗲𝗹𝗲𝘁𝗲 𝘁𝗵𝗲 𝗰𝗵𝗮𝗿𝗮𝗰𝘁𝗲𝗿 under the cursor 𝚍𝚍: 𝗗𝗲𝗹𝗲𝘁𝗲 𝘁𝗵𝗲 𝘄𝗵𝗼𝗹𝗲 𝗹𝗶𝗻𝗲 𝚞: 𝗨𝗻𝗱𝗼 𝙲𝚝𝚛𝚕 + 𝚛: 𝗥𝗲𝗱𝗼 Yesterday I had to SSH into an server instance on AWS to figure out how to deploy some code that Parsity grads have been working on through an internship. I realized how often I've had to do tasks like this to troubleshoot issues on remote servers. It can be stressful. Without knowing some basic terminal commands, it's really stressful. Our grads jumped into this codebase made by contractors who we have no contact with. Ruh roh. 𝗜 𝘄𝗼𝗻𝗱𝗲𝗿𝗲𝗱 𝗵𝗼𝘄 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲 𝘄𝗮𝘀 𝗯𝗲𝗶𝗻𝗴 𝗱𝗲𝗽𝗹𝗼𝘆𝗲𝗱 𝘁𝗼 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿. Turns out, the original developer would SSH into the box, pull down the code from GitHub and then restart the server manually. No judgment... except of course I am. The only way I figured that out was to investigate their bash history by doing: 𝚌𝚊𝚝 ~/.𝚋𝚊𝚜𝚑_𝚑𝚒𝚜𝚝𝚘𝚛𝚢 Now I could see the evil genius at work here and why our app was crashing. I made a code change on the fly and the work our grads created was now LIVE. 𝘖𝘩 𝘺𝘦𝘢𝘩, 𝘥𝘰𝘯'𝘵 𝘥𝘦𝘱𝘭𝘰𝘺 𝘰𝘯 𝘍𝘳𝘪𝘥𝘢𝘺𝘴. 𝗧𝗟𝗗𝗥; learn some terminal commands. Learn some vim. It won't suck and you'll look way cooler when you're at the coffee shop working on that SAAS app.	UNKNOWN	Brian	Jenney	7,065	7,065	55	14	0	0.009766	null	2024-01-13 09:56:02	https://www.linkedin.com/feed/update/urn:li:activity:7151992660340232192
urn:li:activity:7151619954801295360	I’ve gone too far down the YouTube tech rabbit hole. Apparently: - coding is a waste of time - you can learn JS in 100 minutes - no one is hiring - cyber security is the only safe bet - JS sucks - learn Python! - Python sucks - learn JS! - AI will replace everyone in 420 days 𝗠𝗲𝗮𝗻𝘄𝗵𝗶𝗹𝗲, 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝘄𝗼𝗿𝗹𝗱: - developers are getting hired - interviews still suck - MERN/SERN is boring and popular - I’ve been learning JS for 10 years… I messed up apparently YouTube/IG/X/LinkedIn ≠ Real life	UNKNOWN	Brian	Jenney	14,502	14,502	202	27	6	0.016205	null	2024-01-12 09:42:38	https://www.linkedin.com/feed/update/urn:li:activity:7151619954801295360
urn:li:activity:7151297452803809280	𝘞𝘢𝘪𝘵, 𝘺𝘰𝘶'𝘳𝘦 𝘣𝘭𝘢𝘤𝘬? I have an interesting background: I'm half black, never really met my white family and get mistaken for everything except for what I am, which has led to so many interesting conversations over the years 😅 Anywho, 𝗜'𝗹𝗹 𝗯𝗲 𝘀𝗽𝗲𝗮𝗸𝗶𝗻𝗴 𝗮𝘁 𝘁𝗵𝗲 𝗡𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗦𝗼𝗰𝗶𝗲𝘁𝘆 𝗼𝗳 𝗕𝗹𝗮𝗰𝗸 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 this evening in case you were wondering how me and my bald head got invited. Obviously, everyone is welcome and I'm looking forward to hearing from the other speakers (one of whom I've been following on X for a while now) as well as talking about all the mistakes I've made in my career... and some of the stuff I got right along the way.	UNKNOWN	Brian	Jenney	3,132	3,132	31	7	0	0.012133	null	2024-01-11 12:06:02	https://www.linkedin.com/feed/update/urn:li:activity:7151297452803809280
urn:li:activity:7151239024110657536	Last year I helped over a dozen software engineers land their first role or their next one. Here’s what I learned: - 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝘄𝗼𝗿𝗸𝘀. 𝗖𝗼𝗹𝗱 𝗮𝗽𝗽𝗹𝘆𝗶𝗻𝗴 𝘄𝗼𝗿𝗸𝘀. Do both. - 𝗕𝗲𝗶𝗻𝗴 𝗹𝗶𝗸𝗲-𝗮𝗯𝗹𝗲 𝗶𝘀 𝗺𝗼𝗿𝗲 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘁𝗵𝗮𝗻 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸. Do some mock interviews or record yourself solving a problem. Would you hire you? - 𝗝𝘂𝗻𝗶𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗔𝗥𝗘 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗵𝗶𝗿𝗲𝗱 but less companies are explicitly recruiting for them. - 𝗦𝗻𝗲𝗮𝗸 𝗶𝗻 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝗮𝗻𝗼𝘁𝗵𝗲𝗿 𝗱𝗼𝗼𝗿. QA, DevOps and Product can be a better fit and leverage your coding skills. - 𝗗𝗦𝗔 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗮𝗿𝗲 𝗹𝗲𝘀𝘀 𝗹𝗶𝗸𝗲𝗹𝘆 𝘁𝗵𝗮𝗻 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀. You still need basic DSA skills but don't study 500 LC problems. Learn the most common structures and approaches. (𝘐 𝘩𝘢𝘷𝘦 𝘢𝘯 𝘢𝘳𝘵𝘪𝘤𝘭𝘦 𝘰𝘯 𝘵𝘩𝘪𝘴 😎) 𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘁𝗵𝗶𝗻𝗴 𝗜 𝘁𝗼𝗼𝗸 𝗮𝘄𝗮𝘆 𝗳𝗿𝗼𝗺 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗼𝗳 𝘆𝗼𝘂: Your timeline will be different than someone else’s. Luck plays an important role. To be lucky you must be consistent.	UNKNOWN	Brian	Jenney	14,551	14,551	211	17	5	0.016013	null	2024-01-11 08:00:48	https://www.linkedin.com/feed/update/urn:li:activity:7151239024110657536
urn:li:activity:7150148193874288640	The 3 worst parts about being a software engineer: 1. 𝗕𝗲𝗶𝗻𝗴 𝗼𝗻 𝗰𝗮𝗹𝗹 - why does no one talk about this one? When something breaks at 3am on Sunday you may be first in line to figure it out. 2. 𝗞𝗲𝗲𝗽 𝘂𝗽 𝗼𝗿 𝗴𝗲𝘁 𝗹𝗲𝗳𝘁 𝗯𝗲𝗵𝗶𝗻𝗱. Tech moves fast but your company doesn't. Fair or not, you will need to keep up somehow with mega-trends in the industry. 3. 𝗦𝘁𝗿𝗲𝘀𝘀. Deadlines, high expectations and the potential to cause catastrophes from deploying code. (𝘴𝘦𝘦 𝘪𝘵𝘦𝘮 1). To be clear, I still love what I do and so do most devs I know. Between the big bags, flexible schedules and unlimited PTO you hear about is also... reality. Anything you'd add?	UNKNOWN	Brian	Jenney	7,568	7,568	51	20	1	0.009514	null	2024-01-08 07:52:22	https://www.linkedin.com/feed/update/urn:li:activity:7150148193874288640
urn:li:activity:7149084732448804864	You’ll never “know” JS. It’s ok, that’s what it makes it fun… I think 🤔 Did you know there’s a not-so-secret committee that reviews new proposals for JS features and decides if they will be adopted or not? They’re called TC39 and they're one of the reasons you'll never "know" JS. Check out this weird experimental feature, 𝚑𝚊𝚌𝚔-𝚙𝚒𝚙𝚎-𝚘𝚙𝚎𝚛𝚊𝚝𝚘𝚛 which might become a thing in the future but you can use right now with the power of 𝚋𝚊𝚋𝚎𝚕.	VIDEO	Brian	Jenney	4,697	4,697	61	4	0	0.013839	null	2024-01-05 09:19:33	https://www.linkedin.com/feed/update/urn:li:activity:7149084732448804864
urn:li:activity:7148689851716878336	I’ve told you not to use the term “passionate developer” in your profile. I still think you need to be one. In the short time I’ve been coding, web dev and JS has gone through an incredible amount of changes. I started with JQuery, AngularJS and ES5. I even wrote some JScript (look it up). Since then we’ve collectively had to learn: • ReactJS • Serverless • GraphQL • TypeScript • ES6/7/8/9/10/11… • NextJS • Webpack • Jest 🥵 If you don’t find some intrinsic joy in coding, I imagine it’s tough to keep up. Am I off base here? Do you need to enjoy coding to be good at it?	UNKNOWN	Brian	Jenney	8,767	8,767	80	32	1	0.012889	null	2024-01-04 07:29:26	https://www.linkedin.com/feed/update/urn:li:activity:7148689851716878336
urn:li:activity:7148346212247654402	𝗠𝘆 𝘁𝗲𝗰𝗵 𝘀𝘁𝗮𝗰𝗸 𝗳𝗼𝗿 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗶𝗻 𝟮𝟬𝟮𝟯: Create-React-App GraphQL Cypress AWS CSS Modules 𝗠𝘆 𝘁𝗲𝗰𝗵 𝘀𝘁𝗮𝗰𝗸 𝗳𝗼𝗿 𝗺𝘆 𝗻𝗲𝘅𝘁 𝗳𝗮𝗶𝗹𝗲𝗱 𝘀𝘁𝗮𝗿𝘁𝘂𝗽 𝗶𝗱𝗲𝗮 𝗶𝗻 𝟮𝟬𝟮𝟰: Typescript NextJS tRPC Playwright Vercel Edge Functions OpenAI API What are you building with this year?	UNKNOWN	Brian	Jenney	5,766	5,766	58	23	0	0.014048	null	2024-01-03 08:50:08	https://www.linkedin.com/feed/update/urn:li:activity:7148346212247654402
urn:li:activity:7147967081869684736	A while ago, I wrote that create-react-app is dead and boy did some people get upset. Lemme double down... NextJS is our future as React devs. Ignore it at your own peril. There are really only 2 trends I am watching in 2024 as a web dev: 1. NextJS 2. AI AI is gonna AI. I’m not on the existential crisis team… yet. I do see a proliferation of “AI” startups which basically wrap around OpenAI’s API. For this reason, I think you should spend 10 bucks for some tokens on the Open AI dev platform and experiment with fine tuning and working with their API. Since I like you, I’ve done some of the heavy lifting for you and you can 𝗰𝗵𝗲𝗰𝗸 𝗼𝘂𝘁 𝗺𝘆 𝗔𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗿 𝗸𝗶𝘁 𝘂𝘀𝗶𝗻𝗴 𝗡𝗼𝗱𝗲/𝗘𝘅𝗽𝗿𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗵𝗲 𝗢𝗽𝗲𝗻𝗔𝗜 𝗔𝗣𝗜 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀 𝗯𝗲𝗹𝗼𝘄. If you use this to make a startup that destroys humanity please don’t forget to credit me and mail me a box of donuts or something.	UNKNOWN	Brian	Jenney	16,599	16,599	149	29	3	0.010904	null	2024-01-02 07:53:38	https://www.linkedin.com/feed/update/urn:li:activity:7147967081869684736
urn:li:activity:7146145521089327104	We get it, networking is important. But what the hell does that mean? Especially on a platform like LinkedIn? Well, I can certainly tell you what it’s not: - DMs to strangers asking to look at your resume - Posts romanticizing a string of rejections - Messages to connections you’ve never spoken to, asking for referrals So what do you do? - Genuine engagement with other people by commenting on their posts - DMs where you give first (a link to a helpful article for example) - Posts that share what you’re learning (and struggling with) I break down a strategy to build and grow on LinkedIn without becoming a mini-influencer you can listen to here: https://lnkd.in/gjR-AEtk	VIDEO	Brian	Jenney	6,553	6,553	89	18	3	0.016786	null	2023-12-28 06:39:45	https://www.linkedin.com/feed/update/urn:li:activity:7146145521089327104
urn:li:activity:7145805558749511680	I’ll turn 40 in a couple days. This last decade started off pretty rough for me. Here’s the timeline: 𝗘𝗮𝗿𝗹𝘆 𝟯𝟬𝘀 - Friend dies, his brother (and my business partner) sentenced to prison - Had new baby - a boy 🐣 - Quit dabbling in the streets and got a legal job - Mom and girlfriend do an intervention. Got sober cold turkey 🦃 - Drive Lyft/Uber and meet software engineers - Hmm, I’m bored lemme try coding to pass time 👨‍💻 - Switch addictions to coding and candy - Learn HTML/CSS/Jquery - first coding job is C#, SQL and AngularJS 🙄 𝗠𝗶𝗱 𝟯𝟬'𝘀 - One more kid - a daughter this time 🐣 - Got kinda fat from candy and started working out - Finally get a six pack at 37 💪 - Job hop, get monies and learn from smart people and make many mistakes - Buy a few investment properties 🏡 𝗟𝗮𝘁𝗲 𝟯𝟬'𝘀 - Move into management role as a software engineer - Start writing on LI about code stuff - Heart issue almost kills me - consequence of past life - Start business coaching developers and make first dollars online - Purchase first business 😬 I don’t have many lessons to share here. I’m an average person with an above average tolerance for rejection. I’m a stubborn SOB and probably have some unresolved addictive traits which have helped me in certain aspects of life. I’m naive enough to try a lot of things and expect they will work out for me. I’m happily dissatisfied with my progress so far. I share some of these unglamorous parts of my life online because I distinctly remember feeling very alone in the early stages of this transformation. If you’re reading this and going through a rough period I hope you feel a little less alone and realize that there is another life on the other side. It's all possible. There’s more of us out there than you realize and most just don’t talk about it online. You got this.	UNKNOWN	Brian	Jenney	27,136	27,136	366	39	1	0.014962	null	2023-12-27 08:09:30	https://www.linkedin.com/feed/update/urn:li:activity:7145805558749511680
urn:li:activity:7143632860405481472	6 services I've used to improve my skills as a software engineer: 1. AlgoExpert - finally someone made a 𝘀𝗼𝗹𝗶𝗱 𝗼𝗳𝗳𝗲𝗿𝗶𝗻𝗴 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗝𝗦 𝗮𝗻𝗱 𝗥𝗲𝗮𝗰𝘁𝗝𝗦 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 with practical exercises 2. 𝗖𝗼𝗱𝗲𝗖𝗿𝗮𝗳𝘁𝗲𝗿𝘀.𝗶𝗼 - I like this site so much. You 𝗯𝘂𝗶𝗹𝗱 𝗰𝗼𝗺𝗽𝗹𝗲𝘅 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝘁𝗵𝗮𝘁 𝗽𝗮𝘀𝘀𝗲𝘀 tests to see if it works. Addictive. 3. 𝗞𝗶𝗻𝗱𝗹𝗲 - 𝗜 𝗿𝗲𝗮𝗱 𝗯𝗼𝗼𝗸𝘀 𝗳𝗿𝗼𝗺 𝘀𝗺𝗮𝗿𝘁𝗲𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀. I won’t give you a listicle here, there are plenty out there already. (𝘖𝘬 𝘧𝘪𝘯𝘦 - 𝘊𝘭𝘦𝘢𝘯 𝘊𝘰𝘥𝘦 𝘪𝘯 𝘑𝘚, 𝘠𝘋𝘒𝘑𝘚 𝘚𝘦𝘳𝘪𝘦𝘴, 𝘗𝘩𝘰𝘦𝘯𝘪𝘹 𝘗𝘳𝘰𝘫𝘦𝘤𝘵) 4. Plato - when I became a manager I was overwhelmed. I needed 𝗺𝗲𝗻𝘁𝗼𝗿𝘀𝗵𝗶𝗽 and they provided some of the best I could’ve asked for. 5. ByteByteGo - 𝘀𝘆𝘀𝘁𝗲𝗺 𝗱𝗲𝘀𝗶𝗴𝗻 is where it’s at. As coding can increasingly be handled by AI tools, it’s more important than ever to understand the bigger picture. 6. Taro (YC S22) - there aren’t a lot of resources out there for mid and senior level devs. Taro fills in the gap here with 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗰𝗮𝗿𝗲𝗲𝗿 𝗮𝗱𝘃𝗶𝗰𝗲 that I steal from time to time 🤫 Honorable mention to John Crickett who is a person not a service BUT 𝗵𝗲 𝗰𝗿𝗲𝗮𝘁𝗲𝘀 𝗿𝗲𝗮𝗹𝗹𝘆 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗰𝗼𝗱𝗶𝗻𝗴 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀 which you should totally be taking advantage of. Here's 2 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗜 𝗰𝗮𝗻'𝘁 𝘃𝗼𝘂𝗰𝗵 𝗳𝗼𝗿 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹𝗹𝘆 but have heard nothing but good things about 1. Scrimba 2. Frontend Masters No one paid me to write this. I just use these tools and think they’re super lit! Not mid. No cap! (𝘺𝘦𝘴 𝘐'𝘮 𝘵𝘶𝘳𝘯𝘪𝘯𝘨 40 𝘴𝘰𝘰𝘯) Anything out there I missed?	UNKNOWN	Brian	Jenney	78,426	78,426	333	35	28	0.005049	null	2023-12-21 08:29:34	https://www.linkedin.com/feed/update/urn:li:activity:7143632860405481472
urn:li:activity:7143292939710914561	How do you get better at JavaScript and ReactJS? Build stuff 🙄 Not specific enough? Try this: Here are the subjects I struggled with the most and how I learned them through practice: - 𝘗𝘳𝘰𝘮𝘪𝘴𝘦𝘴 - implement 𝙿𝚛𝚘𝚖𝚒𝚜𝚎.𝚊𝚕𝚕 or promise-ify a timeout - 𝘊𝘭𝘰𝘴𝘶𝘳𝘦 - create a function that returns another function that can only be called 1 time - 𝘛𝘩𝘪𝘴 - implement 𝚋𝚒𝚗𝚍 and 𝚌𝚊𝚕𝚕 from scratch by leveraging 𝚊𝚙𝚙𝚕𝚢 - 𝘙𝘦𝘤𝘶𝘳𝘴𝘪𝘰𝘯 - make a function that searches a deeply nested object for a value - 𝘞𝘦𝘣𝘱𝘢𝘤𝘬 - 𝚗𝚙𝚖 𝚎𝚓𝚎𝚌𝚝 create-react-app and analyze the bundle size - 𝘙𝘦𝘥𝘶𝘹 - study the observer pattern and add Redux to a small app using Ducks architecture (look it up 😎) If you’re feeling brave, record a video going over the concept and share it with others so you can spread and reinforce your own knowledge.	UNKNOWN	Brian	Jenney	30,695	30,695	239	17	2	0.008405	null	2023-12-20 09:57:25	https://www.linkedin.com/feed/update/urn:li:activity:7143292939710914561
urn:li:activity:7142921469096841216	Your goals might suck. Now let's make them suck less: ❌ Get hired ✅ Apply to 5 jobs a day and go to 1 meetup a week ❌Scale your business to 6 figures ✅ Book 10 new leads per day ❌Six pack abs ✅ Figure out your TDEE (look it up) and eat 80% of that ❌Learn DSA ✅ Build 6 most commonly used data structures from scratch ❌Learn Rust ✅ Re-build your Node/Express app with Rust Goals are great. Stacking habits to reach those goals make them more likely to become reality.	UNKNOWN	Brian	Jenney	10,403	10,403	132	16	4	0.014611	null	2023-12-19 09:05:24	https://www.linkedin.com/feed/update/urn:li:activity:7142921469096841216
urn:li:activity:7142550411365789696	CTO enters the Slack channel for devs only. Ruh roh. “𝘖𝘶𝘳 𝘢𝘱𝘱 𝘪𝘴𝘯’𝘵 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘢𝘴 𝘦𝘹𝘱𝘦𝘤𝘵𝘦𝘥. 𝘊𝘢𝘯 𝘴𝘰𝘮𝘦𝘰𝘯𝘦 𝘵𝘢𝘬𝘦 𝘢 𝘭𝘰𝘰𝘬?” It was around 12:30AM on a Thursday and I was the only developer on call at this time. I decided to do what any good developer would do at this time and REST: 𝗥eproduce the bug locally. 𝗘xamine the source code. 𝗦et breakpoints. 𝗧est the fix. I go over this method to find and fix bugs which I hope helps you create a repeatable process you can use for debugging and how it actually got me promoted along + a short video for debugging. Listen here 👉 https://lnkd.in/gN2gW-_8	UNKNOWN	Brian	Jenney	11,619	11,619	84	13	3	0.008607	null	2023-12-18 08:32:30	https://www.linkedin.com/feed/update/urn:li:activity:7142550411365789696
urn:li:activity:7141467883083116546	Let me supercharge your debugging process by 420%. I remember scratching my bald head a few years ago at work while trying to debug a Node/Express API with my manager. We had an important demo that day and something was breaking. No pressure 😅. We added no less than 69 console logs in the code with no luck. Luckily, a smart nerd on the team showed us this method which I'm shocked more of you aren't using. Maybe you're like me and didn't know it existed within VS Code. Here's a short video of me breaking down how to debug a Node/Express app using breakpoints just like you might do in your front end code. I mean, you are using 𝚍𝚎𝚋𝚞𝚐𝚐𝚎𝚛 in your JS code right? Right?! Hope it saves you a little hair.	VIDEO	Brian	Jenney	35,818	35,818	244	18	28	0.008096	null	2023-12-15 08:50:48	https://www.linkedin.com/feed/update/urn:li:activity:7141467883083116546
urn:li:activity:7140738096152625153	Not using this software design pattern can cost you. How much exactly? Well - a few months ago a software engineer on here wrote that his team was doing a 6 month refactor to replace a js library for dates that had been deprecated. Oops. To think, if they only used this pattern they could've saved about 5.5 months of time.	ARTICLE	Brian	Jenney	5,577	5,577	39	2	2	0.00771	null	2023-12-13 08:36:14	https://www.linkedin.com/feed/update/urn:li:activity:7140738096152625153
urn:li:activity:7140429737734078464	If you’re reading this post, I’ve made some assumptions about you: 1. You’re a software engineer 2. You have above average intelligence 3. You probably look pretty good (don’t tell HR) I’ve given a lot of advice and now I want yours, you good looking nerd. I recently became the owner of a coding bootcamp, Parsity . Updating the curriculum to include NextJS and Typescript (coming soon) was the fun part, now the real work begins. I know the power of a bootcamp is not just in the knowledge transfer but in getting people hire-able. I’m working on a LinkedIn course that is short, sweet and super actionable to help grads avoid most of the mistakes I’ve seen. 𝗪𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗜 𝘀𝗵𝗼𝘂𝗹𝗱 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗳𝗼𝗿 𝗻𝗲𝘄 𝗴𝗿𝗮𝗱𝘀? - Internships 𝘖𝘙 - Curating open source opportunities What’s your take?	UNKNOWN	Brian	Jenney	11,925	11,925	92	56	6	0.012914	null	2023-12-12 12:19:28	https://www.linkedin.com/feed/update/urn:li:activity:7140429737734078464
urn:li:activity:7139990536186195968	What does Erik Andersen really think about the junior developer job market and learning in public? Do I agree with him? I sat down with the world’s happiest engineer and chatted about: - why LinkedIn is better than X - how to actually get hired in tech - gaining experience as a developer when you have none - his hot takes on coding bootcamps and the developer job market 🥵 I may not agree with all his views but I respect the hell out of him for keeping it real and taking time in between being a tech lead, YouTube content creator and one of my favorite people on LinkedIn to talk with us and you give the kind of practical advice you don’t find often enough. Check out his YouTube channel "The Junior Jobs Podcast" and listen to our convo below. 👉 https://lnkd.in/gSC_D9HN 👈	IMAGE	Brian	Jenney	2,479	2,479	39	5	4	0.019363	null	2023-12-11 06:58:25	https://www.linkedin.com/feed/update/urn:li:activity:7139990536186195968
urn:li:activity:7139022531633565696	While most LinkedIn influencers are selling courses, SAAS apps or bootcamps (I’ve done all 3 don’t hate me 😅) Victor Moreno has launched a kids book on coding. It actually looks really good too.	UNKNOWN	Brian	Jenney	3,368	3,368	36	3	1	0.011876	null	2023-12-08 15:02:26	https://www.linkedin.com/feed/update/urn:li:activity:7139022531633565696
urn:li:activity:7138954727043604480	Learn to code and b̶e̶c̶o̶m̶e̶ ̶a̶ ̶s̶o̶f̶t̶w̶a̶r̶e̶ ̶e̶n̶g̶i̶n̶e̶e̶r̶ • become a product manager • start your own business • do data analysis • become a technical writer • do DevOps • try QA • do whatever the hell else you want Coding is a foundational skill. It can be a destination in itself or the key to another door.	UNKNOWN	Brian	Jenney	54,795	54,795	688	36	55	0.014217	null	2023-12-08 10:33:41	https://www.linkedin.com/feed/update/urn:li:activity:7138954727043604480
urn:li:activity:7138559434850537473	Are you a JavaScript developer or a ReactJS developer? Your job probably depends on you being a solid ReactJS developer. Unfortunately, those same skills don’t necessarily translate to being a proficient JavaScript developer. Last year I did a mock interview with a person who tried to use 𝚞𝚜𝚎𝚂𝚝𝚊𝚝𝚎 while solving a problem that required a pub-sub implementation. Here’s the thing, we were using Vanilla JS. No frameworks or anything. 🥲 I give a challenge to most of the mentees I’ve worked with in the past and I’m going to share with you. Nothing ground breaking. - Create a form with a button that submits some data to an API and shows a success message on the screen for a couple seconds. Maybe you’ll find this easy. Good. Maybe this will be a reminder to practice your JS skills along with whatever framework you’re currently using. Also good. Check it out in comments below.	UNKNOWN	Brian	Jenney	56,871	56,871	314	24	10	0.006119	null	2023-12-07 08:31:43	https://www.linkedin.com/feed/update/urn:li:activity:7138559434850537473
urn:li:activity:7137846730078781440	What is the 1 thing that separates developers who get hired vs those who don’t? I’ve thought about this a lot, especially as I’m now the owner of a coding bootcamp. I’ve seen too many success stories (and failures) from unlikely people. - The guy who could barely complete a for-loop? Hired before the bootcamp ended. - The woman with a CS degree? Nearly a year and 100’s of applications for her to get a break. There is very little rhyme, reason or “hack” I can confidently suggest. Except this: Grit and consistency WILL get you to the finish line. 𝗧𝗵𝗲 𝘀𝘂𝗿𝗲𝘀𝘁 𝘄𝗮𝘆 𝘁𝗼 𝗳𝗮𝗶𝗹 𝗶𝘀 𝘁𝗼 𝗾𝘂𝗶𝘁. Most people will choose this route. 𝗗𝗼𝗻’𝘁 𝗹𝗲𝘁 𝘆𝗼𝘂𝗿 𝘀𝗸𝗶𝗹𝗹𝘀 𝗮𝘁𝗿𝗼𝗽𝗵𝘆. Build stuff or do LeetCode or Odin Project. Do something where your hands are on a keyboard making code do stuff. 𝗡𝗼𝘁 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀? Maybe work on that. Focus on your resume, networking and the volume of applications. 𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗮𝗻𝗱 𝗳𝗮𝗶𝗹𝗶𝗻𝗴? This is actually a more straightforward obstacle to overcome. Try Colt Steele's DSA course on Udemy or Codewars or whatever other courses are out there. Fail. Learn. Iterate.	UNKNOWN	Brian	Jenney	9,003	9,003	99	18	3	0.013329	null	2023-12-05 09:19:13	https://www.linkedin.com/feed/update/urn:li:activity:7137846730078781440
urn:li:activity:7137478274405830658	I wrote to Kyle Simpson about a week ago. I asked him if he'd be a guest on my podcast and I honestly never expected to get this response: ... “I’d be happy to appear on your podcast” 😎 Wait, what? Holy sh*t, I’m going to be interviewing my idol? So many intruding thoughts: - 𝘐 𝘴𝘵𝘪𝘭𝘭 𝘥𝘰𝘯’𝘵 𝘬𝘯𝘰𝘸 𝘑𝘚. - 𝘞𝘩𝘢𝘵 𝘪𝘧 𝘩𝘦 𝘳𝘦𝘢𝘥𝘴 𝘮𝘺 𝘰𝘭𝘥 𝘱𝘰𝘴𝘵𝘴 𝘢𝘯𝘥 𝘵𝘩𝘦𝘯 𝘣𝘢𝘪𝘭𝘴? - 𝘈𝘮 𝘐 𝘴𝘮𝘢𝘳𝘵 𝘦𝘯𝘰𝘶𝘨𝘩 𝘵𝘰 𝘢𝘴𝘬 𝘩𝘪𝘮 𝘢𝘯𝘺𝘵𝘩𝘪𝘯𝘨? - 𝘞𝘪𝘭𝘭 𝘩𝘦 𝘲𝘶𝘪𝘻 𝘮𝘦 𝘰𝘯 𝘤𝘭𝘰𝘴𝘶𝘳𝘦? 😬 I’m a bit neurotic if it wasn’t clear. You can check out our conversation below. 𝗞𝘆𝗹𝗲 𝗯𝗿𝗲𝗮𝗸𝘀 𝗱𝗼𝘄𝗻 𝗵𝗶𝘀 𝗷𝗼𝘂𝗿𝗻𝗲𝘆 𝗶𝗻𝘁𝗼 𝗰𝗼𝗱𝗶𝗻𝗴, the 𝗽𝗿𝗼𝘀 𝗮𝗻𝗱 𝗰𝗼𝗻𝘀 𝗼𝗳 𝘀𝗼𝗰𝗶𝗮𝗹 𝗺𝗲𝗱𝗶𝗮 𝗳𝗮𝗺𝗲, 𝗵𝗼𝘄 𝗵𝗲 𝗺𝗶𝗴𝗵𝘁 𝗹𝗲𝗮𝗿𝗻 𝗝𝗦 𝗻𝗼𝘄𝗮𝗱𝗮𝘆𝘀, his interview experience and a 𝘀𝘂𝗿𝗽𝗿𝗶𝘀𝗶𝗻𝗴 𝘁𝗮𝗸𝗲 𝗼𝗻 𝗝𝗦 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀 that caught me off guard. 𝗜𝗳 𝘆𝗼𝘂’𝗿𝗲 𝗮 𝗵𝗶𝗿𝗶𝗻𝗴 𝗺𝗮𝗻𝗮𝗴𝗲𝗿 𝗹𝗼𝗼𝗸𝗶𝗻𝗴 𝘁𝗼 𝘀𝗻𝗮𝘁𝗰𝗵 𝘂𝗽 𝗠𝗿 𝗦𝗶𝗺𝗽𝘀𝗼𝗻, he shares what his dream role might entail as well 😉. 𝗧𝗵𝗲 𝗺𝗮𝗶𝗻 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆 𝗜 𝗴𝗼𝘁 𝗳𝗿𝗼𝗺 𝘁𝗵𝗶𝘀 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗶𝘀 𝘁𝗵𝗮𝘁 𝗞𝘆𝗹𝗲 𝗶𝘀 𝘁𝗿𝘂𝗹𝘆 𝘄𝗵𝗼 𝗵𝗲 𝘀𝗮𝘆𝘀 𝗵𝗲 𝗶𝘀 - a human-centric technologist and not in some corny, superficial way. He took time to chat with me in the hopes it will help others who may be on a similar journey and offered a candid glimpse into his own career and struggles. My one regret is that I did not ask him about his majestic beard routine. Maybe next time... Listen here:	EXTERNAL_VIDEO	Brian	Jenney	19,616	19,616	740	18	147	0.046136	null	2023-12-04 08:40:19	https://www.linkedin.com/feed/update/urn:li:activity:7137478274405830658
urn:li:activity:7135635106387423233	Before you take my advice, let me be clear: I will only ever give you suggestions based on my own experience or what I’ve seen work for others. Will it work for you? Perhaps. As a junior developer, almost any advice can be helpful. Your problems are fairly generic at this stage and what you mostly need is direction. As a team lead or senior, more context is needed to deliver useful advice and you have to be pickier with what advice you accept. The reasons I post on here are two-fold: 1. I have received considerable help from strangers online and I feel it’s only right to give back 2. I have a business and attract potential students through posting I’ll continue to give you spicy, and not-so-spicy advice because I want to see you win the game. I encourage you to take what makes sense and ignore what doesn’t.	UNKNOWN	Brian	Jenney	9,157	9,157	96	10	0	0.011576	null	2023-11-29 06:52:09	https://www.linkedin.com/feed/update/urn:li:activity:7135635106387423233
urn:li:activity:7134942314292015104	If you're a junior developer or recent bootcamp grad preparing for interviews - don't fall into the LeetCode rabbit hole. You're more likely to encounter: - JS trivia - String and Array manipulation problems - Frequency counters - Build a React component that fetches data - Tell me about a project you worked on Instead of: - Traverse this tree in O(n) 🧐	UNKNOWN	Brian	Jenney	80,659	80,659	412	27	14	0.005616	null	2023-11-27 08:42:16	https://www.linkedin.com/feed/update/urn:li:activity:7134942314292015104
urn:li:activity:7132444287987830785	Like many of you, I follow Erik Andersen and get a lot of value from what he posts, even though I'm not looking for a job. A little over a year ago I chatted with him to get his advice on LinkedIn, content creation and how to help junior developers. Who would've thought I'd be chatting with him on his podcast a year later? We tackle some practical, no-nonsense ways for you (yes you!) to stand out on your team as a developer, negotiate and different career paths to explore within software.	UNKNOWN	Brian	Jenney	3,973	3,973	35	2	0	0.009313	null	2023-11-20 11:22:28	https://www.linkedin.com/feed/update/urn:li:activity:7132444287987830785
urn:li:activity:7131327805920874496	Humans suck at predictions. Lemme make some anyway. Here’s what I think is in store for devs in 2024: 1. 𝗡𝗲𝘅𝘁𝗝𝗦 𝘄𝗶𝗹𝗹 𝗲𝘅𝗽𝗼𝗻𝗲𝗻𝘁𝗶𝗮𝗹𝗹𝘆 𝗴𝗿𝗼𝘄 𝗶𝗻 𝗽𝗼𝗽𝘂𝗹𝗮𝗿𝗶𝘁𝘆 and front end devs will need to get more comfortable with server side stuff like API’s and Server Components as well as Vercel (more on that below). 2. 𝗔𝗜 𝘄𝗶𝗹𝗹 𝗱𝗼𝗺𝗶𝗻𝗮𝘁𝗲 𝗯𝘂𝘁 𝗻𝗼𝘁 𝗶𝗻 𝘁𝗵𝗲 𝘄𝗮𝘆 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸. More “AI” startups will sprout up that leverage AI rather than creating AI models. Google leaked a memo that lends itself to this prediction. The money is in products that use AI; not better and faster models. 3. 𝗪𝗵𝗶𝘁𝗲𝗯𝗼𝗮𝗿𝗱 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 𝗱𝗲𝗰𝗹𝗶𝗻𝗲 as cheating increases and hiring in non-tech sectors ramps up. Debugging and pair programming interviews continue to rise as well as system design that is more client-side focused. Follow Ricardo A. Morales who is one of the few people tackling FE Sys Design. 4. 𝗖𝗹𝗼𝘂𝗱 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗣𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝘄𝗮𝗿𝘀. NextJS is a pain to deploy outside Vercel at the moment (if you want their cool features). I think AWS will begin to offer more NextJS specific tooling to retain their market share and Vercel will need to think of ways to keep customers on their platform. What do I know? I’ve been trying to figure out a good pointing system for years now. I’ll bet you 5 bucks at least 2 of these trends will be… trending. How wrong am I?	UNKNOWN	Brian	Jenney	5,750	5,750	56	20	2	0.013565	null	2023-11-17 09:22:05	https://www.linkedin.com/feed/update/urn:li:activity:7131327805920874496
urn:li:activity:7130952767807913984	Most developers would benefit more from reading “How to Win Friends and Influence People” than “Cracking the Coding Interview”. Here's the thing: Technical skills can get your foot in the door. Soft skills open the rest of the house. Knowing how to 𝗻𝗮𝘃𝗶𝗴𝗮𝘁𝗲 𝗵𝘂𝗺𝗮𝗻 𝗱𝘆𝗻𝗮𝗺𝗶𝗰𝘀, empathize and connect, 𝗮𝗿𝘁𝗶𝗰𝘂𝗹𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝘁𝗵𝗼𝘂𝗴𝗵𝘁𝘀 and influence others – these are the tools that build careers better than learning another programming language. They're learnable for the most part. 𝗦𝗽𝗲𝗮𝗸 𝗶𝗻𝘁𝗼 𝗮 𝗰𝗮𝗺𝗲𝗿𝗮 at home and explain something you learned. 𝗩𝗼𝗹𝘂𝗻𝘁𝗲𝗲𝗿 𝗳𝗼𝗿 𝗮 𝗱𝗲𝗺𝗼 at work. Write something online. I get it, you're a shy developer so 𝘀𝘁𝗮𝗿𝘁 𝘀𝗺𝗮𝗹𝗹 𝗯𝘆 𝗮𝘀𝗸𝗶𝗻𝗴 𝗮 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝗱𝘂𝗿𝗶𝗻𝗴 𝗮 𝗺𝗲𝗲𝘁𝗶𝗻𝗴. 𝘈𝘭𝘴𝘰 - 𝘳𝘦𝘢𝘥 𝘛𝘩𝘦 𝘗𝘩𝘰𝘦𝘯𝘪𝘹 𝘗𝘳𝘰𝘫𝘦𝘤𝘵 𝘪𝘧 𝘺𝘰𝘶’𝘳𝘦 𝘭𝘰𝘰𝘬𝘪𝘯𝘨 𝘧𝘰𝘳 𝘴𝘰𝘮𝘦 𝘯𝘰𝘯-𝘥𝘳𝘺 𝘤𝘰𝘥𝘪𝘯𝘨 𝘬𝘯𝘰𝘸𝘭𝘦𝘥𝘨𝘦 𝘵𝘩𝘢𝘵 𝘺𝘰𝘶 𝘥𝘪𝘥𝘯’𝘵 𝘨𝘦𝘵 𝘪𝘯 𝘤𝘰𝘭𝘭𝘦𝘨𝘦 😉.	UNKNOWN	Brian	Jenney	18,892	18,892	143	27	1	0.009051	null	2023-11-16 08:25:15	https://www.linkedin.com/feed/update/urn:li:activity:7130952767807913984
urn:li:activity:7130595501837598720	Git really doesn’t have to be that complicated: - 𝗰𝗼𝗺𝗺𝗶𝘁 your work 𝚐𝚒𝚝 𝚊𝚍𝚍 . 𝚐𝚒𝚝 𝚌𝚘𝚖𝚖𝚒𝚝 -𝚖 “𝚜𝚘𝚖𝚎 𝚐𝚘𝚘𝚍 𝚖𝚎𝚜𝚜𝚊𝚐𝚎” 𝚐𝚒𝚝 𝚙𝚞𝚜𝚑 - uh oh, got work 𝗜 𝗱𝗼𝗻’𝘁 𝘄𝗮𝗻𝗻𝗮 𝗰𝗼𝗺𝗺𝗶𝘁 𝗿𝗶𝗴𝗵𝘁 𝗻𝗼𝘄 𝚐𝚒𝚝 𝚜𝚝𝚊𝚜𝚑 - now I want to 𝗴𝗲𝘁 𝘁𝗵𝗮𝘁 𝗰𝗼𝗱𝗲 𝗯𝗮𝗰𝗸 𝚐𝚒𝚝 𝚜𝚝𝚊𝚜𝚑 𝚙𝚘𝚙 - double uh oh - 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗱𝗼𝗲𝘀 𝗻𝗼𝘁 𝘄𝗼𝗿𝗸 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝗮𝗻 𝗼𝗹𝗱 𝗰𝗼𝗺𝗺𝗶𝘁 𝚐𝚒𝚝 𝚕𝚘𝚐 to find the issue then 𝚐𝚒𝚝 𝚛𝚎𝚟𝚎𝚛𝚝 <𝚌𝚘𝚖𝚖𝚒𝚝 𝚑𝚊𝚜𝚑> - on second thought let’s 𝗮𝗱𝗱 𝗯𝗮𝗰𝗸 𝗶𝗻 𝘁𝗵𝗮𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 𝘆𝗼𝘂 𝗿𝗲𝘃𝗲𝗿𝘁𝗲𝗱 𝚐𝚒𝚝 𝚕𝚘𝚐 to find the revert commit hash and 𝚐𝚒𝚝 𝚛𝚎𝚟𝚎𝚛𝚝 <𝚛𝚎𝚟𝚎𝚛𝚝 𝚌𝚘𝚖𝚖𝚒𝚝 𝚑𝚊𝚜𝚑> - 𝘀𝘄𝗶𝘁𝗰𝗵 𝗯𝗮𝗰𝗸 𝘁𝗼 𝗯𝗿𝗮𝗻𝗰𝗵 I was just working on 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 - - 𝘂𝗻𝗱𝗼 𝗮𝗹𝗹 𝘁𝗵𝗲 𝗷𝘂𝗻𝗸 𝗰𝗼𝗱𝗲 I wrote 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 . - 𝗜 𝗼𝗻𝗹𝘆 𝘄𝗮𝗻𝘁 𝘁𝗵𝗮𝘁 𝗼𝗻𝗲 𝗳𝗶𝗹𝗲 from my other branch 𝚐𝚒𝚝 𝚌𝚑𝚎𝚌𝚔𝚘𝚞𝚝 <𝚋𝚛𝚊𝚗𝚌𝚑_𝚗𝚊𝚖𝚎> — ./𝚙𝚊𝚝𝚑/𝚝𝚘/𝚏𝚒𝚕𝚎 - 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗰𝗼𝗻𝗳𝗹𝗶𝗰𝘁𝘀 find all <<<< then fix conflicts, test your branch and commit that sh*t I’ve been using some version of this flow for nearly a decade to push my work, find and revert changes and triage critical incidents. Any git moves you’d add here? (don’t say rebase, don’t say rebase 😅)	UNKNOWN	Brian	Jenney	72,409	72,409	257	68	21	0.004778	null	2023-11-15 09:11:12	https://www.linkedin.com/feed/update/urn:li:activity:7130595501837598720
urn:li:activity:7130314399881256961	60+ people asked me to do my own podcast in the last day. So I recorded one. It’s about 5:30 seconds long. It’s all about the 3 strategies I use to land a job during a recession. It’ll be released tomorrow at 9:05AM EST in replacement of my text based newsletter! Subscribe now if you’re in the market and want an almost guaranteed way to succeed in this environment. Link in comments. #code #jobs #softwareengineering	UNKNOWN	Brian	Jenney	0	0	27	3	3	0	#code ,#jobs ,#softwareengineering	2023-11-14 14:56:37	https://www.linkedin.com/feed/update/urn:li:activity:7130314399881256961
urn:li:activity:7129866550785802241	One way to ensure you don't grow as a developer: - take on tasks you are 100% sure you will finish Instead: - take on tasks just outside of your comfort zone - google what you don’t know - ask for help Grow your confidence by force.	UNKNOWN	Brian	Jenney	21,117	21,117	235	29	11	0.013023	null	2023-11-13 08:29:43	https://www.linkedin.com/feed/update/urn:li:activity:7129866550785802241
urn:li:activity:7128778505001074689	Let me save you 90 hours of watch time from the Udemy Course you're going to buy this weekend. Between tutorial hell and your own side project is tutorial purgatory. The awkward phase when you’re not quite ready to create a complex side project but aren’t getting much out of following along with a video. Here’s how you limit your stay here: - 𝗗𝗼𝗻’𝘁 𝗲𝗾𝘂𝗮𝘁𝗲 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝘄𝗶𝘁𝗵 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗶𝗼𝗻 - there is no Gold Star for finishing a 100 hour course - Gain enough knowledge to be dangerous - 𝗘𝘅𝘁𝗲𝗻𝗱, 𝗯𝗿𝗲𝗮𝗸 𝗼𝗿 𝗿𝗲-𝘄𝗿𝗶𝘁𝗲 𝗮 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 from the tutorial - Write detailed comments about what is happening in the code and why Now you have a project that is similar to the tutorial but NOT exactly like it and you’ve removed the training wheels from your learning exercise.	UNKNOWN	Brian	Jenney	42,873	42,873	123	15	2	0.003265	null	2023-11-10 08:48:35	https://www.linkedin.com/feed/update/urn:li:activity:7128778505001074689
urn:li:activity:7128414034604781568	"𝘉𝘶𝘵 𝘮𝘺 𝘧𝘳𝘪𝘦𝘯𝘥 𝘨𝘰𝘵 𝘩𝘪𝘳𝘦𝘥 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 𝘰𝘧 𝘵𝘩𝘦𝘪𝘳 𝘱𝘰𝘳𝘵𝘧𝘰𝘭𝘪𝘰!" That's great for them. I would still caution the majority of developers from spending too much time on a site that: 1. 𝗡𝗼 𝗼𝗻𝗲 𝘄𝗶𝗹𝗹 𝗿𝗲𝗮𝗹𝗹𝘆 𝗹𝗼𝗼𝗸 𝗮𝘁 2. 𝗕𝗲𝗰𝗼𝗺𝗲𝘀 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆 𝗶𝗿𝗿𝗲𝗹𝗲𝘃𝗮𝗻𝘁 𝗮𝗳𝘁𝗲𝗿 𝘆𝗼𝘂𝗿 𝗳𝗶𝗿𝘀𝘁 𝗷𝗼𝗯 𝗮𝘀 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 3. 𝗧𝗮𝗸𝗲𝘀 𝘁𝗶𝗺𝗲 𝗮𝘄𝗮𝘆 𝗳𝗿𝗼𝗺 𝗽𝗿𝗲𝗽𝗮𝗿𝗶𝗻𝗴 𝗳𝗼𝗿 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 You've heard it's the golden ticket for junior devs to land a dream job. But let's be real: your portfolio probably won't be the reason you get hired. If you are hell bent on creating a portfolio please: 1. 𝗠𝗮𝗸𝗲 𝗶𝘁 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝘃𝗲 2. 𝗨𝘀𝗲 𝗮 𝘁𝗲𝗺𝗽𝗹𝗮𝘁𝗲 or learn some design (or have GPT style it for you 😉) 3. 𝗖𝗹𝗲𝗮𝗻 𝘁𝗵𝗲 𝗰𝗼𝗻𝘀𝗼𝗹𝗲 from all those logs you added	UNKNOWN	Brian	Jenney	10,055	10,055	85	16	2	0.010244	null	2023-11-09 08:20:33	https://www.linkedin.com/feed/update/urn:li:activity:7128414034604781568
urn:li:activity:7127695205935288320	5 phases of a developer’s career: 1. I got hired! My work is done! 2. I know nothing. I’m an awful developer and a burden on this team, the company and the world at large. 3. Can’t believe I solved that problem and delivered that feature. Perhaps I’m not the absolute worst developer in the entire universe. 4. I should be paid more. Time to grind DSA and system design. 5. I got hired! My work is done! Which stage are you in?	UNKNOWN	Brian	Jenney	16,171	16,171	134	50	3	0.011564	null	2023-11-07 09:31:47	https://www.linkedin.com/feed/update/urn:li:activity:7127695205935288320
urn:li:activity:7127329139144937472	Your idea of the 10x developer is all wrong. It’s not a coding robot pumping out ten times as much code as us regular flesh bags. They’re not producing code that is wildly more efficient or faster than the average developer either. - Great developers magnify the power of the team. - They take on tasks with more leverage to have greater impact. - They mentor, document and create patterns for others to leverage. Their greatest contribution might not include writing any code at all. If your goal is to be a mega-hyperbole-super-senior software engineer, you need to take a step back from writing better and better code and start thinking “𝘏𝘰𝘸 𝘤𝘢𝘯 𝘐 𝘮𝘢𝘬𝘦 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘰𝘯 𝘵𝘩𝘪𝘴 𝘵𝘦𝘢𝘮 𝘢𝘯𝘥 𝘰𝘶𝘳 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘣𝘦𝘵𝘵𝘦𝘳?” - Can the deployment process be improved? - Are code reviews useful? - How can we ship code faster with less bugs? These kinds of questions will lead you down rabbit holes that lead to more interesting problems to solve and make you the kind of developer who stands out on your team.	UNKNOWN	Brian	Jenney	8,415	8,415	72	12	0	0.009982	null	2023-11-06 08:41:07	https://www.linkedin.com/feed/update/urn:li:activity:7127329139144937472
urn:li:activity:7126236176021155840	You should be learning in public. But let's be honest: - You're nervous to create a post - You feel like you don't know enough - You're afraid of coming across like a cringe influencer with a blue background surrounding their big, bald head... Or something like that. First off, you're over-thinking it and no one really cares that much about what you're going to post. We're here to scroll and troll 😎. BUT - there is 𝗮 𝘄𝗮𝘆 𝘁𝗼 𝗴𝗮𝗶𝗻 𝗳𝗼𝗹𝗹𝗼𝘄𝗲𝗿𝘀, 𝗺𝗮𝗸𝗲 𝗴𝗲𝗻𝘂𝗶𝗻𝗲 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗲𝘃𝗲𝗿 𝗽𝗼𝘀𝘁𝗶𝗻𝗴. Check out this video where I go over a strategy that has worked for me to make some really great connections, business deals and even some friendships on LinkedIn.	VIDEO	Brian	Jenney	7,961	7,961	95	13	1	0.013692	null	2023-11-03 08:59:59	https://www.linkedin.com/feed/update/urn:li:activity:7126236176021155840
urn:li:activity:7125872869057732608	Listening to too many influencers on LinkedIn will get you stuck in a learning loop. Goes a little something like this: - Tech bro with a blue background tells you about hawt technology 🔥 - You, a little insecure about your own skills, think this is THE way to get noticed - You buy a course or a book or go down a YouTube rabbit hole Repeat this a few times and you will be a sub-par developer in many technologies instead of good at a couple. 😅 ♾️ Instead: - Focus on your core skills and identify trends in the local and global market (hint: ReactJS ain’t going away) - Resist the urge to add more tools to your tool belt early on - Focus on getting interviews and learning from your failures or successes - Use a side project to reinforce your current skills and incrementally add new technologies	UNKNOWN	Brian	Jenney	6,650	6,650	81	10	1	0.013835	null	2023-11-02 09:00:34	https://www.linkedin.com/feed/update/urn:li:activity:7125872869057732608
urn:li:activity:7125477091562721282	I have a confession: I never really wanted to become a talking head on LinkedIn. I actually just wanted to promote my mentorship program and share the advice I wish I’d been given earlier in my career. Maybe people will find this stuff helpful I figured. 20k followers, hundreds of coffee chats and a dozen podcasts later and I now see writing on here has been one of the best decisions I ever made. I’ve met too many amazing people to count and even made some real friends. I also sold some products…. so there’s that too. Well, now I can finally reveal the next chapter in this twisty story: I am now the owner of Parsity. What started as a DM on LinkedIn from the owner, Aaron Hayslip, turned into a partnership and finally an offer to take over the ownership. I’ll be honest, I’m a little scared. I’m also excited for what’s next. Massive curriculum updates, more community engagement and partnerships and so many Slack emojis 😎. I’m honored to take Parsity to the next level with Aaron’s guidance and the amazing program he’s built up. I can’t wait to indoctrinate, I mean educate, many more developers with a program I’m proud to be part of.	UNKNOWN	Brian	Jenney	5,843	5,843	110	18	0	0.021907	null	2023-11-01 06:57:21	https://www.linkedin.com/feed/update/urn:li:activity:7125477091562721282
urn:li:activity:7124783683818950656	It’s OK to self-reject. But most of you are doing way too much of it. If you meet 50% of the requirements and are within 1 - 2 years of the desired YOE you must apply. If you meet 100% of the requirements and have all the YOE, you’re probably over-qualified.	UNKNOWN	Brian	Jenney	13,644	13,644	127	18	4	0.010921	null	2023-10-30 08:51:11	https://www.linkedin.com/feed/update/urn:li:activity:7124783683818950656
urn:li:activity:7123723702071934976	I bet 50% of you are not using these dead simple keyboard shortcuts in VS Code. I've pair programmed with enough of you to know that this video may be more helpful than another 420 hour Udemy course on the parts of Javascript you though you knew but kinda don't but are going to... Hope it's helpful. Any shortcuts I missed?	VIDEO	Brian	Jenney	8,942	8,942	103	7	12	0.013643	null	2023-10-27 10:43:32	https://www.linkedin.com/feed/update/urn:li:activity:7123723702071934976
urn:li:activity:7123327941333155841	Perhaps I’ve fooled you. You see my title or follower count and make some assumptions. Just to be clear, I still: - get very nervous about public speaking - google the difference between slice and splice - fail interviews - feel like I should know more than I do - buy courses that I never finish Luckily, I have the benefit of history to give me confidence. In between my mistakes and fumbles, I’ve actually done some cool stuff. That doesn’t mean I’m immune to my own insecurities. I’ve just learned to ignore them better.	UNKNOWN	Brian	Jenney	8,255	8,255	155	17	3	0.021199	null	2023-10-26 08:28:02	https://www.linkedin.com/feed/update/urn:li:activity:7123327941333155841
urn:li:activity:7122244304210706432	Am I... average? In reality, amazing teams are made up of mostly "average" developers. Not teams of ninjas/rockstars/wizards/elves 🧝‍♂️ As an average developer there’s still a lot of room to make impact outside being the highest technical authority. As a very non-rockstar coder, here are some things I’ve done over the years which helped me stand out: - start an engineering book club - volunteer for on-call - onboard junior members - create a PR template to streamline the code review process - offer to assist with others’ work - actually talk during pointing sessions and clarify tasks instead of just nodding my head Of course, getting work done in a timely manner and not significantly adding to the number of bugs in our backlog didn’t hurt either. Let me be clear, you cannot be technically incompetent, start a book club and expect to get recognized and promoted… BUT you also don’t need to wait until you understand JS on a Kyle Simpson level to offer your insight, suggest changes and speak up.	UNKNOWN	Brian	Jenney	27,903	27,903	84	18	1	0.003691	null	2023-10-23 08:49:44	https://www.linkedin.com/feed/update/urn:li:activity:7122244304210706432
urn:li:activity:7120082946685890560	Creating a side project is draining. Here's my cheat sheet so you'll never run out of side project inspiration. 4 easy ways to generate quality side project ideas: 1. 𝗦𝘁𝗲𝗮𝗹 𝗳𝗿𝗼𝗺 𝗼𝘁𝗵𝗲𝗿𝘀. Check out sites like Acquire[dot]com and WellFound[dot]com to see what small startups and 1 person businesses are building. Build something similar. 2. 𝗗𝗼𝗻’𝘁 𝗯𝘂𝗶𝗹𝗱 𝗮 𝗵𝗼𝘂𝘀𝗲. 𝗔𝗱𝗱 𝗮 𝗯𝗿𝗶𝗰𝗸. Check out the feature requests or reviews for an app you’re using. What do people want? Maybe build that. 3. 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝗮𝗻 𝗔𝗣𝗜 on rapidAPI or use OpenAI (everyone’s doing it 😎) and think what you can build around it. For example, can you scrape a user’s top posts as a way to train GPT on their voice and content? 4. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗯𝗼𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝘁𝗲𝗱𝗶𝗼𝘂𝘀. Is there something at work or in your personal life that you do manually that could be automated? Spreadsheets are an easy target. Fix it for yourself and others. You also don’t need to solve anything. A great side project really only has 1 metric for success: you learned something.	UNKNOWN	Brian	Jenney	34,524	34,524	325	24	13	0.010485	null	2023-10-17 09:36:53	https://www.linkedin.com/feed/update/urn:li:activity:7120082946685890560
urn:li:activity:7119717343127117824	I’ve spoken with about 500 developers in the last 12 months. I won’t be doing any more 15 minute chats in the foreseeable future. But the truth is, most beginners ask the same 3 questions: - What’s wrong with my resume? - What should I build for a side project? - How do I get hired? So I want to answer them for free: 1. 𝗬𝗼𝘂𝗿 𝗿𝗲𝘀𝘂𝗺𝗲 𝗶𝘀 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗮𝗻𝗱 𝘀𝗼𝘂𝗻𝗱𝘀 𝗹𝗶𝗸𝗲 𝗺𝗮𝗻𝘆 𝗼𝘁𝗵𝗲𝗿𝘀. Remove any mention of junior or aspiring and use this framework: did [x] using [y] which led to [z]. Think from the recruiter’s perspective: 𝗗𝗼 𝘆𝗼𝘂 𝘀𝗼𝘂𝗻𝗱 𝗹𝗶𝗸𝗲 𝗮 𝗿𝗶𝘀𝗸 𝘁𝗼 𝗵𝗶𝗿𝗲? Make yourself less risky and don’t tell them everything. Why do they need to know your last job was at a french fry shop? Lead with your developer experience or technical projects. 2. 𝗦𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘀𝗵𝗼𝘂𝗹𝗱 𝘁𝗲𝗮𝗰𝗵 𝘆𝗼𝘂 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗻𝗲𝘄 or keep your skills sharp if you’re not working. Really, they should be enjoyable. They’re an alternative to grinding away at toy problems and expose you to challenges which you can give yourself. Want to understand how to implement role-based authentication or get your hands dirty with Serverless? Build it out. Also follow John Crickett , he has a ton of cool projects to make. 3. Now here’s the hard part and the truth no one wants to hear: 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗵𝗶𝗿𝗲𝗱 𝗶𝘀 𝗮 𝗴𝗮𝗺𝗲 𝗼𝗳 𝘀𝗸𝗶𝗹𝗹 𝗮𝗻𝗱 𝗹𝘂𝗰𝗸. If there is one trait that I see in successful grads, it is their consistency. They just didn’t stop. They outlasted their fears, insecurities and the fear mongers. They changed what didn’t work and picked a strategy. Mass apply or network or do both. Then don’t stop.	UNKNOWN	Brian	Jenney	52,485	52,485	340	32	20	0.007469	null	2023-10-16 09:35:29	https://www.linkedin.com/feed/update/urn:li:activity:7119717343127117824
urn:li:activity:7118658458123464704	A few areas where most devs struggle after they are hired: 1. Code quality 2. Git 3. Estimations It's not all about getting your code to run. Like it or not, you will be judged on whether or not you delivered working code on time. I'm not a fan of estimates. Humans naturally suck at them. When I mentor developers who were recently hired, I show them this tactic I've used to 𝗿𝗲𝘁𝗿𝗼𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲 their work and suck a bit less. Hope you find it useful.	VIDEO	Brian	Jenney	8,723	8,723	78	11	5	0.010776	null	2023-10-13 11:08:40	https://www.linkedin.com/feed/update/urn:li:activity:7118658458123464704
urn:li:activity:7117496233539026944	Someone called me a "cringe tech influencer" 😢. It's OK though, I've been called worse. In addition to being a talking head on LinkedIn, I also manage a stellar team of software engineers at The Clorox Company. "𝘞𝘢𝘪𝘵, 𝘭𝘪𝘬𝘦 𝘵𝘩𝘦 𝘣𝘭𝘦𝘢𝘤𝘩 𝘤𝘰𝘮𝘱𝘢𝘯𝘺?" Yeah, same one. In addition to bleach, they also have a number of e-commerce sites which my team supports. ReactJS, GraphQL, AWS, Adobe Commerce Cloud and NextJS. Ya know, cool kid stuff. Today I'll get the chance to share how we've been an integral part of Clorox's digital transformation, our front end architecture, the mistakes we've made and the successes we've had at Meet Magento New York 2023.	UNKNOWN	Brian	Jenney	7,596	7,596	96	20	0	0.015271	null	2023-10-10 06:22:26	https://www.linkedin.com/feed/update/urn:li:activity:7117496233539026944
urn:li:activity:7116093352067952640	I bet 50% of you are still using 420 console logs to debug your buggy code 🐞. There's a better way. Check out my debugging walkthrough below to learn how to investigate and debug unexpected features in your JS apps.	VIDEO	Brian	Jenney	30,685	30,685	216	27	20	0.008571	null	2023-10-06 09:27:45	https://www.linkedin.com/feed/update/urn:li:activity:7116093352067952640
urn:li:activity:7115720837546078208	A co-worker called me out at a small start up some years ago. “𝘐𝘵’𝘴 𝘩𝘢𝘳𝘥 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘺𝘰𝘶 𝘴𝘪𝘯𝘤𝘦 𝘺𝘰𝘶 𝘥𝘰𝘯’𝘵 𝘳𝘦𝘢𝘭𝘭𝘺 𝘬𝘯𝘰𝘸 𝘵𝘩𝘦 𝘣𝘢𝘴𝘪𝘤𝘴 𝘰𝘧 𝘑𝘢𝘷𝘢𝘚𝘤𝘳𝘪𝘱𝘵”. It stung to hear that. He was also right. I was not junior either. I had been using AngularJS for a couple years. (don't judge me) 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: I’d become a framework developer. I knew how to use AngularJS but didn’t understand the JS behind it. I resolved to suck less at JS. I went back to the basics including: - promises - async/await - 𝚝𝚑𝚒𝚜 - design patterns I went through all the Kyle Simpson books. I made janky apps to internalize the information. I gained knowledge and confidence. Understanding the fundamentals provides a lot of benefits: - frameworks become less magical - you start seeing patterns everywhere - less learning curve when switching between technologies - libraries become more read-able Frameworks are great. You need to know them. Just don’t build your house on a shaky foundation.	UNKNOWN	Brian	Jenney	45,104	45,104	475	47	13	0.011861	null	2023-10-05 08:40:45	https://www.linkedin.com/feed/update/urn:li:activity:7115720837546078208
urn:li:activity:7115005206278406145	Sometimes I feel like a fake engineering manager but that’s ok. Before this, I was a fake senior software engineer and before that I was pretending to be a developer. At each new stage, there’s a little voice in my head reminding me why I shouldn’t be in my position. I peruse LinkedIn and compare myself to others. Terrible habit. I know it will happen again and I’m prepared. Here’s how I get over that little voice in my head: - 𝗳𝗶𝗻𝗱 𝗮𝗻 𝗮𝘃𝗮𝘁𝗮𝗿 - who do I want to be like? - what do they know that I don’t? - 𝗰𝗿𝗲𝗮𝘁𝗲 𝗮 𝗰𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁 with the items from the previous step - 𝗳𝗶𝗻𝗱 𝗺𝗲𝗻𝘁𝗼𝗿𝘀 𝗼𝗿 𝗯𝗼𝗼𝗸𝘀 or both to bring me closer to the avatar - 𝗰𝗵𝗲𝗰𝗸 𝗶𝘁𝗲𝗺𝘀 𝗼𝗳𝗳 𝘁𝗵𝗲 𝗹𝗶𝘀𝘁 and prove to myself that I’m where I need to be Rinse and repeat for each promotion, new company or new role.	UNKNOWN	Brian	Jenney	9,399	9,399	95	13	3	0.01181	null	2023-10-03 09:11:55	https://www.linkedin.com/feed/update/urn:li:activity:7115005206278406145
urn:li:activity:7114640993747881986	450 conversation with developers later and I’m convinced that most of us need a sympathetic ear as much as we need career and coding advice. Here’s the thing: coding is fun. It can also be: - lonely - stressful - tedious - confusing Don’t wrap too much of your identity in the code you write. It can be a fickle beast. Sometimes I’m pretty damn good at slinging code. Sometimes I suck. So I hit the gym. Run around a lake. Read stuff. Write on here and in my newsletter (you better have signed up, seriously wtf). This way when one area drags me down, I use another to lift me up. Outside of coding, what are some hobbies you’ve picked up?	UNKNOWN	Brian	Jenney	11,706	11,706	110	24	2	0.011618	null	2023-10-02 09:21:44	https://www.linkedin.com/feed/update/urn:li:activity:7114640993747881986
urn:li:activity:7113563029048332288	Someone said my videos were too long... they have a good point. I can't really dive into RSC in 60 seconds but this should be enough to get your noggin' joggin'.	VIDEO	Brian	Jenney	6,503	6,503	61	4	2	0.010303	null	2023-09-29 09:47:35	https://www.linkedin.com/feed/update/urn:li:activity:7113563029048332288
urn:li:activity:7113186725153161217	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 an asshat, you will have a hard time getting promoted - Shipping code fast is 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 didn't negotiate your salary - you left money on the table - The business doesn't care about your refactoring efforts… do it anyways - Your first job will validate you - your second will get you paid - Switching jobs is the easiest way to increase your salary - Stability is a myth - don't put all your eggs in one basket What would you add?	UNKNOWN	Brian	Jenney	53,933	53,933	377	51	13	0.008177	null	2023-09-28 08:59:24	https://www.linkedin.com/feed/update/urn:li:activity:7113186725153161217
urn:li:activity:7112472940939542528	There’s too much to learn. A new framework to replace the old one that you just learned. Obscure algorithms from dudes with too many letters in their last name. Everyone is switching to AI/ML now? Should you learn Python? While you can’t JUST stick to the basics, if you chase every shiny new technology you will become a Swiss Army Knife developer. You can do a little of everything… poorly. Instead: - 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝗺𝗲𝗴𝗮 𝘃𝘀 𝗺𝗶𝗰𝗿𝗼 𝘁𝗿𝗲𝗻𝗱𝘀 in software development: - Recent mega trends include Docker, NextJS, Serverless and TypeScript - Micro trends might include tRPC, Rust and Nuxt - Use side projects to gain experience with technologies that make up mega trends and keep your skills relevant - 𝗚𝗮𝗺𝗯𝗹𝗲 𝗮 𝗯𝗶𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗺𝗶𝗰𝗿𝗼 𝘁𝗿𝗲𝗻𝗱𝘀 If you’re lucky, some of them will become mega trends and you’ll be first in line to take advantage.	UNKNOWN	Brian	Jenney	11,897	11,897	131	16	5	0.012776	null	2023-09-26 09:32:14	https://www.linkedin.com/feed/update/urn:li:activity:7112472940939542528
urn:li:activity:7112103876434046976	Is copy/pasting really so bad? Honestly, it’s how I’ve survived over the years as a developer. Every new workplace where I went and every contract I completed, I took note of what the smarter developers were doing. - what books have they read? - how do they write their pull requests? - I copied their styles for writing tests, React components and backend code. - I asked how they investigated and debugged critical issues. - I imitated their mannerisms and studied how they spoke in meetings. I’ve been lucky. I copied from the right people at some amazing companies and worked with developers who I truly think might be genius. You don’t have to get lucky though. Nowadays, through the University of YouTube, you have the ability to learn from other amazing developers and copy what makes sense to you. A few professors at UYT who I’ve learned from recently include: - The Primeagen - Theo from Pinglabs - Blue Collar Coder Anyone else you’d suggest?	UNKNOWN	Brian	Jenney	13,776	13,776	104	20	5	0.009364	null	2023-09-25 09:03:41	https://www.linkedin.com/feed/update/urn:li:activity:7112103876434046976
urn:li:activity:7111018680880140289	One of my most embarrassing interviews happened a few years ago. It was so bad, I actually ended it early. The interviewer gave me a medium level LeetCode problem. It could have been solved recursively or with dynamic programming. Just 1 problem... I didn't know how to approach either solution 🥲 Within 10 minutes, I politely suggested we just end the interview. He was very kind and encouraged me to keep trying. He gave me hints. But there was no use. Why waste both our times? Since then I've spent around 10k learning DSA. I'm better than I was and I've passed (and failed) many interviews since. In the video below I walk through a DP approach to solving that same question I bombed. Hopefully you find it useful.	VIDEO	Brian	Jenney	12,412	12,412	115	7	4	0.010151	null	2023-09-22 09:17:57	https://www.linkedin.com/feed/update/urn:li:activity:7111018680880140289
urn:li:activity:7110305365426110464	There's just not enough time. You want to finish the Udemy course, grind LeetCode, learn TypeScript and workout to spite your ex. I get it. One of my mentees asked me how I juggle being a father of 3, running a side business, a full time job and keeping a consistent work out routine. Easy - I just neglect my children. 😅 It’s actually a fairly simple process I’ve been using for years to create time where there is none which I share in the article below along with a video on how to make better estimates as a software developer. Hope it's helpful.	ARTICLE	Brian	Jenney	11,727	11,727	135	14	2	0.012876	null	2023-09-20 09:59:54	https://www.linkedin.com/feed/update/urn:li:activity:7110305365426110464
urn:li:activity:7109926565668425728	The job market for developers doesn’t suck. It’s just less piping hot. And expectations have risen. So yes, getting that first role is difficult and more luck is involved than many would like to admit. A mentee of mine had that same issue last year and I suggested we pivot into searching for QA roles. Here’s what he did: - 𝘚𝘵𝘶𝘥𝘪𝘦𝘥 𝘊𝘺𝘱𝘳𝘦𝘴𝘴 𝘢𝘯𝘥 𝘚𝘦𝘭𝘦𝘯𝘪𝘶𝘮 - 𝘗𝘳𝘢𝘤𝘵𝘪𝘤𝘦𝘥 𝘸𝘳𝘪𝘵𝘪𝘯𝘨 𝘢𝘶𝘵𝘰𝘮𝘢𝘵𝘦𝘥 𝘵𝘦𝘴𝘵𝘴 𝘢𝘯𝘥 𝘸𝘦𝘣 𝘴𝘤𝘳𝘢𝘱𝘦𝘳𝘴 - 𝘜𝘱𝘥𝘢𝘵𝘦𝘥 𝘩𝘪𝘴 𝘳𝘦𝘴𝘶𝘮𝘦 𝘵𝘰 𝘳𝘦𝘧𝘭𝘦𝘤𝘵 𝘳𝘦𝘭𝘦𝘷𝘢𝘯𝘵 𝘘𝘈 𝘱𝘳𝘰𝘫𝘦𝘤𝘵𝘴 𝘧𝘳𝘰𝘮 𝘵𝘩𝘦 𝘱𝘳𝘦𝘷𝘪𝘰𝘶𝘴 𝘴𝘵𝘦𝘱 - 𝘈𝘱𝘱𝘭𝘪𝘦𝘥 𝘢 𝘭𝘰𝘵 (𝘭𝘪𝘯𝘬 𝘪𝘯 𝘱𝘳𝘰𝘧𝘪𝘭𝘦 𝘵𝘰 𝘨𝘳𝘢𝘣 𝘴𝘰𝘮𝘦 𝘧𝘳𝘦𝘦 𝘮𝘢𝘵𝘦𝘳𝘪𝘢𝘭 𝘵𝘰 𝘭𝘦𝘢𝘳𝘯 𝘵𝘦𝘴𝘵𝘪𝘯𝘨 😉) He landed a role at a tech company shortly after as a QA automation engineer where he wrote code for end to end test suites. There’s more to the tech-o-sphere than ReactJS. There’s DevOps, QA, product, data, sales... Don’t limit yourself to what your bootcamp taught you	UNKNOWN	Brian	Jenney	19,838	19,838	185	26	7	0.010989	null	2023-09-19 08:56:18	https://www.linkedin.com/feed/update/urn:li:activity:7109926565668425728
urn:li:activity:7109578957385056256	The dirty secret about coding interviews: No one knows what the hell they’re doing. We all think we have THE way to find the right candidates. I’ve spoken with many of you who are devastated after failing an interview. You believe this is a signal that you are not talented and lack fundamental skills. It may be true. It also could be that: - Your interviewer is not equipped to determine your ability - They are biased from their own experience and ONLY looking for solutions which they are familiar with and understand - They don’t know closures very well or how to explain promises to a 5 year old either - They’re just having a bad day… 🥲 There is less formal training for interviews than you might imagine. Especially at non-tech companies and startups. Lord knows I’ve failed more than my fair share of interviews. It hurts. I also know it’s a winnable game. Learn from the loss and keep playing.	UNKNOWN	Brian	Jenney	16,122	16,122	177	12	4	0.011971	null	2023-09-18 10:08:25	https://www.linkedin.com/feed/update/urn:li:activity:7109578957385056256
urn:li:activity:7108491733780353024	What the hell is RSC? Developers love acronyms and RSC is one you'll want to be familiar with. React Server Components are React Components... but rendered on the server. Duh. This means data fetching and bundling is done on the server to compose the component and it is sent to the client fully rendered. 𝗧𝗵𝗶𝘀 𝗴𝗶𝘃𝗲𝘀 𝘁𝗵𝗲𝗺 𝘀𝗼𝗺𝗲 𝘀𝘂𝗽𝗲𝗿 𝗽𝗼𝘄𝗲𝗿𝘀: - reduced bundle size - database connections and other server-y stuff - improved SEO 𝗔𝗻𝗱 𝘀𝗼𝗺𝗲 𝗴𝗼𝘁𝗰𝗵𝗮𝘀: - no Window or browser APIs - can't use React hooks This video explores a few differences you might find useful as you explore them on your own.	VIDEO	Brian	Jenney	5,415	5,415	62	7	1	0.012927	null	2023-09-15 10:54:00	https://www.linkedin.com/feed/update/urn:li:activity:7108491733780353024
urn:li:activity:7108113645363949569	The recipe for an amazing side project when you don’t know what to do: 1. 🤖 𝗣𝗶𝗰𝗸 𝗮𝗻 𝗔𝗣𝗜 - OpenAI, Binance, RapidAPI and Govt APIs are the first places I’d check. 2. 🧠 𝗜𝗱𝗲𝗮𝘁𝗲 - what are the features of this API you can build something around? Perhaps a stock tracker that integrates with OpenAI to give targeted trading advice. 3. 🩹𝗠𝗨𝗣 - what is required to build the minimally usable product? Pick 1 or 2 core features. 4. ✍️ 𝗦𝗸𝗲𝘁𝗰𝗵 - a white piece of paper and pen will do. Draw out the main features of the app. Ask “and then what?” For example, they visit your site and then what? They click on a button and then what? 5. ✨ 𝗣𝗶𝗰𝗸 𝟭 𝗼𝗿 𝟮 𝗻𝗲𝘄 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝗶𝗲𝘀 you want to learn and use them. Maybe this is your chance to learn TypeScript or COBOL. Whatevs. 6. 🚀 𝗗𝗲𝗽𝗹𝗼𝘆 𝗶𝘁 and buy a domain on Route53 (or whatever) for like 15 bucks. It will look pro. Get frustrated. Pull out your hair (I don’t have this problem) and learn more than any tutorial can teach you.	UNKNOWN	Brian	Jenney	10,634	10,634	129	10	9	0.013918	null	2023-09-14 09:18:50	https://www.linkedin.com/feed/update/urn:li:activity:7108113645363949569
urn:li:activity:7107765452449206272	I became an engineering manager a couple years ago and I’ve seen all your resumes. They go something like this: - “𝘗𝘢𝘴𝘴𝘪𝘰𝘯𝘢𝘵𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘢𝘯𝘥 𝘢𝘴𝘱𝘪𝘳𝘪𝘯𝘨 𝘤𝘰𝘥𝘦𝘳 𝘭𝘰𝘰𝘬𝘪𝘯𝘨 𝘧𝘰𝘳 𝘧𝘪𝘳𝘴𝘵 𝘳𝘰𝘭𝘦 𝘪𝘯 𝘵𝘦𝘤𝘩” - “𝘉𝘶𝘪𝘭𝘵 𝘵𝘩𝘪𝘴 [𝘵𝘩𝘪𝘯𝘨] 𝘶𝘴𝘪𝘯𝘨 𝘵𝘩𝘪𝘴 [𝘵𝘦𝘤𝘩𝘯𝘰𝘭𝘰𝘨𝘺]” - Github link to site that I put in mobile view immediately. And it breaks 😅 Last week, some members of the Not Another Course community (link in profile 😉) and I pair programmed one member’s resume. He got an interview the next week. 𝗛𝗲𝗿𝗲’𝘀 𝘁𝗵𝗲 𝗧𝗟𝗗𝗥; - 𝗱𝗲-𝗿𝗶𝘀𝗸 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 - no one wants to take a chance on someone and recruiters have even less incentive to do so. Sell yourself as a developer. Remove junior. Remove aspiring. - 𝘁𝗵𝗲 𝗽𝗼𝘄𝗲𝗿 𝘀𝗲𝗻𝘁𝗲𝗻𝗰𝗲 𝘁𝗲𝗺𝗽𝗹𝗮𝘁𝗲 - [role] on [x] with [y] which led to [z] - “led development on unit testing suite using Jest and React-Testing-Library which led to increased stability for code releases and a 50% decrease in bugs” - 𝘂𝘀𝗲 𝗯𝗼𝗹𝗱 𝗳𝗼𝗿𝗺𝗮𝘁𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗴𝗼𝗼𝗱 𝘀𝘁𝘂𝗳𝗳 - it’s easy to gloss over a resume when you have 100 to go through so lead their eyes where you want them to go - 𝗼𝗻𝗹𝘆 𝗶𝗻𝗰𝗹𝘂𝗱𝗲 𝗹𝗶𝗻𝗸𝘀 𝘁𝗼 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘆𝗼𝘂 𝗿𝗲𝗮𝗹𝗹𝘆 𝘄𝗮𝗻𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗼 𝘀𝗲𝗲 - if you don’t have one then build one or just don’t add it. The risk is higher than the reward in many cases - 𝗮𝗱𝗱 𝘀𝗼𝗺𝗲 𝗾𝘂𝗶𝗿𝗸 - a little humor can go a long way and can make you stand out in a sea of resumes that sounds basically the same There’s more for sure but this should improve 99% of the resumes I’ve come across.	UNKNOWN	Brian	Jenney	62,761	62,761	418	44	39	0.007983	null	2023-09-13 10:39:18	https://www.linkedin.com/feed/update/urn:li:activity:7107765452449206272
urn:li:activity:7107386056022327296	Popular open source repo Turbo went from TS → JS and developers are furious. 𝘑𝘢𝘷𝘢𝘴𝘤𝘳𝘪𝘱𝘵 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴 𝘢𝘳𝘦𝘯’𝘵 “𝘳𝘦𝘢𝘭” 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳𝘴. 𝘛𝘺𝘱𝘦𝘚𝘤𝘳𝘪𝘱𝘵 𝘪𝘴 𝘶𝘴𝘦𝘭𝘦𝘴𝘴. 𝘐𝘵 𝘸𝘢𝘴 𝘰𝘯𝘭𝘺 𝘮𝘢𝘥𝘦 𝘧𝘰𝘳 𝘊# 𝘥𝘦𝘷𝘴 𝘵𝘰 𝘸𝘳𝘪𝘵𝘦 𝘤𝘭𝘪𝘦𝘯𝘵 𝘴𝘪𝘥𝘦 𝘤𝘰𝘥𝘦. These debates and low blows aren’t helping anyone. Truth be told - I don’t love TypeScript... yet. I won’t ignore it however. You shouldn’t either. It’s a mega-trend in software, like Serverless, SPA and React. It’s more than just JS with types but that’s a fine place to start. 𝗛𝗲𝗿𝗲’𝘀 𝗵𝗼𝘄 𝗜 𝗴𝗼𝘁 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝘄𝗶𝘁𝗵 𝘁𝘆𝗽𝗲𝘀 𝗶𝗻 𝗝𝗦: - add JSdoc notation to an existing app - a nice warm up for TypeScript and thinking in types - convert a small existing project to use TS and figure out how the TS config works - start a new project with TS and restrict the use of 𝚊𝚗𝚢 types 😉 with a linter - refactor previous code to use advanced features like unions, generics and 𝚘𝚖𝚒𝚝 I’m what I’d consider a TS n00b. For those learning, how did you start?	UNKNOWN	Brian	Jenney	5,909	5,909	33	14	2	0.008292	null	2023-09-12 09:33:16	https://www.linkedin.com/feed/update/urn:li:activity:7107386056022327296
urn:li:activity:7107018206778658816	The most talented developers I’ve met in real life are NOT on LinkedIn, X or Medium. Like 99% of the people reading this - they’re here to scroll and troll. What does that mean for you? Take our advice with a grain of salt. We may be the most vocal developers but it doesn’t mean we are the best to listen to. Myself included. Ask yourself these 3 questions before blindly following what some talking head posts on a social media platform: 1. Does this person seem happy? 2. Do I want to be anything like them? 3. Do their actions support their claims? If the answer to all 3 is no. Maybe don’t follow their advice.	UNKNOWN	Brian	Jenney	7,263	7,263	75	9	1	0.011703	null	2023-09-11 08:50:57	https://www.linkedin.com/feed/update/urn:li:activity:7107018206778658816
urn:li:activity:7105956118459293696	Check out the video below to check out some debugging techniques I guarantee most of you aren't using that beats the hell out of using 142 console logs. 𝘽𝙪𝙩 𝙛𝙞𝙧𝙨𝙩, 𝙖 𝙙𝙚𝙗𝙪𝙜𝙜𝙞𝙣𝙜 𝙣𝙞𝙜𝙝𝙩𝙢𝙖𝙧𝙚 𝙄 𝙚𝙣𝙘𝙤𝙪𝙣𝙩𝙚𝙧𝙚𝙙 𝙮𝙚𝙖𝙧𝙨 𝙖𝙜𝙤: By 12AM we knew something was wrong with the migration. Our line charts were no longer displaying data. The realtime word cloud was frozen. Half the widgets for our data intensive application just weren't working. I had volunteered to be on call during this migration. I wanted to stand out. It was gonna be a cake walk they told me. Nothing major. Easy. Breezy. Oops. The Director of Engineering Slacked me just after midnight and asked me to investigate. My anxiety went 📈 Here's what I did: 1. 𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗲 𝘁𝗵𝗲 𝗯𝘂𝗴 locally 2. 𝗡𝗮𝗿𝗿𝗼𝘄 𝗱𝗼𝘄𝗻 𝘁𝗵𝗲 𝘀𝘂𝗿𝗳𝗮𝗰𝗲 𝗮𝗿𝗲𝗮 (what files seemed to be the culprit?) 3. 𝗔𝗱𝗱 𝗱𝗲𝗯𝘂𝗴𝗴𝗲𝗿 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁𝘀 to pause execution near the site of the issue 4. 𝗦𝘁𝗲𝗽 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲 𝗹𝗶𝗻𝗲 𝗯𝘆 𝗹𝗶𝗻𝗲 to see exactly where things went wrong 5. 𝗙𝗶𝘅 𝘁𝗵𝗲 𝗼𝗳𝗳𝗲𝗻𝗱𝗶𝗻𝗴 𝗰𝗼𝗱𝗲 and write up a suggestion on how to avoid in the future Hope this helps you debug your buggy-ass code.	VIDEO	Brian	Jenney	13,245	13,245	123	15	9	0.011099	null	2023-09-08 11:09:47	https://www.linkedin.com/feed/update/urn:li:activity:7105956118459293696
urn:li:activity:7105572361621413888	They told you don't need Redux. 𝘛𝘩𝘦𝘳𝘦'𝘴 𝘵𝘰𝘰 𝘮𝘶𝘤𝘩 𝘣𝘰𝘪𝘭𝘦𝘳𝘱𝘭𝘢𝘵𝘦! 𝘜𝘴𝘦 𝘵𝘩𝘪𝘴 𝘭𝘪𝘣𝘳𝘢𝘳𝘺! 𝘐𝘵’𝘴 𝘸𝘢𝘺 𝘣𝘦𝘵𝘵𝘦𝘳! My least favorite one: "𝘑𝘶𝘴𝘵 𝘶𝘴𝘦 𝘊𝘰𝘯𝘵𝘦𝘹𝘵! " With around 8.2 million downloads just last week, there’s a pretty high chance the next company you join will leverage this library. So stop being scared of it. Try learning these concepts/tools: - observer pattern - Functional Programming basics - Ducks pattern - Redux DevTools extension And when you're ready to get your hands dirty with some old (and new school) Redux check out my e-com React App Challenge here 👇 https://lnkd.in/gqnbpDCH	UNKNOWN	Brian	Jenney	18,332	18,332	135	23	4	0.008837	null	2023-09-07 09:36:08	https://www.linkedin.com/feed/update/urn:li:activity:7105572361621413888
urn:li:activity:7105217842928631809	I used to take pride in the fact I was not good at CSS. As if this made me a “real” developer. What a fool I was. I know JS is moving at a breakneck pace lately with major changes in React, NextJS, NodeJS and whatever framework is trying to replace ReduxJS today 🙄 CSS has been quietly keeping up and introducing a ton of cool new features. - Container queries (media queries based on the parent container) - Nested rules (goodbye Sass!) - Scoped CSS (basically native css modules) There’s a lot more that I have yet to experiment with but it’s an exciting time to re-introduce yourself to CSS.	UNKNOWN	Brian	Jenney	12,351	12,351	173	37	4	0.017327	null	2023-09-06 09:12:31	https://www.linkedin.com/feed/update/urn:li:activity:7105217842928631809
urn:li:activity:7104825093406564352	A mentee of mine asked me a great question last week: “𝘞𝘩𝘢𝘵 𝘪𝘴 𝘢 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘢𝘭 𝘵𝘩𝘪𝘯𝘨 𝘐 𝘤𝘢𝘯 𝘥𝘰 𝘵𝘰 𝘨𝘦𝘵 𝘤𝘭𝘰𝘴𝘦𝘳 𝘵𝘰 𝘴𝘦𝘯𝘪𝘰𝘳 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳?” I thought about what worked for me and others I’ve seen over the years. What was one thing they all had in common? I mean, they all wrote above average code. They took ownership of large areas of the codebase. 𝗕𝘂𝘁 𝘄𝗵𝗮𝘁 𝘄𝗮𝘀 𝟭 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝘀𝗸𝗶𝗹𝗹 𝘁𝗵𝗲𝘆 𝗮𝗹𝗹 𝘀𝗵𝗮𝗿𝗲𝗱? ❌ Understanding closure? ❌ Command of recursion? ❌ Writing code in Vim? Or Emacs 😮? ✅ Debugging. When sh*t hits the fan, the seniors are the first to get called. They understand how the different systems are orchestrated. They keep cool (or at least fake it) under pressure. They have a fix and insight into the origin of the issue and how to avoid it in the future. 𝗧𝗵𝗮𝘁 𝗯𝗲𝗶𝗻𝗴 𝘀𝗮𝗶𝗱, 𝘆𝗼𝘂 𝗰𝗮𝗻𝗻𝗼𝘁 𝗰𝗵𝗲𝗮𝘁 𝘁𝗶𝗺𝗲. You don’t have to take the long route though. Volunteer for an on-call rotation, look up the fix your team mate created for a bug that you don't quite understand and raise your hand when a fire happens. 𝗦𝗲𝗲𝗸 𝗼𝘂𝘁 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝘄𝗮𝗶𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝘁𝗵𝗲𝗺 𝘁𝗼 𝗵𝗮𝗽𝗽𝗲𝗻 𝘁𝗼 𝘆𝗼𝘂 as a way to accelerate your journey.	UNKNOWN	Brian	Jenney	6,788	6,788	60	13	1	0.010902	null	2023-09-05 07:51:42	https://www.linkedin.com/feed/update/urn:li:activity:7104825093406564352
urn:li:activity:7103412836659286019	You probably don't need another course. BUT - if you're going to take advantage of Labor Day sales 🇺🇸 here are 5 services I think are worth the money: 1. 𝗔𝗹𝗴𝗼𝗘𝘅𝗽𝗲𝗿𝘁/𝗙𝗿𝗼𝗻𝘁𝗘𝗻𝗱𝗘𝘅𝗽𝗲𝗿𝘁 - there are few FE focused offerings out there and this one is solid AF 2. 𝗖𝗼𝗱𝗲𝗖𝗿𝗮𝗳𝘁𝗲𝗿𝘀 - advanced challenges for software developers. I really like the workflow here which involves pushing to a repo where automated tests run to see if your project works 3. 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝗖𝗮𝗸𝗲 - this was my intro to algos and data structures and really helped me develop a mental model for attacking these kinds of problems 4. 𝗧𝗮𝗿𝗼 - the insight and practical advice from mid -> senior -> leadership engineers is filling a massive gap for developers who have moved past junior and want to know what it takes to get to the next level 5. 𝗡𝗼𝘁 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗖𝗼𝘂𝗿𝘀𝗲 - My own offering. A learning library with community support. Build complex stuff with JS as well as interview prep. (spoiler: no Labor Day Sale 🥲) 𝘏𝘰𝘯𝘰𝘳𝘢𝘣𝘭𝘦 𝘮𝘦𝘯𝘵𝘪𝘰𝘯 𝘵𝘰 𝘍𝘳𝘰𝘯𝘵𝘌𝘯𝘥𝘔𝘢𝘴𝘵𝘦𝘳𝘴 𝘢𝘯𝘥 𝘚𝘤𝘳𝘪𝘮𝘣𝘢. 𝘐 𝘩𝘢𝘷𝘦 𝘯𝘰𝘵 𝘱𝘶𝘳𝘤𝘩𝘢𝘴𝘦𝘥 (𝘺𝘦𝘵) 𝘣𝘶𝘵 𝘐 𝘩𝘦𝘢𝘳 𝘯𝘰𝘵𝘩𝘪𝘯𝘨 𝘣𝘶𝘵 𝘨𝘰𝘰𝘥 𝘵𝘩𝘪𝘯𝘨𝘴 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘦𝘴𝘦 𝘴𝘦𝘳𝘷𝘪𝘤𝘦𝘴. Now excuse me as I buy another Udemy course that I'll get to... later 😉.	UNKNOWN	Brian	Jenney	20,041	20,041	78	12	3	0.00464	null	2023-09-01 09:53:53	https://www.linkedin.com/feed/update/urn:li:activity:7103412836659286019
urn:li:activity:7103041420369817600	Here's how I've seen most successful coding 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 - De-risks themselves by using strong language in their profile and resume - Is practically optimistic that opportunity will present itself Why most bootcamp grads fail: - Relies on motivation instead of routine - Applies to only junior roles - Highlights their "junior-ness" - Tutorial - Tutorial - Tutorial - Doesn’t get hired in 3 months - 𝘎𝘪𝘷𝘦𝘴 𝘶𝘱	UNKNOWN	Brian	Jenney	12,813	12,813	102	11	3	0.009053	null	2023-08-31 08:58:04	https://www.linkedin.com/feed/update/urn:li:activity:7103041420369817600
urn:li:activity:7102691470171656192	I've worked with a lot of amazing junior developers so far in my career. Here’s what made them stand out: - 𝙩𝙝𝙚𝙮 𝙖𝙧𝙚 𝙥𝙧𝙤𝙖𝙘𝙩𝙞𝙫𝙚 - they seek out work to complete and pair with others without being asked. Oh, the pipeline blew up? They don't know the fix but are still investigating it. - 𝙩𝙝𝙚𝙮 𝙬𝙧𝙞𝙩𝙚 𝙩𝙝𝙤𝙧𝙤𝙪𝙜𝙝 𝙋𝙍𝙨 - screenshots and before and after pics for UI changes - videos for bonus points! The best PRs have taught me something about a feature or approach I was not familiar with. - 𝙩𝙝𝙚𝙮 𝙜𝙤𝙩 𝙜𝙪𝙩𝙨 - they volunteer to take on the tough stuff. They work on tickets just outside their comfort zone, get stuck, freak out and ask for help when needed - 𝙩𝙝𝙚𝙮 𝙖𝙧𝙚 𝙘𝙪𝙧𝙞𝙤𝙪𝙨 - how does HotPotatoService work? Why are there so many tests? Why are there none 😮? They assume good intentions and ask why decisions were made... often we learn we don't have a reason 😅 Anything you've seen juniors on your team do that makes you go 😮?	UNKNOWN	Brian	Jenney	10,568	10,568	137	13	4	0.014572	null	2023-08-30 10:33:06	https://www.linkedin.com/feed/update/urn:li:activity:7102691470171656192
urn:li:activity:7102311502409347072	5 things the gym can teach you about coding: 1. 𝗚𝗿𝗼𝘄𝘁𝗵 𝗺𝗶𝗻𝗱𝘀𝗲𝘁. Our body, like our mind, is not fixed or as limited as we believe. 2. 𝗛𝘂𝗺𝗶𝗹𝗶𝘁𝘆. There is always somebody better than you. Learning a new programming language or lifting a larger weight will keep you humble. 3. 𝗗𝗲𝗹𝗮𝘆𝗲𝗱 𝗴𝗿𝗮𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻. If you stick with either endeavor you will see long-term benefits and fulfillment. 4. 𝗡𝗼 𝗼𝗻𝗲 𝗶𝘀 𝗷𝘂𝗱𝗴𝗶𝗻𝗴 𝘆𝗼𝘂 (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. 5. 𝗔𝗴𝗲 𝗹𝗶𝗺𝗶𝘁𝘀 𝗱𝗼𝗻’𝘁 𝗲𝘅𝗶𝘀𝘁. Despite what you think - the gym, like the software industry is not controlled by 20 somethings and as long as you’re breathing, it's 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	10,018	10,018	135	37	5	0.017668	null	2023-08-29 08:59:14	https://www.linkedin.com/feed/update/urn:li:activity:7102311502409347072
urn:li:activity:7100874625810640896	You should be learning in public. But let's be honest: - You're nervous to create a post - You feel like you don't know enough - You're afraid of coming across like a cringe influencer with a blue background surrounding their big, bald head Or something like that. First off, you're over-thinking it and no one really cares that much about what you're going to post. We're here to scroll and troll 😎. BUT - there is 𝗮 𝘄𝗮𝘆 𝘁𝗼 𝗴𝗮𝗶𝗻 𝗳𝗼𝗹𝗹𝗼𝘄𝗲𝗿𝘀, 𝗺𝗮𝗸𝗲 𝗴𝗲𝗻𝘂𝗶𝗻𝗲 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗲𝘃𝗲𝗿 𝗽𝗼𝘀𝘁𝗶𝗻𝗴. Check out this video where I go over a strategy that has worked for me to make some really great connections, business deals and even some friendships on LinkedIn.	VIDEO	Brian	Jenney	10,839	10,839	125	16	3	0.013285	null	2023-08-25 09:35:18	https://www.linkedin.com/feed/update/urn:li:activity:7100874625810640896
urn:li:activity:7100499507829735424	17k followers and 1.5 million impressions on LinkedIn and I’ve barely had a “viral” post. Here are a few lessons I’ve learned along the way: - 𝗕𝗲 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁 - LinkedIn rewards it and your audience will reward you - Commenting on posts from larger accounts can grow your following and create connections you could never dream of - 𝗣𝗿𝗼𝗺𝗼𝘁𝗶𝗻𝗴 𝗼𝘁𝗵𝗲𝗿𝘀 𝗶𝘀 𝗮 𝗴𝗿𝗲𝗮𝘁 𝘄𝗮𝘆 𝘁𝗼 𝗽𝗿𝗼𝗺𝗼𝘁𝗲 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳 - 𝗣𝗲𝗼𝗽𝗹𝗲 𝗰𝗮𝗻 𝘀𝗺𝗲𝗹𝗹 𝗳𝗮𝗸𝗲𝘀 - don’t be one and write what you actually think - You’re smart but 𝗻𝗼 𝗼𝗻𝗲 𝘄𝗮𝗻𝘁𝘀 𝘁𝗼 𝗿𝗲𝗮𝗱 𝗮 𝗯𝗹𝗼𝗰𝗸 𝗼𝗳 𝘁𝗲𝘅𝘁 𝘄𝗶𝘁𝗵 𝗯𝗶𝗴 𝘄𝗼𝗿𝗱𝘀 - write at a 5th-grade level and don’t be afraid to use “bro-etry” If we wanted an essay we’d read Medium - 𝗙𝗶𝗴𝘂𝗿𝗲 𝗼𝘂𝘁 𝘄𝗵𝗼 𝘆𝗼𝘂𝗿 𝗮𝘂𝗱𝗶𝗲𝗻𝗰𝗲 𝗶𝘀 and write for them - Wrote a great post? Sweet, post it again a few weeks later - I guarantee most of your audience did not see it or already forgot about it - T𝗵𝗲 𝗼𝗽𝗲𝗻𝗶𝗻𝗴 𝘀𝗲𝗻𝘁𝗲𝗻𝗰𝗲 𝘄𝗶𝗹𝗹 𝗺𝗮𝗸𝗲 𝗼𝗿 𝗯𝗿𝗲𝗮𝗸 𝘁𝗵𝗲 𝗽𝗼𝘀𝘁 - start off with an interesting number or a hard stance which you can elaborate on further I think harvesting likes is a silly goal if you’re trying to land a job as a developer but for those of you who are trying to build a brand as an engineer for business, fun or whatever, I hope you find this helpful.	UNKNOWN	Brian	Jenney	6,760	6,760	91	25	0	0.01716	null	2023-08-24 09:07:13	https://www.linkedin.com/feed/update/urn:li:activity:7100499507829735424
urn:li:activity:7099767231336652800	How does it feel to be the worst developer on a team? I had the unpleasant experience of holding this title when I worked at a small startup several years ago. It sucked. I also had more technical growth in the short time I was there than at any other company I’ve worked since. You’ve probably heard the advice “If you’re the smartest person in the room, it’s time to leave the room.” Easier said than done. The guilt and anxiety I felt daily was difficult to deal with. I was confronted with my technical limitations and the realization that this wasn’t just all in my head. Everyone was better than me at writing code. 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. They were the kind of developers who gave speeches at conferences and wrote the libraries that other devs use in their daily work. I could either quit or at least attempt to keep up with the other devs and contribute to the best of my ability. I resolved to suck a little less each day. I asked the smarty-pants devs what books they suggested I read I audited my Javascript knowledge and wrote out what I knew I had to learn to contribute to discussions I enrolled in a course to learn DSA and comp sci fundamentals Someone made a joke about Djikstra once… who the hell is that? I would find out. I never became the 2nd worst developer at this company, but I grew my technical skills, confidence and threshold for failure which helped me get to senior at the next company. As uncomfortable as it was, I now see just how pivotal this experience was. So if you’re learning to code, or maybe you're on a new team and discovering just how little you know… good. Embrace the suck, expose your ignorance, identify your knowledge gaps, make a plan to fill them in and be prepared to learn.	UNKNOWN	Brian	Jenney	9,396	9,396	135	12	7	0.01639	null	2023-08-22 08:19:15	https://www.linkedin.com/feed/update/urn:li:activity:7099767231336652800
urn:li:activity:7097952237255102464	Let me break down your next ReactJS interview for you: - Fetch some data from this API - Display the data according to this mock up - Add some user events How you fail: - Not understanding the basics of `useEffect` - No keys in your list or using the index as a key - Ignoring error handling - Mutating state directly - Coding silently like a 🤖 How you study: - Open up CodeSandbox or Codepen or Gitpod - Use a placeholder API like Typicode or FakeStoreAPI - Practice without the aid of intellisense or ChatGPT - Time yourself - Record yourself explaining the code as you write it… ya know, kinda like you do in an interview If you recently had a React focused interview - what was yours like?	UNKNOWN	Brian	Jenney	20,648	20,648	253	35	17	0.014771	null	2023-08-17 08:36:59	https://www.linkedin.com/feed/update/urn:li:activity:7097952237255102464
urn:li:activity:7097608051322494976	Some of my most hated advice for junior developers or boot camp grads is to contribute to open source. 𝗪𝗶𝗹𝗹 𝗶𝘁 𝗺𝗮𝗸𝗲 𝘆𝗼𝘂 𝘀𝘁𝗮𝗻𝗱 𝗼𝘂𝘁? 𝘔𝘢𝘺𝘣𝘦. (I think a lot of you overestimate just how involved most software developers are in the coding community. Twitter and LinkedIn are a bubble rife with the most passionate developers) 𝗪𝗶𝗹𝗹 𝘆𝗼𝘂 𝗽𝘂𝗹𝗹 𝘆𝗼𝘂𝗿 𝗵𝗮𝗶𝗿 𝗼𝘂𝘁 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼 𝗳𝗶𝗴𝘂𝗿𝗲 𝗼𝘂𝘁 𝗵𝗼𝘄 𝘁𝗼 𝗴𝗲𝘁 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗲𝗿𝗴𝗲𝗱 𝘁𝗼 𝗮𝗻𝘆 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘁𝗵𝗮𝘁 𝘄𝗼𝘂𝗹𝗱 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗶𝗺𝗽𝗿𝗲𝘀𝘀 𝗽𝗲𝗼𝗽𝗹𝗲? Absolutely. 𝗔𝗿𝗲 𝘁𝗵𝗲𝘆 𝘀𝘁𝗶𝗹𝗹 𝘄𝗼𝗿𝘁𝗵 𝗲𝘅𝗽𝗹𝗼𝗿𝗶𝗻𝗴? For sure. Open source is a beautiful thing. We stand on the shoulders of tech giants... for free. It's crazy that software like React, NextJS, Serverless and the millions of NPM packages you need to scaffold a simple app are available on the web 😅. That being said, it's not a great place for junior devs to start: - overwhelming complexity - a high bar for entry - lack of guidance Instead, try this - clone down a popular project - try to get it working locally - update a small feature - try and hit a debugger statement that you’ve added This gives you the benefit of exploring open source and what it’s like to interact with a production-grade codebase instead of fishing around the 1169 open issues only to fix a typo in the README 😅	UNKNOWN	Brian	Jenney	16,004	16,004	164	19	2	0.01156	null	2023-08-16 09:38:57	https://www.linkedin.com/feed/update/urn:li:activity:7097608051322494976
urn:li:activity:7097247596838088705	The difference between a junior and senior developer is NOT that the senior writes code without bugs. It's how they handle them. In fact, a few weeks ago, I created a pretty embarrassing bug at work 😅. It wasn't my first time. It won't be my last. Here are 3 ways you can tackle your next blow up like a freakin' pro.	ARTICLE	Brian	Jenney	4,908	4,908	44	4	1	0.009984	null	2023-08-15 09:17:38	https://www.linkedin.com/feed/update/urn:li:activity:7097247596838088705
urn:li:activity:7096875632638271488	You’re having trouble coming up with solutions to problems as a software developer because you’re reinventing the wheel. As a junior developer, there are zero problems you will encounter that have not been solved a dozen times over. There are tried and true approaches for that feature you’re working on. But you don’t know what you don’t know. Here’s where I’d start: - lookup meta-software patterns- the general design patterns that dominate the field - familiarize yourself with language-specific patterns - for JS it could be the module pattern - read up on framework patterns like presenter/container and HOCs You’ll begin to notice that much of the code you write either fits into a larger pattern or implements smaller patterns. You’ll be a more confident and efficient developer because of it.	UNKNOWN	Brian	Jenney	14,702	14,702	126	6	7	0.009454	null	2023-08-14 08:37:09	https://www.linkedin.com/feed/update/urn:li:activity:7096875632638271488
urn:li:activity:7095796300020920322	When you land the job, that’s the last thing you’ll need to know how to do is traverse binary trees in O(h). There will be bugs. There will also be network requests to debug. The junior-est way to go about investigating an issue on the server is to replicate the scenario on the front end to hit the server and repeat this process 100+ times until you figure out what’s going on. I’ve seen too many of you doing this 😅. Check out the method in this video that you can use for some ethical hacking and more efficient debugging of your own codebase.	VIDEO	Brian	Jenney	10,506	10,506	94	9	4	0.010185	null	2023-08-11 09:02:15	https://www.linkedin.com/feed/update/urn:li:activity:7095796300020920322
urn:li:activity:7095441223385026560	Ok, we’ve seen enough well-written code on this damn site. It's hard to know what good code is if you can't identify bad code. Below is some janky ass code for you to refactor. Here's the thing though - it does work with the expected arguments. Could it be improved? Hell yeah it can. I’m curious, what’s the most unforgivable mistake I’ve made here and how would you fix it?	IMAGE	Brian	Jenney	14,442	14,442	52	46	2	0.006924	null	2023-08-10 09:38:11	https://www.linkedin.com/feed/update/urn:li:activity:7095441223385026560
urn:li:activity:7095063689199788033	How do you get better at Javascript? Build stuff. Not specific enough? Try this: Here are the subjects I struggled with and how I learned them through practice: - 𝙋𝙧𝙤𝙢𝙞𝙨𝙚𝙨 - implement Promise.all from scratch - 𝘾𝙡𝙤𝙨𝙪𝙧𝙚 - create a function that returns another function that can only be called 1 time - 𝙩𝙝𝙞𝙨 - implement bind and call from scratch - 𝙍𝙚𝙘𝙪𝙧𝙨𝙞𝙤𝙣 - make a function that searches a deeply nested object for a value If you’re feeling brave, record a video going over the concept and share it with others so you can spread and reinforce your own knowledge.	UNKNOWN	Brian	Jenney	21,230	21,230	221	10	13	0.011493	null	2023-08-09 08:33:53	https://www.linkedin.com/feed/update/urn:li:activity:7095063689199788033
urn:li:activity:7094339012525514752	You know you need a good side project but you don’t know where to begin. As much as I want to build 1 of these 𝟱 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀, I just don't have time. So steal 'em. If you succeed - I'll take the credit. If you fail... don't mention me. 𝗣𝗲𝗿𝘀𝗼𝗻𝗮𝗹𝗶𝘇𝗲𝗱 𝗷𝗼𝗯 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀: Web scraper that gathers some initial user information and explores a few sites like Craigslist, LinkedIn, Indeed and Monster for particular jobs which meet the user criteria and emails the user each morning with a list of jobs to apply for. 𝗖𝗦𝗩 𝘁𝗼 𝗖𝗵𝗮𝗿𝘁: A user uploads a CSV file and some information about the columns which is used to create 1 of [x] charts. Pie chart, time series, bar and scatter plots. The charts can be exported as an SVG or image type to be used on a site or report. 𝗠𝗲𝗮𝗹 𝗽𝗹𝗮𝗻𝗻𝗲𝗿: A user enters some information about their height, weight and lifestyle to get a custom meal plan and workout routine using OpenAI. Each week they get updates to their current plan based on progress and goals. 𝗧𝗵𝗿𝗲𝗮𝗱𝘀 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗲𝗿: This one can't be done... yet. Once Threads becomes web-based (and it will) users will want to schedule posts, gather stats on their posts and get ideas based on the most popular threads. There are already popular apps that do this for Twitter. I guarantee you will see a few million dollar businesses using this model. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝗮 𝗯𝗼𝗿𝗶𝗻𝗴 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀: I worked for a startup that scraped the web for information about shipping containers and served it in an easy to read format. There are lots of industries still using notepads, excel sheets and email for mission-critical workflows. Find them and figure out what people would pay to automate.	UNKNOWN	Brian	Jenney	6,778	6,778	61	13	1	0.011065	null	2023-08-07 08:34:46	https://www.linkedin.com/feed/update/urn:li:activity:7094339012525514752
urn:li:activity:7093274896373317633	100.5% of coding is debugging. Or something like that. If you're working on Node/Express apps, I bet you're making the same mistakes I did while debugging: - using 128 console logs - slamming your API with requests - crying a little There's a better way and I'm surprised more developers are NOT using the method I share below. Hope you find it useful.	VIDEO	Brian	Jenney	8,089	8,089	89	7	4	0.012362	null	2023-08-04 10:14:49	https://www.linkedin.com/feed/update/urn:li:activity:7093274896373317633
urn:li:activity:7092895548323598336	Eat code sleep is not a process for progress. It’s a recipe for burnout. I’ve seen some of you trying out this method and I’ve yet to see it work. Hell, I tried it myself. It led to: - anxiety - less enthusiasm for my work - decreased thought quality Counter-intuitively, the more I tried to cram in material or optimize my schedule, the less progress I was making. It was frustrating. For me, having a non-negotiable workout routine forced me to detach from work. Few things can interrupt my workout besides a sick kid or a critical bug at work. This is where I clear my mind and come up with my best ideas. Getting in shape was honestly a side effect of this routine and perhaps the best “hack” I’ve discovered for keeping me sane in a fairly stressful occupation. If you want my workout/diet routine that took me from a fluffy, anxiety-ridden developer to a less fluffy, and slightly less anxiety-ridden developer just DM your email and I'll send it over 💪.	UNKNOWN	Brian	Jenney	2,936	2,936	76	14	3	0.031676	null	2023-08-03 09:17:01	https://www.linkedin.com/feed/update/urn:li:activity:7092895548323598336
urn:li:activity:7092157126013292544	Let’s clear up some of the dumb advice you’ve read on LinkedIn: - Titles don’t matter - Seniors need at least [x] years of experience - Seniors are the best coders on the team - Get experience and the titles will come 𝗧𝗵𝗲𝘆’𝗿𝗲 𝗮𝗹𝗹 𝗿𝗶𝗴𝗵𝘁. 𝗔𝗻𝗱 𝘁𝗵𝗲𝘆’𝗿𝗲 𝗮𝗹𝗹 𝘁𝗲𝗿𝗿𝗶𝗯𝗹𝘆, 𝘁𝗲𝗿𝗿𝗶𝗯𝗹𝘆 𝘄𝗿𝗼𝗻𝗴. The Senior Developer title can be wildly different at each company. You still need to chase it. There’s a bit of an unhealthy obsession developers have (me included) with getting to Senior but there is a good reason. 𝘖𝘯 𝘰𝘯𝘦 𝘦𝘯𝘥 𝘰𝘧 𝘵𝘩𝘦 𝘥𝘦𝘷𝘦𝘭𝘰𝘱𝘦𝘳 𝘴𝘱𝘦𝘤𝘵𝘳𝘶𝘮 𝘪𝘴 𝘫𝘶𝘯𝘪𝘰𝘳. They are expendable for the most part. Cheap and plentiful and need lots of guidance. They are an important investment and also a bit of a gamble. 𝘖𝘯 𝘵𝘩𝘦 𝘰𝘵𝘩𝘦𝘳 𝘦𝘯𝘥 𝘰𝘧 𝘵𝘩𝘦 𝘴𝘱𝘦𝘤𝘵𝘳𝘶𝘮 𝘪𝘴 𝘵𝘩𝘦 𝘴𝘦𝘯𝘪𝘰𝘳. They can make or break your team through their influence on the codebase, team and processes. They squish the really tough bugs. They make sure the team doesn’t over-commit or refactor unnecessarily. They’ve made costly mistakes and understand how to avoid them. I know you’re in a rush but you can’t cheat time in the saddle. You’ll need to collect enough experiences, errors and tacit knowledge to make it to the next level. Take on some high-profile features, work with people outside of the eng department and of course... understand closure 😅.	UNKNOWN	Brian	Jenney	8,557	8,557	57	9	0	0.007713	null	2023-08-01 08:07:13	https://www.linkedin.com/feed/update/urn:li:activity:7092157126013292544
urn:li:activity:7091797921343406080	LinkedIn or Twitter fame is a silly goal if you’re building in public to land a role. Your real goal is to demonstrate technical depth and showcase your work. You want the right eyes on your profile. You don’t want sympathy for the 1000th rejection you’ve had (or maybe you do, I dunno actually). Instead of fishing for likes, try writing about: - a hairy bug you squished - your deployment strategy - how you’re handling QA - TDD? TaDD(testing after development is done)? Or no tests? - your take on React Server Components If you’re feeling brave, post a code snippet, seek feedback and watch how anyone who ever wrote a line of code becomes an expert on how you can optimize a for loop 😅	UNKNOWN	Brian	Jenney	6,933	6,933	105	20	2	0.018318	null	2023-07-31 08:15:41	https://www.linkedin.com/feed/update/urn:li:activity:7091797921343406080
urn:li:activity:7090361812239462400	I got called a cringe tech influencer earlier this year. It's ok. I've been called worse. 10 years ago my life was unrecognizable. I was lost in addiction and living a life that slowly catching up to me in the worst ways possible. I'm not exaggerating when I say that I was headed for death or prison. One intervention later and I started getting things together. - I got a normal job. - I read books. - I ate a sh*t ton of candy. - I started working out after gaining weight from all the candy. Then I started coding to pass the time. 𝗖𝗼𝗱𝗶𝗻𝗴 𝗱𝗶𝗱𝗻'𝘁 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝘆 𝗹𝗶𝗳𝗲. 𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝘀𝗼𝗯𝗲𝗿 𝗮𝗻𝗱 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗼𝘂𝘁 𝗱𝗶𝗱. The discipline from those efforts did give me the tools to learn to code at 30 with zero prior programming experience. I didn't use a computer for most of my adult life believe it or not. I'm not that old either (I think at least...) Anyways, I don't like sharing that part of my past. It's embarrassing, uncomfortable and seems so far away that it feels surreal. I share it every once in a while because I know that some of you may be struggling with your own demons or think people "like you" just aren't cut out for whatever goal is in your head. Don't listen to that voice. I linked up with one of your favorite influencers on LinkedIn Harley Ferguson through the power of networking (I follow my own advice 😉) who invited me to his podcast. We chat about coding, getting into tech and a little bit about my past. Check it out below. https://lnkd.in/gxAUf5T7	IMAGE	Brian	Jenney	9,353	9,353	171	31	1	0.021704	null	2023-07-27 09:53:22	https://www.linkedin.com/feed/update/urn:li:activity:7090361812239462400
urn:li:activity:7089990264987009024	Front-end development stopped being easy a while ago. It’s a lot less: - Move this a few px to the right. - Make this button a little greener. - Sprinkle a little JS to submit this form. - Translate this design to HTML and CSS. It’s a lot more: - Decrease the initial page load! - Oh, you know JS? Can you help debug this lambda function written in NodeJS? - SSG vs CSR vs SSR. - Who’s on-call to investigate the code pipeline being broken?! - Move this a few px to the right 😉.	UNKNOWN	Brian	Jenney	13,953	13,953	225	26	7	0.018491	null	2023-07-26 08:50:46	https://www.linkedin.com/feed/update/urn:li:activity:7089990264987009024
urn:li:activity:7089627876840378368	5 Biggest mistakes of my coding career? 1. Not learning the fundamentals before diving into frameworks 2. Refusing to admit when I didn’t know something 3. Only taking on tasks I knew I could finish 4. Not understanding how engineering relates to business goals 5. Staying silent 🤐 That last one hurt me the most. I thought I was playing it safe by taking on easy tickets. I nodded my head during estimation sessions and gave bland status updates. I never shared my ideas during meetings. I just wanted to blend in. It was the most dangerous thing I could’ve done. They say the tallest blade of grass is the first to get cut. Yeah, I guess. It’s also the one growing the fastest. Companies need average developers more than they’d like to admit. But, if career trajectory and increased hire-ability is your goal, then playing it safe is your greatest threat.	UNKNOWN	Brian	Jenney	6,382	6,382	110	17	5	0.020683	null	2023-07-25 09:14:54	https://www.linkedin.com/feed/update/urn:li:activity:7089627876840378368
urn:li:activity:7089265491260637187	A few controversial things I believe about careers in software development: 𝟭. 𝗕𝗲𝗶𝗻𝗴 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗶𝘀 𝗴𝗼𝗼𝗱 𝗲𝗻𝗼𝘂𝗴𝗵 I’m not saying this will make you rich or get promoted. I’m just saying you don't HAVE to climb the engineering ladder. Plenty of developers are very happy doing their work, going home and not touching their laptops for the weekend. 𝟮. 𝗔𝗹𝘄𝗮𝘆𝘀 𝗯𝗲 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝗶𝗻𝗴 Stability is a myth. - You can be talented. - Your company can be profitable. - You can still be let go. Nothing personal. Letting your skills get stagnant is a fast track to becoming obsolete in a fast-moving industry. 𝟯. 𝗬𝗼𝘂𝗿 𝗱𝗿𝗲𝗮𝗺 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗲𝘅𝗶𝘀𝘁 Your dream team might. When you say dream company, you (probably) mean: - High salary - Autonomy - Supportive team members - Learning opportunities Your manager and team have a lot more to do with your individual experience than the larger company. 𝟰. 𝗬𝗼𝘂𝗿 𝗽𝗲𝗼𝗽𝗹𝗲 𝘀𝗸𝗶𝗹𝗹𝘀 𝘄𝗶𝗹𝗹 𝗯𝗲 𝗺𝗼𝗿𝗲 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝘁𝗵𝗮𝗻 𝘆𝗼𝘂𝗿 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝘀𝗸𝗶𝗹𝗹𝘀… 𝘀𝗼𝗼𝗻 Knowing how to speak, write and influence are the skills that make developers indispensable. And high paid. Writing code becomes a given when you move past junior. Chat GPT can do a decent job of writing code and solving difficult bugs. You're a human. Lean into it.	UNKNOWN	Brian	Jenney	25,150	25,150	183	16	5	0.008111	null	2023-07-24 09:11:40	https://www.linkedin.com/feed/update/urn:li:activity:7089265491260637187
urn:li:activity:7088180633419591681	Ok, that's enough coding for you. Yes, learn closure, bind, call, apply, promises and whatever new framework just replaced the last new framework. (𝘨𝘰𝘰𝘨𝘭𝘦 𝘯𝘰𝘵 𝘢𝘯𝘰𝘵𝘩𝘦𝘳 𝘤𝘰𝘶𝘳𝘴𝘦 𝘪𝘧 𝘺𝘰𝘶 𝘸𝘢𝘯𝘯𝘢 𝘭𝘦𝘢𝘳𝘯 𝘵𝘩𝘢𝘵 𝘴𝘵𝘶𝘧𝘧 😉) But before you do all that, please learn how to use your code editor. Your future team mates will be grateful you did. Trust me. This article will take you through some of my favorite shortcuts for VS Code to make to you more efficient with your editor, save keystrokes and maybe save your life... or at least make you look like less of a n00b 😉.	ARTICLE	Brian	Jenney	6,840	6,840	54	11	6	0.01038	null	2023-07-21 09:38:38	https://www.linkedin.com/feed/update/urn:li:activity:7088180633419591681
urn:li:activity:7087822828309270528	A couple of developers I mentor got hired (𝘺𝘦𝘴 𝘥𝘦𝘷𝘴 𝘢𝘳𝘦 𝘴𝘵𝘪𝘭𝘭 𝘨𝘦𝘵𝘵𝘪𝘯𝘨 𝘩𝘪𝘳𝘦𝘥 𝘥𝘦𝘴𝘱𝘪𝘵𝘦 𝘢𝘭𝘭 𝘵𝘩𝘦 𝘴𝘵𝘶𝘱𝘪𝘥 𝘧𝘦𝘢𝘳-𝘮𝘰𝘯𝘨𝘦𝘳𝘪𝘯𝘨 𝘰𝘯𝘭𝘪𝘯𝘦). Now the real work begins: - Exploring a new codebase - Finding areas to make an impact - Learning the engineering culture - Using git… but like, for real this time - Having good 1 on 1s - Peer reviews - Estimations I now see that the period after the interview and offer is when developers need the most support. The job search is stressful. It's also the shortest stage of the developer life cycle. I'm going to release a developer survival guide in the next 6 weeks. Videos, documents and challenges to prepare you for the technical and non-technical parts of the job. I'm excited to put this together. It's the stuff I learned through trial and error over the years. It's GOING to make you a better developer and shorten your path to the next stage of your career. If you were recently hired or a manager who recently hired someone, what are some areas you think I should cover in my survival guide?	UNKNOWN	Brian	Jenney	9,091	9,091	135	10	3	0.01628	null	2023-07-20 09:32:09	https://www.linkedin.com/feed/update/urn:li:activity:7087822828309270528
urn:li:activity:7087453547742519299	I met a developer who created a full-stack app that worked pretty well. It even looked nice. But when I asked how it worked… Oof. 𝗔𝗻𝗼𝘁𝗵𝗲𝗿 𝗰𝗮𝘀𝗲 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹 𝗮𝗯𝘂𝘀𝗲. Too many developers fall into the trap of looking at a tutorial, following along with the instructor and typing what they type. 𝗧𝗵𝗲 𝗽𝗮𝘆𝗼𝗳𝗳: a shiny new app. 𝗧𝗵𝗲 𝗰𝗼𝘀𝘁: a false sense of mastery. It’s an enticing trap and it may even fool someone into hiring you. I know I'm not the only one to go through a tutorial, turn it off, open the code editor and realize I have no f*cking clue how to replicate what I just created. 😬 I'm no tutorial hater though. They have their time and place and I'll buy several more this year but I've learned the most when I take the training wheels off, get stuck and build something from scratch. It's the same approach I use with developers I mentor. I made janky apps and sites to learn new concepts, frameworks and even join a startup as a mid-level developer in a completely new tech stack. Every side project doesn’t need to be a masterpiece. Leverage them to learn what you won’t at work or what you would like to work on next. 𝗜𝗳 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 𝗺𝘆 𝘀𝘁𝗲𝗽 𝗯𝘆 𝘀𝘁𝗲𝗽 𝗴𝘂𝗶𝗱𝗲 𝗼𝗻 𝗰𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗮 𝘀𝗼𝗹𝗶𝗱 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗴𝗿𝗮𝗯 𝗶𝘁 𝗵𝗲𝗿𝗲: https://lnkd.in/gQ94kA97 𝗧𝗶𝗿𝗲𝗱 𝗼𝗳 𝘁𝘂𝘁𝗼𝗿𝗶𝗮𝗹𝘀? 𝗖𝗵𝗲𝗰𝗸 𝘁𝗵𝗶𝘀 𝗼𝘂𝘁: https://lnkd.in/ezpqmVbU	UNKNOWN	Brian	Jenney	23,821	23,821	182	25	9	0.009068	null	2023-07-19 08:46:02	https://www.linkedin.com/feed/update/urn:li:activity:7087453547742519299
urn:li:activity:7086728770186854401	The bootcamp is over. You wonder, “what now?” Do you create a side project? Pound LeetCode? Mass apply? Learn in public? Some bandicoot said you should just switch to CyberSec or DevOps. So many options. From speaking with a few hundred of you - I know that many of you just need direction. Here are the 2 paths I would explore if I was a new grad: 𝙁𝙤𝙧 𝙩𝙚𝙘𝙝𝙣𝙞𝙘𝙖𝙡 𝙨𝙠𝙞𝙡𝙡 𝗧𝗵𝗲 𝗗𝗦𝗔 𝗽𝗮𝘁𝗵 - go all in on DSA. Just understand you may limit the types of interviews you can “win” with this path. That’s OK. Many tech companies use DSA challenges and will continue to do so. Don’t just blindly tackle LC problems though: learn the structures, patterns and common approaches and practice with another human. 𝗧𝗵𝗲 𝘀𝗶𝗱𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝗽𝗮𝘁𝗵 - create a complex side project. What’s “complex”? I typically think of something you could potentially sell. If you’re unsure of where to start, look up APIs and build something around that API. Pick at least 1 or 2 new hot technologies to use that your education skipped. Typescript, NextJS, AWS and unit testing would be my top choices. 𝙁𝙤𝙧 𝙜𝙚𝙩𝙩𝙞𝙣𝙜 𝙝𝙞𝙧𝙚𝙙 𝗟𝗲𝗮𝗿𝗻 𝗶𝗻 𝗣𝘂𝗯𝗹𝗶𝗰 - use what you are learning for content and remember who your audience is. You want to create connections with software engineers and hiring managers so post the challenges you are facing, post some code for feedback and get into the weeds. You’re not posting for likes - you’re posting for the right kind of engagement from people in tech who can offer help, targeted advice or maybe a job. 𝗠𝗮𝘀𝘀 𝗮𝗽𝗽𝗹𝘆 - this works and I don’t care who says differently. Don’t JUST mass apply, however. Try a few resumes to see which one works. If you get no hits after 100 attempts, maybe hire a resume writer. Try multiple platforms including LI and those other older sites like Craigslist (yeah, they have a section for software). The only wrong path is the one you can’t commit to. Pick a strategy, stick with it, find what works and do more of that.	UNKNOWN	Brian	Jenney	14,300	14,300	144	14	7	0.011538	null	2023-07-17 08:47:05	https://www.linkedin.com/feed/update/urn:li:activity:7086728770186854401

Subsets and Splits

No community queries yet

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