[astonecipher]

Started formulating your actual resignation and your piss off resignation?

[jon.kiparsky]

By the way, it's the peak of the Perseids tonight, and there's hardly any moon at all - if you can, go out and look up, the viewing should be good.

[depricated]

after moving last night I sat out and watched some from the porch while drinking. I'm so damned exhausted though.

And today we're having fiber installed in the house.

[astonecipher]

Congrats on the new place, but make sure that fiber is going in. You don't want the new place getting constipated.

My module is coming along... Other than the first place it is getting use is using an OLD version of jQuery and breaking. Found a nice migration class though.

[BenignDesign]

Taking a sick day tomorrow, as I have over 200 sick hours that I won't be paid for when I leave... might as well use a couple of them. Hipster and I will be house hunting this weekend... I'd like to get into a place BEFORE school starts so the kids can start the year just as lost as everyone else. Having trouble writing a resignation letter that doesn't contain f-bombs. So nervous and excited I can barely eat and all I do is pee. Not sure how many bladders I have, but I'm pretty sure it's more than one.

Spoiler

[alapee]

Menu Today:

Projects



Tonight: more moving prep

[no2pencil]

BenignDesign, on 13 August 2015 - 09:11 AM, said:

Having trouble writing a resignation letter that doesn't contain f-bombs.

Having written my fair share, I can only say that I just keep it simple. As of this date, I will no longer be with the company. Thank you for your time.

Tonight I'm finally going to make my Aluminum Casting Foundry

[depricated]

Super excited for you B9, that's wonderful!

[NeoTifa]

Congrats B9.

Other coworker got the job we both interviewed for yesterday, which is great because that still leaves room to have interviews for jobs I want.

[rgfirefly24]

@B9 Congrats on getting the new job. I'm glad things are working out for you, and Derpicorn will be a long forgotten spec.


Today I'm pushing more things out to production in anticipation of a very big release coming in the next few weeks. Phase 2 is finally coming to a close with a "get it done or there will be consequences" date coming up next month. Gotta love those when delays have been all because of TPVs and unknowns that come up because you are blazing a completely new trail. It's all good though because I'm pretty much done at this point. Now it's down to waiting for another team to finish up a supplement app and then wiring it into my stuff.

Also started the house buying process. It's still a year away, but we are getting all of the stuff out of the way that we can now. We have to take a first time home buyer class as well as a financial planning class in order to qualify for a specific type of mortgage. If we get these classes out of the way we can qualify for a 5% down no PMI loan which is exactly what I'm wanting.

[ChrispyChris]

Updating some more computers, trying to figure out why this file won't unzip on this PC, drinking coffee, and working on more C++. Going to get my pull ups, curls, rows, and shrugs in during lunch because I had to work on the front yard at the new place I'm moving into last night. That took hours so I missed my exercise .

[astonecipher]

For all the students thinking they should learn the latest and greatest...

There is A LOT of legacy code out there that your new code will not work on and I really don't want to troubleshoot it!


>>> end rant

[ybadragon]

Question: When working with a team, and you are testing something you implemented and an error occurs in another part of the program that you didn't implement but it stops you from continuing with your debugging session, is it your job to fix that error or is it your job to tell the person who implemented the feature that there was an error in scenario x and it needs to be fixed by them before you can continue?

Edit - If we have a forum for this type of question, what is it? I'll post it there.

This post has been edited by ybadragon: 13 August 2015 - 10:15 AM

[ArtificialSoldier]

I think that depends how your company is structured. We don't have many programmers here, so if I find a bug I usually fix it. I'll typically only pass it off to someone else if they made a stupid mistake, like they didn't consider another part of the application or something when making their change, and I want them to figure that out and fix it.

[NeoTifa]

I would talk to your tech lead, or at least keep them in the loop.