Pretty impressive. Shows what posting on places like this will do for you!

Aarrgghh

Nope. Whole lot of nope.

Any update?

Any facility like that that I know always had financial stuff handled externally.

Nice.

Always nice to get chosen for an interview. Congrats.

@ajstringham They are both nearly dead.

@JaredBusch said:

Just came home from Texas Roadhouse. Was a simple dinner with the kids for our 7th anniversary.

Planning to have my mom watch the girls for our 2nd 7th anniversary on August 10th.

Second seventh anniversary?

Cool, not many people manage to get a Linux desktop at the office.

Yes, email alerts would be greatly appreciated.

Good resource. Can't beat free certs.

Yes, none of it sounds good. Let's highlight:

• He doesn't know how to do his job.
• He doesn't know how documentation should work.
• He takes credit for other people to cover up not being able to do his job.
• He has been in this one job more than long enough to know this stuff - all stuff that he should have known when he was first hired, so after nine years he is not yet up to the level he should have been to be hired!!!

In reality, it is HIS managers that are probably causing the problem.

Azure has its own object storage mechanism (similar to Swift in OpenStack or S3 in Amazon AWS) so to allow you to learn or test behavior they have an emulator so that you can mimic that storage locally.

Had not seen this before. Interesting that you can run a local emulator.

http://msdn.microsoft.com/en-us/library/azure/hh403989.aspx

@Minion-Queen Or be easy to look up.

One of the reasons that How Tos that are public are important is that they get well tested by people using them over and over again. Any gotchas are normally found by other people. Internal documentation of standard processes is just asking for errors or missing pieces.

@thecreativeone91 said:

IS this a huge red flag or is it just normal?

Red flag.

That is unusual. Good documentation, in my opinion, includes everything that is special or unique to your environment. Maybe, at a stretch, it would include links to external resources for general tasks. But the general consensus is that normal or "general case" tasks, those that are just standard IT knowledge, should never be documented in house because then you are documenting things that you do not control and that have no value. In fact you have negative value because you have to spend a lot of time keeping up to date information that you may not be aware is changing. For example, install a new switch and you have to write every document again with new screen shots and instructions that just duplicate what is available from your switch vendor anyway and that they are paying to maintain no matter what.

@JaredBusch good idea. That will get them into bad security habits.

Neither Target nor Experian are companies entrusted with data. One is just a retailer and the other is a company that collects, often false, credit data against the will of the people. Experian's customers aren't the people and so it feels no responsibility beyond what is legally enforced which is nearly nothing.