DEV Community: Nicolas Dupont

How to Parse a CSV File in 4 Lines of PHP?

Nicolas Dupont — Sat, 26 Mar 2022 14:02:43 +0000

CSV is a standard format to integrate data in applications; when doing so, we often have to import data based on this format. PHP comes with native functions to open a file and parse CSV rows.

Let's take the file classic-composers.csv and its content as an example:

"First name","Last name","Born","Died"
"Carl Philipp Emanuel","Bach","8 March 1714", "14 December 1788"
"Johann","Stamitz","18 June 1717","27 March 1757"
"Joseph","Haydn","31 March 1732","31 May 1809"
"Johann","Christian Bach","September 5, 1735","January 1, 1782"

We can also look at it as a table:

First name	Last name	Born	Died
Carl Philipp Emanuel	Bach	8 March 1714	14 December 1788
Johann	Stamitz	18 June 1717	27 March 1757
Joseph	Haydn	31 March 1732	31 May 1809
Johann	Christian Bach	September 5, 1735	January 1, 1782

We can parse and display each line using 4 simple lines of PHP code:

// open the file in read mode
$file = fopen('data/classic-composers.csv', "r"); 
// browse each csv line
while (($row = fgetcsv($file)) !== false) {
  // print the line content
 var_dump($row);
}
// close the file
fclose($handle);

Here is the output of the execution:

array(4) {
  [0]=>
  string(10) "First name"
  [1]=>
  string(9) "Last name"
  [2]=>
  string(4) "Born"
  [3]=>
  string(4) "Died"
}
array(4) {
  [0]=>
  string(20) "Carl Philipp Emanuel"
  [1]=>
  string(4) "Bach"
  [2]=>
  string(12) "8 March 1714"
  [3]=>
  string(16) "14 December 1788"
}
// and more lines

That's it for this simple example using native functions!🚀

If you want to go further with CSV manipulation in PHP, you can explore this comprehensive guide on reading and writing CSV files in PHP. It explores modern libraries to parse CSV, explain how to read a one million-line CSV file using a minimum of memory, and share advanced tips and tricks.💡

What Is the Next Step in Your Software Developer Career?

Nicolas Dupont — Wed, 19 Aug 2020 11:51:11 +0000

You're working as a software developer for a few years and wonder what will be the next step in your career?

Let's review the different paths, the options you may choose to continue to progress and grow your impact.

The Technical Expert Path

You're interested in designing and mastering complex architectures, in teaching technical aspects to your teammates. You like to explain different designs, their pros/cons in the given context, and support solid tech decision making.

The technical expertise path could be a good fit! It leads you to design some larger systems by taking into account architecture, scalability, and security concerns.

The Lead Developer Path

You're interested in leading a technical team and animating this team to collaborate efficiently together. You like to organize the work and to follow the progress on your project. You enjoy making or supporting relevant technical trade-offs. The ones that balance well the business & technical aspects.

This lead dev path could be an excellent fit! It requires to balance strong technical leadership with an excellent team animation to make the project a success. If you wonder what aspects you need to work on to follow this path, I published an extensive article on How to Become a Lead Developer?

The Engineering Manager Path

You're interested in mentoring your teammates and supporting the development team to grow its impact. The business attracts you, and you like to tie the business goals with the technical strategy. You enjoy thinking about team organization. You love to get involved in hiring, onboarding, and training.

The engineering manager path could be a great fit! It's a significant shift, almost a new career. It requires changing your focus from tech leadership to people leadership, to working a lot on communication and organizational topics. If you wonder what aspects you need to work on to follow this path, I published an extensive article on How to Become an Engineering Manager?

Last Thoughts

Each developer's journey is different; there is no one-size-fits-all. What matters is to choose a path that matches what you like to do and who you'd like to become.

Moving into a different position is, first and foremost, a choice. Once you've decided, you'd raise your chance to reach this role with proper preparation. Your current job already offers plenty of opportunities to train yourself, what matters is to identify them, and to be ready to catch them.

Do you envision any other paths to progress in your developer's career?

How to Become a Lead Developer?

Nicolas Dupont — Sat, 15 Aug 2020 11:42:05 +0000

Starting in 2009, I've worked as a software engineer, lead developer, engineering manager, vice-president of engineering, and chief product officer. During this journey, I had the opportunity to support talented engineers in different career transitions, from individual contributor to lead developer, from lead developer to engineering manager. I found many shared struggles while mentoring them; that's why I'm writing a series on how to get prepared to move into these positions.

What is a Lead Developer?

The Lead Developer is the technical leader of a team of developers. She's in charge of the success of a project. She animates the delivery to build the right things, the right way, and on time.

She is responsible for advocating on best practices, communicating on the progress, mentoring other developers, providing technical guidance to the team, and deciding on technical trade-offs.

Depending on the organization, we can refer to a lead developer as a lead engineer, a team lead, a technical project manager, or a tech lead.

Career Path

In an engineering career ladder, the lead developer position often sits between the individual contributor track and the people manager track.

It's not an engineering manager position as engineering management includes people management responsibilities. However, moving into a lead developer position is a solid first step in engineering management.

Moving into a lead developer role is also a significant progression in the technical leadership track. It's an excellent way to get prepared to become a software architect, a staff engineer, or a principal engineer.

