let_var

Nice work @ernaem! It’s pretty and has some freshness to it. I browsed it on my iPhone, so didn’t do any deep dive.

Would you consider sharing anything from the stack, data and tech side?

Great work team enhance.dev, web components is the way to go.

I read a lot of strong opinions about the use of NPM when the framework boasts “No JavaScript”. Probably it’s a fair point. But I’d still like to see more enhance and Lit-like frameworks - yes I said framework, cause it takes you one step closer to the native browser.

None.

And my reasoning could be a strange one. My knowledge of mathematics (esp. probability and statistics) and algorithms, and my memory used to be pretty sharp. I could retain a lot of information, and perform fast manual calculations using log book. All that started to deteriorate when I started relying on search engines for everything. No doubt it was convenient, but I lost touch with foundational concepts. My memory and speed are not what they used to be.

So as long as I can. I’m going to keep co-pilots and ai/tools at bay.

Something else to think critically - 1. Open space has a greater chance to skew your peer evaluations. Social aspects ends up being the numero uno factor. With cubicles you know others thru their work. This is not entirely black and white, but I strongly believe there's some truth to it. 2. Deep thinking is difficult if not impossible in open spaces.

I was fortunate enough to start my career in cubicle in a research lab. That was fantastic! I had a dip when I was introduced to open space. Got lucky again with another company that had cubicles. For the last 5 years, it has been open space mayhem.

Michael - firstly, kudos for sticking to your solo dev plans. Hiccups are part and parcel of the game. I like your Is This Keto app. And second, keep at it!

Mapping is hard, really hard. Now I'm finding it first hand. So kudos to the team for persisting with it and delivering a better result.

Amazon is still good for comparison and reviews, sort of. Hard time filtering the real ones from paid ones. It's no fun buying top line electronics from a 1D scrolling list.

Ah miss that Palo Alto Fry's. 2011 or early 2012 was the time when I got my TV and bunch of other stuffs from Fry's. Not a big TV buff, so the old one still runs well.

+1 to Best Buy as well, they always surprise me with great customer experience.

Cord cutter since 2009 and social media quitter since 2015 here. LinkedIn and WhatsApp are sufficient to maintain professional network and personal ties. HN is interesting when you get to read some obscure articles.

First-call declarative UI support is amazing!

Super. Declarative UI has been one of the differentiator between native UI development vs say React on the browser. ComponentKit and co. are there but having something official from Apple makes it 10x better!

Edit: Also, thank you!

Little late to the party. I am going second the sentiment that is presented here. Startup makes sense for founding members with double digit equity. For everything else go join a BigCo, any BigMediumCo.

Two thumbs up for this "...companies that don’t aspire to grow at all costs to reach a $1B valuation..." If someone is raising capital, not sure if that'd be same as bootstrapping. Access to mentors-cum-support group who has some stake in the game makes them valuable.

IMO it's a misleading premise to begin with "Start with a website, not a mobile". One should try to stay true to target audience. If your product justifies "Mobile first" approach, mobile app is what one should start with.

Few years ago, I started with a website prototype with an end goal of porting UI elements and business logic to mobile. With some exception of reusing business logic, most UI elements required redo.

This is quite brilliant. If quality of tech remains good, few interesting results can be expected in years to come.

There are few challenges for the founder(s) - 1. splitting time (and focus) between university duties and startup work will be tough. And 2. if a startup fail to get traction within 1.5-2 years, and its founders are unable to secure GC/extension, you can expect further dilution of focus.

Really good resource.

Good for adopting the culture of remote working and making it work. But not sure what they'll do if I joined them while living in a big tech hub and then move to smaller cities. Are they going to enforce a pay cut? But nothing has changed, I was remote then, and I am remote now.

It should be based on the value that the talent brings.

Code reviews have been both a useful medium to share new learnings among team members that actually makes the code elegant or perform better, and an endless threads about conventions and nitpicking.

I think it makes sense to set premise or template for a good peer reviewing exercise. New team members should be educated about these guidelines.

I support a point-based H1B and Green Card system allowing individuals to apply for their own green card. Salary should take precedence over lottery any day. Someone mentioned about making it industry specific, but that's just opening a loophole. Something like this might improve domestic salaries across sectors.

This exactly. He's clear about not looking at his project thru the lenses of startup. It's nice recipe for a side-project.

#1 - very good point. Not having a cultural relationship with a Mac/iPod makes it difficult to appreciate iPhones and their non-functional aspects.

I deleted Facebook before deleting Facebook was cool. I'm sure there are few good benefits but drawbacks and ads dwarf them all.

One more thing - the last time when I met my school buddies back in my hometown, we had more things to share, discuss and appreciate. It really felt good and real. Previously this experience was diluted by constant barrage of FB feed, there was nothing new to share or discuss.

I have had good experience (on multiple occasions) when buying consumer electronic from the Best Buy. They do price matching, you get to experience the product, and the customer rep was really helpful.

I can't say the same about the snob at the Apple Store.

Agreed. Yesterday, I replied back with similar sentiments. I was immediately down voted. I second that theory of yours where all the risk seems rational when you are one of the founders.

Here's something from the point of view of a Swift engineer who had multiple conversations with experienced Objective-C developers.

1st. Don't look at it from the language perspective. Look at it from the point of view of the platform and dozens of SDKs that comes with it. It's lot easier to use those SDKs in an environment you are already comfortable with.

2nd. There's no financial incentive for an existing app to be ported to Swift or train experienced developers to this new language. In my manager's own words, "...you have to give me a business justification to port our app to Swift..."

3rd. I'm afraid to say that incredibly high inertia about learning and embracing a new language, and letting go of your stronghold.

Swift is an amazing language, and it's quite easy for you to switch between Swift and other C-style language e.g. ECMAScript. Objective-C has somewhat obfuscating syntax that makes it intimidating for beginners.