Cons: slow, consumes lot of memory plus all of the above
Pros: not as buggy as Skype for Business
315 karma · joined January 25, 2021
Cons: slow, consumes lot of memory plus all of the above
Pros: not as buggy as Skype for Business
Latvia and Lithuania
South Africa and Africa
You get the gist :)
In my current company (one of top us financial institutions) widely spread habit is to use jira title as commit message, be it small jira for a bugfix or something big for twenty commits and two months of work. Just because.
>> If your lead engineer says that you need to spend $2,000 on SSDs
Our physical more or less ok workstations (no ssd though) got replaced by thin clients connecting to virtual machines. Slow in terms of raw performance and video/mouse/keyboard i/o. At the same time big suits like to blah-blah about how important technology is, how "we are not bank we are tech company with bank department" is and how much they invest in tech.
edits: grammar
I've never said that.
I think this conversation is going nowhere, no reason to continue it.
By the way, Linux did well on Android because it is made there with "grandma" in mind.
But seriously, as inflexible, painful and tedious to support our on-prem infra last time we had critical outage was ~3 years ago, for like an hour. We've almost finished migration to azure. I hope this outage and AD outage earlier this month are outliers.
Such big* consulting/outsourcing companies in Eastern Europe(epam, globallogic and the like) have competent engineers.
I can see it especially clearly after moving to the US and having to interview engineers from other big consultancies.
*big - everything with several k employees is considered big in Eastern Europe.
Feels like major news corporations need to balance between maintaining credibility (at least ones that care about it) and publishing something that might (for lack of better term) trigger reaction like "wtf my favorite Blah-news is becoming more and more leftist-marxist/racist-fascist. Fk them, I switching to unicorn-patriot-news-or-something".
Marked-driven confirmation bias. I wish I had a good idea how to fix it but I don't.
In my experience programmers with exposure to multiple PLs/paradigms/platforms tend to perform better than programmers who worked only with one, unless they go very deep and know that single PL/platform really well, like inside out (this is more often the case with C/C++ programmers).
Only few people can afford Lamborghini. Trying out Clojure - books are cheap, tutorials are free, it's just a matter of actually doing it.
edit: replaced "=>" with "becomes"
I'm glad someone said it and I'm glad that that someone is a woman so that there's a chance this message won't immediately get drowned in sexism/male privilege accusations.
I work at one of those US bank.
The amount of inefficiencies in form of red tape, confusing processes, custom half-baked tools that crash half the time is just mind-boggling. I've spent more than a week now for opening firewall on one ip/port on one host just to test my prototype in dev environment(local machine or docker are not an option due to lack of admin rights ), and it's still in change approval stage. If we weren't this giant too-big-to-fail bank we'd be out of business by now.
Next morning after more than ~1 hour of turning my apartment upside down I, out of desperation and thanks to intuition, dove into container and recovered my trash bag. Everything apart from cash survived.
>> most of those "primadona devs", as you call them, would much prefer to write well-designed programs cleanly coded
Most of them - yes. But there's a non-negligible chunk of them who are too careless or incompetent to care about quality - they've been around long enough to gain knowledge about project and get Vice-President title(inflated ego included).
It is especially visible in big banks (I suppose it's typical for other big non-tech corps as well) where tech culture is generally on poor side.
edit: grammar