Hi! I'm Ankush!
I’m a 👨🏻💻 full-stack developer who loves everything technology. From 🕸 web-development, deep-learning to devops.
If you want to hire me, check my resume.
My mission is to help you write faster, cleaner and bug-free code. Because only when we developers right good bug-free code and ship features without going back and fixing do we move the needle forward and improve the world. Quite literally!
On this blog, you’ll find essays on:
- testing to have bug free code.
- clean-code as a way to improve code quality.
- how successful products & businesses work
This blog is the way I process my 🎲 thoughts and solve problems. If you read any, try scrutinizing them and see if they hold.
I also blog about non-technical and collect resources on topics such as life philosophy in a separate section.
Essays (sorted by last updated)
- Have you worked with that external service before?
- Are you integrating one service or are you integrating multiple similar services?
- Does it provide an SDK in your language?
- How do you connect to the external service?
- In case there isn’t a library? How do you verify if something is really from that system?
- Are there rate limits in place on the external system?
- Are there special conditions in place?
- Would you have to release the app on that particular platform?
- Choose the right medium
- Listening
-
Speaking
- Agree to what you find right.
- If you don’t understand something, re-iterate what the person is saying and ask if it’s right.
- Ask neutral questions
- Think before you say and stay in the realm of truth
- Express and explain better
- When talking give the choice to other person
- Keep things civilized
- Don’t attack the person
- If you had an argument
- Tell the Truth 1
- If it sounds too good to be true, it probably is.
- Do/Try/Invest in many things. You don’t have any decision making capacity unless you have an offer.
- If downside is negligible, reversible or it can be capped and upside is very high, do it. 2
- If you need to make a big decision and you can’t decided, say No. 3
- If there are multiple similar options and each seem similar, take the path that seems the hardest in the short term. 3
- If you can’t decide, pick the decision that will lead you to more peace of mind. 3
- Let others make there own decisions
- Delay the impulsive decision by 30 minutes or an hour or a day
- Be decisive
- Metrics
- Say no to many things
- How to read this?
- Commit Version 2: Getting Input and Generating Submission File
- Commit Version 3: Improvements
- Commit 6: ConvNet, and GPU
- Commit 7: Improvement
- Declare the local variable as close to where it is used and remove un-necessary once
- Just return it. Don’t store
- Remove commented code
- Remove functions and variables which you do not use.
- Variable argument lengths
- Default Arguments
- Use annotations/decorators
- Remove duplicates
- Single line boolean evaluation
- Think in terms of Streams
- Create and use base classes
- Keep your implementation as simple as possible
- Knowing the basics of time and space complexity goes a long way.
- Additional Tip: Always use parent interface for the type
- When trying to find duplicates
- Java: If you know the size of the list
- Always have your algorithmic logic in a separate function
- Rather than implementing own logic, take 5 minutes to see if your modules already provide the implementation
- 1. Always Turn On Experimental Feature
- 2. ️ Jump to Definition
- 3. Use GUI for exploring files and Mounting Google Drive
- 4. Creating Custom Snippets
- 5. Get GPU Info
- 6. Opening Notebooks from Github with ease
- 7. Send email when the task is complete
- 8.️ HyperDash
- 9. 10. — Random Filler Tips: Dark Mode and Corgi/Kitti Mode
- Other useful tips:
