We setup a solar on in our home in Pakistan back in 2023. Our primary driver was cost since it was getting extremely expensive during summers when the ACs were on. We expected to get the return in 4 years but inflation went so high in subsequent years that it took just 2 years.
Readit Newsneebz commented on Page is under construction: A love letter to the personal website localghost.dev/blog/this-... · Posted by u/spzb
I remember back in the summer of 1996 in Pakistan our household was one of the first few to have to internet.
At that time angelfire.com used to give free webspace. My brother got hold of a pirated version of CorelDraw and setup a fan website of his favorite rock band Junoon, which incidentally is still online: https://www.angelfire.com/pa/JUNOON
And then when my brother met the band at a concert and they actually recognized him due to the website. I guess first time we realized how impactful internet is going to be.
neebz commented on I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA · Posted by u/proberts
If these employees manage other employees now and will manage other employees in the U.S., then the odds are high actually. Conversely, if these employees aren't managing any employees and won't be managing any employees in the U.S., then, unless their work is highly complex and technical, the odds are low. Does the acquiring company also own the company abroad?
yup - some documentation/legal work remains but they should be able own the company abroad as a subsidiary soon.
how would you suggest we should pursue this once all the paperwork is done? hire an immigration lawyer? any recommendations? we are non-YC.
neebz commented on I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA · Posted by u/proberts
How are the odds for bringing your remote employees to US using the L1 visa? They've worked for us for more than 5 years in management role.
Also the startup got acquired sometime ago, does that impact the L1 application?
neebz commented on Introduction to the Theory of Programming Languages (1991) bertrandmeyer.com/2022/09... · Posted by u/ingve
Bertrand was one of my favorite people in the software field. I really wanted to do a Phd under his supervision.
Two things to think about:
1. Maybe steady-state “feeling happiness” isn’t a good goal? Like, so what if you “feel happy?” If that’s all you want, opiates are widely available.
Maybe a better set of goals would be “peak satisfaction” combined with tangible external outcomes that you consider worthwhile.
2. The accomplishments you have listed are mostly about yourself. They feel empty now because you have basically got yourself under control. What can you improve in the world outside yourself? Can you improve the company where you work? Or your family in some tangible way?
I’ll give you one small example:
My cousin and his wife had failed two expensive rounds of IVF already, and they are comfortable but not in high paying jobs. They were struggling to afford another round. They had asked the family for help with a go fund me but didn’t come close to what was needed.
I had just gotten a bonus, and the total amount needed (several $K) was an amount I could well afford so I just sent it to them. I didn’t make it a big deal, and made sure they understood they owe me nothing.
To this day, I get a warm glow of satisfaction when I see my niece or they send pictures.
Way more than what I get from checking my bank account or reflecting on other “self” accomplishments.
awesome. thanks for sharing.
neebz commented on The Code Review Pyramid morling.dev/blog/the-code... · Posted by u/adrianomartins
previous discussion: https://news.ycombinator.com/item?id=30674159
We're currently in the transition, any chance you have some insights to help ease the mentality shift as the team transitions to this vs bi-weekly/monthly deployments.
Some feedback from our transition:
- automated tests are the pre-req of feature flags. kindly make sure that you have good test coverage. otherwise the team loses confidence in code & feature flags which defeats the whole purpose.
- as part of code review guidelines we added one major feedback item: can this PR be merged right now? why not? what can be done to merge it right away? as part of a cultural shift the code reviewers played a critical role. they kept engineers on the their toes at all times.
- feature flags should be part of user stories. in many cases you can't expect engineers to add a feature flag at the end of implementation. the product team should know this at the time of writing user stories.
- as mentioned in many other comments try to clean up code after feature flags become stale. otherwise the code (and respective automated test cases) becomes a huge mess.
- in our case we decided the granularity of feature flags (per-user, per-customer, per-region, per-server etc). we started with per-customer and went from there. worked out fine for us.
- feature flags have major two benefits: "release often, release small" & "decouple releases with big launches". please make sure to instill this in your team every day. mindset changes takes repetition and emphasis. if at anytime you feel that you are not achieving any of these please take a step back and figure out why.
Yes. Feature flags changed the mindset of my whole team. I absolutely love the fact that it pushes the whole team towards release-small-release-often mentality. It's a technical solution with many benefits but I love the cultural impact the most.
It definitely makes me faster but it's consistent prompt->code-review->prompt->code-review->scratch->prompt-code->review cycle which just requires extreme focus.