You took a picture of the piece of furniture side on. Then you could tap to draw a polygon over the image. The app would then rotate the polygon to find the orientation with the minimum width.
524 karma · joined September 21, 2020
You took a picture of the piece of furniture side on. Then you could tap to draw a polygon over the image. The app would then rotate the polygon to find the orientation with the minimum width.
1. Be willing to be wrong a lot and admit it
2. Show vulnerablility
3. Deal with constant setbacks and disappoinment
Most people get the reigns and are suprised to find out its actually a thing nobody wants. Like being a social worker.
I encourage developers that work for me to just read the code and documentation. My advice to them is usually something along the lines of...
Think of how you would have done it as a sophomore in college completing an overdue assignment... chances are it works just like that
As for the other side, I do hiring on my team. We posted a Senior SRE on linkedin and got 30 applicants within a week. That was not our experience 2 months ago(more like 5). Maybe something has changed. I don't know I don't pay too much attention.
This sort of action is unprofessional, questionably moral, and unforgivable. I think the FANG companies were/are overrated. Why would you want to work for a business displaying this level of incompetence?
They don't try then claim "even I did try what would it get me? making some richy richer, no thanks". Ok so what the alternative? I'm just not willing to sit around complaining. Right now I don't feel like I'm being grifted and if I did I would quit.
I have been rewarded in the past and am confident I will rewarded in the future. The individuals that set it up kooky will be retrained to avoid that situation in the future. I feel bad for all the jaded folks they must live very depressing existences.
From my experience if you have a track record of doing a good job working autonomously and you can demonstrate that you contribute directly to the business's financial interests people just leave you alone and if they don't there is a good chance the boss's of those people will tell them "just leave him alone". Be someone's golden goose and in most organizations you can do whatever you want.
I think the majority of employees in most business do not have much visibility into the financial machine that justifies their existence.
Why do I bring this up? Because this is how most worker's experience their organization. Stay in your lane, get that promotion, best case you get your boss's job. But how did that job come to be? Who setup the training that you took? Most people can't even describe where the money in their business comes from.
It is a tremendous advantage to explore your organization fully. Visit its other offices and learn what your colleagues do and why they do it. Especially as an engineer. You can literally write your own ticket. Last year I was bored and I started to break down our cloud spend. This took me on a little detour. That detour involved a team that was following a process I could not understand. Turns out they didn't understand it either. I little reorganization yielded a $385,000/yr cost optimization. It took me just a couple days. Chances are you swim in a sea of complacency too.
Yep read that guys blog history and the agenda just pops right out. It's not just about cost for Basecamp its ideological. I can't help but imagine this bias leaks into the financial and operational calculations.
We had a similar situation. We had a team did not want to move to the cloud, the business forced them, so they built the system in a way that fought the cloud. Then the self fulfilling prophecy kicked into high gear. "See we told you it was a bad idea, look at all the problems we have!". The problems were created through half baked attempts to be "agnostic" to the cloud. Once we removed those elements we were able to reduce the cost of the system by over 90%. It was far cheaper than when it was running in the Colo. These folks had no interest in optimizing for cloud native execution they were already planning their move back into the Colo.
I don't understand how they are going to achieve that. Does it include routers, switches, IPS's? What about the costs associated with having a physically wired network instead of a software defined network.
Also they state they are region redundant which is probably way overboard. Will they be protected if they lose their entire datacenter? Will they flop over to another geo? If not then you must consider not their current spend but their spend if they were single region. That would further eat into proposed savings.
Don't get me wrong, I do believe you can achieve cost parity in a Datacenter but you need a certain level of scale. I am skeptical that it can be done at $3 million in spend.
This is because I have to factor all the costs. This includes electricity, maintenance, incident response, networking, renting the cage, vendored software for backups, threat detection, fire suppression, equipment upgrades, licensing, alerting, and it goes on and on and on...
I'd challenge you to break down the full cost of owning a server as you see it. I bet you will miss 75% of the actual costs involved. I promise short of seizing a colo like its Nakatomi Plaza and running it at gunpoint you will never in a million years come close to the total ownership cost of cloud instance. You can't compete with the economies of scale and the caliber of the engineering.
I consider the latter to be far more complex.
Having done this several times I can definitively say given my experience it's best to start in the cloud with a cloud native architecture. I can run a fully containerized application in ECS or EKS for a few hundred bucks a month. Why would I incur all the costs and limitations of a VPS or even worse a server I have to look after myself? How much can I really save? $50 a month maybe less?
A long time ago when I was working a major telecomm provider I had the privilege of working with a great software mentor. He instilled in me the lesson of knowing approximately where you are going to land and not do anything now that would jeopardize that landing.
If I was a CTO at a greenfield startup. I would insist we deploy on a PaaS that supports serverless, object storage, and container orchestration. We would recognize and enforce well accepted patterns that will not impair our ability to scale later. There is plenty I can do to keep the costs low(most importantly turning things off) then when I need to scale up its as easy as turning a knob.
Now the real question is do you believe you are right? Do you really(and I mean really deep down) think these people are smart. Do you think you have a better way? Do you wish they'd realize that what you are doing is best path forward?
I have seen this sort of conversation pattern in the past. In my case it was a younger programmer that wanted the team to take a different approach, but at the same time were struggling with the "what if I'm wrong?" dilemma. They didn't want to throw their weight behind a proposed change in direction because of insecurities and fear of rejection. What it came across as to the rest of the team was a person that didn't want to lead but at the same time was always finding fault. When confronted they would say things like "I'm not one of the smart ones ..."
If you really are not smart as they are then trust them and learn from them. If you think you have a better path and are committed then stand up and say "This is wrong and here is a better way". If you are right and they reject you then maybe its not the place. If they are able to demonstrate that you are wrong you should accept it and move on. If you are right and they agree then you are in the promised land.
AI/ML is no silver bullet. It's just another abstraction. It will create new types of jobs. Most likely coordinating/choreographing AI/ML agents in new yet to be discovered applications. It's all part of the endless march of technology. You don't realize how little you are actually capable of until you get the new set of tools that bounce you up to the next level.
Take the tools we have today and present them to some chump shoving punch cards into an early computer and watch their brain melt out of their ears. We can do things with a wristwatch they would have thought impossible. The people that will get burned are the ones that want to stand still. Always be learning.
The number of applications I have inherited that were messes falling apart at the seams because of misguided attempts to avoid "vendor lockin" with the cloud can not be understated. There is something I find ironic about people paying to use a platform but not using it because they feel like using it too much will make them feel compelled to stay there. Its basically starving yourself so you don't get too familiar with eating regularly.
Kids this PSA is for you. Auto Scaling Groups are just fine as are all the other "Cloud Native" services. Most business partners will tell you a dollar of growth is worth 5x-10x the value of a dollar of savings. Building a huge tall computer will be cheaper but if it isn't 10x cheaper(And that is Total Cost of Ownership not the cost of the metal) and you are moving more slowly than you otherwise would its almost a certainty you are leaving money on the table.
>Even a simple merge/rebase leaves one confused.
I've never had this problem. Git always works exactly as its designed for me.
The second is a nice, clean EKS app. Developers build containers and I bind them with configuration drop'em like they're hot right where they belong. The builds are simple. The deployments are simple. Most importantly there are clear expectations for both operations/scaling and development. This makes both groups move quickly and with little need for coordination.
What is the shortest route to a sustainable, defensible revenue stream?
In the 80's IBM built a super quick computer out of pieces you could buy at Radio Shack. The ultimate solution! Why incur all that upfront manufacturing cost when you can assemble it out of existing parts? They learned the answer really quickly. The lower barriers of entry meant anyone could recreate the product. And so a million clones popped up using the same parts. For a decade Apple ate their lunch by investing in a proprietary platform(which a lot people said was madness using the exact reasoning on display in this article)
SaaS is great but you have to have some sort of moat for whatever you are building. Sometimes that moat can be as simple the idiosyncrasies of your over-engineered, prematurely optimized product. I had a hand in the development of one of the major VPS players during the 2010's. There were things we could do just because of the weird decisions people had made in the past. That translated directly to competitive advantage.