I’ve been working on a side project that aims to provide a really simple UX to spin up full-stack web apps with CI and scalable infra by default. The idea is that you would simply enter a domain name you want to purchase and then the tool would do the following:
1. Purchase the domain name using AWS Route53 (perhaps you’d need to setup an IAM role for the website to access your pre existing AWS acct)
2. Setup frontend, API, and CDK infra repos. All in TypeScript.
3. Frontend react, backend Api gateway backed by lambda functions. Have a graphql endpoint that talks to an Amazon auroradb. CI for backend and frontend is defined by a CDK package that is also deployed to the AWS account that also sets up the networking and database for you.
4. Have a basic layer of application code for setting up user authentication and storing user data in the aurora db.
Basically my idea is it kinda sucks that everyone has to do all of this setup yourself if you want to start a new project. Or you have to rely on no-code tools like Squarespace etc which may not be what most engineers are looking for. Having something that can go from simply entering the domain name you want to scaffolding out a fully functional full stack web app with CI and serverless infra defined by code that can scale from day 1 seems both incredibly useful and doable.
Neat, I am working on something similar with almost all the same tech you mentioned (CDK, R53, TS, APIGW+Lambda), and a Dockerized dev env with everything set up. It's meant to be a boilerplate I copy for new side projects. DM me on twitter (same username) if you'd like to compare notes or collaborate.
Hey sourdesi, this is _exactly_ my stack too, and I am also dabbling with a starter. Would also love to discuss and collaborate. Please send me an email (see profile).
I think you’ve misinterpreted the map. The yellow regions in the map are the ones that are actually undervalued relative to local incomes. SF/Bay Area is one of the few regions on the map that is yellow.
It does point out, however, that tech hubs are still struggling due to reasons other than local affordability:
1) higher cost homes are more rate sensitive
2) tech companies and their corresponding stock compensation are experiencing a downturn
3) tech companies have leaned in to remote work more than in other industries, which means employees don’t need to stay in expensive tech hubs for their career opportunities. (this is from my own understanding of the market, not the article. Also, I personally think there’s still some career networking benefits being located near a tech hub)
Side note: One of my favorite authors Michael Pollan recently published a short audiobook on the effects of caffeine, some of the history behind it, and his experience going cold turkey for a few months. Really quick and interesting 2 hour listen. It's called Caffeine.
Thought I'd share since I found out about his last book "How to Change your Mind" on HN and found it fascinating.
The lyrics are meant to be ironic since they condemn plagiarism while praising Wilde and consciously containing bits of plagiarism itself. Morrissey, the lyricist and vocalist, was well known for plagiarizing and even ripped some lines off of Oscar Wilde in a few songs.
Im trying it out right now and the Android app told me to use an identifier that starts with a '9'. I typed `notify -r <my_identifier>`. When I try running `notify` however, it gives me this:
[notify] Encountered an error: ParseError {
code: 141,
message: 'Error 112: Channel name must start with a letter: <my_identifier>' }
I have a Pebble Smartwatch and it definitely does not have 5-7 days of battery life. More like 1.5 days (2 if your lucky). Also, I do think the fact that Android wear makes so much functionality so easily accessible is a huge deal for smartwatches. You just say "Ok Google". The whole point of a smartwatch is to seamlessly integrate technology in your life. That means our interactions on them need to be quick. You can't get that if you have to poke around the Pebble watch UI for 15 seconds before getting to your app and THEN sending out the text, or checking your calendar etc.
Unlike the sibling posts, I have automatic backlight turned off and it regularly lasts a minimum of 5 days. On the fifth or sixth night, I charge it over night and I'm back at it.
With respect to "OK Google," more often than not, I find myself in places where talking to my watch would strike me as obnoxious: the office, outdoors, the subway, an elevator. Sure it's quick, but again, a button press or two strikes me as being more effective in those situations. I really would only think of using voice commands in my own home, or in the car. I guess it's all a matter of personal preference... I know exactly how the UI of the Pebble app works, and exactly what it's going to do in a certain amount of time when I press a particular button, which feels pretty seamless to me.
Lest I only say good things about Pebble, I have to mention that in a little over a year of ownership I'm on my 4th one: 3 RMAs due to persistent screen defects. This 4th one should be sent back, too, but I've yet to get around to the RMA process again. Two of the RMAs were within 1 year of purchase, and one was beyond, so my credit goes to their customer service.
You must be doing some very intensive things with your Pebble. I have the automatic backlight turned on (turn on when I shake it), and mine regularly lasts 3-5 days, even when I go running regularly, which happens to trip the automatic backlight for most of the run.
I also use it to track yards I go swimming, Runkeeper for tracking my runs, and miscellaneous things like the music app and the Swarm app.
I definitely get many days out of my Pebble (I don't bring the charger on weekend trips, etc).
I completely agree though that the Pebble is best as read-only and notify device. Interacting with it, even to change apps, is a chore. But I don't really see the point of putting a lot of interaction on a watch when, at some point, it's easier to just pull out my phone.
I have Misfit installed on my Pebble which monitors my every step during day + sleeping cycles during night, so basically using accelerometer 24/7 and I'm getting around 3-4 days of battery with that usage.
Also I'm getting notifications every few minutes (email, facebook, skype) + vibration is on.
From an Android devs perspective, I will say that the Parse Android SDK is really well made. The API allows for idiomatic, fairly concise, and consistently patterned code. It also adheres to a lot of the coding conventions that android devs are used to like callback functions for asynchronous operations. Set up is super easy too. The offline caching feature is really easy and useful.
That being said, if you have the skill set and time as a developer to be able to implement all of those features and a server/db component, I would. It may not be as robust or clean as the Parse API but hey if its your code it shouldn't be terrible to work with. If you do it yourself, then you get the added benefit of just having to pay for hosting of your server and db.
