And that’s why you’re not safe for work.
And that’s why you’re not safe for work.
C and C derivatives will be fine unless they’re fucking up encoding.
If you try to give notice they’ll kidnap you and you’ll spend the next three decades of your life singlehandedly keeping the server running from a secure location somewhere in the Poconos.
Alternatively, your laptop will spontaneously combust firing you from life.
I seriously don’t understand how that fucking company is still in business.
Looks depressingly at the shiny new ThinkPad my work got me to replace my old ThinkPad… I’d get so much fucking severance if these fucks ever laid me off - is it really never going to happen?
It’s hilarious that you think that proprietary software is actually better.
If you enjoy the work you’ll do well. There are a lot of different roles and specialties in CS with some of them being highly math focused and others quite divorced.
Guaranteed to sort the list in nearly instantaneous time and with absolutely no downsides that are capable of objecting.
It’s no worries - most people don’t realize this but every git repository is, well, a fully functional git repository. Git shell runs over ssh so as long as your machines have sshd running you should be good.
https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server
Git doesn’t need to have a single pull source. It’s probably worth just configuring the visibility on each machine so you can do peer pulls.
I don’t hate the idea of autocommitting in that scenario, though.
Yea, I don’t want to totally shit on SPAs but server-side rendering has a lot of advantages and is so much fucking simpler.
I’m a PHP dev and DB specialist in my day job - there are a lot of good server-side tech options.
By SPA I mean “single page application” it’s currently the dominant approach and powered in a large part by technologies like react and node. I’m not certain when it started precisely… with technology it’s more a case of “rising to prominence” rather than “first happened” I think it probably really started going around 2014 with HTML5?
SPAs are still pretty hot but they’ve waned in popularity due to overuse and general complexity. Essentially your website becomes a single page that just swaps out what’s shown to the user as they “navigate” between different parts of the site. When well done this can make a site incredibly responsive, but it’s often quite poorly done and responsiveness can end up blocked by server requests anyways.
<Pig Latin instructions unclear, entire site rewritten in XHTML />
Hey let’s not lie to ourselves… most of those megabytes of JS are there to disable the copy functionality for anyone browsing our site.
Why? … reasons. Someone in marketing said a thing once.
Nah, a lot of old tech. I used to work on shit like this… loading all your images (including the fucking rounded corners for IE) into a sprite… setting up caching, using prefetching and inlined CSS/JS for critical path stuff.
There was a whole industry around web performance in the days that a customer might be trying to download your site over their 256 kbps connection.
It’s neat tech and I miss fiddling with it. I honestly found it a lot more fulfilling than the SPA era of web design.
Honestly? Pretty fucking awesome if you get it configured correctly. I don’t think it’s super useful for production (I prefer chef/vagrant) but for dev boxes it’s incredible at producing consistent environments even on different OSes and architectures.
Anything that makes it less painful for a dev to destroy and rebuild an environment that’s corrupt or even just a bit spooky pays for itself almost immediately.
Based and vagrant pilled.
Ah, that’s when we fork and pin our version refusing to ever update the dependency ever again.
Please tell me where you are so I can move there immediately.
The joke (and probably the source of the realtors name) is from community:
Ahem, map…
And, of course, everything is a lazy list even if the functions can’t handle more than one element in each list.