About OTC CatchUp

Note OTC CatchUps are weekly informal sessions involving project showcases and technical discussions. They are held every Saturday from 10:30 PM IST. Join in!.
For all summaries, please visit catchup.ourtech.community/summary.

OTC CatchUp #80

Date: 21-05-2022

Duration: 9 hrs 10 mins

Topics Discussed

  • General introductions.

  • Aditeya Sharma asked if WeWork would be a good choice for renting office space for a startup.

    • Harsh Kapadia suggested cost optimisation for a startup by asking people to work from home till it raises enough capital.

  • Himanshu Sharma shared his blog post Build an augmented reality app in Flutter.

  • Ishwar Gowda talked about his reasons behind learning Go.

  • Pratik Thakare talked about his interest and reasons behind getting into DevOps.

  • Darshan Rander talked about gRPC and how it is different from JSON.

  • Pijamo Ngullie asked for BaaS (Backend as a Service) platform options.

  • Aditeya Sharma asked about the resources and time required to build or hire someone to build an app like Dunzo.

    • Harsh Kapadia talked about hink ing about the idea, planning features and requirements out and designing the app before building it.

    • Jaden Furtado asked if it is better to start out with a good architecture and take time to build the app or go with a quickly built prototype and build it out later.

      • The general consensus was to pay a lot of attention to the idea, give a fair amount of thought to the architecture after that (to avoid too much Technical Debt) and then build out a prototype.

    • Sreekaran Srinath and Himanshu Sharma talked about how low-code and no-code platforms help developers to test out certain features and get a rough idea about how someone would want an app to look like.

      • Vaishnavi Dwivedi talked about research, analysis, identification of users who would actually be willing to use an app and how low-code and no-code platforms help out in such cases to check if a product is fit for the market.

    • Anas Khan shared a LinkedIn post about no code.

  • Himanshu Sharma talked about the difference between a library,a toolkit and a framework.

    • A Framework is something that is installed on a machine and one interacts with it via commands to execute/perform actions.

    • A library solves certain problems and a Toolkit is a collection of libraries to solve multiple issues on multiple platforms.

  • Aditeya Sharma asked about how Flutter is as a framework and how much would it cost to hire a Developer for building an app using it.

    • Vaishnavi Dwivedi talked about Flutter, its features and how the cost of building an app depends on the requirements.

    • Pijamo Ngullie asked about the differences between Flutter and React Native.

      • Pratik Thakare told us how his React Native app broke due to an Android update since React Native directly uses native Android components.

  • Sarah Khan asked if it is better to design components before starting with a project or a hackathon.

    • Vaishnavi Dwivedi talked about how a good design makes a project look presentable in the case of a hackathons, and how it gives a clear picture about what to build, in terms of a personal project.

    • Siddharth Bhatia talked about how he started designing his apps before making them.

    • Harsh Kapadia talked about how experience and exposure helps in creating better designs over time.

    • Ishan Sharma talked about how visiting multiple websites helped him to learn about good designs by observing the structure of well built websites. This was one of the reasons for him behind learning GSAP.

    • Tushar Nankani talked about his journey of building projects using the hit and trial method and how he learnt the importance of design over time.

    • Pijamo Ngullie shared Material Design Color Tool for choosing colors for a design.

  • Anil Harwani talked about how the usual principle of Failing Fast and Learning Fast of people building software does not work in the hardware world.

    • Making hardware is expensive, therefore execution of building process should be planned optimally with almost no errors. Even though software errors tend to be easily corrected, one should not always approach a task in a way where it is always okay to fail before getting a certain thing right in the first try.

    • He shared an analogy where a Metro project is planned properly by taking a lot of factors into consideration before execution, since errors are not very easily repairable and might cost Millions.

    • He also talked about how a complex problem can be broken into parts and solved collectively by good communication and proper thinking.

  • Anil Harwani shared his patent on Automatic Memory Overclocking.

    • This tool aims to tune the device memory and CPU for maximum performance, but without extensive manual testing from user side.

      • The tool creates profiles based on the memory attached to the device, by Overclocking and stressing that memory module to breakneck limits, then lowering it to a relatively safer limit and checking where the device stays stable for a long time.

      • It can be manually initiated by the user during certain scenarios like playing games.

      • This tool will be integrated with future AMD processors. Automatic Memory Overclocking works irrespective of the Operating System, since it is handled by the processor itself.

    • Anil Harwani talked about the long process behind creating patents.

    • Pranav Dani asked how the will module work on Motherboards or most consumer equipment like CPUs and RAMs which are usually locked by the manufacturer by default.

      • Anil Harwani answered that most enthusiast-level equipments come with the ability to be Overclocked. So the module would only work on CPUs and RAMs that allow Overclocking out-of-the-box.

  • Pranav Dani asked about the difference between physical cores and execution threads and why some processors don’t come equipped with Simultaneous Multi-Threading (SMT).

    • Anil Harwani talked about SMT and Instruction-Level Parallelism. Each cycle in a processor is very precious, so for optimally utilising each cycle, SMT combines Hardware Multithreading with instruction-level parallelism to help facilitate more than one instruction being executed during a single clock cycle.

    • Hardware SMT is fused on some processors due to various reasons and those processors are sold at a cheaper cost.

  • Anil Harwani compared the software industry and semi-conductors industry on various levels. He suggested that learning more about one’s industry could help one come up with various innovations and solutions for existing problems.

    • Jay Kaku talked about differences between learning software languages and the Hardware Description Language (HDL). Learning HDL is not similar to learning any software language, since all formal verification cases need to be handled using formal testing in order to evaluate the correctness of the intended algorithm. All edge cases need to be manually handled when using HDL.

  • Anil Harwani suggested everyone to learn touch typing (since it becomes second nature and increases efficiency) and go through The Missing Semester of Your CS Education.

  • Anil Harwani shared his Bachelor’s final year project about the Grid Computing Framework.

  • Anil Harwani shared the story of how he got his first graphics card from ATI technologies and hoe ATI was later merged with the AMD graphics division.

    • He also talked about Qualcomm, who bought the mobile division of ATI in 2009. Now that integrated mobile GPU is known as Adreno.

  • Jay Kaku asked about how one could make a project qualify as a viable product.

    • Anil Harwani talked about various ways to build a project and evaluate if on the basis of how the end user needs it.

    • He also talked about how most people interact with devices on a very superficial level.

    • We talked about how one should prioritise knowledge over money in the early stages of their career, provided that they have the luxury of choosing between money and knowledge. Anil shared an analogy where a Developer who works at a company which provides a higher package for working on a technology which might get out dated in a span of few years, looses his job when the technology is no more relevant. This benefits the company, but not so much the Developer. Thus, it is important to not get comfortable and keep learning and evolving.

  • Siddharth Kaduskar asked about Data Structures and Algorithms and different platforms to practice them on.

  • We discussed about various project ideas for final year students from a learning point of view.

Projects Showcased

  • Sarah Khan showcased her Figma design for Accuratus, a Google Maps clone for India that she thought of.

Meet Screenshot

Meet #80 screenshot

Note For all summaries, please visit catchup.ourtech.community/summary.

We rise by lifting others.
— Robert Ingersoll
Kindness always wins.
— Selena Gomez
Alone we can do so little; together we can do so much.
— Helen Keller