---
title: "Discussion on \"Why be a software developer?\" | Hashnode"
description: "Discussion on \"Why be a software developer?\". I've been a professional software developer for around a decade now, and I've worked with roughly a dozen code bases, ranging from the tens of thousands to the millions lines of code. And, while line count is no perfect measurement of scale, it does ..."
url: "https://hashnode.com/posts/why-be-a-software-developer/5cfd3ae2aaa03f835851f0d8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why be a software developer?](https://josephscottstevens.hashnode.dev/why-be-a-software-developer?utm_source=hashnode&utm_medium=feed)

I've been a professional software developer for around a decade now, and I've worked with roughly a dozen code bases, ranging from the tens of thousands to the millions lines of code. And, while line count is no perfect measurement of scale, it does ...

Jun 9, 2019 · josephscottstevens.hashnode.dev  
Read the article

-   [#general-advice](https://hashnode.com/tag/general-advice)
-   [#career](https://hashnode.com/tag/career)
-   [#software-development](https://hashnode.com/tag/software-development)
-   [#productivity](https://hashnode.com/tag/productivity)
-   [#functional-programming](https://hashnode.com/tag/functional-programming)

## Written by

[Joseph S Stevens](https://hashnode.com/@josephscottstevens)

@josephscottstevens · Augusta, GA

  
[View profile](https://hashnode.com/@josephscottstevens)

10 years of Software Development, Husband, Father and Functional Programming enthusiast.

## Responses 2

Markdown supported · ⌘↵ to post

[Tapas Adhikary](https://hashnode.com/@atapas)

[Jun 10, 2019](https://hashnode.com/posts/why-be-a-software-developer/5cfd3ae2aaa03f835851f0d8/comment/5cfdfe9a88be836810cc83a4)

[Joseph S Stevens](https://hashnode.com/@josephscottstevens),

Interesting Observations. I second the feeling of,

> magical fairy project that is gonna be the greatest thing ever

It happens..

Glad that, you called out about "Improving things to make it better". This is really not a overnight thing.. also I have seen, you can not do it without annoying people around you. So great job!

Yeah, I would be surely interested to know more on the "problem solving" in those areas. In fact, something pissed off recently was "usage of linters" in one of the projects and I am sure, you understand that feeling 😡😡😡.

Having said all the above, Being a Software Developer is a Superb Feeling! Once a Developer, Always a Developer(at heart, at least) 😄😄!

[Joseph S Stevens](https://hashnode.com/@josephscottstevens)

[Jun 11, 2019](https://hashnode.com/posts/why-be-a-software-developer/5cfd3ae2aaa03f835851f0d8/comment/5cfdfe9a88be836810cc83a4#reply-5cff07985d419b34753d1fb2)

I've tried a few approaches, and the "you're wrong, do better, direct feedback" works okay. But it's really slow, and starts arguments.

I've also tried doing nothing, which is the worst option.

The best one I've found is say nothing, do the work. Make a pull request, if they ask why the request is "big" or "too much". You've got to give exact reasons. For example, a recent PR had that criticism, my response was.

Well, I think we can all agree code quality is important. Then I listed exact reasons until the guy gave up 😆. Dunno man, it's tough.

[Mark](https://hashnode.com/@mverleg)

[Jun 9, 2019](https://hashnode.com/posts/why-be-a-software-developer/5cfd3ae2aaa03f835851f0d8/comment/5cfd5321d1637b9c0c507db6)

On the one hand I agree with the negativity somewhat. One has to get used to writing worse code than one would like.

Or be genuinely unable to distinguish good from bad code (but nobody thinks they're that guy/gal).

To help with accepting ugly code, it's good to keep in mind that no two people agree what's perfect, and in particular nobody thinks anybody else's code is perfect. Sometimes it later turns out others were right after all (usually not, but keep that option open).

On the other hand, one has to fight back a bit to make the code better than would be convenient. Take a bit more time than ugly code would take. Request budget for the most important re-factoring. Add an auto-formatter to the build chain.

In the long term it helps the company to have maintainable code. If management can't see that, then perhaps it's on us. We're the experts, after all.
