urn string | text string | type string | firstName string | lastName string | numImpressions int64 | numViews int64 | numReactions int64 | numComments int64 | numShares int64 | numVotes int64 | numEngagementRate float64 | hashtags string | createdAt (TZ=America/Los_Angeles) string | link string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
urn:li:activity:6934853871227846656 | The problem with learning ReactJS before Javascript:
So here I was, doing a mock interview and the interviewee is attempting to implement the publish subscriber pattern.
No framework. Just plain old JS.
To their surprise, useState was not available within a Javascript object… oops. The majority of the interview was spent going over the basics of JS objects. Key-value pairs. Dot notation. Context.
You know, table stakes JS stuff.
I felt their pain. I started my Javascript career off with AngularJS and Jquery. I thought because I knew the framework, I knew JS. It took me years to return back to the fundamentals and really double down on the concepts that were holding me back.
I’m not saying don’t learn frameworks. They are a very useful abstraction to create apps.
Just don’t forget to build your house of knowledge on a solid foundation. | UNKNOWN | Brian | Jenney | 65,700 | 65,700 | 678 | 50 | 28 | 0 | 0.011507 | null | 2022-05-24 06:13:26 | https://www.linkedin.com/feed/update/urn:li:activity:6934853871227846656 |
urn:li:activity:6934491842264653824 | You finally did it! You got the freakin’ job!
DFS’ed so many trees.
Searched that sorted array… binar-ily.
Took home that project and beat it into submission… within the allotted time of course 😉.
Now what?
Some next steps you may want to consider now that you’re taking a brief hiatus from the interview grind:
✅ Get good at Git (or at least brush up on the basics like branching/pulling/commits)
✅ Dig into the deployment process and how code goes from a repository to being hosted at an address on the web
✅ Look up common design patterns in the framework you’ll be using - which I’ll bet you a bag of donuts includes one of the letters in MERN
✅ Learn to write some non-trivial tests
Oh… and share your experience!
Remember how you felt during your search and give back. What are the tips you recommend to others on the interview grind or looking to secure their first dev role? | UNKNOWN | Brian | Jenney | 1,892 | 1,892 | 14 | 4 | 2 | 0 | 0.010571 | null | 2022-05-23 06:14:51 | https://www.linkedin.com/feed/update/urn:li:activity:6934491842264653824 |
urn:li:activity:6933405036144205824 | So I did an interview last week.
I'm not looking for a job, either. I'm actually really satisfied in my current role...
I work with JS developers to nail down the concepts they need to pass interviews and I recommend they all enroll in pramp.com - a FREE mock interview site to help them with technical communication and getting over their nerves.
Anyways - here I was, taking my own advice - doing a pramp interview, with basically the lowest stakes possible:
No intention of interviewing in the near future and paired with a stranger I'll never see again.
You know what - I was still a bit nervous. I've done dozens of these mocks in the past year as well.
I fumbled with an async function.
Had to look up how to use mutation observer (I mean, right?)
Forgot to add a return statement to another function.
That's exactly why these types of mock interviews are so important IMO.
Perhaps you're less neurotic/anxious than me (I sincerely hope so) - even the coolest of cucumbers may pickle up a bit during an interview.
Don't let your "real" interview be your first interview. Nothing can really substitute the experience of walking through your code with another human being. | UNKNOWN | Brian | Jenney | 4,537 | 4,537 | 41 | 9 | 1 | 0 | 0.011241 | null | 2022-05-20 06:16:17 | https://www.linkedin.com/feed/update/urn:li:activity:6933405036144205824 |
urn:li:activity:6933039264502870016 | How to fail your next coding interview.
In a few easy steps 👇
✅ Don’t use Glassdoor.com to investigate previous interviews and the questions asked
✅ TeamBlind.com? Nah - no need to check out the super candid information about the company’s interview process there
✅ Only focus on DS/A - who tests front end stuff amirite? Djikstra, A*, BFS, DFS or die!!!
✅ A story in your back pocket about a complex project or a time you disagreed with a coworker? Never!
✅ Google basic concepts like “how to use a for loop” during the interview - you can’t memorize everything!
Now you’re ready to stick it to the man by wasting their engineers’ valuable time and spectacularly fail!
Anything I miss? | UNKNOWN | Brian | Jenney | 3,902 | 3,902 | 16 | 6 | 1 | 0 | 0.005894 | null | 2022-05-19 06:02:50 | https://www.linkedin.com/feed/update/urn:li:activity:6933039264502870016 |
urn:li:activity:6931955412548157440 | Attacks on Asians. A war in Ukraine. Women’s reproductive rights on trial. Now, another racially motivated massacre.
As a black-ish person (half, in case you were wondering), the tragedy in Buffalo, NY is particularly jarring to me. It makes me wonder if my family will be targeted at some point. If we're safe anywhere.
I usually don’t like to bring up these kinds of events outside of friends and family. I don't pretend to expect all my co-workers or internet peoples to feel the same and maybe I'm a little fearful that I'll unearth some opinions I wish I hadn't discovered.
I think some of you will know exactly what I'm talking about 😅 - and if you're a leader hoping to facilitate discussion or offer sympathy, don't be totally shocked if you have employees who would rather skirt the topic - perhaps because they share some of my concern.
At work I prefer to focus on, well, work stuff. Personally, it helps me feel stable and insulated from what feels like an increasingly volatile world. We all have different coping strategies.
I hope you’re doing whatever you need to do to deal with the staggering amount of terrible world news lately and if you've been directly or indirectly affected by the terrorist attack in Buffalo my heart goes out to you. | UNKNOWN | Brian | Jenney | 2,593 | 2,593 | 28 | 4 | 0 | 0 | 0.012341 | null | 2022-05-16 06:15:59 | https://www.linkedin.com/feed/update/urn:li:activity:6931955412548157440 |
urn:li:activity:6930156512459833344 | There are more than enough bootcamps out there for software engineers, but what about engineering managers?
I recently made the jump from IC to manager and am learning in real-time how different the roles are.
I was told by more than a few people that this truly is a career shift and I sort of wrote it off… I mean, how different could it be right?
Well, I write a lot less code which makes me feel less productive and it’s harder to measure myself as I might have in the past.
Leading and defining the vision for a team is nebulous, subjective stuff and learning how to relinquish control of technical decisions is certainly an area where I’ve had to improve.
Outside of the increase in meetings, I’ve found I really do enjoy working with and for my team through mentorship, finding opportunities at work and increasing their autonomy.
Some books I’ve read (or currently reading) which I’ve found useful as a new manager:
For Technical Career Paths
https://lnkd.in/gnfrjX-W
For Better 1x1’s
https://lnkd.in/gJ6JN5NX
For Creating Organizational Change
https://lnkd.in/gMjhMyzt
Now hook me up! What are some courses/books you recommend for new engineering managers? 👇 | ARTICLE | Brian | Jenney | 1,168 | 1,168 | 12 | 7 | 0 | 0 | 0.016267 | null | 2022-05-11 07:07:48 | https://www.linkedin.com/feed/update/urn:li:activity:6930156512459833344 |
urn:li:activity:6929421988159533056 | I’ve fooled a lot of people into thinking I’m smarter than I really am.
In my opinion, being “smart” is overrated.
What I respect more than genius is persistence.
I’ve met a lot of students who feel that [x] language/concept/framework is just too complicated for them. Only really smart people can learn that. Not people like them.
Listen, there are absolutely some geniuses lurking amongst us. The rest of us are somewhere on the scale of average.
With enough persistence and direction I 100% believe ANYONE can reach a certain level of proficiency with anything from calculus to Javascript.
Some people will “naturally” excel more than others, however I have yet to see anyone completely fail to grasp a concept with enough applied studying.
I may not be able to help you with calculus but if you’re feeling stuck with JS - give me a holler 😉 | UNKNOWN | Brian | Jenney | 3,024 | 3,024 | 38 | 8 | 0 | 0 | 0.015212 | null | 2022-05-09 06:29:04 | https://www.linkedin.com/feed/update/urn:li:activity:6929421988159533056 |
urn:li:activity:6928379302644248576 | Does your mouth turn to mush when trying to explain a technical concept?
I’ve seen it happen in a lot of interviews.
We usually write code in silence, alone, snarfing burritos and pounding fizzy canned waters.
Interviews force us to think out loud. All of the sudden that thing you thought you knew isn’t so clear.
Try this:
✅ Get loom.com (FREE)
✅ Record yourself going over a concept or explaining some code you wrote while on your LeetCode grind
✅ If you feel ambitious - share it on social media to help others
Speaking out loud in a low-stakes environment can help build your technical communication muscle.
Talking at a camera with a blurred out background to obscure the stack of laundry behind you is becoming an important skill in an increasingly remote-centric tech world. | ARTICLE | Brian | Jenney | 1,031 | 1,031 | 9 | 6 | 0 | 0 | 0.014549 | null | 2022-05-06 09:25:48 | https://www.linkedin.com/feed/update/urn:li:activity:6928379302644248576 |
urn:li:activity:6927618597632565248 | What is a framework developer?
I used to be one.
So what’s wrong with it?
Well, simply put, a framework developer is a person who depends on the abstraction of their programming language via a framework (or library in the case of ReactJS) to develop applications.
The problem with being a framework (or library) developer is that when your framework goes out of favor, so do you. Without a grasp of the fundamentals upon which it was built, you’re now tied to the abstraction.
So how do you go from framework dev to JS dev?
Double down on the fundamentals.
Async, closure, DOM, promises, prototypal inheritance, design patterns and of course 'this' 😉.
I'm particularly fond of this site for learning design patterns in JS: | ARTICLE | Brian | Jenney | 1,554 | 1,554 | 17 | 3 | 2 | 0 | 0.014157 | null | 2022-05-04 07:03:02 | https://www.linkedin.com/feed/update/urn:li:activity:6927618597632565248 |
urn:li:activity:6925830755331833856 | F*ck that TODO app.
Here's an interactive project I think will impress people.
Or at least learn ya' something.
Resume as an API.
Set up a Node/Express API with some routes which return information about you.
For example 'resume/work-history' or 'resume/education' which returns some JSON about you.
Set up middleware and error handling and deploy to the web for others to interact with.
If you want some starter code for setting up a Node/Express app, with tests and middleware and some routing complete with a short video walkthrough - just DM me with your email 🧐 | UNKNOWN | Brian | Jenney | 13,489 | 13,489 | 115 | 18 | 2 | 0 | 0.010008 | null | 2022-04-29 08:38:47 | https://www.linkedin.com/feed/update/urn:li:activity:6925830755331833856 |
urn:li:activity:6925459781558116352 | Worst interview I’ve had?
That’s a tough one. I mean, I’ve bombed my fair share of interviews, but the worst experience I probably had was during an interview at an office that allowed dogs.
I’m not a dog hater per se…. Also, not exactly a dog lover 😬.
So during an awkward white boarding session where I was flailing around with a canned answer for designing a rate limiter… the 2 dogs in the interview room begin barking loudly at each other and fight!
The respective owners pried the dogs apart as I stared in disbelief mixed with some healthy fear.
My average performance tanked after this incident… not because of it… but it certainly didn’t help.
Not surprisingly I was not offered the role.
So sad. Too bad.
I think the feeling that this wasn’t a good fit was mutual.
If you’re in a position to be picky in your job search, then do so. Job hopping and searching is stressful for most of us. Maybe your deal-breaker is fighting dogs in the office. Perhaps it’s weekend on call shifts?
I’m curious, what’s the worst interview experience you’ve had? | UNKNOWN | Brian | Jenney | 3,745 | 3,745 | 9 | 17 | 0 | 0 | 0.006943 | null | 2022-04-28 08:04:40 | https://www.linkedin.com/feed/update/urn:li:activity:6925459781558116352 |
urn:li:activity:6925068527045423104 | I don’t think I’ve met a developer who had a lack of desire to improve their skills.
What they (including me) usually lack is direction.
What does a lack of direction look like?
Endless tutorials.
A fuzzy end goal.
Dabbling across languages/frameworks/projects.
Without a clear direction it’s easy to go in the wrong one and end up somewhere you didn’t intend to.
So pick a direction, a desired result (and write them down 😉) and double down on the fundamentals of your chosen language, the most popular framework and testing libraries and create a single application that uses all this knowledge.
And of course, if you want some of my very opinionated opinions on your direction feel free to DM me. | UNKNOWN | Brian | Jenney | 6,624 | 6,624 | 77 | 14 | 0 | 0 | 0.013738 | null | 2022-04-27 06:09:58 | https://www.linkedin.com/feed/update/urn:li:activity:6925068527045423104 |
urn:li:activity:6924350528369938432 | Here’s a trend you front end devs should be aware of:
I work with about half a dozen developers, many of whom are currently interviewing.
Of the nearly dozen interviews between them, here’s the breakdown:
6 Take home projects varying from simple HTML/CSS forms to your typical React App that fetches data from an API.
2 On-sites where developers paired with others to build something like a game. Games seem to come up a lot lately 🤷🏽♂️.
2 Multiple question exams 👎- the lamest of all tech screens
0 Algorithm style questions… yet (there is a person ready to interview at some top tier companies where they will absolutely get some DS/A style questions)
Does this mean don’t study DS/A?
I’ll leave that up to you.
I still think understanding common data structures and algorithms for searching/sorting are important.
That being said - for you front end devs on the LeetCode grind, don’t forget to study front-end-y things.
Also - if you are interested in working with me to nail your JS interviews and go from framework dev -> JS engineer, just DM! | UNKNOWN | Brian | Jenney | 3,013 | 3,013 | 31 | 3 | 0 | 0 | 0.011284 | null | 2022-04-25 06:36:54 | https://www.linkedin.com/feed/update/urn:li:activity:6924350528369938432 |
urn:li:activity:6919649111293992960 | Coding... so easy. So freaking easy.
Yup, so easy you can get paid upwards of multiple 6 figures.
So easy bootcamps charge 10k+ to teach you.
So easy, that there is an emerging industry teaching current software developers how to pass wildly difficult interviews.
Too easy, right?
It really boils my potato when I see a post or ad claiming coding is easy. It both trivializes the accomplishments of people that go to school or learn on their own and land jobs and sets up aspiring developers for disappointment and insecurity when they don't just get it!
So no, coding !== easy.
['coding'].includes('easy')
const coding = !easy
That's good though. You don't want coding to be easy. It can be a worthwhile pursuit to learn and like anything worthwhile - like getting in shape, or writing a book or climbing a mountain - it will not be easy. | UNKNOWN | Brian | Jenney | 5,070 | 5,070 | 59 | 11 | 0 | 0 | 0.013807 | null | 2022-04-12 07:15:08 | https://www.linkedin.com/feed/update/urn:li:activity:6919649111293992960 |
urn:li:activity:6915681081086144512 | I’m a little apprehensive to admit this…
But, much of what I’ve done as a mentor for others is NOT technical.
Many times, I’ve simply offered an alternative point of view, a similar experience or a recommendation.
Hey, why don’t you apply for that role? Yeah, the one where you meet a little over half the requirements.
Yes, respond to that recruiter.
Oh, you’re interviewing with Amazon? I’d focus on graphs.
They offered you how much? Whoa! Now ask for x amount more.
Have you watched this video on recursion? It really clicked for me.
When I really dig into what is holding junior developers back in their career (and from my own failures), it IS often a lack of fundamental JS knowledge and design principles. You can read any number of articles and books on OOP, recursion, performance optimization and how React is the best… or worst… library out there.
What we are often in need of more than technical skill is focus, accountability and support. | UNKNOWN | Brian | Jenney | 2,383 | 2,383 | 27 | 4 | 0 | 0 | 0.013009 | null | 2022-04-01 08:27:36 | https://www.linkedin.com/feed/update/urn:li:activity:6915681081086144512 |
urn:li:activity:6914564085699264513 | You’re gonna break stuff.
In fact, you kinda need to.
Ever hang around a bunch of senior developers and hear their war stories?
The ubiquitous dropped database story.
The time they didn’t quite test their code well enough and released a show stopping bug.
The feature that introduced a security vulnerability.
I don’t want to romanticize shoddy work or careless mistakes but I do believe that your personal progress will necessarily put you in a position to break things.
Sure you can play it safe. Take on another ticket to change the color of a button. Update a test.
You can still learn this way.
However, if you want to make significant progress in your career and increase your technical ability at a faster pace, then take calculated risks and make decisions with consequences. | UNKNOWN | Brian | Jenney | 2,736 | 2,736 | 33 | 2 | 0 | 0 | 0.012792 | null | 2022-03-29 06:29:04 | https://www.linkedin.com/feed/update/urn:li:activity:6914564085699264513 |
urn:li:activity:6913130059025321984 | I play it pretty safe on here for the most part.
I talk a lot about code because that’s safe. And I know it decently… at least I think I do.
Just another nerd on LI spouting off about work and productivity in the web world… and there’s nothing wrong with that. In fact, I worked really hard to be able to write about this stuff.
About 8 years ago, though, I was struggling with addiction, involved in crime and was headed towards incarceration or death.
Maybe you’ve met me at a presentation, worked with me or slid in my DMs for my hot takes on your resume. You may have no idea about my past, and for the most part, I like to keep it that way.
I could easily gloss over the not so glorious aspects of my life prior to typing code into an editor, but I’ve met too many people who think that they have fallen too far down to climb back up or that people like them just aren’t cut out for [x].
I used to meet people in tech and get intimidated (I sometimes still do 🤫). Perhaps you feel the same. They went to [fancy] school. Have [inflated] title. Worked at [coveted tech company].
Realize everyone has a past, some more salacious than others, and whatever their current title, salary or company is, they started somewhere. You can also. | UNKNOWN | Brian | Jenney | 8,813 | 8,813 | 86 | 18 | 0 | 0 | 0.011801 | null | 2022-03-25 07:30:45 | https://www.linkedin.com/feed/update/urn:li:activity:6913130059025321984 |
urn:li:activity:6912026902648025089 | When am I gonna get hired?
You’ve seen the horror stories on LinkedIn.
I applied to 300 companies a day and didn’t get a single response!
I sent a box of donuts and a hand-penned letter to every engineer I met during my interview…. Nothing!
Listen - no one can tell you what your timeline for getting your first role as a developer will be.
There is some luck involved.
There’s also a lot of skill involved.
A solid technical foundation, 1 or 2 interesting projects, an optimized LinkedIn and consistency will work wonders. Boring stuff I know right?
Not a box of donuts. Not a different color scheme for your portfolio.
Learn stuff. Build stuff. Don’t quit. | UNKNOWN | Brian | Jenney | 10,435 | 10,435 | 85 | 18 | 4 | 0 | 0.010254 | null | 2022-03-22 06:27:12 | https://www.linkedin.com/feed/update/urn:li:activity:6912026902648025089 |
urn:li:activity:6911652884296216576 | The Glassdoor Interview Hack Strategy:
Sure, you could study for the technical interview using the shot gun approach... a little of this, a little of that or just fallback on what you THINK they might ask. Better than… well, not studying.
As a front end developer I hope you're covering the most common concepts you're likely to encounter: bind, call, apply, closure, string and array manipulation, promises…. Jeez that’s a lot already.
Luckily, a lot of companies have the exact questions you are likely to encounter on Glassdoor.
Previous candidates will often leave their experience, the questions they were asked and even the answer!
Oftentimes, the company in question doesn’t even slightly update their interview based off this knowledge.
Use that to your advantage.
Hell, I’ve talked to Google recruiters who suggest you do as much for their interview.
Other sites where people discuss their interview experience are CareerCup and of course Blind.
#juniordeveloper #interviewpreparation | UNKNOWN | Brian | Jenney | 1,562 | 1,562 | 12 | 0 | 0 | 0 | 0.007682 | #juniordeveloper ,#interviewpreparation | 2022-03-21 05:40:59 | https://www.linkedin.com/feed/update/urn:li:activity:6911652884296216576 |
urn:li:activity:6909490627101544448 | Yes, there are more meetings.
But, that’s the probably the most trivial change I’ve experienced in making the change from IC to manager.
I’m still learning how to be a technical manager and I wrongly assumed it would be more technical than management.
I’ve learned quickly how important it is to manage expectations, morale and dig into what motivates others. Everyone isn’t motivated or inspired in the same ways I am and though that seems obvious when writing it, this was definitely a moment of epiphany for me.
The most rewarding part of management for me is the ability it gives me to mentor and help shape others’ career… ideally for the better.
The most difficult part? Relinquishing control of the code and giving room for others to make mistakes to learn… without jumping in too soon… or too late.
Outside of that… yeah, there are a lot of meetings 😅.
Question:
For those of that you that made the jump from IC to manager - what was the biggest change you experienced? | UNKNOWN | Brian | Jenney | 2,109 | 2,109 | 14 | 6 | 1 | 0 | 0.009957 | null | 2022-03-15 06:28:57 | https://www.linkedin.com/feed/update/urn:li:activity:6909490627101544448 |
urn:li:activity:6908104183745015808 | Easy way to have your portfolio project stand out…
Unit tests.
Yup. It’s not sending a box of donuts to the hiring committee… though that would be nice. Mmmmm, donuts.
Most bootcamps && CS programs simply don’t teach unit testing, especially front-end unit tests. Those I’ve seen that do, don’t have time to dig past the trivial.
Read up on the controversial opinions surrounding mocking, e2e and TDD and DDT… one of those I just made up 😉.
Jest/Mocha/Chai/Testing-Library are the most common frameworks/libraries you WILL encounter on a full stack or front-end focused team. Why not use them now in a side project now?
It’s like learning to code all over again, which, depending on your love of coding may sound really exciting or kinda terrifying.
Here's a video walking you through writing your first simple Jest unit test ⬇️ | EXTERNAL_VIDEO | Brian | Jenney | 4,181 | 4,181 | 45 | 12 | 4 | 0 | 0.01459 | null | 2022-03-11 09:39:43 | https://www.linkedin.com/feed/update/urn:li:activity:6908104183745015808 |
urn:li:activity:6906602902526263297 | Are any of us really self-taught developers?
Throughout my career I’ve relied on the developer community to fill in the gaps in my knowledge.
I attended a meetup nearly 10 years ago where a developer showed me how to use Sublime to write some simple HTML code. I had been using an online IDE until this point and a plain text editor 😬.
A former co-worker spent an afternoon walking me through some of the principles of OOP at my first job.
A friend of a friend who worked for Slack wrote me a detailed page-long email about what I needed to study to become a web developer and materials/books he recommended. (I was like, Slack? What an odd name for a startup… sure it will never go anywhere 😅)
One of my first managers introduced me to the concept of Big O.
I can’t count the number of Udemy videos I’ve purchased over the years… (how many I finished is another story 🤫)
None of us really learn in a vacuum, and the dev community, not without its flaws, has a lot of awesome and selfless people who are happy to help.
That being said, LI has millions of people here at your fingertips. DM some of them. Ask them about what they do. Get advice. Then return the favor! | UNKNOWN | Brian | Jenney | 5,010 | 5,010 | 36 | 16 | 0 | 0 | 0.010379 | null | 2022-03-07 06:14:10 | https://www.linkedin.com/feed/update/urn:li:activity:6906602902526263297 |
urn:li:activity:6906359671712546816 | Now this could be worth checking out ⬇️ | UNKNOWN | Brian | Jenney | 689 | 689 | 5 | 0 | 0 | 0 | 0.007257 | null | 2022-03-06 14:07:39 | https://www.linkedin.com/feed/update/urn:li:activity:6906359671712546816 |
urn:li:activity:6904807101877866496 | Yeah, they’re probably not going to merge that PR.
You’ve probably heard that contributing to open source projects can really make you stand out. That’s true.
The reality is that the maintainers of uber-popular libraries are understandably very picky about what they allow into their masterpieces.
The project set up, PR process and time needed to really solve any less than trivial bug for most popular projects on Github can be incredibly time consuming and depending on the issue you are solving… not really worthwhile.
If your goal is to stand out as a junior developer, gain some valuable skills and learn something new, make your own damn project.
Been deploying to netlify? Try AWS.
Want to write Javascript but, like, a lot more of it? Try Typescript.
Never used Vue.js?… good.
Anyways, yeah. Build stuff. Stuff that you actually like and can talk about with pride. | UNKNOWN | Brian | Jenney | 9,846 | 9,846 | 56 | 21 | 2 | 0 | 0.008024 | null | 2022-03-02 07:18:18 | https://www.linkedin.com/feed/update/urn:li:activity:6904807101877866496 |
urn:li:activity:6904067666693226496 | The invasion of Ukraine may further support your view that the world is indeed a f*cked up place… but I’m continually amazed at the stories I read on here about regular people, from software developers to stay-at-home mothers bearing arms to protect their country and generally just working together to do whatever’s necessary to survive.
Massive corporations are divesting from Russian companies against their own economic interests.
A billionaire offered free internet?!
At our core, I believe humans are resilient, amazing and generally good. To help Ukrainians and their army ⬇️ | UNKNOWN | Brian | Jenney | 148 | 148 | 0 | 0 | 0 | 0 | 0 | null | 2022-02-28 06:20:03 | https://www.linkedin.com/feed/update/urn:li:activity:6904067666693226496 |
urn:li:activity:6902617465398939648 | Yay 🥳. You got the job. You traversed all the trees. You told them about the time you didn’t punch your co-worker for deploying a code change that broke the pipeline on a Friday. Team work.
Now what?
Joining a new team, especially as a junior can be intimidating.
You may not feel you have a lot to offer the team at this stage and you’re likely right… kinda.
A fresh perspective on processes, coding standards and culture can work in your favor.
Question why - politely of course and from a place of genuine curiosity. If you’re feeling bold, offer suggestions to improve.
Code reviews are another place you can stand out.
Be thorough in your review and ask why certain choices were made. Add links to articles. Give props when you see something particularly clever or that taught you something you didn’t know.
Volunteer for at least one ticket/project that will stretch your capabilities. Changing the color of a button is a great first task but if you really want to grow, take on a ticket you’re not quite sure how to handle or in a part of the codebase you haven’t explored.
What happens after nailing the interview is a much less clearly defined process and it’s easy to play the background as a junior developer.
What’s the worst that can happen? You get canned and spin the interview wheel again - and you’re already so good at traversing trees 😉 | UNKNOWN | Brian | Jenney | 2,322 | 2,322 | 28 | 1 | 0 | 0 | 0.012489 | null | 2022-02-24 06:17:28 | https://www.linkedin.com/feed/update/urn:li:activity:6902617465398939648 |
urn:li:activity:6901887157133279232 | Part of your job as an interviewee during an interview is be like-able.
Especially if you are more junior. You will have less technical capability and the ultimate decision may boil down to who the team perceives as easier to work with.
Is it fair? I don't know. But it's reality. And I want to see you hired, not tell you how things SHOULD be.
One of the easiest ways to become more like-able is to ask questions about the other person (this also works in non-interview settings 😉).
Humans love is talking about ourselves!
📌 What do you like most about your job here?
📌 What’s one thing you would change on your team?
📌 Can you walk me through <deployments/incident handling/some process> ? (this question may actually raise some red flags for you - oh you do on-call 1x per week eh... interesting)
So keep reversing those linked-lists or balancing trees or whatever but don't forget to have some canned questions in your back pocket once you hit the optimal solution. | UNKNOWN | Brian | Jenney | 3,794 | 3,794 | 31 | 10 | 0 | 0 | 0.010807 | null | 2022-02-22 05:55:29 | https://www.linkedin.com/feed/update/urn:li:activity:6901887157133279232 |
urn:li:activity:6900519294891900928 | Happy Freakin Friday!
I'm curious, are there any IT Support professionals in my network (Database administrator, IT specialist, tech support specialist, help desk technician, IT support, etc.)?
I'm sure there are and I could use your help.
Don't worry, didn't spill coffee on my laptop or anything... 😅. I have a much higher calling for you 🙇🏽♂️ 👇🏽
Damany M. Fisher, Ph.D. works with an amazing program dedicated to helping formerly incarcerated people find work in the IT support field and could use some insight from you!
Feel free to comment or DM me or Damany M. Fisher, Ph.D. if you'd like to share your insight and experience for a very worthwhile and important cause.
#itdevelopment #databaseadministrator #helpdesksupport #helpingothers | UNKNOWN | Brian | Jenney | 513 | 513 | 2 | 1 | 0 | 0 | 0.005848 | #itdevelopment ,#databaseadministrator ,#helpdesksupport ,#helpingothers | 2022-02-18 11:20:05 | https://www.linkedin.com/feed/update/urn:li:activity:6900519294891900928 |
urn:li:activity:6900072604447711232 | So I still deal with impostor syndrome.
I know what you might want to hear or have already heard:
It just gets better and you're fine the way you are. Think positively or wait it out or go somewhere that makes you feel less impostor-y.
🌈 🦄 🥰
Except, that didn't really work out for me and I will never give you advice that I wouldn't follow.
For me, impostor syndrome signals a disparity in the skills I think a person in my position should have and my current capabilities.
What I've done to close this gap is list out the skills/traits I feel like I'm supposed to have. Often times the list is not as daunting as I imagined.
I start working on this list, little by little. I understand the areas that will make me feel more "worthy" of my position and attack them. Now I have "proof" that I am where I'm supposed to be.
In my experience, it's rare that others perceive us as impostors. People are too caught up in their own world to really care about you 😉. The insecurity that often accompanies change is indeed in your head but that doesn't mean you should ignore it. Identify, attack, move on and repeat.
#impostersyndrome #impostorsyndrome #howdoyouspellimpostor | UNKNOWN | Brian | Jenney | 3,754 | 3,754 | 50 | 9 | 1 | 0 | 0.015983 | #impostersyndrome ,#impostorsyndrome ,#howdoyouspellimpostor | 2022-02-17 05:45:06 | https://www.linkedin.com/feed/update/urn:li:activity:6900072604447711232 |
urn:li:activity:6898986961206423552 | Interviews are weird.
We do them so infrequently that we never quite get used to them.
That’s also why I suggest you never really stop preparing for them…
Do 1 Leetcode problem a day. Read 1 Article a week. Have 1 Side project. Nothing crazy or super time consuming but these small deposits compound over time. You’ll be a better engineer, more prepared for whatever comes your way and maybe, most importantly, more confident.
The worst thing you can do is sit on the sidelines out of fear. Hoping your job is safe. Waiting for a new manager to see your potential or give you interesting work.
My best advice, that even I find difficult to follow, is to separate your feelings from the interview and treat it as a game... a winnable game. You absolutely can't win if you don't play. | UNKNOWN | Brian | Jenney | 6,572 | 6,572 | 56 | 10 | 2 | 0 | 0.010347 | null | 2022-02-14 05:51:08 | https://www.linkedin.com/feed/update/urn:li:activity:6898986961206423552 |
urn:li:activity:6897548952493797376 | Imagine this:
You, on the LeetCode grind, traversing trees, linking lists, BFS'ing graphs, exploring the time and space tradeoffs between sorting algorithms.
You walk into your interview. Or Zoom. Whatever.
They ask you to build a snake game using Vanilla JS.
F*ck.
If you truly are aiming for FAANG roles then I totally understand the LC grind. Honestly, I think LC is a great source for learning and problem solving, even if you aren't interviewing (another story).
But why are so many devs, especially front end, optimizing their interview prep for Google when they won't be interviewing there?
I'm not saying not to go down the LC path, but make sure you are also studying for the kinds of problems you're almost certainly going to encounter in non-FAANG interviews.
#interview #frontend #algorithms #leetcode | UNKNOWN | Brian | Jenney | 15,098 | 15,098 | 68 | 23 | 2 | 0 | 0.00616 | #interview ,#frontend ,#algorithms ,#leetcode | 2022-02-10 06:37:00 | https://www.linkedin.com/feed/update/urn:li:activity:6897548952493797376 |
urn:li:activity:6897173436343435265 | The first 3 years of my career as a software developer, I barely said a word during meetings.
So what changed?
Well, one day I got called out on it. My manager told me I needed to share my opinions more often and ask questions when I didn’t understand them. It stung a bit when he told me this but I took it to heart.
I made it a point to ask a question during each meeting. At the time, it was uncomfortable and I’d “cheat” by writing down a question before the meeting started or during, so I’d have something to say.
Nowadays, speaking during meetings doesn’t carry the same weight it used to, though it’s still not completely natural to me.
One of my goals this year was to use my voice more on LinkedIn. It still feels uncomfortable if I’m being honest but a hell of a lot less so than it used to. I’ve met a lot of great people and reconnected with others as a result.... also some weirdos, but hey, I can't complain 😅.
The simple of act of sharing your thoughts or questions at work can position you as leader on your team. It can inspire others to speak and introduce new points of view. It can lead to better discussions, better software and processes.
So say something. Write something. Start with a question. Even if you have to write it down beforehand 😉. | UNKNOWN | Brian | Jenney | 3,937 | 3,937 | 53 | 1 | 0 | 0 | 0.013716 | null | 2022-02-09 05:44:50 | https://www.linkedin.com/feed/update/urn:li:activity:6897173436343435265 |
urn:li:activity:6896452190727217152 | If you are looking for your first role in software and holding out for a company with a diverse team (in terms of race and gender), I hate to tell you but you may be searching for a while.
For a snapshot of the demographics of professional developers, check out StackOverflow’s yearly survey https://lnkd.in/grs5yMFt
I spoke with a recruiter who told me a lot of the bootcamp grads she was speaking with were apprehensive about joining non-diverse companies… 😬
My concern upon hearing that is that companies whom are attempting to recruit (and retain) people who are not well represented in tech will be negatively impacted by this sentiment.
I get it though.
It’s tough to be the only ____ on a team or at a company. You stand out. It’s harder to hide. I still suggest you do it. If not for your own benefit then for the benefit of others that may come after you, searching for another ____ zoom square on their first day. | ARTICLE | Brian | Jenney | 1,399 | 1,399 | 10 | 5 | 0 | 0 | 0.010722 | null | 2022-02-07 05:58:52 | https://www.linkedin.com/feed/update/urn:li:activity:6896452190727217152 |
urn:li:activity:6895122999553462272 | I know how much developers love to wind down a long day of coding with a good book like Cracking the Coding Interview or Clean Code or maybe a book exploring the time and space trade offs between different sorting algorithms, BUT, if you want a book that's a little lighter and perhaps more related to what you will experience as a developer, I'd highly suggest The Phoenix Project.
Without giving too much away, it's a novel about a struggling IT department under the gun to turn things around. It has some practical advice peppered throughout the book and if you've ever worked on a dev team you'll immediately recognize some of the personalities and issues presented in it. | ARTICLE | Brian | Jenney | 814 | 814 | 13 | 4 | 0 | 0 | 0.020885 | null | 2022-02-03 13:57:08 | https://www.linkedin.com/feed/update/urn:li:activity:6895122999553462272 |
urn:li:activity:6893939033924345856 | I was recently working with some students enrolled in a very popular bootcamp. They were incredibly bright and seemed to have a decent understanding of how to use ReactJS as well as DS/A.
When we were pairing on how to write an event handler for a button, things took an interesting turn...
For the most part, they seemed unfamiliar with some basic syntax for markup as well as very common elements like header and paragraph tags.
This is a trend I've noticed at some bootcamps - basically skipping over HTML and CSS. 😬 Like, hey we know you spent ~20k to learn to code but you figure it out smarty-pants.
It's great you can traverse a binary tree or know the space/time tradeoffs between sorting algos... but if you don't also know the difference between an id and a class, you're going to find it difficult to nail your interviews... or, you know, make websites and stuff.
My non-exhaustive list of FE concepts to brush up on:
📌 Event delegation
📌 ID vs class
📌 Event capturing/Event bubbling
📌 HTML5 semantic elements | UNKNOWN | Brian | Jenney | 1,901 | 1,901 | 16 | 7 | 1 | 0 | 0.012625 | null | 2022-01-31 07:32:28 | https://www.linkedin.com/feed/update/urn:li:activity:6893939033924345856 |
urn:li:activity:6892470069998317568 | I work with a team of developers, mostly in the beginning stages of their careers, and am consistently shocked by how much more they know than I did at that stage.
When I first started writing code, I had the confidence one can only have from being completely ignorant of all the things I did not yet know. This phenomenon is known as the Dunning-Kruger effect.
As a newly minted Engineering Manager, I am now fully aware there are things I do not know, which I don't yet know I don't know...🤔🧐
Like most career transitions, this one has invited impostor syndrome and doubt into my head but also a lot of joy as I get to spend more of my time mentoring others and hopefully creating a culture where people feel safe and included, among all the other software-y things we need to do.
I'm curious, what are some traits of the best managers you've had? Worst? | UNKNOWN | Brian | Jenney | 2,145 | 2,145 | 22 | 11 | 0 | 0 | 0.015385 | null | 2022-01-27 06:15:20 | https://www.linkedin.com/feed/update/urn:li:activity:6892470069998317568 |
urn:li:activity:6891739880595058688 | Over the weekend, a few people from LI reached out to me that are recent bootcamp grads. Like many of the conversations I have with recent grads, it centered on the big question:
How do I get hired?
I don't pretend to have some fool-proof strategy for landing that first role but I do have some opinions and observations that support them from working at bootcamps.
✅ Stop applying for Junior roles, only. They are highly competitive and usually mean a lowball offer.
✅ Use other platforms besides LI. Craigslist, anyone? You'd be shocked how many businesses still post CL ads for developers 🤷🏽♂️. Also checkout angel.co, a job board for startups.
✅ Get 500 connections on LI. It will make you more discoverable when recruiters search for developers using keywords like "Javascript".
✅ Don't stop coding. Keep your Github profile up to date by doing small commits regularly. A lot of employers will look at your GH history and a sharp drop in commits after graduating a program can be a red flag to many people.
✅ Remember luck plays a part in this. This is ultimately a numbers game. Don't stop playing the game until you've "won". The worst thing you can do is give up when things get tough.
✅ Don't do the same damn thing if it's not working. No interviews? Tweak your resume or LI profile. Remove the open to work badge maybe. Failing every interview? Invest in LC premium or AlgoExpert or a mentor to target your weak areas.
Whew... now tell me, what did I miss here? Especially if you're a recent grad that landed a role as a developer, I'm curious to hear what worked for you? | ARTICLE | Brian | Jenney | 3,061 | 3,061 | 38 | 11 | 0 | 0 | 0.016008 | null | 2022-01-25 05:53:49 | https://www.linkedin.com/feed/update/urn:li:activity:6891739880595058688 |
urn:li:activity:6890279660073172992 | A few years ago I was working at a bootcamp and a student was having difficulty with JS. Don’t we all 😉? He approached me after class and I was short with him, as it had been a long day.
He said something to the effect of, “People like you may just get this stuff, but it doesn’t come easy to people like me.”
I apologized and told him we’d work together to get him caught up. He left and I thought, I’ve done it. I’ve finally done it. I’ve successfully reinvented myself.
About 10 years ago I was doing the kind of work that you can’t put on LinkedIn… I was also deep into multiple addictions. 8 years ago, I got sober and found I had a lot of time on my hands. I filled it with code. Building janky sites and barely working apps. With a lot of support and a healthy dose of luck, I landed my first role as a developer.
Lots of coding, studying and fighting against the doubts in my head later and I somehow ended up managing a team of engineers. I can barely believe it sometimes… most times.
I don’t really like to share much about my past. What will people think of me? I wonder. But I also know that I when I read about the struggles of people in positions I aspire to, I feel less alone, like maybe it's possible for me too.
I hope if you’re struggling with addiction or a life that you’re not proud of that you read this and also feel less alone and that no matter how far down you might feel, there is a path out.
I’m no doctor. I’m barely an engineer 😅. But I do know the struggle of sobriety, addiction and reinventing yourself. So if you want any advice or just to vent, my DM is always open. | UNKNOWN | Brian | Jenney | 4,992 | 4,992 | 68 | 13 | 0 | 0 | 0.016226 | null | 2022-01-21 05:11:26 | https://www.linkedin.com/feed/update/urn:li:activity:6890279660073172992 |
urn:li:activity:6889286257571192832 | I've been very fortunate to have some great managers throughout my time as a software developer. Each one has impacted my career and outlook in a different way. While I valued their technical leadership, what I'll remember most is the critical feedback they gave me, the support they offered during personal issues, the opportunities they gave to me that were just outside my comfort zone or simply taking a chance on me.
It's easy to get caught up in the technical aspect of being part of a software team (I mean, it's a pretty technical space) but the most impactful events in my career have little to do with the code I wrote. | UNKNOWN | Brian | Jenney | 1,480 | 1,480 | 24 | 3 | 0 | 0 | 0.018243 | null | 2022-01-18 11:24:00 | https://www.linkedin.com/feed/update/urn:li:activity:6889286257571192832 |
urn:li:activity:6887802540742844416 | If you're concerned with being pigeonholed as a React developer, or an Angular Developer, or a Vue developer (people use Vue right? 🤔) I would spend some time focusing on design patterns.
For years, I worked with AngularJS. I was pretty good at it. Then I switched to Ember. I realized I wasn't so much a Javascript developer as I was an AngularJS developer... and we see where that version of Angular ended up...
I switched again to using React and Redux. More magic I struggled to understand.
I would have had gained a quicker understanding of any of these frameworks/libraries had I studied the underlying patterns they used. Ember and the decorator pattern. Redux and the observer pattern. Angular and dependency injection. React and function composition. Vue and... whatever it uses.
If you're a JS developer (aren't we all 😉) check out this site which breaks down common design patterns in Javascript | ARTICLE | Brian | Jenney | 1,816 | 1,816 | 15 | 7 | 1 | 0 | 0.012665 | null | 2022-01-14 09:08:14 | https://www.linkedin.com/feed/update/urn:li:activity:6887802540742844416 |
urn:li:activity:6887098200906457088 | The LC grind has really spawned an industry of apps and courses dedicated to teaching engineers how to pass these types of interviews. Imagine rolling into an interview for FE role, after weeks of studying heaps, graphs and DP only to be asked to re-create a debounce function 😅 | UNKNOWN | Brian | Jenney | 530 | 530 | 3 | 0 | 0 | 0 | 0.00566 | null | 2022-01-12 10:29:27 | https://www.linkedin.com/feed/update/urn:li:activity:6887098200906457088 |
urn:li:activity:6886681070876655617 | Who am I to negotiate?
This is what I was thinking after getting that first job offer as a software developer. It was surreal for me. When the recruiter called me and asked me what my ideal salary would be I gave a number so low it's laughable in retrospect.
This number was so low in fact, that they gave me more than I asked for... it was still pretty low.
Years later, I would get an offer for double my salary! Negotiate? For What?
I mean, who was I? Here I was, a fairly new developer, getting offered more than I'd imagined and saddled with intense self-doubt. Would they rescind the offer if I asked for more? Laugh me off the phone call? Would my expectations change with more money?
It took me about 4 years until I figured out the power of salary negotiations by taking the advice from a recruiter I was working with. It was uncomfortable and nerve-wracking. But it worked.
Salary negotiation is an unfortunate game that too often leaves POC and women getting shorted, either from ignorance that there is a game being played, fear of rejection or of coming off as ungrateful.
You MUST negotiate. The first offer you receive is almost always lower than what is available. This is because, the company EXPECTS that you will negotiate. When you don't, you've made their job much easier and in return you've left money on the table.
Negotiating isn't always about salary either. Maybe you need an additional day to work from home. Shorter hours on a certain day of the week or a sign on bonus.
I don't care if it's your first role. Negotiate. More money than you expected? Negotiate. Don't want to negotiate? Even more important that you negotiate. 😎 | UNKNOWN | Brian | Jenney | 2,870 | 2,870 | 32 | 12 | 0 | 0 | 0.015331 | null | 2022-01-11 06:51:55 | https://www.linkedin.com/feed/update/urn:li:activity:6886681070876655617 |
urn:li:activity:6885335375141838848 | I've failed a lot in life and in my career so I appreciate reading the stories of people who take the chance and share those failures/setbacks publicly.
What's equally as important though, is what you learned from that failure. Whether is was a job interview or something with more dire repercussions like falling into addiction.
It's comforting to realize others aren't impervious to moments of weakness, cracking under pressure or bombing a dozen interviews. Stories like these can make us feel less alone. What's even more valuable though, is hearing what was learned/gained after the failure.
So you failed another interview? Ok, it happens. What now? Ideally you identify an area where you need to focus. Maybe technical communication, maybe don't drink two Vietnamese Iced Coffees 😬 beforehand.
Deleted a column from a production database with no back up perhaps? Hey, haven't we all? Hopefully something was learned there. Or you're likely doomed to repeat this mistake.
Give us some insight into your failure. Help yourself (and us!) avoid the same pitfalls. | UNKNOWN | Brian | Jenney | 333 | 333 | 5 | 0 | 0 | 0 | 0.015015 | null | 2022-01-07 13:44:36 | https://www.linkedin.com/feed/update/urn:li:activity:6885335375141838848 |
urn:li:activity:6884877543023931393 | I've probably solved more difficult coding problems by going for a run than just powering through a mental block (aka endlessly staring at the screen, coding in circles).
Apparently, there's some science to back up this hack of mine. Exercise can increase brain plasticity by stimulating growth of new connections and also decrease your stress hormones 🧐. I just know that for me, I get my best ideas when I'm sprinting around Lake Merritt.
I remember pairing with a more seasoned developer and after a day of working through an issue we could not solve he calmly said "Let's check this out first thing in the morning. A night of sleep will probably give us the answer we need." I nodded my head, not really convinced, but what did I know? Apparently less than him, because the next day we reconvened and solved the sh*t out of this problem. He suggested this more than a few times when he saw me struggling and generally his advice worked for me.
Whether it's a run, walk or just staring at something else for a while I suggest you <insert alternative activity here> when you're stuck on a problem. | UNKNOWN | Brian | Jenney | 2,145 | 2,145 | 30 | 18 | 0 | 0 | 0.022378 | null | 2022-01-06 07:25:21 | https://www.linkedin.com/feed/update/urn:li:activity:6884877543023931393 |
urn:li:activity:6884137594884624384 | So you really want a remote job eh?
Coding in your pajamas. Snarfing burritos with your camera turned off on Zoom. Or perhaps you want to avoid mega-commutes and spend more time with your family. Whatevs.
If I were a recent bootcamp grad, I would certainly consider non-remote jobs in my search (if possible - I realize living outside tech hubs can limit this possibility). According to LinkedIn, remote jobs can get up to 2x more applicants than non-remote.
Your first job in software can be notoriously difficult to land - so instead of spinning your wheels and courting luck by applying to highly competitive remote roles, FAANG and FAANG adjacent companies, try for non-tech companies and non-remote roles.
I listen to people who I consider to be smart, in the hopes I can perhaps be as smart as them one day. One of these smart people told me that your first job is just preparation for your second job, the one you really want. | UNKNOWN | Brian | Jenney | 1,396 | 1,396 | 20 | 4 | 0 | 0 | 0.017192 | null | 2022-01-04 06:25:03 | https://www.linkedin.com/feed/update/urn:li:activity:6884137594884624384 |
urn:li:activity:6882333055856574464 | Can you be just an average #softwareengineer as a POC (person of color)?
I would hope so.
There is a prevalent feeling though, from many of the developers I've spoken with (and that I share) that as POC in software development and often the only <insert ethnicity/gender here> on a team, you must go above and beyond. You need to continually prove you belong.
Let me paint a scenario for you: you're already dealing with the regular flavor of impostor syndrome just being a developer or joining a new team and to top it off you're worried that any mistake will now label you as a "diversity hire." Ahh - that's how they got this job, your co-workers will think.
It's also just harder to hide during meetings. You inevitably stand out. And you're acutely aware of this fact. You feel like your silence is magnified. Loud silence... 😅
Is this paranoia? Perhaps (though if you read through the comments on Blind app... maybe not 😬). Do more of your black/brown/other coworkers feel like this than you may be aware of? Based on the conversations I've had over they years... absolutely. | UNKNOWN | Brian | Jenney | 829 | 829 | 10 | 0 | 0 | 0 | 0.012063 | #softwareengineer | 2021-12-30 06:54:28 | https://www.linkedin.com/feed/update/urn:li:activity:6882333055856574464 |
urn:li:activity:6881254544643366912 | Do you need to have a side project as a software engineer?
Well, like most things in life... it depends.
I recommend anyone that wants to expand their toolset and knowledge outside of what is offered at their current role, take on a side project. Ideally one that uses some technology, language, or framework that you haven't been exposed to.
I started writing code about 7 years ago using .NET, C#, SQL and #angularjs . And I thoroughly enjoyed it... don't judge me.
But, I kept hearing rumblings about this framework, ReactJS. Surely it will fade into obscurity I thought. AngularJS being a superior framework and all.
Plot twist. ReactJS blows up and Angular make a clean break from AngularJS to release Angular as we now know it.
I was working on a side project at the time and decided to try #reactjs out. Hated it. Props, class based components and a large mental shift AngularJS's two-way data binding.
I slogged through the project and developed a liking to React and even Redux as I learned more.
Despite not having any professional experience with ReactJS I was able to land a role at a company using it because of the knowledge I had acquired from building that janky web app.
Side projects can give you an outlet to learn things you just won't get exposed to during the course of a work day and offer fresh perspective to problems you're likely to encounter as a developer. They don't have to be polished or go into your portfolio or resume either... just build something. | UNKNOWN | Brian | Jenney | 999 | 999 | 9 | 0 | 0 | 0 | 0.009009 | #angularjs ,#reactjs | 2021-12-27 07:28:50 | https://www.linkedin.com/feed/update/urn:li:activity:6881254544643366912 |
urn:li:activity:6879789086232719361 | I know we're all supposed to love remote work. Flexibility! No commute! Work in your pikachu onesie! Yeah!!!
BUT, it can be tough. For many people, being physically isolated can feel, well, isolating. Collaboration has to be more intentional. You can't just walk to Jessica or Bobert's desk and ask for help or to review some code you just wrote.
For junior developers, how do you stand out on a remote team? At an office, just showing up early and leaving late can give people the impression that you are a hard worker and during meetings, simply being there and nodding your head can show sufficient engagement.
On a remote team here a few very simple things you can do to make yourself visible:
Err on the side of having your camera on - people convey a lot of emotion through facial expressions. This is especially important if you don't speak very often.
Write things in Slack (or whatever your team uses)! Give updates, offer to help publicly, give praise publicly and share information like interesting articles or reports.
Nervous about speaking in meetings? Yeah, me too 🤫 - so start with a question. Have a question you've written down during the meeting that you're curious about and simply ask it. This is a great first step to being more involved in meetings and getting comfortable speaking.
I'm curious what other remote work tricks/tips have you found to be most helpful during this sh*t-show of a year 🧐? | UNKNOWN | Brian | Jenney | 860 | 860 | 14 | 0 | 0 | 0 | 0.016279 | null | 2021-12-23 06:25:38 | https://www.linkedin.com/feed/update/urn:li:activity:6879789086232719361 |
urn:li:activity:6879432225880969216 | Most of my growth as a software developer came from critical feedback and making BIG mistakes. I can point to inflection points in my career so far and the failures/mistakes I made that shaped me.
I've released software that crashed on its first day. Missed glaring issues during code reviews, not quite understood how some data structure was used and subsequently wrote a line of code that accidentally sent thousands of emails to customers... oops 😅.
Each of these failures offered me a lesson on what NOT to do and areas where I needed to improve. I stopped treating code reviews as an afterthought, I spoke up when I didn't understand something and started writing tests for my code, among other things.
As a junior (or not so junior) developer you're likely going to make a few high profile mistakes. After the embarrassment has subsided, don't retreat and play it safe by only taking on assignments you KNOW you can complete. Learn, f*ck up and repeat. | UNKNOWN | Brian | Jenney | 1,594 | 1,594 | 27 | 2 | 1 | 0 | 0.018821 | null | 2021-12-22 06:47:36 | https://www.linkedin.com/feed/update/urn:li:activity:6879432225880969216 |
urn:li:activity:6878726440930676736 | Should you be using the open to work badge?
I'm sure LinkedIn would disagree with me, but if I was looking for a job as a #juniordeveloper, I'd remove it.
Why? Well, people are biased. We make assumptions. I wouldn't want to offer potential employers a reason to question my skills or talent. An open to work badge tells people that you aren't currently working (maybe even if you are) and paradoxically, recruiters tend to reach out to people that are already employed 🤷🏽♂️.
Depending on who you ask, the badge can make you more discoverable to people that are hiring or it can be a detriment in your search.
Like any good developer, do some A/B testing on this feature and see how much traction you get with and without the badge.
You can also use your settings to make yourself "available" to recruiters and your headline is searchable as well, so adding keywords and top skills in there will make you more discoverable to recruiters and hiring managers... without a large badge telling the world that you need work.
If you're a recruiter, I'd love to hear your candid feedback on the open to work badge, specifically as it relates to junior developers looking for their first or second role. | UNKNOWN | Brian | Jenney | 847 | 847 | 5 | 0 | 1 | 0 | 0.007084 | #juniordeveloper, | 2021-12-20 08:03:04 | https://www.linkedin.com/feed/update/urn:li:activity:6878726440930676736 |
urn:li:activity:6877652254707499008 | Too many people are under the impression that writing code is the only entry path into tech. I've talked to more than a few developers who have graduated from bootcamps, landed jobs... and hate what they do 😿.
Writing code can be tedious and stressful and that massive dopamine hit that most of us get from solving problems and learning new concepts can push us through the not so fun parts of the job. If you're not getting that rush or satisfaction, I can only imagine how you feel staring at code all day long... and then having to study for interviews or the new framework the VP wants to use...
Luckily, there are other bootcamp style programs out there teaching product management, UX/UI design, sales, and engineering-adjacent skills (that can often pay at or above eng roles 😉). | UNKNOWN | Brian | Jenney | 326 | 326 | 4 | 0 | 1 | 0 | 0.015337 | null | 2021-12-17 08:54:38 | https://www.linkedin.com/feed/update/urn:li:activity:6877652254707499008 |
urn:li:activity:6877336438422286336 | Before you create that weather app, todo list, or that movie finder app... hear me out.
If you really want to stand out, or better yet, challenge yourself with a project that will expose you to some concepts you may not be familiar with - I'd suggest creating an NPM library that exposes some UI components or useful helper functions (e.g. lodash). Publish this library with a useful README and then learn how to link it into an npm project.
Finally, write a small article about it. Then make that todo-list or burrito-finder app you had in mind 😉. | UNKNOWN | Brian | Jenney | 716 | 716 | 10 | 2 | 0 | 0 | 0.01676 | null | 2021-12-16 11:59:41 | https://www.linkedin.com/feed/update/urn:li:activity:6877336438422286336 |
urn:li:activity:6876624027209785344 | So yes, your bootcamp is likely using creative math to come up with those employment numbers. When's the last time you saw a bootcamp with <90% placement rate? ... 🧐
Lambda School most recently got shamed for inflating their own employment numbers by double but I'd bet you a year's worth of burritos they're not the only ones doing this.
I've worked at a few bootcamps and I'm sorry to say that according to my back of the envelope calculations, a little less than 50% of all grads I've followed have landed full time roles as software developers.
Should this discourage you from attending a bootcamp? Absolutely not! These creative numbers are marketing tactics at best and misleading at worst. The knowledge you receive from a good program is still valuable whether or not you get hired in 1 month or 1 year after graduating.
Your timeline and experience finding employment will ultimately be unique to you and influenced by luck, economic health, your tenacity and technical aptitude despite any "statistics" leading you to believe otherwise. | UNKNOWN | Brian | Jenney | 605 | 605 | 10 | 0 | 1 | 0 | 0.018182 | null | 2021-12-14 12:48:49 | https://www.linkedin.com/feed/update/urn:li:activity:6876624027209785344 |
urn:li:activity:6875126838751043584 | Stability is a myth.
The pandemic has exposed the illusion of job security that many of us (me included) believed in.
It's not just the small startups that are ruthlessly cutting people from their real-time-burrito-finder app team (hmm, maybe I should look int this actually 🤔) but major corporations slashing entire departments at the drop of a hat.
It can be jarring to realize that your job is never truly secure, especially during catastrophic external events, but armed with this realization it might be wise to stop chasing "stable" jobs and companies and instead invest in yourself with the same vigor that companies are investing in themselves... this way you'll be in a more enviable position when/if you find yourself on the wrong end of one of those dreaded zoom calls. | UNKNOWN | Brian | Jenney | 2,241 | 2,241 | 20 | 8 | 1 | 0 | 0.012941 | null | 2021-12-10 09:39:32 | https://www.linkedin.com/feed/update/urn:li:activity:6875126838751043584 |
urn:li:activity:6874809838338240512 | If you're doing interview prep you probably notice that most products are geared towards data structures and algorithms. LeetCode amirite?
It's really refreshing to see AlgoExpert offer a front end focused track for software engineers preparing for interviews.
I was a bit skeptical at first.
How the heck are they going to choose problems that cover concepts like closure, binding and DOM manipulation?
Well, I was pleasantly surprised! Thanks Clement Mihailescu! This is definitely my favorite tool for interview prep and refreshing a lot of front end concepts I THOUGHT I had down! | UNKNOWN | Brian | Jenney | 74,982 | 74,982 | 208 | 17 | 1 | 0 | 0.003014 | null | 2021-12-09 12:39:53 | https://www.linkedin.com/feed/update/urn:li:activity:6874809838338240512 |
urn:li:activity:6862109146783850496 | The interview process is BROKEN!
At least that's what I'm hearing from a lot of you out there on LI.
I see/hear/experienced a lot of issues with the current interview trend of focusing on DS/A and the growth of startups and programs dedicated to preparing engineers for these LC-style interviews is testament to their popularity. Or perhaps the perception of it.
So I have to ask - what interview format do you prefer?
Build something in front of people?
Standard LC type questions?
Take home project?
Pair with another person on a typical work task?
Eng trivia (ex - explain the concept from x language?)
Other?
#softwareengineer #interview #leetcode #datastructures #interviewprocess | UNKNOWN | Brian | Jenney | 2,820 | 2,820 | 11 | 8 | 0 | 0 | 0.006738 | #softwareengineer ,#interview ,#leetcode ,#datastructures ,#interviewprocess | 2021-11-04 12:31:52 | https://www.linkedin.com/feed/update/urn:li:activity:6862109146783850496 |
urn:li:activity:6853806900576972800 | Like many software engineers, I've become a bit obsessed with the trend of #leetcode style interviews that seem to have taken over and maybe you have too. I would only caution that many companies will NOT use this style of interview and if you're a front end developer especially, it's worth familiarizing yourself with some of the most common questions you're likely to see in an interview for a #javascript focused role:
* what is closure?
* bind, call and apply - differences and how to use
* what is this?
* map, filter, reduce - differences and how to use
* let vs const
Bonus:
* create a React component that fetches data and displays it in a pleasant way (it's always React... who is using Vue... I'll wait) - how many times have you seen some variation of this exercise?
While you're inverting all those binary trees, don't forget to you know, actually learn how to code and stuff 😉 | UNKNOWN | Brian | Jenney | 4,878 | 4,878 | 23 | 4 | 1 | 0 | 0.00574 | #leetcode ,#javascript | 2021-10-12 14:41:42 | https://www.linkedin.com/feed/update/urn:li:activity:6853806900576972800 |
urn:li:activity:6844793908229222400 | As developers we spend a lot of time studying and worrying about interviews, especially the leetcode style process which it seems a large portion of the industry has standardized on... but what about the interviewers?
A good interviewer can help lead a candidate to the correct solution through a collaborative exercise and learn what it might truly be like to work with them. Meanwhile, a not so stellar interviewer may be completely silent, or worse, discourage an interviewee from a working solution that doesn't fit their ideal - potentially turning down a perfectly suitable candidate or discouraging them from joining based on their experience.
The cost of the bad interviewer is significantly higher than the cost of interviewing the poorly prepared candidate. With so much emphasis being given to DS/A prep it feels like we should be reading more articles about how companies plan to standardize on the expectations for the person at the other end of the table or screen. #interviewing #leetcode #softwaredevelopment | UNKNOWN | Brian | Jenney | 1,655 | 1,655 | 20 | 3 | 0 | 0 | 0.013897 | #interviewing ,#leetcode ,#softwaredevelopment | 2021-09-17 17:47:17 | https://www.linkedin.com/feed/update/urn:li:activity:6844793908229222400 |
urn:li:activity:6843898901938999296 | There are so many articles out there describing how to become a #seniordeveloper but at the end of the day it's simply a title - one that can mean wildly different things depending on the company.
I've worked with senior devs who were the most technically skilled on the team and others who weren't code wizards but had leadership and project management skills.
One underrated skill that I've noticed in every senior dev I've admired is their ability to quickly debug issues and find the root cause. In my mind this is what truly separates a senior dev on the team. Uh oh, site's down, <insert senior dev name here>, can you check it out?
Humans are weird, we don't remember all the good things that happen to us as well as we remember the negative. So that feature you shipped that didn't break may not stand out as much as the time a feature stopped working and you fixed it under pressure. While you're advancing your coding skills, don't forget to sharpen your #debugging skills and take those opportunities to jump into critical bugs when they pop up. | UNKNOWN | Brian | Jenney | 1,044 | 1,044 | 20 | 6 | 0 | 0 | 0.024904 | #seniordeveloper ,#debugging | 2021-09-15 06:30:51 | https://www.linkedin.com/feed/update/urn:li:activity:6843898901938999296 |
urn:li:activity:6839609924482416640 | Every day I read posts from #bootcamp grads who have applied to 100 or more roles with no luck. While I do believe that getting that first role is a bit of a numbers game - I also think you should treat your resume/LinkedIn as an experiment.
If your resume is getting no bites, switch it up... dramatically even. I remember using 3 separate resumes at one point, a very quirky one with nice graphics and more personal information, a traditional one with little formatting and another that was a combination of the former.
I'm pretty embarrassed of that quirky resume and cover letter I wrote back then but it seemed to get more traction than the other "safer" ones and I never would have tried that if it hadn't been for a mentor that pushed me out of my comfort zone.
Run some A/B tests on your job search and see if any trends emerge... what's that saying about trying the same thing over and over and expecting different results 🧐
If you have an interesting approach to your #jobsearch as a #softwaredeveloper that worked please share it and hopefully it helps others. | UNKNOWN | Brian | Jenney | 1,573 | 1,573 | 28 | 6 | 0 | 0 | 0.021615 | #bootcamp ,#jobsearch ,#softwaredeveloper | 2021-09-03 10:27:59 | https://www.linkedin.com/feed/update/urn:li:activity:6839609924482416640 |
urn:li:activity:6837097996568657920 | As new developers, we're often so focused on just getting hired that we forget how much effort and work awaits us when we start writing code professionally. Getting hired is really step 0. There are unspoken rules, jargon and tools that more experienced people often take for granted and that can be intimidating when you land your first role.
So many acronyms. So many ticket numbers.
I distinctly remember my first stand-up meeting and hearing people rattle off ticket numbers and the work they were doing. It was complete gibberish to me and I damn near choked when it was my turn to speak 😓. I think my voice may have actually cracked 😬.
For all you recent #frontenddeveloper and #fullstack hires, especially those that graduated from a bootcamp, what has been a skill or area of #webdevelopment you wish you were more familiar with that wasn't fully covered in your education? | UNKNOWN | Brian | Jenney | 557 | 557 | 9 | 2 | 0 | 0 | 0.019749 | #frontenddeveloper ,#fullstack ,#webdevelopment | 2021-08-27 12:06:29 | https://www.linkedin.com/feed/update/urn:li:activity:6837097996568657920 |
urn:li:activity:6835928661275873280 | Looking to stand out as a new #developer on a team or as a #juniordeveloper? Speak.
I spent the first 3 years of my career in software writing code. Makes sense I guess, that's what I was paid for. I wrote good code overall, fixed a lot of critical issues and didn't drop (m)any databases in production.
During meetings regarding architectural or technical discussions, I'd often just sit and let the senior devs in the room figure it out. I mean what did I know?
Then, at a small startup, one of the founders called me out during a 1 on 1. Why do you never share your ideas he asked? I was caught off guard and didn't really have any reason beyond my fear that I'd be judged harshly or didn't have anything to add. He told me that even bad ideas can help ignite a discussion 🤔.
I made a goal to speak more after that meeting and I noticed how my career accelerated over the years after taking that advice. I'm rarely the smartest person in the room but I've grown more comfortable speaking even though it can still be a bit uncomfortable TBH.
In the age of remote work, it's easy to get lost in code and play a background position on your team... that's OK too. If you DO want to grow into a leadership or senior position I totally think you should share that dumb idea/question you're contemplating during the next zoom meeting 😉 | UNKNOWN | Brian | Jenney | 2,513 | 2,513 | 80 | 8 | 3 | 0 | 0.036212 | #developer ,#juniordeveloper? | 2021-08-24 06:39:58 | https://www.linkedin.com/feed/update/urn:li:activity:6835928661275873280 |
urn:li:activity:6834545556812124160 | If you're a developer on the job hunt with no prior experience I have a bit of a hot take on how to supplement your experience...
Get some experience!
Your mom, aunt, cousin or acquaintance either has a website or wants a website for their business. Likely a simple one but they don't know where to start or have the budget. This is where you come in.
Create this site for them (for an unbeatable price), deploy it on the web-o-sphere and now you are a Freelance Developer. Do this a couple times and now you have some real experience to speak about during an interview which includes working with clients and more importantly deploying code to a live site.
"Freelance Developer" is now your most current role and recruiters will be less confused when they see you applying for a tech role than if your last job was something completely unrelated to tech.
#softwareengineer #jobhunting #bootcamp | UNKNOWN | Brian | Jenney | 1,924 | 1,924 | 37 | 2 | 1 | 0 | 0.02079 | #softwareengineer ,#jobhunting ,#bootcamp | 2021-08-20 11:04:00 | https://www.linkedin.com/feed/update/urn:li:activity:6834545556812124160 |
urn:li:activity:6833388223960633344 | The interview process is broken! When will I ever have to convert a binary tree to a linked-list on the job?! So unfair aaarrgghhh!
Well, however you feel about the Leetcode-style interview that has become increasingly common, if you don't want to limit your prospects as a #softwareengineer it's in your best interest to study common #algorithms and #datastructures.
I was awful at these interviews years ago... I mean, really bad. I spent lots of time on sites like #leetcode and bought programs to understand the most common problems I would encounter during interviews.
My original goal was just to feel more confident during interviews but I also improved my knowledge of computer science fundamentals. I gained a deeper understanding of the performance effects of the code I wrote and my work improved.
I would advise anyone interviewing (or who wants to improve the CS fundamentals) to add sites like #leetcode into their routine. Solve a couple problems a week and when you get stuck read articles walking through solutions.
BTW, could totally turn that binary tree to a linked-list now 👋 | UNKNOWN | Brian | Jenney | 4,081 | 4,081 | 58 | 16 | 0 | 0 | 0.018133 | #softwareengineer ,#algorithms ,#datastructures.,#leetcode ,#leetcode | 2021-08-17 06:25:10 | https://www.linkedin.com/feed/update/urn:li:activity:6833388223960633344 |
urn:li:activity:6830856806089269248 | Am I supposed to know this?
Over the years, I've become more comfortable exposing my ignorance but as a #juniordeveloper and in a #remote world - speaking up to admit you don't know something or are not familiar with some particular acronym can be a nerve-wracking task. What will they think of me? Am I the only one who doesn't know this?
If you are junior dev (or a human with a question), I'd challenge you to ask that question you think you're supposed to know next time you're in a meeting or slack thread. Your team mates will almost certainly appreciate it (they're thinking the same thing) and appreciate your honesty. Often these questions are the best way to spread knowledge across the team and surface shared misunderstandings. If nothing else, it gives you an opportunity to speak up and show engagement. | UNKNOWN | Brian | Jenney | 2,272 | 2,272 | 38 | 13 | 0 | 0 | 0.022447 | #juniordeveloper ,#remote | 2021-08-10 06:46:13 | https://www.linkedin.com/feed/update/urn:li:activity:6830856806089269248 |
urn:li:activity:6828672397550469122 | Just for the record - I don't dislike bootcamps. Far from it. I've used 3 bootcamps style programs over the years to supplement my skills with great results.
The only thing that boils my potato is the rising cost of these programs and the inflated promises. I distinctly remember pulling up to the gas station and performing all sorts of mental math to determine how much I could fill up my tank and still afford food for the week. Affording a bootcamp nowadays would be almost entirely out of the question for me back then.
I've written a non-comprehensive study path that I've shared with friends and family who are interested in learning #frontenddevelopment - whether you are currently in a #bootcamp or a recent graduate - you might find this helpful: | ARTICLE | Brian | Jenney | 4,081 | 4,081 | 50 | 22 | 5 | 0 | 0.018868 | #frontenddevelopment ,#bootcamp | 2021-08-04 06:06:10 | https://www.linkedin.com/feed/update/urn:li:activity:6828672397550469122 |
urn:li:activity:6828339675866955778 | I love when people DM me here for advice or just to vent (about software stuff, not like your dog or weird stuff)... lately, I've received a couple messages from people that have entered into the field of #softwaredevelopment to learn that they actually uhh, don't like coding so much... oops.
I'm not against bootcamps at all but I do think they sell financial freedom packaged as a career in software. There's nothing wrong with wanting money but I'd argue there are other ways to get it besides writing code. Anecdotally, the most successful engineers I've met over the years have thoroughly enjoyed what they do.
Before you take spend upwards of 10k on a #coding #bootcamp I'd really suggest you take a class on #codecademy or get a code editor and learn some code on your own.
A career in software means a career of constant study, learning new skills and being curious. If you want my hot take on bootcamps or career advice just hit my DM ;) | UNKNOWN | Brian | Jenney | 3,858 | 3,858 | 63 | 15 | 0 | 0 | 0.020218 | #softwaredevelopment ,#coding ,#bootcamp ,#codecademy | 2021-08-03 08:04:03 | https://www.linkedin.com/feed/update/urn:li:activity:6828339675866955778 |
urn:li:activity:6810981548695916544 | Great seeing Zignal Labs in the news combatting medical disinformation. Watching this piece on CBS and seeing a chart I worked on while on the team brought back some fond memories and also the stress of learning #d3js ... so many charts
https://lnkd.in/gBWimwr | IMAGE | Brian | Jenney | 1,332 | 1,332 | 34 | 2 | 1 | 0 | 0.027778 | #d3 | 2021-06-16 10:29:03 | https://www.linkedin.com/feed/update/urn:li:activity:6810981548695916544 |
urn:li:activity:6802226486033182720 | And here I thought I was imagining things... hopefully this translates to more opportunities for junior developers as companies struggle to find and retain seniors - and maybe, just maybe less 8 hour take home challenges 🤞 | UNKNOWN | Brian | Jenney | 1,023 | 1,023 | 9 | 2 | 0 | 0 | 0.010753 | null | 2021-05-23 06:39:33 | https://www.linkedin.com/feed/update/urn:li:activity:6802226486033182720 |
urn:li:activity:6793928549993721856 | Guess you could say I'm a little biased but this is truly a great place to work where you can have a serious and immediate impact. If you are a #seniorsoftwareengineer check out the posting below for #clorox | UNKNOWN | Brian | Jenney | 380 | 380 | 5 | 0 | 0 | 0 | 0.013158 | #seniorsoftwareengineer ,#clorox | 2021-04-30 09:06:31 | https://www.linkedin.com/feed/update/urn:li:activity:6793928549993721856 |
urn:li:activity:6783585051138494464 | A student reached out to me and asked if there was something about software development which might surprise people. I answered that people underestimate the stress accompanied with writing code for a living. Whether it's being on call and getting woken up in the middle of the night to patch a critical bug or doing a deployment only to discover bugs in production that need to be fixed or rolled back,
the code we write often has real life consequences ranging from loss of revenue for a company or at worst, loss of life.
I don't mean to discourage anyone from pursuing a career in software. Stress will be in your life either way and the feeling of excitement from solving mission critical issues is a high that is hard to describe to others, but at the same time, I wouldn't expect a new career as a dev to be all foosball tables and LaCroix. #softwaredevelopment #workstress | UNKNOWN | Brian | Jenney | 914 | 914 | 20 | 1 | 0 | 0 | 0.022976 | #softwaredevelopment ,#workstress | 2021-04-01 20:05:08 | https://www.linkedin.com/feed/update/urn:li:activity:6783585051138494464 |
urn:li:activity:6780843095463489536 | I've been doing WFH in some form for the last few years, but it definitely didn't come as naturally as all the WFH advocates would have you believe. In fact, I felt pretty isolated and like I wasn't making an impact. WFH is a skill like any other and takes some thought to not suck at it. #wfh2021 #wfhlife #softwareengineer | ARTICLE | Brian | Jenney | 3,229 | 3,229 | 44 | 14 | 5 | 0 | 0.019511 | #wfh2,#wfhlife ,#softwareengineer | 2021-03-25 06:29:35 | https://www.linkedin.com/feed/update/urn:li:activity:6780843095463489536 |
urn:li:activity:6765282352575971328 | I see you. Adding all those console logs in your code. If you're using VS Code and NodeJS there's a better way. #javascript #nodejsdevelopers #vscode | ARTICLE | Brian | Jenney | 596 | 596 | 10 | 0 | 0 | 0 | 0.016779 | #javascript ,#nodejsdevelopers ,#vscode | 2021-02-10 06:56:45 | https://www.linkedin.com/feed/update/urn:li:activity:6765282352575971328 |
urn:li:activity:6763098666279550976 | Have you ever released a feature only to find out something was missing? The JIRA board says the ticket is done, the developer says it's been merged but it's just not showing up?!
Turns out it was still un-merged.. oops. Humans can make mistakes.
For releases at Clorox DTC we use a small script to help us verify what is going in each release branch in addition to all the wonderful humans that help test and mange it.
Maybe this small script will help you as well:
#releasemanagement #github #bitbucket #clorox | ARTICLE | Brian | Jenney | 467 | 467 | 6 | 3 | 0 | 0 | 0.019272 | #releasemanagement ,#github ,#bitbucket ,#clorox | 2021-02-04 06:19:34 | https://www.linkedin.com/feed/update/urn:li:activity:6763098666279550976 |
urn:li:activity:6757810924415004672 | null | UNKNOWN | Brian | Jenney | 139 | 139 | 2 | 0 | 0 | 0 | 0.014388 | null | 2021-01-20 16:07:58 | https://www.linkedin.com/feed/update/urn:li:activity:6757810924415004672 |
urn:li:activity:6757003367790325760 | Wow! This is one of those rare opportunities to attend a well respected bootcamp for free + housing expenses! | UNKNOWN | Brian | Jenney | 391 | 391 | 2 | 1 | 0 | 0 | 0.007673 | null | 2021-01-18 10:39:01 | https://www.linkedin.com/feed/update/urn:li:activity:6757003367790325760 |
urn:li:activity:6745755529978748928 | null | UNKNOWN | Brian | Jenney | 72 | 72 | 0 | 0 | 0 | 0 | 0 | null | 2020-12-18 09:44:08 | https://www.linkedin.com/feed/update/urn:li:activity:6745755529978748928 |
urn:li:activity:6743532253290348544 | I know there are a lot of junior developers out there looking to get their first break. But who says your first nickel earned from writing code has to be at a traditional workplace?
#juniordeveloper #jobseekers #javascript | ARTICLE | Brian | Jenney | 3,193 | 3,193 | 32 | 3 | 4 | 0 | 0.012214 | #juniordeveloper ,#jobseekers ,#javascript | 2020-12-12 06:29:37 | https://www.linkedin.com/feed/update/urn:li:activity:6743532253290348544 |
urn:li:activity:6735207184168308736 | null | UNKNOWN | Brian | Jenney | 42 | 42 | 0 | 0 | 0 | 0 | 0 | null | 2020-11-19 07:08:46 | https://www.linkedin.com/feed/update/urn:li:activity:6735207184168308736 |
urn:li:activity:6734228676608712704 | Great opportunity for a recent #devops #devopsengineer | UNKNOWN | Brian | Jenney | 573 | 573 | 5 | 0 | 0 | 0 | 0.008726 | #devops ,#devopsengineer | 2020-11-16 14:20:32 | https://www.linkedin.com/feed/update/urn:li:activity:6734228676608712704 |
urn:li:activity:6732435018876108800 | null | UNKNOWN | Brian | Jenney | 127 | 127 | 1 | 0 | 0 | 0 | 0.007874 | null | 2020-11-11 15:33:11 | https://www.linkedin.com/feed/update/urn:li:activity:6732435018876108800 |
urn:li:activity:6725812960289271808 | Our #devteam at #clorox uses #microservicesarchitecture to create store fronts for different brands to sell products. While there are a lot of articles exploring using shared component libraries for #microfrontends to leverage re-usable components what about shared state? #reduxjs | ARTICLE | Brian | Jenney | 345 | 345 | 11 | 0 | 0 | 0 | 0.031884 | #devteam ,#clorox ,#microservicesarchitecture ,#microfrontends ,#reduxjs | 2020-10-24 09:59:29 | https://www.linkedin.com/feed/update/urn:li:activity:6725812960289271808 |
urn:li:activity:6721455203821895680 | Our dev team at #clorox has started doing small coding challenges on Fridays, with the intent to help our team keep our skills sharp and take a little break from work-related tasks.
Last Friday our VP Joey Shakespeare raised the stakes with a cash prize which David Hebert won!
So far, we've been tackling LeetCode style questions but I'm curious about any challenges you have encountered which might be of interest to #javascript focused developers that can be completed within about an hour 🤔 - please share! | UNKNOWN | Brian | Jenney | 1,476 | 1,476 | 24 | 2 | 0 | 0 | 0.017615 | #clorox ,#javascript | 2020-10-12 09:23:19 | https://www.linkedin.com/feed/update/urn:li:activity:6721455203821895680 |
urn:li:activity:6717620835219329024 | A couple days ago, someone on LI messaged me and shared their feelings of #impostersyndrome after graduating from a bootcamp and landing their first role in software.
"Fake developer," he said. That phrase pretty accurately describes how I felt too, sometimes how I feel now (shh, don't tell anybody). I vividly remember the first couple years of getting paid to write code, wondering when/if I would be fired.
To my surprise, almost 6 years later, I'm still here and feeling a little less fake each year.
Cheers to all you fake #software devs out there, you're not alone and hopefully that big voice of doubt in your head will get a little smaller with each bug you squash, problem you solve and on-call rotation you survive. | UNKNOWN | Brian | Jenney | 1,842 | 1,842 | 39 | 5 | 0 | 0 | 0.023887 | #impostersyndrome ,#software | 2020-10-01 19:26:54 | https://www.linkedin.com/feed/update/urn:li:activity:6717620835219329024 |
urn:li:activity:6714945037274378240 | For the first two years of my career as a #softwareengineer I wrote exactly 0 tests... shame on me. If you're new to writing tests and using React hopefully this will help you write your first non-trivial test #react #testingtools #javascript | ARTICLE | Brian | Jenney | 859 | 859 | 25 | 2 | 1 | 0 | 0.032596 | #softwareengineer ,#react ,#testingtools ,#javascript | 2020-09-24 10:14:14 | https://www.linkedin.com/feed/update/urn:li:activity:6714945037274378240 |
urn:li:activity:6705186535375024128 | Just joined this team recently and really enjoying it! Check out the job description below and see if you might be a good fit: | UNKNOWN | Brian | Jenney | 139 | 139 | 2 | 0 | 0 | 0 | 0.014388 | null | 2020-08-28 11:57:26 | https://www.linkedin.com/feed/update/urn:li:activity:6705186535375024128 |
urn:li:activity:6696761009262202880 | If there any junior #devops looking for an opportunity, you should check this out: | UNKNOWN | Brian | Jenney | 152 | 152 | 4 | 0 | 0 | 0 | 0.026316 | #devops | 2020-08-05 05:57:24 | https://www.linkedin.com/feed/update/urn:li:activity:6696761009262202880 |
urn:li:activity:6692526027316572160 | I was reading CNN last night and stumbled on this interview where Anderson Cooper mentions Zignal Labs! While I'm excited for my next opportunity, I'm also sad to leave this place and really proud to say I worked here! #zignallabs #misinformation | UNKNOWN | Brian | Jenney | 310 | 310 | 7 | 0 | 0 | 0 | 0.022581 | #zignallabs ,#misinformation | 2020-07-24 13:29:06 | https://www.linkedin.com/feed/update/urn:li:activity:6692526027316572160 |
urn:li:activity:6689289124274429952 | So many self taught coders and bootcamp grads shy away from the #leetcode grind, and while I agree that there's too much emphasis on learning obscure #algorithms you will likely never use for the sake of interviews, the problem solving aspect of figuring out these coding puzzles offers a lot of benefits... also, #interviews ;)- | ARTICLE | Brian | Jenney | 1,128 | 1,128 | 19 | 4 | 1 | 0 | 0.021277 | #leetcode ,#algorithms ,#interviews | 2020-07-15 15:06:48 | https://www.linkedin.com/feed/update/urn:li:activity:6689289124274429952 |
urn:li:activity:6679102593416998912 | If you’re a former student of mine or someone looking for mentorship as you begin your journey towards #softwaredevelopment this is a very gracious and valuable offer from a seasoned developer/eng manager => | UNKNOWN | Brian | Jenney | 392 | 392 | 6 | 0 | 0 | 0 | 0.015306 | #softwaredevelopment | 2020-06-17 12:29:09 | https://www.linkedin.com/feed/update/urn:li:activity:6679102593416998912 |
urn:li:activity:6676844980029530112 | I hear a lot in tech that it’s hard to find “diverse” candidates - luckily these people have done it for you: | UNKNOWN | Brian | Jenney | 109 | 109 | 5 | 0 | 0 | 0 | 0.045872 | null | 2020-06-11 06:58:13 | https://www.linkedin.com/feed/update/urn:li:activity:6676844980029530112 |
urn:li:activity:6669687789698859008 | I've heard more conspiracy theories from people I know than I ever expected. The misinformation/disinformation about this pandemic is pretty extraordinary.
Check out this piece from Adweek, which uses insights from Zignal Labs to explore how online #misinformation around #COVID-19 is impacting our world. | ARTICLE | Brian | Jenney | 91 | 91 | 0 | 0 | 0 | 0 | 0 | #misinformation | 2020-05-22 12:58:05 | https://www.linkedin.com/feed/update/urn:li:activity:6669687789698859008 |
urn:li:activity:6669604827959451648 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-05-22 07:28:26 | https://www.linkedin.com/feed/update/urn:li:activity:6669604827959451648 |
urn:li:activity:6659592480952066048 | null | UNKNOWN | Brian | Jenney | 50 | 50 | 0 | 0 | 0 | 0 | 0 | null | 2020-04-24 16:22:56 | https://www.linkedin.com/feed/update/urn:li:activity:6659592480952066048 |
urn:li:activity:6659473301934608384 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-04-24 08:29:22 | https://www.linkedin.com/feed/update/urn:li:activity:6659473301934608384 |
urn:li:activity:6654797548475285504 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-04-11 10:49:35 | https://www.linkedin.com/feed/update/urn:li:activity:6654797548475285504 |
urn:li:activity:6649442683389648897 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-03-27 16:11:16 | https://www.linkedin.com/feed/update/urn:li:activity:6649442683389648897 |
urn:li:activity:6647877569087705090 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-03-23 08:32:04 | https://www.linkedin.com/feed/update/urn:li:activity:6647877569087705090 |
urn:li:activity:6646071187896172545 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-03-18 08:54:09 | https://www.linkedin.com/feed/update/urn:li:activity:6646071187896172545 |
urn:li:activity:6644268664851968000 | null | UNKNOWN | Brian | Jenney | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null | 2020-03-13 09:31:34 | https://www.linkedin.com/feed/update/urn:li:activity:6644268664851968000 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.