The staff keep having to rescue packages Amazon drivers have left outside of random building entrances and even neighboring buildings instead of delivering everything to the mail room like the real carrier services have no problem accomplishing.
706 karma · joined July 4, 2014
The staff keep having to rescue packages Amazon drivers have left outside of random building entrances and even neighboring buildings instead of delivering everything to the mail room like the real carrier services have no problem accomplishing.
CSS of any flavor should be modular and semantic, it's just that SASS gives you a big leg up once you're comfortable with those concepts. It's still on you not to shoot your leg off with criss-crossing @extends and deeply nested selectors and and snowflake components.
If you're working on something important, say critical national economic infrastructure, you do the equivalent with automated staging and testing happening before any potentially breaking changes are made to live servers.
Or... you do nothing, as the case may be...
I get it, development is a craft, it's easy to judge the quality or experience level of a coworker after having to deal with their PRs for a month or two. However, it's not like any toy project I could throw on github is going to have real relation to the actual work I do, and trying to replicate e.g. some of the third party integrations I've written internally as public stand-alone packages is going to get me fired and sued by an overprotective employer.
This isn't a hypothetical fear either, multiple times I've gone through phone interviews to a "lets review some of your past work" stage, and my "I can't legally show you any of these things, but here's general descriptions of some of the major internal projects I've led or handled solo" has resulted in failing to make the next interview round.
You can never trust anything a phone/chat rep tells you because they're aggressively pushed by management to integrate sales into support.
Then a staging version of the real environment for final testing.
Progressive enhancement applies to more than just JS, and we've already been provided with a standard way to not have to care about browser support.
It's not quite as automated as publishing a NPM or Composer package, but it's close and works well.
For example, the company I currently work for has 15 years of unaddressed technical debt, and it has enormous impact on everything we're doing today. Fixing it is absolutely necessary, and where it's been possible to do so it's already made a significant impact.
However, in a few years things will likely still be awful and even the shiny new improvements will have been dirtied up, because the cultural and managerial decisions that led to the current state are still in full effect. You're correct in that technical debt is ironically usually as much a people problem as a technical one and solely-technical solutions are usually inadequate.
That doesn't mean that I'm going to stop fixing things where I can and pushing for change though, because at the very least it means my life there will be a little saner (until I finally burn out on fighting the tide and find somewhere different to go).
Big companies use enterprise Java unless they're stuck with a legacy VB/ASP/Coldfusion stack, with C# less commonly.
Fintech companies use a mix of C# and C++.
Small companies started before ~2010 use PHP, with Rails less commonly.
Small companies started after ~2010 use Rails, with hipster Java (Scala/Groovy/et al) less commonly.
I can only remember offhand seeing one job ad for a company using Sinatra instead of Rails for their Ruby stack.
On the other hand, I do not know basic things CS BS-havers learned, like how to implement a bubble sort from scratch, because that is not something that has ever been relevant or is likely to ever be relevant to my day to day work (outside of one-off interview questions from companies I likely don't want to work for anyway if that's their interview process). Algorithm design and high level math is the foundation of CS as a science and as a degree, but it just doesn't factor that much into writing code in a high level language for an established platform like the web.
And having a CS degree is no guarantee that you won't put an expensive call inside a loop or write monolithic functions or any of the other terrible practices I've had to train out of junior devs.
That doesn't mean I'm not glad they all sit clear on the other side of the office in a quarantined section where they can extrovert at each other all day and leave the rest of us to code in peace.
Contract-to-hire at least gives you a couple months of fairly sure income.
Assuming that Go is a general-purpose high-level language, yes, but is it? It was created to replace C++ in critical infrastructure, not Python/Ruby as the end-all be-all of default platforms for every situation. Its syntax simplicity and speed absolutely makes it attractive to a wider audience, sure, but if it does the job it was designed to do very well, should we be angry that it doesn't do all jobs well?
Developer time and execution time are both important metrics when considering a language, and Go is very well situated when the major developer time gains offset the minor execution time losses vs C/C++. That it's less well situated when the developer time losses vs Python/Ruby are incurred on a project when the execution time gains are irrelevant isn't a failing of the language, it's a trade-off.
It's hard to imagine you haven't already thought of these questions and answered them somewhere, but this non-article certainly doesn't address it or point to better resources (besides "buy my book!").
Weirdly a couple months ago my local 7-11 upgraded to readers which have the physical EMV slot but those slots are non-functional.
The people who used to deliver content solely on SA for the audience there now have global reach through other platforms. FYAD and FYAD-lite alumni are behind most of weird twitter, they run large communities on Facebook and Tumblr, and some of them even write for the Guardian and Jacobin among others. Youtube replaced SA-based LPs just as surely as it replaced YTMND.
Meanwhile, the administration policies have been as consistently outdated as the forum software, driving dedicated communities to offsite forums and casual information-seekers to the greater resources of Reddit.
None of which exactly inspire confidence when it comes to something like operating aircraft.
They don't seem to be confining themselves to processing and loans for increasing revenue, but are trying to become a basic ERP/marketing provider as well. Sage/Moneris already does the same thing so it makes sense.
In inflation adjusted terms, worker productivity has increased almost 75% between 1973 and 2013, while compensation for production workers has increased less than 10%. Wages at the top 1% have grown 138% since 1979 compared to 15% for the bottom 90%, and it gets direr if you start looking at the bottom 50% (stagnant) or bottom 10% (5% decrease) instead.
Our economy is producing more and more, we are far from hitting any kind of limits on productivity, but it's only enriching a select few while the vast majority deal with flat income and ever-rising cost of living.
1) is a sentiment I've seen frequently expressed, but is not really panned out by the number or type of job postings in secondary hubs outside the Bay (e.g. Chicago). 2) makes more sense, but the article doesn't really address how to solve the root issue when hiring managers aren't willing to hire from the previous two buckets.