To do what tuco described, yes.It's been awhile but wouldn't that need to be
As it stands, that code would delete the pointer to the first element of the array and leave the other two elements floating around on the heap.
To do what tuco described, yes.It's been awhile but wouldn't that need to be
Just in case other people feel like giving it a shot.Good thing about doing timed coding tests at home is you can weed out people without wasting your employees time.
Deathwing, is the answer to your question, "instantiates three elements of that class on the heap, calls their constructor, then deletes the three instances?"
I'd set up your way in a test environment, get a few tech guys on your side and go pitch someone on it and show them how it already works and saves you time and has advantages a, b, and c. And show them your transition plan and explain that the guys who actually commit stuff already know how to use Git and so it should be pretty seamless.Thanks for this.
Quick question. What's the best way to broach an organizational change in the way things are done? I ask because this place uses an antiquated VCS (SourceSafe) and I think they'd benefit immensely from shifting to something like Git. Being the junior guy with extremely little experience, I'm wary about suggesting such a thing without lining up my ducks, so to speak.
Look at job ads on dice, stackoverflow careers and wherever else they are posted. Look for a job you find interesting (with your math background, I bet data science stuff would catch your eye). Anyway, find a job that sounds interesting and see what skills it requires. Learn those skills.Looking for advice. ~5 years out of school with a BSEE. Finishing up my MS in communication/DSP while working full time and will be done this December. I currently work for a defense contractor and it is quite boring/lowish pay (~80s in LA while my 2 friends that do SW are making 95k&115k in LA/SF). After doing EE/Systems Engineering for the past 5 years, I've discovered it really isn't for me and although the grass is always greener, CS seems to have higher pay, better job security/options, and I think I would enjoy it. I have a decent CS background from AP CS in high school and I'm quite proficient at MATLAB but besides that I don't have too much software experience. Once I finish my degree this winter I'd really like to transition into SW but I'm not sure how realistic that is.
Anyone else transition from engineering to SW? I assume Python would be the closest language to MATLAB but are there other languages that I should look into? Anyone learn SW development on their own and have tips? I have the basics down but when I start to look at some more advanced code I quickly get over my head.
Dont go to Github, Try first Team Foundation, you can become the team foundation overlord.Thanks for this.
Quick question. What's the best way to broach an organizational change in the way things are done? I ask because this place uses an antiquated VCS (SourceSafe) and I think they'd benefit immensely from shifting to something like Git. Being the junior guy with extremely little experience, I'm wary about suggesting such a thing without lining up my ducks, so to speak.
Memory Leak will be my guess, u are deleting the pointer to the class array and u are leaving it hanging around on the memory.My favorite from my last round was 'what would this do?'
Out of curiosity, what kind of tests do they throw at you?Most of the coding during my last set of interviews was done on my computer at home. It was timed but I could use whatever resources I wanted to solve the problem.
Not github, just git. I don't think I could sell using github enterprise since sourcesafe is being used "without cost".Dont go to Github, Try first Team Foundation, you can become the team foundation overlord.
Keep in mind I was interviewing for a test engineering position.Out of curiosity, what kind of tests do they throw at you?
Many large companies are starting to do away with the Traditional Test Engineer position and instead are requiring that developers properly Unit / Integrate test their code.Keep in mind I was interviewing for a test engineering position.
I was given 4 small executables and was told how they *should* act. They wanted me to write a script that would automatically assess whether they adhered to the expected behavior. Bonus points for thorough and creative stressing of the inputs.
I didn't know what to expect, so I spent more time than I should have refamiliarizing myself with perl(ugh). Knowing what I know now about Python, this test is dead easy. Still was able to tell them which ones did and did not work within the time limit, just wasn't able to automate it.
I think the point of the test was to see how you approached testing because it got me to the next stage of interviews and eventually the job. Though, I do sometimes wonder if they "settled" for me. The position was open for at least 6 months and it's not exactly like people are clamoring to be test engineers.
I was a Release Manager at my last place of employment and over the course of about a year we lost about half our QE people, including the Director, through attrition. More and more stuff for QE started to fall into the laps of the teams programming it all and all of a sudden we started having less and less problems pop up during deployment that needed on-the-fly builds and releases (second push) until that went away completely, all on its own. We had tried to remove the second push previously as a conscious effort but got a lot of flack for it. Instead it happened organically and we only overtly called attention to it after it became the new normal. This in turn resulted in a few additional benefits across the board which made (mostly) everyone happy.Many large companies are starting to do away with the Traditional Test Engineer position and instead are requiring that developers properly Unit / Integrate test their code.
My Business Unit has recently moved towards a new model which drops the entire "Test" word in general. We instead focus on understanding how customers will use our product so we can catch Cross-product/System level issues.
Our change came about due to the absolute sewage our dev team was producing. We had to push the testing off to them and make them responsible for the product up to a certain point as a cultural change.
I personally would have just fired them all and hired a new team but that's not possible :<