Consider: millions of years ago our antecedents gave a massive sacrifice of their left hemisphere.
We lost a tremendous amount of short term memory and replaced it with Broca’s, Wernicke & the phonological loop.
But why?
So we can—talk.
Thus chimpanzees can do this—we can’t:
The deployment frequency downward spiral in 6 steps:
1. Team doesn’t write sufficient automated tests and doesn’t automate deploys.
2. Team spends significant time manually testing each release and getting it to prod.
3. Releases must be batched to make manual testing practical. Testing the entire app for each ticket would take too long, and getting code to prod is time-consuming and risky.
4. Production deploys are infrequent, late, and buggy because the release is big,and risky. Manual testing is too slow and insufficient to catch all issues.
5. Management loses trust in the dev team, so it creates even more non-prod environments and more mandatory manual checks and approvals.
6. Bugs still slip through and late releases become even later due to more environments and more manual validations. So management institutes a “Change advisory board” that must approve every change and every release. This further slows progress and makes releases even bigger and thus, higher risk.
To break this downward cycle:
1. Automate checks and deploys.
2. Make developers responsible for quality. Embed QA with dev if separate and enforce using the same testing tools.
3. Break work down into small pieces. Commit, merge, and ship daily. Continuously deliver.
4. Use Canary releases and feature flags to reduce deployment risk.
5. Empower delivery teams. Give the team increasing autonomy as they earn trust.
What makes a good API?
It could be a function, a class/method, a URL, a protocol, etc.
What are some good guidelines to use when thinking about API design?
1/n
@allenholub@netflix While netflix invests in even more chaotic UI, illegal streaming sites like lookmovie have fully integrated imdb ratings in their search. Worth a look to get a sense for user needs, and the real competition
I care about code quality. But, I also recognize it’s a tradeoff.
My old boss didn’t believe in automated testing. He thought worrying about “code quality” was silly.
He’d say “We don’t need QA - we have users!” 😬
Result? He sold the company for $135 million.
Duplicated string in some code.
New developer: "Approved."
Mid-experienced developer: "This violates DRY and should be extracted to a constant."
Experienced developer: "Approved."
@businessbarista@immad Guest Experience Platform for hotels (https://t.co/aplOGNZBiL). Help guests to improve their stay experience while streamlining the operations and great upsell opportunity.
The more experience I have as a developer, I've noticed that I'm less and less likely to add a dependency or library to my app unless absolutely necessary.
I'd rather copy and paste some boilerplate into a local service or utility if I have to than depend on something that will probably break anyway at some point soon, or add another abstraction that might be tough for someone else to figure out quickly.
I'm also noticing I'm less and less likely to use a library unless I understand exactly what's happening under the hood for the most part.
I'm a fan of magic when it works and I know why, but when I don't, it brings more anxiety than anything....
Friendly reminder that you should upgrade your Android React Native apps to at least v0.71 (or Expo SDK 48+) before August 31 ✨
If you face challenges upgrading, my DMs are open 📩
@immad Guest Experience Platform (https://t.co/aplOGNZ3td). Help guests to improve their stay experience while streamlining the operations. We have great feedback from customers and we want to expand sales internationally.
A couple of us had a very productive discussion with an expert on Cognitive Warfare. A relatively new term, but exceptionally significant and relevant in times to come. The key takeaways :
1. Defence forces need to recognise this threat and start building barriers to safeguard against it.
2. The solution lies at both policy and operational levels
3. We do not control the environment. But we can create an effective and solid response mechanism by conducting training’s and engaging experts.
4. The Def Forces may continue to believe that the threat from propaganda warfare and social media is an alien concept, but that is not true as the infiltration of social media at all levels has the capability of hitting deep and strong
5. Awareness, conversations and training of troops is a must. This knowledge cannot be limited to top brass only.
And many more relevant points came up. It’s a debate that needs to happen more often.
@adgpi@IAF_MCC@indiannavy
As someone who has raised five dogs of various (friendly to ferocious) breeds, my advice to both debating camps :
1. Your dog loves YOU and may never bite you. But you can never guarantee how he/she will respond to a stranger and might react if they sense a threat, however illogical.
2. Your pet is your choice and passion. It’s not other person’s burden to bear. Others may be even a bigger animal lover than you, but still may not comply to your demanding nature to accommodate you and your pet.
3. Better to be safe than sorry. Why risk other people’s safety. Muzzle them around kids especially in cramped up places like lifts, stairs etc.
4. Lot of people are very uncomfortable and scared around / with dogs. Respect their feelings when they visit you or meet you. Tie your dog, keep them inside a room. Don’t keep laughing and saying “ oh he’s harmless” when your large dogs pounce on someone, even if lovingly. For whatever it’s worth, maybe the other person doesn’t like getting licked by a dog or probed in crotch.
It all comes down to why should we force out opinions on others. You don’t like pets, you have no right to criticise those who have them. And same way, if you love having pets, it’s your choice. Don’t expect the world to stop spinning coz you snuggle up to a Dalmatian. Respect others and act like a responsible pet parent.
If you're an engineer and you've never used Earthly before, I would love to watch you go through our new onboarding flow for the first time.
We'll reward you with your choice of swag / gift card.
DM if interested!
Retweet for reach!
You're under no obligation to remain the same person you were a year ago, a month ago, or even a day ago. You are here to create yourself, continuously.
Continuous integration:
✅ No PRs
✅ No branches
✅ No gating code reviews
✅ Commit directly into trunk
Frequent Integration:
✅ Small PRs
✅ Simple, short-lived feature branches
✅ Code review before merge
✅ Merge branches ~daily
Frequent integration is often good enough.
@shreyas Backpropagation algorithm leverages the idea of learning from mistakes to create artificial neural networks. Don't you think what you said has context boundaries?