877 karma · joined April 23, 2017
Long after I am dead, ended this bitter journey, Many another whose heart holds no light, Shall your solemn sweetness, hush, awe, and comfort, O my companions, Wind, Waters, Stars, and Night.
https://www.sketchapp.com/support/requirements/other-platfor...
Apparently our brains can only decode ~1.5 conversations at a time, and noise that is distracting you, whether from TV commercials or others speaking, takes up valuable bandwidth.
I also dislike this gamification of subscriptions
You don't _need_ to share your location with Google Maps in order to utilize it, unless you want turn-by-turn directions from your current location.
One example would be the original main tagline: "The programming language that empowers _everyone_ to become a systems programmer"
Which is now: "Empowering everyone to build reliable and efficient software."
Additionally, Amazon receives several seconds of audio _before_ the trigger word was used
Edit: I can't find a source for this, but IIRC this was part of the initial Echo roll out, and one of the reasons I decided not to purchase. Perhaps Amazon has changed this so now it only listens and sends data after the wakeword.
It does appear to have been updated: "When you use the wake word, the audio stream includes a fraction of a second of audio before the wake word, and closes once your request has been processed."[0]
[0]: https://www.amazon.com/gp/help/customer/display.html?nodeId=...
It seems like once we give any data to any company/entity/organization in this age that it will likely be around, somewhere, forever :(
> They do not apply to life, long‐term care, or disability insurance.
> Be not addicted to wine.
> Hate no one.
> Be in dread of hell.
> Fear the Day of Judgment.
> Attribute to God, and not to self, whatever good you see in yourself.
Wow! I had no idea this was part of the original code of conduct
I agree with you, but many job applications often have ridiculous hoops that you must jump through, and these often have a negative impact if you do not adhere to the predefined criteria.
Companies are often looking for very specific skills and talent, but many look beyond the exact code that you write and value additional things like attitude and communication skills.
I ask this as someone who sincerely sympathizes with the frustration of being dragged through many modern applications/interviews: If you were a hiring manager, would you want to hire someone who clearly cheated on or didn't adhere directly to your application process?
I am in a similar position, and have no social media. To echo some of your points, when I first left FB there were some events that I missed out on that I would consider high importance to me. At first, I was shocked, I tried to hide it with the "real friends with mail me!" excuse, but I was still "disappointed" (for lack of a better word)
I'm lucky enough where a observant extrovert in my social circle noticed my preferences, and now they email/text me about most events. I try to keep in touch with the rest of my friends over phone, and people i'm not super close with over email. I don't do the best job, but I don't miss FB
Much of what you should do depends on your specific situation, company type, and if you anticipate other devs eventually joining you.
The specific stack and container technologies that you choose for the architecture will vary greatly depending upon your scenario, but I will say that picking something stable, with a large community that other devs are familiar with will make your life easier in the long run.
Since you are currently alone, something that a solo developer can be quickly productive in (like Rails + React) would be ideal!
For workflow, you need some sort of beta/staging environment so that code isn't going directly to production. This is simple to setup and has big pay offs: you can use it to showcase new features to stakeholders and gathering feedback before "pushing to production", as well as increasing stability. In the future with other devs you could scale this to a full pipeline with auto CD/CI etc
I would also recommend trying to keep fairly decent documentation. If other devs join you in the future, they will greatly appreciate this. If you leave this job and they hire another contractor or dev, they (and hopefully your company) will appreciate this.
If you have to manage a lot of cloud servers or network architecture, I would highly recommend taking the "Infrastructure as code" approach. It's pretty simple to get up and running on Digital Ocean with just a few lines of Terraform, and the benefits to devops are huge
Best of luck!