Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Believe me, I would want nothing more than to add asserts, guards, and logging, probably rewrite the data layer as well (I'm writing a configuration validator to diagnose typical configuration issues). Unfortunately it's not up to me. I can make a request to have something pushed into source safe, but the typical response is 'your intentions are good, but this is not something we should be focusing on'. Alas, I am but a junior with 1/2 years experience. I'll be climbing this mountain for a while.

Igneous01
– Igneous01

2016-01-14 04:26:43 +00:00
Commented Jan 14, 2016 at 4:26
9

@Igneous01 Honestly, try to find a different mountain to climb. Work conditions at other places may not be perfect, but I guess at least most are significantly better than what you are experiencing. If your gatekeepers reject your improvements with "this is not something we should be focusing on", it's their decision to make, and they will reap the results of that failed policy (they are already loosing tons of money in terms of lost development time). The question is, do you want to stick with them until they do?

cmaster - reinstate monica
– cmaster - reinstate monica

2016-01-14 06:54:27 +00:00
Commented Jan 14, 2016 at 6:54
6

And keep in mind that when bad policies fail, everyone involved looks bad, even those who disagreed.

user53141
– user53141

2016-01-14 06:59:21 +00:00
Commented Jan 14, 2016 at 6:59
1

Yup, start logging & tracing. Also start documenting, and adding comments. Bit by bit, it will all add up. Also, you say that you are lucky enough to still have some of the original coders in the company, if not the team. Push management to get accecss to them If possible, persuade them that they would rather produce some docs than be constantly approached with questions.

Mawg
– Mawg

2016-01-14 13:10:20 +00:00
Commented Jan 14, 2016 at 13:10
4

@Igneous01: Run, don't walk. This place is sick and will make you sick.

Martin Schröder
– Martin Schröder

2016-01-15 23:09:51 +00:00
Commented Jan 15, 2016 at 23:09

| Show 1 more comment

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »