I don’t think it’s the parking attendants, grocery store cashier's, or cleaners job to “commit to their craft.” That’s a load of nonsense, and it’s also not in a normal contract.
Some people just have jobs, either because of ability, or choice.
If it was only to gap fill then that sounds reasonable, but other risks here is the voice agent picks up slack and lowers the pressure for staffing and working on solving these problems in the first place.
What is worse, that no one is available to listen to you when you're suicidal, or that you lack so much value that only a machine would talk to you. I'm sure some people would have an extremely poor reaction to that.
I had a similar experience when it offered to connect me to the office manager so I could remove PII from the system, where it just stated it was taking an action and went idle.
Snapchat is overwhelmingly the primary way my much younger sister uses to talk to people of her age, discord is the second.
It was quite surprising, I was also surprised people of her age are exchanging discord handles IRL like we used to with MSN/ICQ etc. and then just use it for DMs. She doesn’t even use Snapchat stories because “no one watches stories” and are just direct DMing her friends, and posts general audience stuff to TikTok.
I immediately went and bought Snapchat shares when I found that out.
I’m also I’m a similar situation, but I get the call when the thing has been on fire for a while so it’s a lot easier.
I can’t imagine a software engineer developing an interest defensive software engineering will be very visible until after there has already been a crisis to screw people’s heads on straight.
A lot of people seem to see “Do things that don’t scale” and think that’s a phrase meant for engineering.
This was my exact reaction to. I was a customer for CircleCI for years and it was my go to choice and introduced it to countless companies, they were clearly at first an engineering led company that obsessed about functional programming.
At some point after their series C they became rent-seeking, their support became increasingly distant, and the quality overall started degrading. Then I get an email that we need to pay for seats.. on top of paying for CI minutes.
It was an extra > $500 a month for no additional service, no additional usage, no nothing, and they would not budge on their new pricing plan. So I just moved all the stuff to GitHub who was barely mature enough at that point and never looked back.
Putting the finance department in charge of product decisions is a mistake with long term reproductions and CircleCI is only seeing the results of this. Treating your oldest customers like a financial liability is a mistake.
When I was early in my career freelancing my AWS account was shut down for no payment for over a year, more than half a decade later I re-opened it through support and they wouldn’t even let me pay my old bill.
I’ve been able to reduce reserved instances when the market has turned unpredictable.
AWS isn’t a pushover, not even a little bit. Dealing with them externally has just been a good experience with professional understanding and a flexible business sense.
Also currently actual AWS staff is answering on the new community support forum re:post, I’ve been taking full advantage of that.
There are some things which AWS suck at unless you have an enterprise support plan, like having a deep review of a technical issue in their products, and having visibility into product bugs in general.
Even then after reporting a significant issue like Aurora query execution being non-deterministic in a very specific case, I only found out it was solved months later after working around it from reading patch notes.
I had an incident a couple of years back where AWS couldn’t swap a cancelled CC on AWS after we had for an unknown exception, and we kept getting overdue invoice alerts. and it was during December holiday season. AWS singapore has to escalate to US since it was a billing issue.
A false negative security alert from 6 months earlier was the cause, which had blocked CC changes. It took months to resolve but it was manageable.
I know from first hand from a different experience that you can be months overdue with tens of thousands of missing payments on AWS, and tens of thousands in recurring costs without them closing your account. You can effectively run a quarter of credit line from your hosting costs without any issue if you need that.
Your account manager doesn’t even start raising it personally for the first 3 months, they are very easy to deal with.
It was so light weight that when they did user tests, the user didn’t start typing. They just waited there waiting for the rest to load. So they added the copyright notice in the footer. According to Marissa Mayer
Copyright never has to be declared, and I think in many ways Google is responsible for websites having copyright in footers not realising it’s not a legal requirement.
I would refactor your second example into an exists using Arel, because at best the IN will result in the same performance. At worst it will be significant my slower. There are also particular issues with NOT IN and NULL. This is at least true in PG.
I also deal with a lot of scale, the issues people have here doesn’t match my reality. I think people have issues and rather than looking at what is fundamentally happening with their call patterns, they jump to calling out rails itself.
Rails does have some specific issues, but you’d have to go pretty deep to see them and boot times are terrible.
I mean I see rails perform horribly too, it's my job to go in and fix things, and I focus a lot on fundamentals (what's your DB doing, what data do you need to serve the request, what shouldn't be inside of the request-response cycle).
Because a lot of web developers these days build applications and ORM's are great but make certain patterns convenient so it's really easy to code yourself into places that don't scale. Then people reach for various caching solutions rather than taking a step back and looking at what's actually executing.
I've seen just about every bad pattern you can imagine and it's not usually obvious because the code looks simple enough. Like that permission check in your controller is actually serializing 1000 ids and querying against them, or that .first doesn't have an index so you're sorting the whole table, and much worse than that.
That's not remotely true. If this is happening to you then you're almost certainly having N+1 problems which is architectural and would affect any solution you're using. Add google trace to get a breakdown of your requests SQL that's executing.
In an unusual situation it is possible in PG to have a very large pg catalog if you have thousands of tables and schemas which is resolved at run-time because Rails resolves models and types through db introspection, and the types specicially are only loaded during runtime. But that would be very unusual. I'm working on solving this in Rails because this unusual sittuation is affecting us.
In 2018 there was 9 updates to the Olsson timezone database, it's not as irregular as you'd think. It doesn't always get communicated with notice, and sometimes applies retroactively depending on which government and point in history.
Independent of all that the train still leaves at 2pm local time and I need to be on it.
Media Pop has been building websites, web apps and mobile apps in Singapore over the last couple of years and we’re looking to expand our team. We’re a group of technically strong full stack developed that primarily work with Python/Django, node.js and Cordova (in that order) on a modern development stack.
Our projects are weeks to months long and together span the full range of modern web development.
We utilize and you will pickup:
* Django, with a plethora of modern tools available to us like Django
rest framework, South and Celery and much more.
* Continuous integration
* Unit tests
* AWS with linux servers running Ubuntu.
* Git/GitHub
* Responsive designs
* Phonegap/Cordova
* Just about anything that relates to HTML5, javascript and css.
* Dozens of API's to Facebook, Instagram and other places.
Initially your responsibilities will be to support our currently ongoing and maintained projects. Over time you will accumulate projects where you'll be the point person by virtue of having done the work last or being the original developer.
It's our goal to nurture any candidate into a full fledged full stack developer that can confidently execute on projects, as well as assist our accounts people and clients in their needs. You'll be given as much responsibility and experience as you're interested take on.
We are willing to solve a visa for the right candidate.
Some people just have jobs, either because of ability, or choice.