Skip to content

My Career Roadmap

This article was written over 18 months ago and may contain information that is out of date. Some content may be relevant but please refer to the relevant official documentation or available resources for the latest information.

Every developer has their own unique roadmap. I love hearing these stories as they’re constant reminders that there is no right way. Anyone can become a successful developer as long as they have the passion for it.

I’ll be sharing my roadmap in hopes that someone also realizes that there are multiple ways to be part of the programming world.

My journey started when I attended a junior college in an effort to complete the prerequisites for a Biochemistry degree. I actually got far enough to start taking Organic Chemistry courses. However, my heart wasn’t in it. I found it boring and dreaded anything related to those science classes. I did find it cool that I could recognize some of the fancy ingredients in a shampoo. It just wasn’t what I connected with.

I knew that something had to change. I was on track to transfer to a four year university in less than two years. I was always interested in computers and thought about programming. I still don’t know why I was drawn to that: maybe social media made it look cool?

The dilemma was to either continue or take a risk by starting a whole new career. I didn’t want to spend more time at junior college, so I needed to make a hard decision: either continue with Biochemistry or drop it completely to pursue programming, but still transfer within the estimated year.

I probably would have chosen to experiment with both at the same time if I had realized this a couple of years prior. However, I ended up changing majors within a week. It was one of the best decisions I have ever made.

My first programming class felt a bit scary. The building was run down and cold. The room was cramped. There were only two females (including myself). The course wasn’t hard or discriminating against genders but it probably felt that way due to being completely new to the field and not knowing anyone.

It didn’t discourage me from programming. In fact, I still remember typing up my first Hello World program. It was the feeling of writing code that made me realize that I was on the right track.

Luckily, the junior college had opened up the new STEM building a year later. This really made the place more welcoming. It was actually pretty cool. There were outlets everywhere! A dream for programmers that we take for granted.

One of the courses that I took was Internet Programming. This was a turning point for me. My professor recommended that I participate in the local hackathon that was coming up soon. He suggested forming a team with the two other females in class. I never once thought he was discriminating. I honestly believe that he saw potential in all of us but we were lacking confidence in a male-dominated world.

We participated in the hackathon as a female group. It was my first time working with a team and presenting our project to the public. We didn’t win any awards, but it provided some of the confidence that I was lacking. I finally understood that it didn’t matter what gender you are. I found a love of programming and wanted to be one of the best.

I ended up getting recruited for a local internship through the hackathon. I was able to learn about realistic expectations when building a project for a client. The lead developer was also very open to teaching a complete newbie. This is where I learned the basics for web development.

It was this type of support that helped shape my career.

I graduated from junior college with an associates degree in Chemistry and transferred the next semester.

The one regret that I do have in my career is the university that I chose. It didn’t have the best resources for the Computer Science students. The classes were boring and most of the professors didn't seem to care. If you weren’t on the game research cohort, you were just another student passing through.

During this time, I got a chance to be part of a research team. However, I decided to accept an internship instead. It was another difficult decision as both had great opportunities. I still think that the internship was the best route as it helped me later on.

The internship only lasted for the summer. I learned Polymer during this time. The project was my first deployment and it was used by the city. It was also another great confidence booster.

I returned to school with the goal to find my first job before graduation. Truthfully, it was very discouraging, even with my internship experiences. Most companies wanted developers with years in programming. They really don’t make it easy for junior developers.

I’m almost positive that I placed over 100 applications. When I did get a response, it was a decline. I also attended the career fair that the university organized. That’s where I found the company that gave me a job offer.

I started working for them after graduation. This led to web development in the Drupal world for a little over 2 years. It was a small company but provided development growth. I learned the importance of quality assurance and time management. I also acquired the skill to advocate for higher priority tickets.

The most important lesson was that a project can only thrive with a unified team and proper documentation.

However, the company had a tremendous downsize due to the pandemic.

I was once again on the job hunt. Fortunately, the connections I made during the summer internship helped me find a job at This Dot. There was still an interview process, which I passed due to all the career choices that were made.

I’m very excited to be here. I’m working with LitElement projects and more structured work environments. It really is a big difference from a very small company. I’m now pursuing the path of being a mentor, a dream that I had since my first internship. I’m working on improving a mentorship program and making sure my mentee has all the support she needs.

