HN user

shipit

54 karma

[ my public key: https://keybase.io/sumeetparmar; my proof: https://keybase.io/sumeetparmar/sigs/5x6dNtBABnMkdBFbwCY5pEtUTIJp1gatPx37l64BUYM ]

Posts4
Comments27
View on HN

Dude, first of all congratulate yourself for making the choice to pick the better version of yourself. Your choices are between what feels good right now and what is most important. This is a journey and you must allow yourself the time to transition to the better self. Stop beating up yourself you can do and realize that this is a new set of skills you much acquire, that you are going to learn a brand new behavior and transform to this new state. I share what worked for me.

1. Do not drink alone. Just make this rule. No sitting at home and putting away a 12-pack. You seem to be ok for weeks. So challenge yourself to a 3-week limit, put it on your calendar. Pick a nice, upscale bar, dress up and treat yourself.

2. Start waking up early. For extra credit before sunrise. Get out of bed. Go for a walk in the chill of the morning. Feel that air in your lungs. Just do this.

3. Loose the friends. This is the hard one. They are not your friends. You help them feel secure in their lack of agency over their lives. Just very very slowly start being less available. And here is the opportunity to gauge who is a good friend - "I am making a change, lets meet for a walk/movie/museum instead of the bar". The ones who berate this path, loose them.

4. Of the few people remaining from step #3. Appoint someone as overwatch. There will be a time you will be like "fuck it" and get yourself a bottle of wine, 12-pack or whatever. Call or text this person for overwatch request. Take a video of you pouring the booze down the sink. And send it.

5. Finally, remember what Tony Stark said to Peter Parker -- if you are nothing without the suit, then you shouldn't have it.

Epilogue: Guilt. This is the worst thing. All our learning is based on institutional guilt. Tests. Grades. Evaluations. Re-imagine yourself as in third person. Your body is a resource. And you are equipping it. Guilt is rear view mirror stuff and a poor motivator.

What will happen with you is this. You will fall in love with early mornings. You will have time in the morning to do something you truly endear. You will trust yourself with this block of time and this capacity will overflow into all aspects of your life. And in about 6 months' time, you will dress up, you will go to the nice bar, order that drink and very very likely just walk away from it.

Good luck and godspeed.

I think this is where `gRPC` shines. It can feel tedious but really, define the interface and use the tooling to generate the stubs, implement and done. It prevents having to think up and implement a protocol and importantly versioning for if/when the features of the containerized apps start to grow/change.

its a `2 vCPU, 7.5GB RAM` -- so far tested with open source projects including NDK and it stood up pretty well. Build times post close to what it would take on the local dev machine. Overall experience is that once you push your commit in about `2 mins + (local build time) mins` you'll get an email with the CI result.

Product wise we don't want the user to worry about machine resources as long as CI executes within reasonable time.

Thank you! And you are correct -- I am indeed ESL :) tbh writing the copy for landing site has taken me longer than some of the code :p

I shall revisit with fresh eyes and get it sorted out. Thank you! Please keep us in mind whenever you do need CI.

We deploy the pipeline as a kubernetes job, once the build completes and posts logs/artifacts (apk) -- the job is archived and pods are evicted. So yes, starts from the beginning.

hehe - actually I am an Android dev primarily and I thought that starting a project without CI sucks way more. So I built this for myself and was happy paying $7/mo for not having to spend weeks+$$$ on setting one up with current solutions.

Spot instances do take upto ~2 mins to come up so probably a turbo add-on that devs will feel happy paying for or please feel free to suggest.

The goal of DevOps is to get code as developed to testing, staging, production. The deeper objective should be transfer of context- what is being deployed? do we know how? does it work as tested? and the who. As much DRY to reduce surprises and increase precision all through dev to deploy cycle.

Some of the best open source projects have CI included- thats the right approach to DevOps -- its not an alien, bolt-on after the fact practice, its code that takes care of code.

I live in Palo Alto and whenever I have to take a meeting in San Francisco, weather permitting, I hop on my bike and get up there.

Distinct advantages are not getting stuck on 101 especially on the 3rd street exit and easy parking -- just sneak between two cars. Time permitting, therapeutic to return by 280 or Skyline :)

One of the things taught in Motorcycle Safety Foundation (MSF) course is SIPDE.

Scan Identify Predict Decide Execute.

On a motorcycle, you have to keep absorbing data on the road, traffic conditions, cellphone drivers et al and always know what you are going to do - brake, slow down or zoom past.

Startups or rather any project is sort of like that. Inform yourself, decide and execute. Anything else is certain death.

This is a late response, however, to Stallman's credit he acted on his convictions of free software, invented GPL, gave away gcc, bash, emacs, libc, binutils, hurd and hundreds other pieces that enabled a kid in Finland to cook Linux. Stallman's core is exposed which cannot be said about the man who estranged his own daughter (and he did rectify it after two years of denial) and maintained secrecy around all aspects of his life and work.

Richard Stallman and Steve Jobs is the same personality. Stallman's belief is around intellectual expression as free software and Jobs' was design for culture. In the pursuit of their ideals, both have demonstrated similar zeal and reputation for offending people. We overlook Steve Jobs' quirks because we cherish the beautiful products from Cupertino and we seek to absorb that into our own process. As a culture, very few actually care for emacs or gcc. In an alternate universe, Stallman's Lisp-ness would be worshipped and aesthetics would be relegated to vanity.

I was about to post this very link! It takes upwards of 1 year to get stable and rewriting at that point without considering refactoring and/or creative solutions is cumulative team/company failure.