On top of what @izzion has stated - hey, an opinion from someone who actually knows the business! - the US and state tax rules around depreciation of business assets are fucking brutal to any sort of business that needs a significant capital base of electronics. (Yes, motherfucker, businesses pay taxes, and they can be pretty fucking substantial, despite what all the communists think.) Even on the most accelerated depreciation schedule, businesses in the US still have to depreciate assets over at least five years IIRC. Of course, electronics are always getting faster, cheaper, better in every way, on a much shorter time frame than that, which means that all the hardware you buy today is utterly obsolete by the time you can finally stop paying taxes on it. In other words, if you make the wrong tech choice, you'll be lucky to pay for it twice - once to buy the wrong shit (and pay taxes on its depreciation), then a couple years later to buy the right shit (and pay taxes on its depreciation).
The unlucky ones go bankrupt. That's a pretty serious risk - one for which any business with reasonably sane management compensates by doing what it can to get a better profit margin. No, asshole, they aren't wanting to play Scrooge McDuck; they just want to have enough in the bank to survive a fuck-up like that.
@anotherusername Thanks. I had forgotten about that.
So perhaps it's just a problem with me for a change that's counter to my expectations?
With that option enabled, it used to be that posting would only jump to that post in only the same tab that I posted in, but now posting will cause all tabs open to that thread to jump to my new post. And the latter was the originally intended functionality...?
@anotherusername It's Discoursistent on that too in infini-mode. I just tried ?page=174 with a post url (topic/22798/blahblah/2?page=174) and it showed all the posts like normal, unlike what I had seen with just the topic url (topic/22798/blahblah?page=174)
Coding paradigms change. My code meshes well with my other code, so it all calcifies into one hodge-podge framework that is hard to tear apart. OSS code is by design modular and interchangeable.
Will my colleagues be able to maintain my code without me? Will they understand my vision for the code's organization and general usage pattern? Or will the next guy just bolt on their crap on top of mine? A 3rd party lib will generally have well established patterns, so there will not be problems like that.
Finally, will other coders even want to work on my artisinally made in-house framework? I mean, even if my thing is superior, once the time comes to update their CV, I bet they'd rather have "2 years of express+mongo+slim+whatevers-hip" there, than "2 years of cartman's internal framework no one's ever heard of before".
Pretty much sums up my feelings on it.
If it is a decent open source library that is actively maintained. used, popular and has unit-tests then use it.
At the moment me and another dev are making a .NET web app. I need to do some Image processing, I could use System.Drawing and write a load of code for cropping, rotation and a few other things we have to do with incoming images.
@Arantor Yeah, mine were mostly patent/general IP lawyers.
They're the worst in my experience. Not even mikeTheLiar worst of the worst but John Oliver's 'you are the WORST, the WORST!'
My two best (read: worst) stories:
I get home from work at about 8:00 one evening, and within half an hour I get a phone call from a coworker. Apparently, the lawyers never checked to make sure that someone had written the expert report that was due the next day. So I get to spend the next four hours working at home, then we have half the office spend all of the next day helping to throw something together.
After spending several days trying to explain database tables to a lawyer, he finally has the much-needed epiphany: rows and columns intersect each other.
I believe the original talk was translated from Japanese so it is possible some stuff got mixed up in translation. This quote is from the article of the guy who translated it (I think):
Their development tools didn’t even have keyboard support, meaning values had to be input using a trackball and an on-screen keyboard. By modern standards, it’s unthinkable, and nobody would ever do it, but at the time, Sakurai was a 20-year-old rookie, so he just thought that was the way it was done. There were some benefits to this type of workflow, however: it made the data processing load easier, and so they were able to create a game that had a very smooth movement for a Game Boy game.
...which...yeah I don't know. Maybe he meant having to use the specific developer tool [the Famicom system with Game Maker] let them optimize the game more.
A doctor at a fertility clinic in the Mississippi capital of Jackson has made a startling revelation concerning a couple who sought treatment at the center. The married pair, who cannot be named to due to patient confidentiality restrictions, had been struggling to conceive and came to the clinic...
At the bottom of the article:
(pasted image because the wankers disabled text selection - and I'm too lazy to try tweaking that)
@tsaukpaetra stares aghast at @izzion , "hey! Don't go blaming yourself only for the performance of the team! Surely we all know we still have work to do, our effectiveness as teammates won't fix itself so quickly, and you can't expect miracles to happen just because you were named leader!" he (softly) exclaims, "stop quibbling around and help make plans for us to improve. You don't become a good leader by whining, and we need you to focus and help get us back on track. If you let these self-doubts cloud your mind, it won't matter if you're not the leader, you'll be so distracted that my bumbling about yesterday will look like... Like... Oh whatever. Look, we all need to get better, but team morale is the first place to start. Ok?"
Last time around was 2011 using Dice. I prefer to look for listings that have a name and phone number so that I can pester them about my resumé/application. I don't think my present employer furnished that information, but somehow things worked out anyway.