We've been using @Google Search for ages, but somehow never realised that the 'I'm Feeling Lucky' button skips all the ads and search results to take you straight to the relevant website.
The bootcamp fostered a remarkable collaborative environment for learning which is crucial for growth, especially in Software Development. Highly recommend applying.
P.S. @oolhaas is a great teacher.
Looking for engineering grads who passed in 2024 for a 12-week in-person bootcamp in Mumbai.
Last year, I had the most fulfilling time of my career when I taught 10 driven folks about different modalities of product engineering. The end result? We hired 5 highly skilled and curious devs at @ProcedureHQ.
So we asked ourselves, why not do it again?
Apply if you want to break into a product engineering role. More info here - https://t.co/CchoA6S8Ca
I'm working on a young project in its spaghetti-code phase. The first instinct was to clean that up by introducing service and repository layers. However, it wasn't the best choice in this case because ''Before software can be reusable, it should be usable". Here's why,
CI/CD Pipeline Explained to Kids
Section 1 - SDLC with CI/CD
The software development life cycle (SDLC) consists of several key stages: development, testing, deployment, and maintenance. CI/CD automates and integrates these stages to enable faster, more reliable releases.
When code is pushed to a git repository, it triggers an automated build and test process. End-to-end (e2e) test cases are run to validate the code. If tests pass, the code can be automatically deployed to staging/production. If issues are found, the code is sent back to development for bug fixing. This automation provides fast feedback to developers and reduces risk of bugs in production.
Section 2 - Difference between CI and CD
Continuous Integration (CI) automates the build, test, and merge process. It runs tests whenever code is committed to detect integration issues early. This encourages frequent code commits and rapid feedback.
Continuous Delivery (CD) automates release processes like infrastructure changes and deployment. It ensures software can be released reliably at any time through automated workflows. CD may also automate the manual testing and approval steps required before production deployment.
Section 3 - CI/CD Pipeline
A typical CI/CD pipeline has several connected stages:
- Developer commits code changes to source control
- CI server detects changes and triggers build
- Code is compiled, tested (unit, integration tests)
- Test results reported to developer
- On success, artifacts are deployed to staging environments
- Further testing may be done on staging before release
- CD system deploys approved changes to production
β
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/FIzCeaWsZV
Introducing the magnificent Proteges, gearing to solve real-world tech challenges.
In these few weeks, they combine their expertise and creativity with a relentless drive to create real-world innovation.
#productmanager#founders#CTO#RubberDuck#bootcamp#BYOP#Protege
I've been working on my #portfolio website for quite some time. Here is Version 1 of the website.
Let me know your thoughts. Built with @reactjs#FrontEnd#React#Webdesign
Link - https://t.co/1rMT3dJYQT
Attending #OEF23 hosted by @OnePlus_India was an absolute delight! The sessions were incredibly informative, and the co-creation opportunities showcased just how community-centric the brand truly is. Thank you for an amazing experience! #OnePlus#OpenEarsForum
Hey, this is Alagappan. I'll be graduating from college next week and I'm actively looking for #Internships/#Fulltime opportunities in #softwaredevelopment. I'll be grateful if you can help me connect with any opportunities that you have to offer. Thanks! #hiring#opentowork