This is the same by type. Twitter is hardly the only company engaged in this.
70 karma · joined January 29, 2023
This is the same by type. Twitter is hardly the only company engaged in this.
It's a net win over the previous government censorship and blue check system.
Add a small feature to an existing system. This estimate can be anywhere from several months to a day. Most of the error bars are org and system specific rather than anything to do with the feature. The exact same feature built by the same person in different orgs and different systems can be opposite ends of the range.
Seldom do people have the contextual understanding to provide an accurate narrow estimate, particularly since both org and system are in flux. They change constantly. Unseen landmines potentially await in both.
> If you don’t, your boss is going to ask you for exactly that in a roundabout way and micromanage you because you are forcing them to do your job.
And such orgs take forever to get anything done.
> It still baffle me than approximately half of developers don’t understand things which are obvious to any seasoned blue collar worker.
Software is probably the hardest kind of engineering you can do. All the system constraints are virtual. Just consider comparing a dirt ground for consistency and behavior vs libc... 304 stainless vs react.
You can go deep in both, but a shallow understanding of one takes you much much further than a shallow understanding of the other.
It may feel good to have some of the times quantified. But... If your estimates are literally fiction. It won't stop being fiction in front of the client. You should really spend that energy that went into the estimate for something useful instead.
Not to say you can't derive some useful information from a short planning session. Just don't expect anything other than thumb to the wind guesses.
The primary factor to success and happiness in life is your family structure and having their loving guidance and support.
Today, the village mostly hinders. Few people have experience with children anymore and most are self centered. Their "help" mostly consists of direct criticism, or indirect criticism in calling the authorities.
Instead of a mutually beneficial compromise like give everyone private individual dressing spaces and listening to potential victims of trans abuse in gendered spaces. You go full offensive mode on me for even suggesting the possibility.
It seems that you don't want political allies, but rather political subjects...
If you're actually open to seeing the issue there are plenty of stories you can search up on this topic. What I mention is hardly unique, I see them with some frequency.
Ignoring these concerns will just cement the political divide and harden political opponents who want to protect female gendered spaces and youth from predators.
Local story... Boy who claims to be female and goes into the girls locker room to watch them change. He doesn't actually change or participate. Just a spectator. The girls try to hide from him. It's pretty clear by the details that he's a peeping tom just there to ogle the girls. One of the girls speaks up about how uncomfortable he has made life and many girls no longer want to change their clothes for gym, even asking for private spaces but this girl is ostracized and vilified by the local media for not being supportive.
It's pretty amazing how we went from being so protective of these spaces. Particularly from sexual predators. To one where we openly allow predatory behavior and tell the reporter of the incident that she is the bad one. Deny them privacy and security.
Numerous reports of trans males dominating girls sports, and from information that is the primary reason for the 'change'.
All these stories of particularly men going trans for transparently selfish reasons of advantage do not help the cause among people who really care about their daughters well being.
Production access should only be allowed from a locked down system with no open ports and a very small whitelist set of software. Operations for said system should be simple. Deploy version x with necessary provisioning. Backup system. Restore system. View monitoring and logs.
You must minimize the surface area connected to production.
On the network side the system with the keys for production is also firewalled off from general Internet access. So potential malware can't phone home.
Society generally had adopted intolerance and seeks to punish detractors. Both sides are doing this. Again, this is not... measured...
This is also a terrible waste of resources to rebuild the wheel over and over. A few components, sure, when there is a compelling case for custom. But you do the business a disservice by consuming so much time on items just because you want to.
I also find it incredibly demoralizing trying to advance a project and the bug log is full of bugs about basic component behavior you would just get out of the box with a pre built set.
The most likely alternative to boring, functional, and WORKING, is BROKEN and dysfunctional. Please don't break navigation. Have predictable menu behavior. Etc... There are other ways to be creative.
It is more complicated. It works best when the user has a distinct data bucket that is exclusively theirs. A note taking app. Personal finance. But they may have multiple devices so syncing is desirable.
This use case is reasonably common and turns out to be relatively simple to do.
If you have shared data between users. If you have a significant amount of data that just requires being online to interact with the system. Then it has pretty minimal benefits over just centralizing the data and it should be avoided to minimize complexity.
I'm really surprised more companies don't pick this stack.
Money is on, it was homogeneous. Which means, You can't even see your own biases as other points of view were culled in creating and nurturing the org structure.
One more point.
Companies never ever have evil anti user dark patterns enter production because of code reviews, do they?
I think you have it the other way around. The bias is institutionalized so deeply that the process makes it essentially impossible to get a non curated with bias point of view out of the organization.
Look at how tightly political leanings are tied to news outlets.
If it were as easy and objective as you say we would get a lot more random pieces out of outlets instead of the rather rigid ideological publications we see in existence today.
Even Reddit subs and hacker news, which are much more random than news outlets, have pretty clear political leanings. With sufficient samples you can even break down the subgroups within the community.
News orgs don't have nearly the internal diversity required to possibly remove such bias. They are homogenous.
Because... Editors couldn't possibly have motives that similarly contain bias, corruption, out other such common frailties of the human condition?
It's like a drug that attaches to your love receptors preventing you from really loving and receiving love. And most steeped in its grasp don't even know it because it is hard to explain color to someone that has only ever seen black and white.
All the other products that shipped on Intel 7 had to also be designed for the process. Intel was also late on arc, which wasn't even fabbed on Intel process nodes. Ponte Vecchio... Late late late.
It wasn't process problems that kept sapphire rapids from being released till now. 10nm/Intel 7 has been ramped up and fabbing products for over a year.
They are very late on critical products that are clearly not the fault of the foundry side. This is squarely on the design side.
Running good engineering orgs is hard, Intel's problems run deep and on many levels.
The rotten orgs around the service are getting flushed, which is good for honest users and uses. Don't trust other orgs with your holdings. Hold your own crypto keys.