OutsmartDan

This may be too ambitious- throwing away control over code, editors, infrastructure, and having a sub-par offline experience seems like a dangerous move.

After watching both videos, Dark just looks like a more managed version of AWS Lambda, with a fancy proprietary editor.

Paw is fantastic- just missing GraphQL support to be even more fantastic.

TLDR: DEHP disrupts testosterone leading to lower sperm quality.

DEHP can be found in carpets, plastic toys for children, and dog toys. Humans are also exposed by eating microwaved food stored in plastic containers.

Stay away from microwaved food. Keep dogs away from plastic toys.

This is great. Not gonna lie though, took me like 3 minutes to find the Download button.

Would love to see better separation on the page between "Bad" and "Good" examples. While a good read, it's difficult to quickly distinguish between the two.

For example: https://github.com/airbnb/javascript

Likewise. Sometimes it doesn't make sense to stitch graphs together. We have a gateway that proxies different services and exposes their graphs individually.

Just out of curiosity, how much does this all cost?

Some hard lesson's i've realized while working in "professional" environments:

1. You must earn respect before you trash the system, no matter how shitty their code is or lack of tests. It's usually best to start by "doing your job"- whether that's issues assigned to you or bug fixes; you are at the bottom of the totem pole right now. Once you're "respected", implementing better solutions will be a lot easier.

2. Excuses for why shitty code is in production are probably legitimate excuses; a company that makes profit on a SaaS product needs to launch and iterate quickly. Product managers/sales/marketing do not care about your unit tests. Your users also don't care about your unit tests. Unfortunately this is a dilemma that's hard to swallow, because when things break, it comes back around.

You have to realize a team that's been there before you has done things in certain ways for certain reasons- whether that's good or bad, you must adapt to it before you go king kong on their shit.

Or you can just start your own company and make your own rules.

Good idea but in terms of performance, the markdown processing is super slow- making it very inefficient and not practical for everyday use.

http://cl.ly/0y2e162s2Z3K

VS comparing to a product such as Bear:

http://cl.ly/371S1q241Q3G

After browsing the website on said iPhone, I still don’t know what your product is, looks like, or does. There’s no screenshots besides the videos but I’d rather not watch videos to learn about something.

In terms of the article, pretty graphs and good explanation at first but extremely flawed at running the actual test against these technologies. Wouldn't recommend.

So amazing

Agree. The Apple logo eco-design is the worst thing I've seen since iOS 11.

True; though the life cycles on update seemed much more frequent on Gmail vs ST3.

Amazing, I don't think i've ever used "beta" products for so long. Glad it's finally official!

I just broke your Vue website.

http://cl.ly/2I2r2S2v171T

Just like any democracy, things were voted on, people didn't like the outcome, so now the output is to rebel.

The system doesn't work if you don't respect the system.

Amazing work!

That's why you need product owners/managers to cover the business logic and design a system that incorporates it. There needs to be tiers of coordinations to make sure a system is built to spec. TDD plays a big part in rebuilding legacy codebases.

Correct- rewrites should be done in tandem with maintaining legacy systems until the new system is finished.

There should be some sort of overlap before completely sunsetting the old system.

Software is only as good as the people that write it. In an ideal world, you'll have a team that specializes in this sort of things, can understand the business needs, and get it done.

There are always risks with every action taken. You can't be scared to take a big risk for a bigger payout versus sucking it up and doing things the way they've been done for 15 years.

Big bang rewrites are needed in order to move forward faster.

A huge issue with sticking to an old codebase for such a long time is that it gets older and older. You get new talent that doesn't want to manage it and leave, so you're stuck with the same old people that implemented the codebase in the first place. Sure they're smart, knowledgable people in the year 2000, but think of how fast technology changes. Change, adapt, or die.

With some small research, it looks like there is some bits and pieces around;

https://github.com/chendo/sense-api.cr https://www.chameth.com/2016/04/10/sense-api/

Is it possible for you to throw up the contents of ApiService in a gist somewhere?

Best part is the hamburger menu on desktop. Real cool

don't burn bridges, bro.

Hi Philip, does your app build really take 20 minutes?

Hope they finally fix weather.com.