I barely have a bit over 3 years of work experience. The time went by very quickly and I’m still excited to be programming. I can’t wait to see where my roadmap will be in the next upcoming years.

Tweet me your favorite moment in your roadmap!

This Dot is a consultancy dedicated to guiding companies through their modernization and digital transformation journeys. Specializing in replatforming, modernizing, and launching new initiatives, we stand out by taking true ownership of your engineering projects.

We love helping teams with projects that have missed their deadlines or helping keep your strategic digital initiatives on course. Check out our case studies and our clients that trust us with their engineering.

You might also like

The Importance of Finding a Career Mentor cover image

The Importance of Finding a Career Mentor

What is a Mentor? > Mentor (noun): an experienced and trusted adviser. > "He was her friend and mentor until his death in 1915." > Similar: adviser, guide, confidant, confidante, counselor, consultant > - Google A mentor is someone who can be approached for advice. Some are informal like parents or friends. Others are more official through work. Regardless of their title, a good mentor is someone who can help you move forward. However, mentors are not for everyone. This is completely fine. There is no right or wrong path when it comes to advancing your career. Keep in mind that mentees have just as much responsibility as a mentor when participating in some form of mentorship. I have had a few mentors since my early years of being a developer. It wasn’t until the last few months that I got assigned a formal mentor. It’s been a great experience for me in both scenarios. There are many highlights that I want to share with you. These are some of the main reasons why I advocate for mentoring programs for career development. 1. Coding Skills Developers thrive by being exposed to all types of coding styles. I especially learn more when someone can review my code and provide feedback on improvements. There’s only so much you can learn from reading code or documentation. My mentors have provided their thoughts on different approaches to coding. One advice that has stuck out to me is the need for comments. Time can be saved by writing useful comments for future development even if you’re the only coder. They’re meant to explain the code versus having to take time to translate the lines into your native language. A mentor’s time is valuable. The less time they need translating, the more time they can provide a good review of your code. I knew that comments were important but it wasn’t until it was emphasized from someone that I respected that their value solidified in my mind. Some mentors are able to let you shadow them during their work day (mentees should also feel comfortable requesting this). If you have this opportunity, take it. You will be getting a first hand experience of how another developer reviews a task and implements it. I recently learned from a mentor that technical design documentation is crucial when preparing to add a major feature. It’s important to centralize the data and propose the best solution for the team along with your reasonings. This is something that was never mentioned in any of my college courses. 2. Work Culture Your mentor will have more experience with the company. Listen carefully to their time there. They can point you in the right direction when it comes to work related issues or concerns. For example, you will want to know how to officially request time off. If the mentor doesn’t know, they should be offering to help. Mentors are also great for connections. You may want to learn a new technology but your mentor may not be familiar with it. They might be able to recommend another developer. Let’s not forget that they have experience working in teams. This is a necessary skill to grasp as soon as possible. There may be times when you work with someone with a personality that doesn’t mingle well with yours. Your mentor may have worked with that same person or someone similar. They can surely provide advice on how to interact with this person. 3. Confidence Boost I can’t tell you enough how much it’s helped me be more confident as a developer when hearing my mentors voice their same concerns. I’m still considered new in the world of developers with almost 3 years of work experience. There are times that I experience imposter syndrome. I couldn’t believe my ears when a senior developer said that he still gets that same feeling. This was coming from a man who is highly respected in our community and has led multiple projects over his entire career. If someone like him feels the same, I honestly shouldn’t worry about it. It’s simply a feeling that everyone experiences. This syndrome doesn’t make me or you any less of a developer. It also helps to hear a mentor say that you’re doing great. It not only makes you feel better hearing it from someone you respect in the field, but it also gives you an insight that you are making good decisions. I was told that my compassion for newer developers is an excellent attribute to have. This was so important for me to hear from a mentor because one of my goals is to become a good mentor. Appraisals are great confidence boosters in any career role. It’s like getting a gold star in elementary school. Moving On Unfortunately, there are some people that are not meant to be mentors. If you happen to find yourself as a mentee in this situation, you need to move on. Find someone who you can safely share your concerns with. This may be the human resources department. They will probably give you suggestions on how to improve the situation before completely removing the mentor. Be open to their suggestions, especially if there is a chance of salvaging. However, there are times that you may have to push back. Don’t let this discourage you, though! This mentor was just not suited for you or maybe they really weren’t ready to be a mentor. This also applies for mentees. Mentors have the right to end the mentorship due to mentee participation. A mentoring relationship succeeds when both parties have their hearts in it, just as any relationship. Final Thoughts Mentors are practically anchors at the end of the day. They’re amazing people that remind us that we can one day be in their shoes: formally or informally. They are there for you! Don’t be afraid to talk to them. Send them a message! Make meetings! Take charge if needed! Mentors signed up to be available to you. It saddens me greatly to hear mentees get discouraged with their careers because their mentors refuse to do the program they signed up for. I recently became an official mentor for the apprenticeship program at This Dot. I want my mentee to feel comfortable talking to me. I truly believe that a mentor should be available and provide feedback and encouragement. Tweet me with your mentorship experiences! Are you in any? Planning to? Scared and need a push?...

