Chanchal Kumar Ghosh

Glad @Meta added this feature.

#WhatsApp needs a "summarize since last read" feature, especially for group chats! Keeping up with medium/large groups is a struggle. Am I just getting old?😅 #FeatureRequest 😢

Initial prompt: can you please write a short announcement, no longer than 250 words, announcing the departure of my colleague Ilya from Openai. Please make sure to convey how much I respect him and his work and ideals. Also announce that Jakub will be taking the role of chief scientist. Do all this in a very concise sam altman tone.

@rakyll 💯

If your only definition of software development is feature development, it's potential to believe that LLMs can replace developers.

The hype of Hyperloop is finally over !! theverge.com/2023/12/21/240…

This actually happened to Evernote. They took the advice of “keep talking to your customers and ship whatever they want” as the only guiding principle for product development. And what ended up happening was paying users liked it, but the product become unintuitive and feature overload for the new user. To the extent that they had to rebuild a version for the new user. Users don’t always know if they really want something. It’s your job to take the extra step to think on their behalf: whether they really need this. Or can what they ask be done through something much simpler. Or can you solve multiple problems of different users with one new redesign rather than a bunch of changes. The right principle is: “Keep talking and listening to your users, spend the additional time thinking on their behalf what they actually want, and ship that”.

Scrum is a cancer. I've been writing software for 25 years, and nothing renders a software team useless like Scrum does. Some anecdotes: 1. They tried to convince me that Poker is a planning tool, not a game. 2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing. 3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention. 4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint. 5. I had to use t-shirt sizes to estimate software. 6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points." 7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this. 8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously. 9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind. I believe in Agile, but this ain't agile. We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it. The result was always the same: It didn't work. Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control. But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team." Sure it is.

@rpilocator down?

@elonmusk But the previous app (looks suspicious) takes more space.

Sorry this app takes up so much space

That's how you should conduct interviews 😂

@golang @val_deleplace @JulienBreux GOMAXPROCS is still not cfs-aware.

Go 🤝 Kubernetes. Go fits especially well in container orchestration systems like Kubernetes. Watch @val_deleplace and @JulienBreux as they highlight three advantages of choosing Go to build your next app in Kubernetes → goo.gle/41YdkIB

@golang Here is a simple library to use a zap logger as a slog handler: github.com/chanchal1987/z… In case you don't want to change your production logger yet but want to migrate your library to use slog.

📦 The Go team is looking to add a new package to the standard library for structured logging. Jonathan Amsterdam covered what this means at Go Day 2022. Tune in 👉 goo.gle/3GF6kZU

@DJISupport Mobile: Pixel 3 Browser: Chrome (Install unknown apps allowed)

@chanchal0609 Thank you for the screenshot. May we confirm what mobile device you are using? In addition, did you try to launch the APK file using the browser app of your mobile device or the file manager app? Thank you.

@DJISupport When should we expect DJI mimo in the Play Store again? It has been pending for a long time. Do you really have any plans?

@chanchal0609 Thank you for the information. Apologies for any inconvenience. You may kindly allow 3rd party applications to be installed on your mobile device and install the DJI Mimo app. Thank you for your cooperation.

@DJISupport Google's advanced security is not allowing me to install external apks.

@chanchal0609 You can visit our website at dji.com/downloads/djia… to download the latest DJI Mimo app. Thank you for your understanding. 2/2

@evacide R.I.P.

I wasn’t going to say anything, but since ZDNet has republished the AWS “Sustainability with Rust” blog post, a short thread about why that post is misleading (at best) about Go. 1/