Brian Jenney
/brianjenney
Real Talk JS - no nonsense tips for JavaScript developers looking to get ahead in their careers.
Brian Jenney
2y ago
Super Simple Weight Loss Guide
Step 1: Know Your TDEE
Total Daily Energy Expenditure. Basically, how many calories do you burn per day doing you. https://tdeecalculator.net/
Use the calculator in the link above to determine your TDEE. (HINT: choose 'Sedentary' for Activity Level).
Great. Now you have a baseline for how many calories you need a day.
Step 2: Measure What You Eat
99% of us eat more than we think.
Now that you know the number of calories needed to sit on your ass all day, we have some basic math to do:
Eat less calories than used for your TDEE.
Buy a digital food measuring scale. You cannot eyeball the amount of rice you're stuffing down your face... yet.
Track everything you eat into MyFitnessPal. It's also free.
Step 3: Plan Out Your Staple Meals
I don't meal prep.
Maybe you don't want to either.
Pick a couple staple meals that fit your calorie goals.
Perhaps you like sweets like me so make sure to incorporate those into your calorie budget. Be realistic!
Honestly, it doesn't really matter where your calories come from as far as weight loss is concerned.
You can lose weight eating nothing but twinkies as long as you are eating less than the number of calories needed to maintain your current body weight.
Don't do that of course.
Some easy to make, low calorie foods that I use for my daily meals:
Egg whites
Ground turkey (99% fat free)
Zero pop popcorn
Chocolate rice cakes
Chicken breast
Quest Protein bars
Low calorie mozzarella
Remember, measuring is key!
I buy foods that I can easily measure like cartons of egg whites and ground turkey.
I use measuring cups for my cheese and popcorn... yeah, I know.
Eating out can be a bit of a guessing game but MyFitnessPal has a shocking amount of data for restaurants. Don't be lazy. Also, maybe eat out less.
Step 4: Weigh Yourself Everyday. Every. Day.
Your weight will fluctuate. Sometimes by a lot.
This is why it's so important to weigh yourself everyday. You want a downward trend but don't freak out if there are spikes here and there. That's normal.
Here's what my chart looks like:
Always weigh yourself in the morning when you are at your lightest. This is both for your own mental health and to keep an accurate record of your progress.
Don't be shocked when you go up 5 pounds after binging on salty foods or after a weekend drowning your sorrows at an all-you-can-eat buffet.
On top of weighing yourself, take a revealing picture of yourself every Friday. A nice spicy pic for just your eyes.
The number of pounds you've dropped is not always the most accurate reflection of your progress.
Do you look better without clothes? Progress.
Step 5: Know Weight Loss Math.
You know your TDEE.
You are tracking calories.
I hope you are exercising.
So how fast will those rolls disappear?
Depends.
It takes roughly 3500 calories to add a pound. So work backwards.
Can you decrease 500 calories a day from your maintenance calories to be in a 3500 calorie deficit?
I'd say that's aggressive but possible.
You have a few options:
Eat roughly the same and burn more calories from working out
Eat less and don't work out
Eat a little less AND workout (the best way)
At the end of the day, you must re-calibrate based on your weight goals.
Not losing weight for 2 weeks? Lower your calories by 200 a day or exercise more.
As long as you are on a downward trend, you are doing great.
Some additional food math you might find useful:
4 Calories per gram in carbs
4 calories per gram in proteins
9 calories per gram in fats
You may notice fats have significantly more calories than proteins and carbs which means if you want to eat more then stay away from high fat foods.
Brian Jenney
Real Talk JS
3y ago
I only know 2 things fairly well:
Coding
Getting in shape
I've only shared my advice on #1 thus far and I feel guilty because I know that my "secret" to success as a developer and in life has been my exercise routine and diet.
Shame on me.
Don't worry, this won't become a fitness influencer newsletter and next week we'll be back to hard-hitting topics like front end system design.
Like coding, there is no silver bullet to getting in shape. My goal is to show you a path that has worked for me and help you avoid all the mistakes I've made over the years.
Whether you want to lose weight for the Summer, show your ex what they're missing or just see a picture of me shirtless to laugh at... I got you.
Exercise makes you a better coder.
Since it's likely you're a nerd - you may want to know the scientific benefit of working out:
Regular physical activity improves blood flow to the brain and helps to stimulate chemical changes in the brain that enhance learning, mood, and thinking. These chemical changes involve the production of more brain-derived neurotrophic factor (BDNF), which is involved in brain cell growth and learning. The result is improved concentration, memory, and mental sharpness, which can all contribute to better coding skills
That's great. I mean who doesn't want more brain power?
I didn't need to know this to understand the benefit personally however. You see, 10 years ago I was about 50 pounds heavier and living a life that can only be described as... criminal 😅.
Think of a low budget music video from a local rapper. Yeah that's kinda what my life was like.
I got sober, learned to code and now I'm an engineering manager.
Easy right?
Not so much.
I had the discipline of a grown toddler. I hadn't held a job in years. I was a smoker during that time too. I ate Jack in the Box everyday. Every. Day. Embarrassing.
Once I quit my vices after an intervention I realized how much time I had on my hands.
What the hell was I going to do?
I started working out just to pass time. I got a small high from running. I like this, I thought. My fitness journey started as a replacement for the high I got from other sources. It was only after a few years of keeping this habit that I noticed just how deeply connected it was to my success as a software developer:
I would think of my best ideas while running
Coding is stressful - my workout routine always decreased the tension headaches I would get from staring intently at a screen
I understood delayed gratification - it takes consistency over months to see results in the gym just like it takes time to progress as a developer
I see working out as my super power and I've been reluctant to share it with you. I was worried you might not "get it" or not care.
If you've read this far I hope I've sold you on the benefits of working out. Now here's the no-fluff steps to tackle your diet and a workout routine to get you started.
Step 1: Get you diet in check
I paid thousands to a personal trainer and read 3 books on diet and exercise to gain this knowledge:
Measure what you eat
Get enough protein
Be in a caloric deficit
Ground breaking, I know.
Here's the issue though; if losing weight was this simple then everyone would have a glistening six pack.
Most people do NOT weight out their food or track calories. Instead they rely on stupid diets that force them not to eat things like carbs or eat during magic windows of time.
It's all about calories in and calories out. Don't over-complicate it.
Calculate your TDEE (Total Daily Energy Expenditure) using this free calculator.
This is the amount of calories you expend just doing you.
To lose weight you can multiply this amount by 0.8 or 0.85 to understand around how many calories you need to eat daily to lose weight.
Some quick weight math:
There are 3500 calories in a pound of fat.
Eat 3500 calories a week less than you currently do and you will lose about a pound of fat. That's 500 calories less per day. I would consider that an aggressive cut and I suggest working towards a 250 calorie deficit which is sustainable and will net results.
You probably don't even know how much you're eating though.
Don't guess.
I worked out for 5 years straight before I could see a six pack.
What changed?
2 things:
I weighed out my food
I tracked my calories with myFitnessPal
Yes, I still eat cake, bread and tacos. I just make sure I'm hitting my calorie budget and not simply guessing how much rice is in a cup. I weigh out my meat before cooking and eat basically the same stuff everyday.
Here's what my typical day looks like:
2 cups of egg whites with low fat cheese
2 oz of beef jerky
4 chocolate rice cakes
1/4 pound of Ground turkey
2 cups of popcorn
1 protein bar
[Whatever the hell else I want to eat]
The last meal of the day I like to have fun with. Depending on how much I have left in my calorie budget, I may eat some marshmallows, ice cream or go out. It's not an every day thing but it gives me flexibility. My staple meals (ground turkey and egg whites) make sure I'm not re-inventing the wheel each day.
Step 2: Steal my workout routine
Before I paid a trainer to help me with my exercise routine, I would hit the gym and head straight to the treadmill. I didn't really know what else to do.
Here's my workout plan that does not require a gym! If you want my gym routine, lemme know and I'll write it up and send it over to you.
Chest/Triceps
5 sets of incline pushups until failure (you can't do anymore)
3 sets of dips until failure
300 pushups (break them up however you want with 30 second rests between sets)
5 sets of diamond pushups until failure
1 min rest period between each set
Legs
25 squats for 4 sets
7 sets of 7 jump squats (30 seconds between each set)
4 rounds
25 squats
30 second wall hold
10 lunges each leg
25 squats for 4 sets
1 min rest period between each set
Back/Biceps/Shoulders
5 sets of wide grip pull ups until failure (most will need to do assisted pull ups to start with or replace with pushups)
5 sets of close grip pull ups until failure
4 sets of lateral raises until failure
3 sets of front raises until failure
5 sets of alternating curls until failure
3 sets of hammer curls until failure
If you're looking at this and thinking 😬 - don't worry. The goal is to get started and do what you can. I couldn't do a single pull up years ago. I couldn't a run a mile without stopping.
The trick is to get started, make it doable and keep it going. I guarantee you will see results.
Brian Jenney
3y ago
Over the last 12 months, I've spoken with 343 developers from every corner of the planet. Nearly 100 hours of yapping on the phone with many of you reading this.
These were short, 15 minute conversations meant to tackle your most pressing issues as a developer. Sometimes these conversations lead to mentorship services or sales of my course but that's never the goal.
I continue to learn a ton from these conversations which help me in my own business and career. Also - I see giving back as a duty from all the help I've received over the years.
I understand the major pain points in the community. I hear what's working. What's not working. The successes, failures and most importantly - the patterns.
Your problems are not unique. At all.
The kid in Pakistan from a family of engineers and doctors who got a computer science degree is struggling with the same issues as the woman in California who graduated from a bootcamp after working as a cashier.
Ok, so you're dealing with the same problems. Now what?
You're a software engineer. You want solutions not sympathy. I have a bit of both for you 😅.
Here are the top 3 problems that nearly every developer struggles with and some material to help you overcome it.
1. Impostor Syndrome: The Silent Battle
"I feel like the worst developer on the team"
"I'm not ready to apply yet"
"I just don't get this stuff"
We all know this feeling and often, there is some truth to our feelings. I have been the worst on a team. It's not fun.
Here's what I've done and what I recommend you do:
Write out the skills you are missing from your toolbox. What do the "smart" developers know and do that you do not?
Make a plan to acquire these skills.
Prove to yourself that you deserve the position that you're in.
Check out this doc here to get started.
Also - just know that I've yet to speak to a person that felt "ready" for anything.
Confidence comes AFTER you start, not before.
2. The First Job: A Daunting Mountain to Climb
I know, I know. You've applied to every company in the Tri-State area.
No one is hiring.
The market is saturated.
I've heard some version of all these frustrations for nearly 10 years. In fact, the ONLY time I stopped hearing these phrases was during the pandemic hiring spree.
Some harsh truths:
Mass applying does work - I don't care what influencer tells you differently
Networking works too
Luck is a factor no one wants to admit
You can control your skills - not the timeline to get hired
Some stuff you should fix quickly:
Get 500 connections on LinkedIn to be more discoverable
Remove any mention of junior/aspiring/student from your profiles
Don't apply for only junior roles - let the market decide your title
Use strong language on your resume to stand out
Check out this guide here to fix your resume.
3. Choosing Projects: The Art of Decision Making
"What should I build?"
Depends.
First off - forget the portfolio. Barely anyone will ever look at it. The purpose of a side project is 2-fold:
Create some emotional attachment to your learning so you don't quit
Improve your RELEVANT practical skills
Most bootcamp grads and university students find that their productivity drops off a cliff after graduating. Without structured learning, they rely on random tutorials or get sold on another language to learn.
It's hard to sustain interest in your craft when you're pounding LeetCode problems or infinitely watching YouTube videos.
Having a side project you actually care about will naturally keep you interested and involved in your education.
Don't stray too far from your stack at first either. If you are a recent grad, your project should involve mostly technology you are familiar with and maybe 1 or 2 new things you'd like to add to your tool belt. I strongly suggest TypeScript and unit testing since 98.5% of coding programs don't touch these topics.
I like you so here's a side project starter template.
Now What?
I hope you find some comfort in knowing that you are not alone in your struggles. I was pretty shocked to find out just how common these problems are. Against advice from my own mentors, I plan to continue these calls, free of charge.
I also have launched a paid version to dig further into your problems with targeted advice specifically for you that will be recorded and yours to keep forever. You can schedule a time here.
Brian Jenney
Real Talk JS
3y ago
I'm going to give you a formula for learning the basics of system design to help you prepare for your next interview but more importantly, to develop big picture thinking.
Writing code is great. I mean, you have to know how to write sexy, working code in order to be a developer. But at some point, that's a given. You move past junior developer and you must start thinking larger.
Unfortunately too many developers get caught up in the trap of the LeetCode grind only to discover that more leverage, respect and opportunity is at the system design level.
System design basics.
There are a few buckets of concepts you need to familiarize yourself with so you can mix and match features for the correct system:
Databases (SQL vs NOSQL)
Caching and Distributed Caching
Message Queues
CDNs
Database Partitioning
I would simply ask ChatGPT or do a quick Google search on each topic.
Here's a list of the top 4 system design questions you are likely to encounter and how to approach them:
Design a URL shortener
https://www.geeksforgeeks.org/system-design-url-shortening-service/
Design a web scraper
Design a News Feed
https://liuzhenglaichn.gitbook.io/system-design/news-feed/design-a-news-feed-system
Design a system to find friends near me
https://www.enjoyalgorithms.com/blog/design-yelp
Honestly, if you just memorize these 4 answers you will be prepared for the majority of system design interviews 🤫.
Memorization does !== understanding though.
Once you've gotten some familiarity with the topics above, here's how you can approach a system design interview:
Here is the pattern I follow:
Discuss constraints of the system
How many users do we expect?
Are there any SLA’s (service level agreements)?
Understand the big ask: What exactly are we building and how should it work from a user’s perspective?
High level architecture
Draw out the main components of the system (you can always add more later)
Sketch out the general flow - (ex: a client makes a request which is routed to a load balancer and then distributed to a network of servers where API/s handle and store data in a database)
Data modeling
What type of data do we expect to store
For videos/pictures/images - do we want to use a CDN (hint: yes)
Should we use SQL/NO-SQL (hint: safe bet is no-sql)
Draw out the schema for the data
APIs
High level overview of their functionality
Are there any algorithms we should leverage (ex: can we shorten a field by using a common hashing algo like MD5?)
Scaling the System
Caching to speed requests (hint: LRU cache is safest bet)
Will we need to leverage message queues/workers?
Monolith API or Microservices (hint: safe bet is microservices)
Can we partition the databases? How?
Once you’ve gone over a high level overview of the system and its different components, it’s time to dive into the particulars of a certain layer.
For example, for a problem that deals with geo-location, it’s probably important to dive further into the database layer and how you plan to store the location of users.
For a newsfeed, you may want to dig into the APIs that generate a newsfeed for a user.
Remember to work with the interviewer. This type of interview is more conversational than your typical coding exercise. Discuss tradeoffs and always steer the conversation towards an area you are more knowledgeable - for example as a front-end developer, you may want to focus on the APIs as opposed to database design.
Lastly, to get some real practice with system design interviews, sign up for pramp.com (FREE) and do some mock interviews with a real human.
See ya' next weekend!
Brian Jenney
Real Talk JS
3y ago
You've probably heard of software design patterns like DRY, SOLID and other acronyms.
Design patterns aren't just some academic jargon. They can make your life as a developer easier. They are time-tested methods for solving common problems.
Unfortunately, many developers are unaware of these patterns or how to use them practically.... I know this because I've worked with a ton of developers at various companies and seen this particular mistake way too often.
Tech moves fast. Your code should be able to keep up.
We are going to cover a very specific pattern which will help you and your team to move faster and write better code.
Let's take a look at some code that looks harmless on the surface
import axios from 'axios';
function SomeComponent() {
const [data, setData] = useState([]);
useEffect(() => {
axios.get('https://jsonplaceholder.typicode.com/todos/1')
.then(response => setData(response.data))
}, [])
return (
<div>
{data.title}
</div>
)
}A little component fetching data with Axios, an incredibly popular HTTP request library. What's the big deal?
Well, nothing. Yet.
Your app grows.
More components are added.
Many more requests are made using Axios.
Then.... the team decides to switch to using fetch due to a request from the legal team now that your app has scaled to a million users and the US Govt wants to buy it. You picked a good company 😎.
Ruh roh.
The app now has 420 instances of Axios being called directly. This will be a monumental task to replace all those calls, make sure they still work AND update the tests.
This isn't just a doomsday scenario, it's more common that you might think.
A popular LinkedIn tech influencer shared his experience with a similar issue that took his team 5 months to fix! 🤯
Here's how to avoid that costly error:
The Proxy Pattern
A proxy is basically a wrapper around another object. Like a substitute.
So instead of calling Axios or some other 3rd party service directly, you proxy your request through a wrapper.
Here's a proxy which wraps around the Axios library:
import axios from 'axios';
class HttpService {
async get(url) {
const { data } = await axios.get(url);
return data;
}
async post(url, body) {
const { data } = await axios.post(url, body);
return data;
}
}
export default new HttpService();And here is our component using the proxy.
import httpService from './httpService';
function SomeComponent() {
const [data, setData] = useState([]);
useEffect(() => {
httpService.get('https://jsonplaceholder.typicode.com/todos/1')
.then(data => setData(data))
}, [])
return (
<div>
{data.title}
</div>
)
}It's now trivial to replace Axios with another library because our methods exposed through the HttpService are the same!
Let's replace Axios with fetch and now all 420 components using it will be updated as well:
class HttpService {
async get(url) {
const response = await fetch(url);
const data = await response.json();
return data;
}
async post(url, body) {
const response = await fetch(url, {
method: "POST",
body: JSON.stringify(body),
headers: {
"Content-Type": "application/json"
}
});
const data = await response.json();
return data;
}
}
export default new HttpService();
Amazing.
If you see examples in your own codebase which are similar, consider leveraging this pattern and maybe avoid a 5 month long refactor.
Want to learn with me?
Join my community which includes weekly group sessions to learn things like design patterns, testing and more and get lifetime access to my growing list of challenges and tutorials guaranteed to level you up.
This past Friday we learned how to write tests for React components. Coming up next is AWS Lambda. Join here.
Brian Jenney
3y ago
2 years after I joined my first company as a developer I knew it was time to leave.
The decision was not easy. I liked my co-workers, managers and the company. But I knew that in order to grow as a developer I needed to be exposed to a more modern tech stack and different ways of working. I successfully passed an interview for a very early stage start-up using EmberJS, Rails and Postgres. At this time I had been using C#, SQL and AngularJS.
My salary also doubled. Making the move was a no-brainer.
On day one I knew I was in over my head.
The co-founders at this 5 person start-up were featured in Forbes. They had worked at multiple letters in FAANG. The lead developer was the creator of a popular library for EmberJS.
And then there was me. I had no experience with Ember, Ruby or working in a start-up.
But at least I knew Javascript... or so I thought.
On day 1 there was no onboarding. I jumped straight into pairing with the lead developer and CTO.
There were jokes about Djikstra. Who the hell is that?
A bug with closure scope. Huh?
Hoisting was affecting a test. I had never written a test before.
Overall, the team was very patient with me. Until...
I finally got called out on my lack of fundamentals and performance
First there was the bug I caused from misunderstanding how enums work that resulted in a thousand emails being sent to customers.
Then there was the feature that took about 1 month longer than it should have because I didn't reach out for help.
I simply could not keep up with my workload and concepts like closure, classes and testing still escaped me which made pairing with the other developers a chore.
I had a 1 on 1 with the CTO/co-founder and he told me some areas where I needed to improve.
learn the fundamentals of JS (closures, promises, es6 classes)
speak up and ask for help when needed
stop making quick fixes and investigate root causes of problems
These seemed do-able.
Then I had an epiphany.
I knew this wouldn't be my last company. I was never going to be better than the super seniors around me so I made a resolution to suck a lot less. I would use this as a learning experience. What's the worst that could happen, I thought.
Here's what I did NOT do:
Buy a bunch of Udemy courses (ok, bought 1 on EmberJS)
Read a ton of articles and mistake that for progress
Get lost in a YouTube rabbit hole
Get mad and rage quit
Here's what worked really well for me to improve my communication and coding skills.
Asked the lead developers for book recommendations (more on that below)
Read about classes, closure and promises THEN actually coded out examples using them to really understand the concepts
Set a goal to ask at least 1 question per meeting and be very transparent with my status updates
Volunteer to investigate critical issues to learn what was causing them
I never became the 2nd worst developer on the team 😿.
Eventually I left the company to work at a larger startup where I got promoted to senior using the lessons I learned here. The CTO did me a massive favor by giving me that feedback even though it stung in the moment.
If reading is your thing... and it should be honestly. Here are a list of books that have made me a better developer and engineering manager
System Design Interview by Alex Xu
If you're feeling like the worst developer on the team that sucks. It's also a learning opportunity. I can throw a bunch of cliched advice your way but that won't help.
Action cures anxiety.
Identify your weak areas, make a plan to strengthen them and maybe read some of the books above and level up.
Hope that's helpful.
- Brian
Oh yeah - join my dev community and access a ton of training to make you a better developer. Price goes up Monday and we meet next Friday to do our first group meeting to learn unit testing which is worth the price alone. Check it out here.
Brian Jenney
Real Talk JS
3y ago
Let’s face it. The majority of us who write code for a living won’t be the next Kyle Simpson. Even within our own teams, there are those members who just seem to write the kind of code which you envy. They’ve been programming for decades or maybe they truly are a genius. You pore over their code, hoping to glean some wisdom from them, only to realize it may be years before you reach their level of mastery.
Technical proficiency doesn’t always parallel career trajectory in software, as it shouldn’t. At the most basic level, software teams are groups of humans building products with details and requirements often dictated by other humans that will be eventually released to, you guessed it, more dirty humans.
With all these non-machines in the mix, you’d better bring more to the table than an ability to write sexy code. Luckily, there are 4 ways to stand out on your team even if you aren’t a code wizard.
1. Contribute to Discussions
We’ve all been in one of those technical planning meetings where one voice is more present than others. It’s likely the senior developer explaining the library or approach they would use to tackle the issue at hand. Linda suggests the team write their end to end tests using Selenium to mimic user behavior and DOM interaction.
Erica has heard of a Javascript framework, Cypress.io, which sounds like it might be a better fit for their needs but doesn’t say anything. Everyone silently nods in agreement. Linda’s been here for 5 years and written the majority of the front end tests. She must know what she’s talking about.
Don’t assume the most senior person on your team is correct! Oftentimes, their voice is the loudest in the room because there is an unspoken expectation that they at least offer an opinion or suggestion.
Personally, I feel really relieved when there is some discussion around my suggestions. Sometimes, this results in a change of course that makes everyone happier and our code better. Ask that question!
2. Run Towards Fires
The VP of Engineering posts a cryptic comment in the Slack channel that only full-stack developers use:
"Can someone check out what's going on with our endpoint to fetch customer data? Seems to be really slow and we're getting some emails regarding it."
You stare at the comment. Your heart races a bit faster as you mentally replay all the scenarios that could be contributing to the issue. We recently deployed a change to the middleware used to fetch user information. Perhaps more servers would help decrease the load. Is that something DevOps can do…
"I'll check it out and see what's up", writes Dennis. Your heart settles and feel thankful that he’s checking out the issue. An hour later, the issue just sort of disappears. Dennis reports his findings, or lack thereof and the VP moves on to more important issues. We’ll keep an eye on it, Dennis reassures.
Dennis didn’t really do anything. The VP will remember his effort though. He stood up after a few minutes of awkward Slack silence to take lead on an issue that he likely didn’t know how to resolve himself.
Practice saying Yes to fires. You won’t always know how to solve them but you will learn a lot about working under duress and get a much more intimate familiarity with your codebase. This may actually be one of the most crucial aspects to getting promoted as a developer.
3. Onboard New Members
One of your coworkers hit the two year mark on your team and promptly left for greener pastures. Such is life. Alan starts on Monday after next and needs an on-boarding buddy. Dennis and Linda are the top prospects for pairing with Alan but you know how those super-senior developers are…. you know.
Before your manager thrusts the responsibility on them, you raise your hand to volunteer. Now they are the ones silently thanking you.
On-boarding new team mates is incredibly important as it will either set them up for success and allow them to quickly contribute to the team or leave them feeling unsure of their decision to join your company and confused about how to write the sexy code you need for your mission critical application: a food truck finder.
Teaching others how your various processes, apps and ceremonies work reinforces your own understanding and can often lead to new discoveries with a fresh perspective. Why does this work like this? your mentee asks. Good point, perhaps this custom API client can be replaced with a library like axios. You make a note.
If your team is in a high growth stage, refining the on-boarding process can lead to tangible results. The faster and easier developers are able to get set up and begin contributing, the better for morale, retention and velocity. Managers love velocity 😉
4. Teach What You Do Know
Linda and Dennis have been writing Javascript since the beginning of time. They’ve contributed to open source projects and frameworks that are widely used not in just your organization but around the world. What are you going to teach them?
Well, probably not much about Javascript but perhaps you went to a bootcamp where you were exposed to Ruby, Python, Heroku or AWS. If your company hosts show and tell sessions where developers get to share expertise across domains then offer to present on a topic you’re familiar with. If your company doesn’t have any forum for developers to learn from each other then you need to make one.
Having a space for developers to learn from one another helps everyone’s career trajectory. Show off that new React UI library you used last weekend on that project you’re never going to finish. Maybe you’ve discovered a code editor that is not VS Code that you think would make the team’s lives collectively better.
These presentations don’t need to be the most technically advanced to be useful. Bonus points if you spearhead the effort to begin monthly or bi-monthly knowledge sharing sessions.
You Are More Than the Code You Write
While you will be judged largely on the code you produce, the scrutiny over your choice to use a functional or object oriented approach will likely go unnoticed by your managers and customers. To have a larger impact on your organization, look at other areas where you can contribute to make your life and your team mates’ just a bit better.
😎 Tired of endless tutorials? Get your hands dirty with challenges guaranteed to level you up as an engineer 🚀
Interview prep and learning community 8 week program you can sign up for here [10 spots left]
Brian Jenney
4y ago
Sure, you can take on the "easy" assignments, keep your head down during meetings and be rewarded with a 3% increase each year to stave off inflation and hope you aren't cut when the economy goes through a rough period. I did this for the first 3-4 years of my career as a software developer and felt stuck.
Within about a year of implementing the steps I will share with you, I was senior developer at my current company and had another offer for senior at a fast paced tech startup in the San Francisco Bay Area.
At my current company I worked my way up to staff level and then engineering manager within 2 years. I'm not teaching you based on a theory here - these are the 3 things I did to accelerate my career, gain credibility and get promoted:
Step 1: Run towards fires
Handling high visibility issues immediately gives you credibility as an engineer (even if you reach out for help). Working on call and volunteering to triage severe outages or bugs also introduces you to parts of the codebase you might not otherwise be exposed to.
The Engineering Director my former company cited my late night bug fix for a critical incident as one of the deciding factors for my promotion to Senior Developer. At my next company, I volunteered to be on-call as soon as possible because I wanted to quickly establish myself as a technical peer.
Volunteer for on-call at your company if you haven't already AND next time you see someone raise a critical incident in a public channel - raise your hand to investigate.
Step 2: Write excellent peer reviews
One of the most underrated ways to gain influence on your team is through writing really thorough code reviews.
Do not just LGTM your way through reviews. Really dig in and ask questions about the choices made. Give praise, offer suggestions and take discussions offline if needed.
Act as a shepherd of the codebase and enforce high quality. Catching bugs before they hatch will save your team mates from embarrassment and establish you as a technical authority.
Once I started really taking reviews seriously, I actually got thanked by team mates during yearly reviews which influenced my manager's decision to fight for my promotion.
Step 3: Do things in public
It's great that you sped up that slow query by 50% through a minor refactor. But how in the hell will anyone know unless you tell them? Make your manager's decision to promote you an easy one. Document and share your wins. Remember, they have other reports and their own workload. They are NOT digging around checking out your peer reviews and code quality.
There are a few public forums available for you as an engineer to show off your achievements without feeling like you're "bragging"
Demos of your current sprint work during demo days
1 on 1's with your manager
Lunch and learns (bonus points if you introduce them to your company)
As an FYI in a public channel (e.g. FYI - noticed a problematic widget on our homepage. A fix has been implemented and please let me know if you see this problem again in the future)
The most technically proficient engineers aren't always the ones who get promoted. So yes, you must be good at writing code but that's not always enough to get to the next level.
Pssst...
Speaking of getting to the next level, enrollment opens next week for my front end interview prep group. At the end of this experience you will understand Javascript better than you ever have before, know how to tackle the 2 most common ReactJS interview formats and know how to implement and leverage the 5 data structures which make up the majority of DSA problems. Reply "interview" and I'll save you a spot or go here
Brian Jenney
4y ago
You want to lose weight. For health reasons. To look good shirtless. To show your ex what they're missing. I get it. No judgement.
After a solid decade of drinking, partying and generally eating like an asshole, I finally got sober and got my life together. Dropping the bottle was hard. Dropping the 30 pounds I had put on over the years was maybe harder.
I started exercising once I stopped drinking but nearly all of the results I got happened in the last 18 months.
Unfortunately, there is so much "information" out there about dieting and weight loss that it's easy to get confused or led down the wrong path.
You have good intentions but poor implementation.
Extreme diets aren't sustainable
There are no magic foods or times of day which you should eat
You're eating more than you think
You're making it too complicated
It's actually pretty simple
It is certainly NOT easy.
Here's how I did it:
Step 1: Know Your TDEE
Total Daily Energy Expenditure. Basically, how many calories do you burn per day doing you. https://tdeecalculator.net/
Use the calculator in the link above to determine your TDEE. (HINT: choose 'Sedentary' for Activity Level).
Great. Now you have a baseline for how many calories you need a day.
Step 2: Measure What You Eat
99% of us eat more than we think.
Now that you know the number of calories needed to sit on your ass all day, we have some basic math to do:
Eat less calories than used for your TDEE.
Buy a digital food measuring scale. They're not expensive you cheap bastard. No excuses. You cannot eyeball the amount of rice you're stuffing down your face.
Track every goddamn thing you eat into MyFitnessPal. It's also free.
Step 3: Plan Out Your Staple Meals
I don't meal prep.
Maybe you don't want to either.
Pick a couple staple meals that fit your calorie goals.
Perhaps you like sweets like me so make sure to incorporate those into your calorie budget. Be realistic!
Honestly, it doesn't really matter where your calories come from as far as weight loss is concerned.
You can lose weight eating nothing but twinkies as long as you are eating less than the number of calories needed to maintain your current body weight.
Don't do that of course.
Some easy to make, low calorie foods that I use for my daily meals:
Egg whites
Ground turkey (99% fat free)
Zero pop popcorn
Chocolate rice cakes
Chicken breast
Quest Protein bars
Low calorie mozzarella
Remember, measuring is key!
I buy foods that I can easily measure like cartons of egg whites and ground turkey.
I use measuring cups for my cheese and popcorn... yeah, I know.
Eating out can be a bit of a guessing game but MyFitnessPal has a shocking amount of data for restaurants. Don't be lazy. Also, maybe eat out less.
Step 4: Weigh Yourself Everyday. Every. Day.
Your weight will fluctuate. Sometimes by a lot.
This is why it's so important to weigh yourself everyday. You want a downward trend but don't freak out if there are spikes here and there. That's normal.
Here's what my chart looks like:
Always weigh yourself in the morning when you are at your lightest. This is both for your own mental health and to keep an accurate record of your progress.
Don't be shocked when you go up 5 pounds after binging on salty foods or after a weekend drowning your sorrows at an all-you-can-eat buffet.
On top of weighing yourself, take a revealing picture of yourself every Friday. A nice spicy pic for just your eyes.
The number of pounds you've dropped is not always the most accurate reflection of your progress.
Do you look better without clothes? Progress.
Step 5: Know Weight Loss Math.
You know your TDEE.
You are tracking calories.
I hope you are exercising.
So how fast will those rolls disappear?
Depends.
It takes roughly 3500 calories to add a pound. So work backwards.
Can you decrease 500 calories a day from your maintenance calories to be in a 3500 calorie deficit?
I'd say that's aggressive but possible.
You have a few options:
Eat roughly the same and burn more calories from working out
Eat less and don't work out
Eat a little less AND workout (the best way)
At the end of the day, you must re-calibrate based on your weight goals.
Not losing weight for 2 weeks? Lower your calories by 200 a day or exercise more.
As long as you are on a downward trend, you are doing great.
Some additional food math you might find useful:
4 Calories per gram in carbs
4 calories per gram in proteins
9 calories per gram in fats
You may notice fats have significantly more calories than proteins and carbs which means if you want to eat more then stay away from high fat foods.
Conclusion: Don't Give Up
Most people won't follow the steps I've outlined above. They will make every excuse why they can't. They have a very unique situation which prevents them from weighing food or tracking what they eat. They simply don't have the time!!!
I know those people. I was a member of their group for quite a while.
Don't be those people.
I'm not a certified personal trainer or dietician but I do know what has worked for me.