Showing posts with label application performance. Show all posts
Showing posts with label application performance. Show all posts

Sunday, September 6, 2015

Random readings from the wilderness


Some very interesting comments about resume file names and searchability, plus other ATs / LinkedIn info.  Very much worth a read.  This is item #4.  It also makes the point that - yes - companies are tracking how many times you've applied for jobs with them.  The reading I've been doing says three rejections in phone screens or interviews and you might as well not go back.

In the interest of clarifying which job titles might be "shaking out" for a standard of "data scientist", this blog entry has some great definitions.  Data Science Central is also a good blog to be registered with if you do the kind of work I used to do.  Believe me, you will be asked on occasion who you are reading.

One of the interesting side lines I've been pursuing is performance measurements out here in the wild.  The general IT / web programming has led to the development of performance measurements & testing results

Load Impact
API metrics
VoIP call quality issues
Dynatrace
Continuous Performance in Continuous Integration
Web application performance testing
Soasta white papers on performance engineering






Wednesday, August 5, 2015

je ne regrette rien


The cycle is swooping back up again and today I feel like I've made another "break-through" in this transition process.  I don't know why I didn't notice this before, maybe I thought it was too far beyond me, but there's this whole industry building up around performance engineering for software development in mainstream IT.  I've got an interview - not because they picked my resume out of the slush pile, but because a friend forwarded my resume to a recruiter, who forwarded me to the hiring manager.  The hiring manager asked to speak to me, so he's read my resume.  I meet with him in the next few days, so I am brushing up on what I don't know based upon the job description.

I sorted the job description into what I knew (and why I applied) and pulled out what I didn't know.  This time though, instead of ignoring the software I didn't know, I went to their websites and viola.  There was some fan-fuckin'-tastic technical documentation about IQA  (Integrated software quality assurance) tools and what that is.  I feel like I hit paydirt.

The best, however, by far is the Dynatrace site.  Not only do they describe what application performance is and how it hits bare metal, but there's an extensive section on cloud KPIs worth reading for those who still aren't impacted by having to get down to the application layer.  That said, I think application performance management and performance testing is going to be part of "everyone's" future.  This site, and others have a lot of very interesting information.

Keyword search guys is "Application Performance" - there's testing and best practices, you want to pay attention to.  Also, you want to watch for "Continuous Integration" these days, folks.

Here's the Microsoft link to their document.

*****************************************************

My favorite pickle guy asked me how the job search was going yesterday.  I sighed, "Have you done much dating before?"

He nodded.  Of course he has, he's a cutie and smart and funny.

"I've had a lot of first  dates.  You know what that's like, right?  How easy those are?"

<insert nod, but confused look here>

"Now, how many second dates come from the first?  Fewer, right?  And then how many third dates come from the second."

<smiles>

"I haven't made it to the one night stand yet."

He got it.