ikhare

We just have to keep calling it out. Lazy thinking has always been an issue, but at least it could be coachable.

A long time ago Google used to have a program called "bureaucracy busters," where submissions were reviewed by the CFO to find internal barriers to getting things done.

On the topic of calculators. I discovered Figr[1] on HN a while ago, and it really helps when doing one off multi variable thing, like helping a customer estimate their bill etc.

Kudos on building this. I occasionally search for these on Google and am always disappointed by the mess. Bookmarked.

[1] https://www.figr.app/

Nice project! Very polished. It reminds me of a prototype I built a couple years ago: https://github.com/ikhare/just-speak

Awesome to see these ideas turn into real products. Congrats.

I switched back to Pixel after two years of using an iPhone recently. It’s got a lot better phone and text spam detection. I get 5-10 spam calls and texts a day. The iPhone got unusable.

Thanks for the kind words. Feel free to share any feedback in the discord community!

You can use http directly for your functions [1]. Or you can create custom http actions [2]. We encourage websocket usage because it allows for reactivity and UI consistency and it plays nicely with reactive frontend frameworks like React etc.

[1] https://docs.convex.dev/http-api/#functions-api [2] https://docs.convex.dev/functions/http-actions

Back when I took compilers in college we wrote a compiler for Oberon. I couldn’t quite find my original class site, but this one seems roughly right (from a few years before I took the class): https://cseweb.ucsd.edu/~wgg/CSE131B/

It was a great teaching language.

When I first learned about isolation levels in databases I was shocked that databases could “lie” to me. I think like most devs focused on the product end I just expected databases to be a magical black box that worked perfectly. Which I assumed was just the strictest definition of serializability without really thinking about it.

After watching some of Andy Pavlo’s lectures[1] it all just dawned on me: Databases are just like any other piece of code you write and have to think about all the tradeoffs with algorithms and book keeping to keep things efficient and providing the guarantees you want.

I highly recommend that lecture series.

Shameless plug: the reason I watched those lectures was to understand the internals of DBs better because I started working at Convex. Where we try to make sure things like this is something an app developer doesn’t have to worry about. Though we do mention it in our docs[2] for the curious.

[1] https://www.youtube.com/watch?v=LWS8LEQAUVc&list=PLSE8ODhjZX... [2] https://docs.convex.dev/database/advanced/occ

Thanks for the reminder! I’ve been listening to this since sometime in the late 90s early 2000s. I spent so much time focused because of this, and it became a formative part of my music taste in high school.

I am a downtempo person so classic Groove Salad kept me going.

Hey no problem! We’re all trying to make this space better. Thanks for all the work you put into it too!

(I work at Convex)

I was the one of the original TLs of Google Photos, specifically on Android and eventually managed all of the frontend teams for Google Photos. So I hope it's not a stretch to say that I have deep empathy for frontend problems. We also have great frontend oriented folks on the team.

I also worked with jamwt at a previous company (Bump) doing frontend work. When we worked together, I remember the acceleration of our ability to execute when the backend people were closely involved in our data syncing problems. Heck jamwt and team even wrote most of the initial client syncing code. When backend and frontend folks work closely together to solve data problems you can make magical things happen. In the end we're just product oriented engineers trying to ship delightful experiences.

The Trash option available while signed in vs. Deleting locally mean different things. The first is moving the file to trash where it can be recovered for a little while, the second is blowing the file away from your file system. We wanted to keep these features distinct and clear.

Though I can understand for those using the app entirely signed out this can be frustrating. Thanks for the feedback. I do hope you sign in however, there are a lot of things available to you signed in that simply don't exist in the signed out view.

You are using the device folders view. Try the default photos view.

You just filed it ;-) We'll fix this soon for local photos.

Chrome has a concept of multiple users in it's preferences. When you turn it on then you can pick an icon per account and it shows up on the top right of the browser window. To switch to a different user click on that and switch to a different user. Each user can sign into a different google account.

Each user has it's own cookies, chrome extensions etc. Keeps work and personal accounts very separate.

I'd love to hear more. I've been through this more than once and don't have a good answer on how to get out.

People here have given great motivating responses. But In don't think anyone has answered the whether it would be hard to get an job again after a big gap if you decide to get one again. It seems like you want to continue coding in some form, so really there will be no gap of experience in your resume.

If anything finding people who have built products themselves and put them out there is great to see and are hugely valuable to an enlightened organization. Whenever I interview people this is always a fun part of the conversation. I find that those people are very likely to be tuned to building great products and are the kind of people I want to work with.

I can easily imagine what some of the dependency management issues could be, but I'd love to hear your thoughts on the following two options:

In the Java world there is a concept of a .war file which packages everything up so it's easy to deploy on app servers that handle it like: Tomcat or Jetty.

Also what's wrong with giving out a prebuilt virtual image for a single server install? Github enterprise does this.

This whole situation makes me think: is there a static analysis tool for excel? Seems like missing a few rows in an excel calculation could be flagable.

Seems like the author has only worked with iOS.

On Android push notifications are done through GCM (Google Cloud Messaging), when it's sent your application gets a callback (Intent). So it is up to the application to decide what to do with it, whether it is to show a notification or do something else entirely. So on Android you have a pretty good idea that the the user is actually getting a notification. Jelly Bean and up you can also do very rich notifications with images and actions built right into it.

On iOS when a remote push notification is received there is no indication sent to the application at all. The only way the application knows something has happened is if the user actually opens the notification.

I haven't programmed on windows phone, so I am not sure how much an app developer knows that a user is viewing a live tile or not. Maybe someone who's built one can chime in.

Overall it seems to me, that what the author is describing is Android, where the app developer has at least some feedback as to whether a user is seeing the notification (albeit not an exact: user has seen x notif).

Edit: Wording

and mine: http://nightweb.net/#type=user&userhash=prn3nvnrikl7ewpf...

Mine too: http://nightweb.net/#type=user&userhash=prn3nvnrikl7ewpf...

We use C quite heavily at Bump in our mobile apps. With our recent app Flock, we wrote nearly all non UI logic in C to be shared between iOS and Android. This made moving to a new platform much faster and easier than in times past. A lot of this core code is also used on the server to manage incoming connections from the clients as well.

Aside from the ability to share code, it also makes sure that we are not using anymore memory than we really need. Avoiding unnecessary GCs is an important concern in writing performant Android Apps. Having the core C layer only hold on to as little memory as possible is a huge win.

On a less objective note: When I left undergrad I thought I'd never write C again, but it was such a pleasure working with it again. Knowing (almost) exactly what operations your code is doing is quite liberating after working with so many other higher level languages and frameworks.

Fun fact: early versions of d3 came out of a project in this class from 2009. I was in this class and d3 (Not called that then) was one of the more impressive projects that came out there. Here's a link to Mike's project description:

https://graphics.stanford.edu/wikis/cs448b-09-winter/FP-Bost...

Physical bumping is important. We use the sensor data on the devices bumping at the time of bump to determine if two devices match.