This role opens a lot of opportunities.

Become a Lead Developer?

If you want to become a lead developer, a critical aspect to consider is the shift of responsibilities.

A lead dev is responsible for the result of a team on a project. It's not anymore about your own technical excellence, or what you individually build or contribute to building. It's now about the success of the development team. Let's discuss the main areas to work on to be prepared to move to a lead developer position.

Technical guidance

You can usually pretend to become a lead developer after a few years of experience as a developer or software engineer. These first years are critical to consolidate your technical skills and learn to be autonomous in your developments.

You start to have a solid sense of how to build things to answer the business needs, and you did it with success on several projects.

A useful exercise is to discover how to articulate larger pieces of software. You need to understand the technical decisions and the trade-offs regarding a given architecture. You can muscle your tech decision-making by reviewing existing projects and chatting with current tech leaders on how and why we build this way.

Be a role model

As for any leadership position, it's critical to embody the excellence and the behavior that your organization expects for developers.

If you lead a team of developers, you become their representative, and they deserve to be well represented. To become a lead developer, you need to become first a great developer.

Work organization

A critical success factor is how the team collaborates.

Get interested in project management practices. How to prepare the work? How to slice the tasks? How to measure and communicate on the progress?

Get interested in each other skills. Who is comfortable doing what? What your teammates like or not like? What do they want to learn?

Any teamwork requires some upfront preparation and a proper animation to collaborate efficiently. Ask if you can contribute in a way or another in these aspects. Your tech lead or manager should be happy to delegate you some parts of it, and it will be an enjoyable exercise to train your leadership muscle.

Be a mentor

A lead developer contributes actively in helping her teammates to learn, to become better software engineers.

There are plenty of opportunities to strengthen your mentoring skills. You can improve by explaining an intricate part of the tech stack. You can also help to onboard a new developer on the team. You can mentor a junior developer or an intern.

The most important aspect is to have the proper attitude: be always willing to help. You can evaluate your progress by how often your teammates are coming to you to ask for your help or work with you.

Communication

The foundation of efficient teamwork is efficient communication. As a team, we need a shared understanding: why we do things, what's our mission, what our goals are.

Frictions, duplicate work, or a waste of effort often come from a few misunderstandings between team members. To mitigate this inherent challenge, you'll need to work on your communication skills.

You can improve by training yourself to be crystal clear when communicating. Listen carefully, ask genuine questions to ensure you understand correctly, re-phrase with your own words. Adapt your message to the audience's knowledge and domain of expertise.

Contribute to helping the team communicate well, document the significant changes, and amplify the essential pieces of information.

Earn Trust

Last but not least, to move to a lead developer position, you will need to earn your teammates' and manager' trust.

We build trust by our actions and our behavior, by being consistent, by being reliable, by helping others.

A lot of small and concrete actions will contribute to building the strong grounds, the foundations of the team's trust. And if you want to become a lead developer, you can start making these actions right now!

I formerly published the How to Become a Lead Developer story on my blog. I write a couple of articles per month; about software engineering, product management, and work organization.

Your Error Messages Deserve Some Love

Nicolas Dupont — Sun, 26 Apr 2020 14:59:06 +0000

I recently attended a compelling presentation. 😍

In our distributed company, English is a second or third language for most of the teammates. We have a dedicated English teacher. Camille runs training and workshops to help us to improve.

Camille recently worked on our products' error messages with our product management team.

The first goal was to ensure the correctness of these messages.

She pushed the exercise at a far more advanced level.

Error messages

When running into an error message, the experience is, most of the time, frustrating.

Something unexpected happened, and it breaks your productivity flow. You now have to understand why this piece of software does not work the way it's supposed to. You have to figure out what to do to be able to move on. And you have more interesting to do.

An error message has to be crystal clear

Each message has to guide the user and must be self-explanatory, concise, and accurate.

When we write error messages, the temptation is high to detail as much as possible. What happened, what are the business rules. We should focus on helping the user to work around the issue and to move on.

Error messages don't have to be boring or impersonal. An error message is a way to engage with your users. It can be user friendly, using "you" and "we" pronouns creates a more human feeling.

For instance:

"Cannot remove this attribute used as a variant axis in a family variant."

"You cannot remove this attribute because it is used as a variant axis in a family variant."

Our messages have to be consistent across your whole application. We can adapt their content depending on the user persona we're talking too. But keeping a consistent tone of voice is essential.

Another good practice is to write them positively and to avoid negative sentences.

For instance:

"This value should not be blank."

"This value is required."

Conciliate these pieces of advice can be challenging, what to do when in doubt?

"The Platinium rule, if you're not sure, the rule overriding all the others, is your message has to be crystal clear." (Camille B.)

Error messages are a critical part of the User eXperience

Looking at most of the software I use, error messages appear to me as a second class citizen of the UX.

We can fix this in our industry. We can improve. We can craft great error messages. We can make them more engaging and as enjoyable as success messages.

Last words

Dear Camille, thank you! For pointing out this problem, for evangelizing and training our teams. Write great error messages is a step forward to deliver a more engaging experience to our users. 🦄

I formerly published the Your Error Messages Deserve Some Love story on my blog; it gathers short stories about product management, software engineering, and work organization. 📝