Its 2024. Software Development has changed. Completely.

Its 2024. Software Development has changed. Completely.

In this conversation, Krish discusses the need for software development to evolve. He emphasizes the importance of adapting to change and exploring new ways of doing things. Krish also highlights the role of AI in software development and the potential benefits it can bring. He encourages reevaluating problem-solving approaches and finding more efficient ways to document and create tickets. Ultimately, Krish emphasizes the need to embrace change and stay ahead in the rapidly evolving software industry.

Takeaways

  • Software development needs to evolve by adapting to change and exploring new approaches.
  • AI can play a significant role in improving software development processes and delivering solutions more efficiently.
  • Problem-solving approaches should be reevaluated to ensure they are still relevant and effective.
  • Efficient documentation and ticket creation processes can enhance productivity and collaboration.

Chapters

00:00 Introduction

01:01 Adapting to Change

03:54 Reevaluating Problem Solving

05:18 Approaching Documentation

06:40 Efficient Ticket Creation

07:08 Embracing Change

Jaksot(410)

I do a lot of our Software Design work while walking!

I do a lot of our Software Design work while walking!

When I am sitting in front of my machine, I want to be coding (or doing something that I really need the machine for). Design work doesn't necessarily fall in that category for me - at least not all the time.

15 Tammi 20216min

Should your Product Manager have to be cognizant of your Architecture?

Should your Product Manager have to be cognizant of your Architecture?

The correct answer is "No". Or, is it? It really depends on a few different factors. Let's talk about a few pros and cons of either approach.

14 Tammi 20214min

When we embarked on building a product, we expected some challenges. But not a few others.

When we embarked on building a product, we expected some challenges. But not a few others.

I knew we would have engineering challenges and that didn't bother me (having done this for a while). But what kept me awake were the roadblocks that were bound to be there that I had little clue about!

12 Tammi 20219min

The True Cost of Meetings - it is more than what you think

The True Cost of Meetings - it is more than what you think

How much time are you spending in meetings? And are you sure you needed to be in these meetings?

10 Tammi 20219min

One approach to create UX Designs is to draw them out quickly without relying on tools

One approach to create UX Designs is to draw them out quickly without relying on tools

If you can draw, this approach will work really well! But, even if you are like me and cannot really draw, it will still save you a ton of time if you manually drew out the UI pages to share with your development team.

31 Joulu 202010min

User Experience(UX) Designs for Web and Mobile Apps

User Experience(UX) Designs for Web and Mobile Apps

While it would save time (which is priceless for everyone, not to mention smaller startups where it is even more valuable!) to use UX designs created for the Web for Mobile Apps, and vice-versa, it is hardly ever possible (if a seamless User Experience across devices is at the top of your priority list).

26 Joulu 20207min

How to deal with the issue of Bot Sign ups?

How to deal with the issue of Bot Sign ups?

Well, as technology improves, we get smarter as humans. But, so do bots. There's any number of things you can, and should, do to ensure your app is not hit with bot (aka: fake) sign ups.

26 Joulu 20202min

GitHub Projects - How we manage our repo-specific issues

GitHub Projects - How we manage our repo-specific issues

We use our own product (obviously!) to give us a federated view of all the projects that our ecosystem comprises of but at a code repository level, we use GitHub's Project feature to manage repo-specific issues. Here's how we do it.

1 Joulu 20202min