Ask HN: How to navigate an interview where the interviews has it against you
8 points • 20 comments
@joddystreet | Hacker News
From 1/23/2017, 4:27:17 PM till now, @joddystreet has achieved 293 Karma Points with the contribution count of 84.
Recent @joddystreet Activity
- Sin City
- Forrest Gump
what are you using? as a code editor of course.
By win, I mean, it has a blazing adoption rate. Nearly all the libraries (eg tailwinds) is coming with VS Code plugin.
VS code clearly is something devs are paying attention to.
Ask HN: Why Did VSCode Win?
7 points • 15 comments
Behave - Robert Sapolsky https://www.goodreads.com/book/show/31170723-behave
BTW, the software is still being used by their OPS team, it’s used to monitor a third of India’s internet backbone infrastructure.
The guys who caught me were the actual users of the software, their team actually.
Saves them a millions of $ per annum, because of being able to meet SLA.
It’s now running for 7 years in their NOC.
Users revolted against their CIO (second or third replacement CIO), who proposed replacing this software (and others in their NOC), with an HP unified monitoring suite(a part of CIO’s digital transformation initiative). Apart from this software, rest of the monitoring systems have been replaced.
:)
I was sitting in an escalation-call, called by one of our most important customer and India’s largest ISP. There were 13 of them, 3 of us, and only 1 technical (that’s me). Things were super intense, extremely heated debates were going on, I was fixing a few issues, while answering the questions coming my way, in parallel I was also chatting with my teammates, who were back in the office and were on support calls with the same client’s ops team. And, then it happened - rm -rf /var/lib/mysql (i was already sudo su)
Escalation got further escalated - “Dashboard is not opening”
For a moment, I was shell-shocked, couldn’t hear a thing, just sitting there frozen.
Then i remembered the backup, i, against my usual style, took and the mysql replica i hosted, just as an insincere effort to calm the people in the room, i got to work. Restored the database, re-ram a few etl jobs, and we were back up online.
I was relieved, and actually quite happy, started interacting with the people in the room again, and showed them the system robustness even under a disaster, two of the 13 caught my bluff, but were smiling, They winked, turned back to face the others, and the heated debate continued.
The escalation went up till the CIO, but the guys who caught my bluff, never gave my deed away (in return i had to code a few more features and reports, just for them).
Don’t multitask, especially with a sudo access.
Please share your experiences, also, how do you think(/know) it all started?
- How you do anything, is how you do everything.
- Fall 7 times, stand up 8
- robotic process automation
- built-in collaboration
- offline storage, data cache
- internet-archive's client, permanent web
PostgreSQL (it just keeps blowing my mind).
Firefox.
Build something.
- aligning multi-party interests
- understand and manage the complexity
- finding a way to keep moving forward
- keeping things in balance
- knowing when to stop arguing
- accepting better solutions
- when stand corrected, have the courage to say "you are right, i was mistaken"
what topic would you be pursuing for rnd?
This is how we do the API -
- Database models should contain all the possible mechanisms/methods for data I/O
- Data Transformation utilities/ helper functions that do one job well, that is - sort, filter, validation, whatever -- -- If an API is using (more on API below), utils become immutable code
- Finally the API level -- -- treat the API code as immutable, once shipped -- -- The code should look like a pipeline of functions -- -- -- eg: serialize(...) validate(...) filter(...) db(...) -- -- -- need not be chained -- -- new API version, new router, new routing logic
- Review API with an intent to extract out any possible util methods. final API methods should look like a series of data transformation functions
- Overtime the utils would become extremely messy, but the APIs would be very clean
------------------------------------------------
The layer running business logic would be the most interacted with layer, if you can keep it clean, then you can keep frustration low in your fellow devs. A lot of people can work on the API level, irrespective of their experience.
Utils and Models should be managed by more experienced devs. Rate of change in Utils and Models is quite low as compared to the rate of change in the API levels.
------------------------------------------------
Not sure, I guess I am writing something very trivial and obvious.
We tried building NoCode (used to be hosted at noapp.mobi), I think around January 2017. The project has been abandoned since then, you can find the project at -
1. Docs - https://github.com/veris-pr/v3-docs/wiki
2. Core - https://github.com/veris-pr/v3-core
3. Backend - https://github.com/veris-pr/v3-api/tree/develop
4. Mobile App - https://github.com/veris-pr/v3-app/tree/feat-offline
5. Mobile App - https://github.com/veris-pr/v3-client
Quick demo (forced under 2 minutes time, we tried to take this to TechCrunch), https://www.youtube.com/watch?v=HfZT75rduPg
This was a POC project. It was quite suitable for simple business process management based apps. One of our customers has been using a conference room manager built on this platform, for 3 years now.
- Conflicts are resolved by asking questions, not by providing solutions
- Salary and coming to work are anti-patterns
- People expect perfection from a team, but readily accept mistakes of an individual
- Every job is easy, lest one should be held responsible
- With every person leaving the company - even after all the documentation, KT and handholding - a large chunk of knowledge leaves the company (or say wisdom); pretty much everybody is irreplaceable
- It's extremely hard to get your idea across. If you want your idea to get accepted, sit with one person at a time, before revealing your big idea. People still would not understand it, but they would accept it when discussed, again, in a group
- It's easy to work if there is a trust among the team members
- If you have KPIs and OKRs in your company, be ready for cross-functional conflicts, the introduction of time-wasting processes, and ultimately erosion of all the trust - giveth number, taketh soul
We tried building NoCode (used to be hosted at noapp.mobi), I think around January 2017. The project has been abandoned since then, you can find the project at -
1. Docs - https://github.com/veris-pr/v3-docs/wiki
2. Core - https://github.com/veris-pr/v3-core
3. Backend - https://github.com/veris-pr/v3-api/tree/develop
4. Mobile App - https://github.com/veris-pr/v3-app/tree/feat-offline
5. Mobile App - https://github.com/veris-pr/v3-client
Quick demo (forced under 2 minutes time, we tried to take this to TechCrunch), https://www.youtube.com/watch?v=HfZT75rduPg
This was a POC project. It was quite suitable for simple business process management based apps. One of our customer has been using a conference room manager built on this platform, for 3 years now.
Ask HN: What did you work on in 2019?
1 points • 0 comments
Ask HN: Unexpected product features that pleased you?
1 points • 0 comments
site design / logo © 2022 Box Piper