A senior engineer with about 8 experience in my team and company for almost a year now. Believe it or not, still hasn't setup local dev environment.

Every time we ask this person to set it up / refer to guide in Confluence / or just use the docker image the person says ok.

Starts sending code for pull request. The code would not even compile in most cases just from a quick scan. When questioned how was this tested, answer would be more or less 'oh my local setup not working, could you test it out for me.'

Doesn't know how to write tests. Fairly recently instead of storing string values in a list, (I swear am not kidding) decided to come up with 20 string variables.

8 years plus experience! I think this is retarded even for a fresh grad.

holy fuck...

I have setup my dev environment like 5 or 6 times this year for various reasons, on diff platforms, and at home (for learning job stuff).

I cannot imagine not being able to do that.

We had a similar case beginning of year.

They didn't let him write the coding test, because he had so much experience and probably was so convincing. Allegedly had written some flight simulators. Deep in C. But didn't know a double pointer.

Worked quite some time for automotive, maybe their coding guidelines forbid this stuff altogether. Still strange. - Also strange guy. Actually I liked him, but I think he had some issues. Depression or so. Was talking the whole time. About is grand plans and his girls.. Only lasted a month.

Talking as a senior here - who strangly enough had a similar story...
Background:
1. Setting up a local dev is not easy. Requires deep knowledge on how the build works.
2. Build is a convoluted Makefile mess with multiple steps that requires 3 diffrent code generators, before the actual build starts.
3. code generators requires very specific plugins, with very specific version, not documented anywhere.
4. The team lead keeps me on other tasks, and away fron the code.

After 1 month of not working on the project, my env got out of date, and could not build anymore. took me 3 month to get away from the stupid non backend task and get back to the dev....

Took me a couple of days to setup a working dev env - mostly becuase I had to figure out what generator plugins version are required....

Hey...
I am only 5 years in since learning to code and 2 years in to uni

Could you explain me and give a link on what do you mean by dev env. here? I know docker btw

@gitlog Dev environment means the actual tool stack you need to code and test software locally on your device (IDE, development kits, unit test tools or libraries, and so on), or integrated with an external test environment where you have an automatic build pipeline. In the latter, it will be possible to trigger builds as soon äs you have pushed to a repository. And the deployment might actually also be published automatically when all tests are green.

@magicMirror

If setting up a dev env is that hard I suspect either the build-pipeline is shit or the documentation is shit, likely both.

Our main project, one of several, runs Java (multiprohect setup), uses JNI to access C++ libraries we wrote and some of these use Python.

This whole thing is managed via Gradle and the C++ libraries are built using our own CMake scripts.

I mean, our documentation ain't perfect, just today we talked about some stuff. But we have a Wiki and documentation, where all software, plugins and steps are described in detail.

Just recently I wrote a script to do all the setup. Install a list of software described in the wiki (with versions), clone repo, run script - you're good to go.

Some people may be bad at setting up environments, but oftentimes codebases and docus are simply maintained incredibly poorly.

@Maer
No docs.
Build pipeline is a horrible mess. I'm changing it for the better, and documenting - but it is hard to change, as all of the team depends on that pipeline to build/test/deploy.

> A senior engineer with about 8 experience
ITS OVER NINE THOUSAND
i mean eight what? warnings per line of code?

@bvs23bkv33 8 years.