PhD candidate, a foreigner, after few years of unofficially using Python/C/C++ for studies and research but majoring in computer networks, Radar imaging, then deep learning now, decided that software developing/engineering is what I am going to pursue.

Went for freelancing, I didn't get anything. I applied to remote entry positions, failed during interview (after successfully passed the technical challenge part in all of them) in 4 occasions, to finally get a part-time (well not exactly), 3-4 days a week 9-10h a day.

Actual situation

Since I joined them (6 months ago) I am:

  1. Working as main CV (DL) developer 20% of the time which I liked,

  2. The other 80% is all putting inconsistent code (APIs) together with writing little to no programs which is my issue;

Now this second part is actually sucking my soul, calling inconsistent C++ tracking library together with its demo Java/Kotlin as a component to a react-native interface with a 0 experience with Android/react-native is actually killing my hopes in doing great right here. I hoped that I will join what other normal people in the same place are doing here but I was assigned impossible shit to build for a complete new product as a part-time.


is actually not writing programs most of the time even considered a software developer/engineer experience?

closed as primarily opinion-based by gnat, Jim G., The Wandering Dev Manager, IDrinkandIKnowThings, thursdaysgeek Dec 27 '18 at 22:38

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 4
    This sure sounds like programming to me. In fact, most of the time programming (as a profession) is not about writing shiny new systems, but writing middle-level glue code to hold old rusty contraptions together. Programming is very much about dealing with other peoples messes, and you seem to be doing just that. Another aspect is that they might need someone to learn this new and odd stuff not quite in the main field of operation, and it's easier to have the "new guy" do that than taking someone off the main team. – Joe Terror Dec 25 '18 at 9:59
  • grateful for you sharing your knowledge. However, It seemed to me for a while that I am loosing the sens of problem solving rather than actually strengthening it. Which made me ask the question at the first place. – idriss Dec 25 '18 at 10:45
  • These days most code is written by others and used as libraries. This mean tinkering with API's which can be even harder than just writing it yourself (but then you lose the benefit of the work of others). In the end you need to ship, and getting there is all part of the trade. – Thorbjørn Ravn Andersen Dec 25 '18 at 11:57

Documenting the system is absolutely within the realm of a software engineer.

You’ll also be asked as a software engineer to integrate and test at multiple levels. This would be considered a component level integration seeing as you are at the API level.

Understood you are not an expert on React and what not. Not many people are at the moment. Consider that this is an opportunity to learn the code base more.

Maybe what else you can do is ask for more interesting work to help the team and work on this part time in case you get stuck or at a coders block.

It’s all going to be valuable experience in the end.

  • React is becoming the primary framework used, with not much else in the future for now (Vue is great, but hardly as popular. Angular shows up here and there, but feels to be losing popularity). Therefore getting React experience is quite valuable even if you don't intend to do frontend work in the future. It is helpful to know how it is used when you do eg. APIs to be used by the frontend. – Juha Untinen Dec 25 '18 at 9:38

You ask yourself if a task is part of the work of a software developer. You can decide this very easily: If it's not part of your job, then some non-developer must do it. Who would use these APIs if you don’t? Nobody, it is a developer’s job.

Not the answer you're looking for? Browse other questions tagged or ask your own question.