How to Optimize Your Profile and Build a Developer Network on LinkedIn cover image

How to Optimize Your Profile and Build a Developer Network on LinkedIn

LinkedIn is a social network where you can connect and build relationships with other professionals in your field. A strong developer profile can lead to potential job opportunities and more connections in this industry. But how do you go about optimizing your profile and building a developer network on LinkedIn? In this article, I will walk you through each of the sections for a LinkedIn profile and show you the best ways to optimize them. I will also share tips on how to build relationships with other developers on Linkedin. Table of contents - What title should you use on Linkedin? - How to optimize your profile and background images - Is it ok to not include a profile image? - Do I need a background image? - How to create a custom Linkedin URL - How to optimize your about section - How long should the about section be? - What is the features section in Linkedin? - How to optimize your experience section - Should you show unrelated tech experience on your Linkedin profile? - How to optimize your education section - Should you have recommendations on your profile? - Should you take Linkedin skills tests? - Exploring other sections of the Linkedin Profile - How to connect with other developers on Linkedin What title should you use on Linkedin? A lot of people will say that titles don't matter, but in reality titles do play a role in our society whether we like it or not. If you are currently working as a software developer, then your title can say Software Developer or Software Engineer at XYZ company. If you are a lead, staff engineer, senior, etc., then put that in your title. If you are looking for your first job, then use "Software Developer" and list the technologies you are comfortable with. You want to avoid titles like "Aspiring Developer" or "Soon to be Developer" because that may disuade potential employers from looking at you before they are given an opportunity to understand what you have accomplished as a web developer despite not yet finding a formal role. How to Optimize Your Profile and Background Images When it comes to your profile picture, it is important to remember that you are interacting with other professionals in your industry. You want to choose a clean head shot that would be acceptable in professional settings. Avoid using pictures of you partying in college, or pictures that don't even show your face. You don't need to spend tons of money on professional head shots. You can even have a friend or family member take a head shot of you wearing a nice shirt. Is it Ok to Not Include a Profile Image? If you want to optomize your profile, it is very important to include a profile image. A lot of hiring managers and recruiters are actively looking for developers and your profile image helps put a face to the skills and experience listed. By omitting that image, you might get passed over for potential opportunities. Do I Need a Background Image? A clean and simple background image can help your profile standout. Canva is a free design tool that you can use to create a Linkedin banner. They have dozens of free templates to choose from that you can customize and apply to your profile. Here is what my LinkedIn profile and banner image looks like. How to Create a Custom Linkedin URL Linkedin has a feature where you can customize your profile URL making it easier for people to find you. To learn how to create a custom URL, please read through this Linkedin article. When it comes to naming your URL, I would suggest keeping it short and simple. I would suggest using your name and occupation like this: How to Optimize Your About Section This section is your opportunity to provide a short background on who you are professionally. It is best to talk about the types of projects you have worked on and tools/languages you are most familiar with. It is also good to talk about how you are involved with the community. For example, you might want to highlight your participation in open source projects, or your experience as a content creator. Here is my current "About" section: "I am a classically trained musician turned software developer who enjoys building solutions to unique business problems. I primarily work with React and TypeScript to provide clean efficient solutions to build better software products. I am actively involved in giving back to the community by participating in open source projects like freeCodeCamp. I have also written over 100 technical articles on HTML, CSS, JavaScript, Python and career development." How Long Should the About Section Be? I personally like "About" sections that are a few sentences long. You can also have 2-3 paragraphs for your "About" section. However, I don't think it should be any longer than what can be read in a minute or two because the goal is to provide a brief overview of who you are, not a complete autobiography. What is the Features Section on Linkedin? This is a section on your Linkedin profile where you can show off some of your recent projects and articles. In my opinion, it can act as a small portfolio, and is often underutilized by software developers. Here is a screenshot of my features section. I chose to list my Black Excellence Music Project and a couple of my top performing freeCodeCamp articles. This is a visually appealing way to show potential employers and recruiters your top work. How to Optimize Your Experience Section This section should be reserved only for work experience. There are other sections in your Linkedin profile where you can add volunteer experience or education. Just like on a resume, you would place your most recent jobs first. Try to focus on highlighting significant contributions you made to the projects. Here is an example from my experience section on Linkedin. - Implemented a light/dark theme solution for the This Dot Labs website - Performed accessibility audits for the This Dot Labs website and provided solutions for increasing performance and accessibility scores - Performed extensive smoke testing for client applications and reported bugs and feature requests to the rest of the development team - Built out several UI examples for a client's documentation page If you have freelance experience, talk about the types of projects you built for them, and how you added value to their business. Should You Show Unrelated Tech Experience on Your Linkedin Profile? If you are a career changer like myself, there is nothing wrong with showing your previous work experience from another industry. That shows potential employers that you have worked in a professional setting before and have been gainfully employed for the past few years. As long as you place your relevant tech experience at the top, then you will be fine. How to Optimize Your Education Section If you have a college degree, even if it is not in computer science, definitely list that on your Linkedin profile. If you have certifications, like the AWS certification, then list those as well. There is some debate about whether or not to list certifications from online courses like Udemy. In my opinion, there is no harm in listing those, but it won't carry as much weight with employers and recruiters as AWS certifications, bootcamp certificates, or computer science degrees will. Should You Have Recommendations on Your Profile? Yes! When people can vouch for your work, it goes a long way with future employers and recruiters. This will be especially helpful for those looking for their first full time software job who have done contract work or freelance work in the past. Should You Take Linkedin Skills Tests? There is a section on Linkedin where you can take different skills tests in areas like HTML, CSS, JavaScript, etc. If you pass those tests, then you can list them on your profile. These skill tests don't hold a lot of weight with recruiters or potential employers because they will provide their own skills tests during the interview process. There is no harm in taking them if you want to, but doesn't add a whole lot to your profile. Exploring Other Sections of the Linkedin Profile We have covered all of the core sections of the Linkedin profile, but there are additional sections you can choose to add. Here are some sections you might consider exploring: - Volunteer experience - Projects - Organizations - Publications - Courses You can find all of these additional sections when you click on the "Add Profile" button at the top of your Linkedin profile. For more information and suggestions on how to optimize your profile, I suggest you watch Danny Thompson's Linkedin series on YouTube. How to Connect With Other Developers on Linkedin There are many ways to build out your network on Linkedin. One common way would be to send a connection request to another developer. If you have been following someones' work online, or previously connected through a conference or online meetup, it would be a good idea to connect with them on Linkedin too. Here is a sample message you can send along with your connect request. "Hi, this is Jessica Wilkins and I enjoyed talking with you at the last Women in Tech meetup. I would love to be able to connect with you here on Linkedin too." Now, when that person receives that connection request with a personalized message, they will be more inclined to accept. If you just send a connection request to a complete stranger without a personal message, then you will most likely be ignored. Another way to connect with developers, is by commenting on and sharing others' posts. If someone is sharing an article or posting a hot topic, feel free to jump in the conversation. If you really enjoyed the article, then share it and/or reach out through personal message letting the author know you enjoyed it. Those small gestures will go a long way to build connections over time. Conclusion I hope you enjoyed that article on optimizing your Linkedin profile and building connections with other developers. Linkedin is a very powerful tool and can help you advance in your career. If you are interested in connecting with me on Linkedin, then please visit my profile....

Computer Science Degrees are Optional  cover image

Computer Science Degrees are Optional

Degrees aren’t always needed. In today’s job market, there is most likely an alternative option for a degree: self-taught, bootcamps, etc. However, there are still companies that require a college degree. One of my colleagues at work expresses that “*unless you really want to work as a research engineer for one of the very large tech companies like Google, etc I don’t see the value in an advanced degree in CS.*” This statement should not discourage you from pursuing this career path, especially if you want to become a research engineer. There has been a recent conversation at work that provided a number of those with a college degree versus those who do not. The College Path I am categorized with those who have a Computer Science B.S. degree. It was the safe option for me. I would have the degree just in case (being the first in my family to obtain one was also a motivator) and I gained some coding experience through courses. I still don’t regret taking this path. It’s given me the opportunity to get a glimpse into both sides. However, college only teaches you so much, especially where you attend. My college was still very new compared to its affiliates, so the Computer Science department was still developing. I was taught the basics (how to do a for loop, etc). The classes were boring and I never felt that the important parts of coding were taught. The closest I got was through the Software Engineer course that was taught by a Facebook developer. He showed us how things really went in the “real world.” We were assigned a semester project that would be presented at the Facebook headquarters in Menlo Park. This class taught me the importance of teamwork: team interaction, code management, and leadership roles. I came out of college with a good programming foundation. It also provided me with internship experience. The college I attended advertised a local hackathon. I wouldn’t have known of this event occurring in such a small city if I had not taken the college route. I was introduced to the founder of a local website creation company. Due to my professor’s recommendation, I became one of the interns at this location. It was the first time that I was able to get a glimpse of how business was conducted with a client. Unfortunately, this wasn’t taught in any of the courses I took. College gave me the extra time to figure out what type of programmer I wanted to be. I’ve coded in multiple languages like Java, Python, and React. I even dabbled a bit with game development. I was able to find the most joy from working with web development. College can also provide one of a kind experiences. Some partner with local businesses to give students an opportunity to get work experience. I was fortunate to be enrolled in a university that had this opportunity available. In partnering with a local business as a student, we were presented with a problem and it was our job to create a proof to concept and demonstrate it to our client. We had the entire semester to complete the solution. During this time, we had multiple deadlines (just like any real project) that we stressed over. There were times that we did have to work late into the night because a bug was found before our next release. We were thrown into multiple situations that I have seen occur during my work experience. These are the moments at college that helped me navigate through stressful moments at work. Bootcamp may not provide the same opportunities. Another of my colleagues who went to college was able to participate in a similar program. He worked with the company for two years, forming connections with his co-workers. It was one of these connections that led him to accept a job offer with another company. If it had not been for this company being persuaded to attend AngularConnect, he might not have been introduced to our current CEO. He does voice that college is not needed to be a good developer. However, he does add that “*If I hadn't gone to uni, who knows what kind of path I'd have taken, but 100% the connections I gained as a result of uni has helped me get to where I am now.*” Alternative Paths All roads lead to the same destination. It just depends on where you want to learn your base. Another of my colleagues stated: “*It's like building a foundation before building the house.*” I agree: people want to hire someone that understands the importance of the foundation regardless of the background in order to build a strong house. One of my professors said something that still stays with me: "School only teaches you about 10% but your job will teach you the rest." I completely stand by this. I was able to understand the basics like Git by the time I entered the work field. However, the business side like time frames was something that I picked up from trial and error at work. This experience has been iterated at work as well: “Almost all of my learning of development was on the job, although I've reached back to my coursework as I got further in my career to help me make sense of more of the tougher algorithmic challenges on some projects I worked on in the past.” - Colleague I’ve only been in this field for about 4 years. I’ve met strong programmers on both sides. I’ve seen a teacher’s aide that can write structured scripts for a complex game. I’ve also seen a developer (without attending college) who has delivered many successful projects at such a young age. It’s their commitment to become a better programmer that has them thrive in any environment. It just boils down to which environment you want to experience. “I don’t really regret anything about going to university except that I wasn’t the best student in my late teens and twenties so I wish I’d had the option of fast tracking the practical knowledge and jumping right into my career. I wish coding bootcamps had been available to me instead of college honestly.” - Colleague My college background never was asked when I was being interviewed by the companies that ended up employing me. It all came down to my coding skills and the connections (along with my personality). It really depends on the company who is hiring. That’s why it’s important to do your research before investing your time in the application process. College is not for everyone. Don’t let the pressure stop you from doing what you want to do with your career. Success as a programmer can be accomplished regardless of a degree. There are pros and cons with any path. Code bootcamps can provide the same benefits as college. Some bootcamps might be even more intense than college, which can lead to great learning opportunities. I’ve met an amazing developer who came from a bootcamp. Her skills have landed her a position with a company as a developer within months of her graduation. There hasn’t been a task that she wasn’t able to handle. Bootcamps are just as beneficial. Remember, it’s not where you learn the foundation that matters, it’s whether you understand it. Keep learning, coding, and seeking out connections. Tweet me your coding start. I would love to share your story with other people who need that extra motivation to get one step closer to their goal....

The Quirks And Gotchas of PHP cover image

The Quirks And Gotchas of PHP

The Quirks And Gotchas of PHP If you come from a JavaScript background, you'll likely be familiar with some of its famous quirks, such as 1 + "1" equaling "11". Well, PHP has its own set of quirks and gotchas, too. Some are oddly similar to JavaScript's, while others can surprise a JavaScript developer. Let's start with the more familiar ones. 1. Type Juggling and Loose Comparisons Like JavaScript, PHP has two types of comparison operators: strict and loose. The loose comparison operator in PHP uses ==, while the strict comparison operator uses ===. Here's an example of a loose vs. strict comparison in PHP: ` PHP is a loosely typed language, meaning it will automatically convert variables from one type to another when necessary, just like JavaScript. This is not only when doing comparisons but also, for example, when doing numeric operations. Such conversions can lead to some unexpected results if you're not careful: ` As you can see, the type system has gotten a bit stricter in PHP 8, so it won't let you commit some of the "atrocities" that were possible in earlier versions, throwing a TypeError instead. PHP 8 introduced many changes that aim to eliminate some of the unpredictable behavior; we will cover some of them throughout this article. 1.1. Truthiness of Strings This is such a common gotcha in PHP that it deserves its own heading. By default, PHP considers an empty string as false and a non-empty string as true: ` But wait, there's more! PHP also considers the string "0" as false: ` You might think we're done here, but no! Try comparing a string such as "php" to 0: ` Until PHP7, any non-numeric string was converted to 0 when cast to an integer to compare it to the other integer. That's why this example will be evaluated as true. This quirk has been fixed in PHP 8. For a comprehensive comparison table of PHP's truthiness, check out the PHP documentation. 1.2. Switch Statements Switch statements in PHP use loose comparisons, so don't be surprised if you see some unexpected behavior when using them: ` The New Match Expression in PHP 8 PHP 8 introduced the match expression, which is similar to switch but uses strict comparisons (i.e., === under the hood) and returns a value: ` Unlike switch, there is no "fall-through" behavior in match, and each branch must return a value, making match a great alternative when you need a more precise or concise form of branching—especially if you want to avoid the loose comparisons of a traditional switch. 1.3 String to Number Conversion In earlier versions of PHP, string-to-number conversions were often done silently, even if the string wasn’t strictly numeric (like '123abc'). In PHP 7, this would typically result in 123 plus a Notice: ` In PHP 8, you’ll still get int(123), but now with a Warning, and in other scenarios (like extremely malformed strings), you might see a TypeError. This stricter behavior can reveal hidden bugs in code that relied on implicit type juggling. Stricter Type Checks & Warnings in PHP 8 - Performing arithmetic on non-numeric strings: As noted, in older versions, something like "123abc" + 0 would silently drop the non-numeric part, often producing 123 plus a PHP Notice. In PHP 8, such operations throw a more visible Warning or TypeError, depending on the exact scenario. - Null to Non-Nullable Internal Arguments: Passing null to a function parameter that’s internally declared as non-nullable will trigger a TypeError in PHP 8. Previously, this might have been silently accepted or triggered only a warning. - Internal Function Parameter Names: PHP 8 introduced named arguments but also made internal parameter names part of the public API. If you use named arguments with built-in functions, be aware that renaming or reordering parameters in future releases might break your code. Always match official parameter names as documented in the PHP manual. Union Types & Mixed Since PHP 8.0, we can declare union types, which allows you to specify that a parameter or return value can be one of multiple types. For example: ` Specifying the union of types your function accepts can help clarify your code’s intent and reveal incompatibilities if your existing code relies on looser type checking, preventing some of the conversion quirks we’ve discussed. 2. Operator Precedence and Associativity Operator precedence can lead to confusing situations if you’re not careful with parentheses. For instance, the . operator (string concatenation similar to + in JavaScript) has left-to-right associativity, but certain logical operators have lower precedence than assignment or concatenation, leading to puzzling results in PHP 7 and earlier: ` PHP 8 has fixed this issue by making the + and - operators take a higher precedence. 3. Variable Variables and Variable Functions Now, we're getting into unfamiliar territory as JavaScript Developers. PHP allows you to define variable variables and variable functions. This can be a powerful feature, but it can also lead to some confusing code: ` In this example, the variable $varName contains the string 'hello'. By using $$varName, we're creating a new variable with the name 'hello' and assigning it the value 'world'. Similarly, you can create variable functions: ` 4. Passing Variables by Reference You can pass variables by reference using the & operator in PHP. This means that any changes made to the variable inside the function will be reflected outside the function: ` While this example is straightforward, not knowing the pass-by-reference feature can lead to some confusion, and bugs can arise when you inadvertently pass variables by reference. 5. Array Handling PHP arrays are a bit different from JavaScript arrays. They can be used as both arrays and dictionaries, and they have some quirks that can catch you off guard. For example, if you try to access an element that doesn't exist in an array, PHP will return null instead of throwing an error: ` Furthermore, PHP arrays can contain both numerical and string keys at the same time, but numeric string keys can sometimes convert to integers, depending on the context> ` In this example: - "1" (string) and 1 (integer) collide, resulting in the array effectively having only one key: 1. - true is also cast to 1 as an integer, so it overwrites the same key. And last, but not least, let's go back to the topic of passing variables by reference. You can assign an array element by reference, which can feel quite unintuitive: ` 6 Checking for Variable Truthiness (isset, empty, and nullsafe operator) In PHP, you can use the empty() function to check if a variable is empty. But what does "empty" mean in PHP? The mental model of what's considered "empty" in PHP might differ from what you're used to in JavaScript. Let's clarify this: The following values are considered empty by the empty() function: - "" (an empty string) - 0 (0 as an integer) - 0.0 (0 as a float) - "0" (0 as a string) - null - false - [] (an empty array) This means that the following values are not considered empty: - "0" (a string containing "0") - " " (a string containing a space) - 0.0 (0 as a float) - new stdClass() (an empty object) Keep this in mind when using empty() in your code, otherwise, you might end up debugging some unexpected behavior. Undefined Variables and isset() Another little gotcha is that you might expect empty() to return true for undefined variables too - they contain nothing after all, right? Unfortunately, empty() will throw a notice in such case. To account for undefined variables, you may want to use the isset() function, which checks if a variable is set and not null: ` The Nullsafe Operator If you have a chain of properties or methods that you want to access, you may tend to check each step with isset() to avoid errors: ` In fact, because isset() is a special language construct and it doesn't fully evaluate an undefined part of the chain, it can be used to evaluate the whole chain at once: ` That's much nicer! However, it could be even more elegant with the nullsafe operator (?->) introduced in PHP 8: ` If you’ve used optional chaining in JavaScript or other languages, this should look familiar. It returns null if any part of the chain is null, which is handy but can also hide potential logic mistakes — if your application logic expects objects to exist, silently returning null may lead to subtle bugs. Conclusion While PHP shares a few loose typing quirks with JavaScript, it also has its own distinctive behaviors around type juggling, operator precedence, passing by reference, and array handling. Becoming familiar with these nuances — and with the newer, more predictable features in PHP 8 — will help you avoid subtle bugs and write clearer, more robust code. PHP continues to evolve, so always consult the official documentation to stay current on best practices and language changes....

Let's innovate together!

We're ready to be your trusted technical partners in your digital innovation journey.

Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.

Prefer email? hi@thisdot.co