mephitix

Mark Erikson (dev on React) explains this very well: http://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet/.

"If you're only using Redux to avoid passing down props, context could replace Redux - but then you probably didn't need Redux in the first place. Context also doesn't give you anything like the Redux DevTools, the ability to trace your state updates, middleware to add centralized application logic, and other powerful capabilities that Redux enables."

I actually don't want any of those things, not even markdown support.

The site IMO does what it needs to very well and I value the minimalism a lot. Would hate to see it cluttered with extra chrome, images, karma, summaries. And instead of social login try using a password manager.

It's a good point about whether they should be on public roads. At the same time, it's crucial to their success that they are and experience outlier situations.

The hope is that by experiencing an outlier and making a mistake, the algorithms will be able to adapt to ensure that mistake never happens again. Humans today don't have this kind of networked, massively parallel mind to avoid the mistakes of others. Again, that's the hope.

I think it'll be a long time before learning algorithms will take over the wheel completely - but I think we are at or near a time when these systems can and should let us know of low confidence, insufficient data to make a decision, or equal confidence of multiple outcomes. A networked AI should be able to tell us far enough in advance (e.g. while driving) for humans to step in and make the final call, based on their own rationalization, empathy, etc.

Autopilot marketing is bad and Elon deserves a lot of the blame, but do we still expect to be able to trust these systems enough to not put hands on the wheel and look at the road?

IMO we are still in the very early stages of this work in the industry. Personally I think bugs and flaws in systems like this are normal at this stage. I would expect the same with GM Super Cruise and I wouldn't trust that either to let go of the steering wheel.

If you're worried about FB analyzing/selling your data then "deleting" does nothing. It effectively just sets a boolean flag on a record in a database which is more like 'hiding'.

It may not appear anymore in the frontend but you can be pretty sure it's still being used by FB. Now that may change after GDPR but who knows...

If you've ever used Total Commander or even Windows 7+ native file explorer it's very hard to go back to or use Finder. Keyboard shortcuts, tokenizing/detokenizing file paths, opening in terminal, searching within files, search for duplicate files, bulk rename, plugins, and more.

Whenever I have a new Mac I spend a couple minutes customizing Finder: adding things like the Path button, showing the Path bar, showing the Status bar, etc. I get that it's supposed to be simple but it's surprising to me that such basic things aren't in the starting configuration.

I do love the spacebar preview though :)

>> I've never worked at a company that takes data protection as seriously as FB, or has the caliber of people protecting data.

I don't doubt this, but I think Facebook has a flawed culture that allows and encourages employees to use this mindset as a rationalization for unethical things like:

- run emotional experiments on news feeds

- silently logging all Android users' calls and texts

- allow proliferation of fake news

- allow buying of propaganda ads from state actors

- zero safeguarding of data to ensure it wasn't sold by app creators/devs.

Data is central to facebook's business model and the ability to collect, analyze, and sell lots of data (a natural result of the 'big data' hype) became an infatuation for facebook employees.

The Boz memo supports my point - except he cleverly hides it as 'grow at all costs' rather than the underlying 'collect/analyze/sell data at all costs'.

Here's a radical thought - maybe Extreme Programming (I still think this is a genius marketing name :) works for some people and doesn't work for others?

After trying so many of these methodologies I've come to realize that people just work differently. It's self-defeating to try to push Extreme Programming or whatever on someone who prefers and is efficient at working alone.

Maybe adopt some of Scrum/XP/whatever that can be adopted at a high-level, but trying to push it through a team composed of people with different personalities and different ways of working just defeats the entire purpose.

I tried and eventually got tired of Jira, Trello, Team Foundation Server, and Pivotal Tracker.

The one tool that I've been loving for the past year is http://clubhouse.io. Such a well-designed product and extremely flexible (I think it could fit most teams' requirements around Agile/Kanban/etc.)

The only two experiences I had with Pivotal were with RabbitMQ (a very well designed product) and with Pivotal Tracker - I tried it about a year ago. I felt like I was fighting the software; they were extremely stubborn about adhering to Scrum 'best practices' that may not work in practice.

Pivotal also owns RabbitMQ - as of 2013.

It is really time consuming. But somehow more approachable for a non-artist like myself. I've tried freehand drawing but I wasn't happy with the results... I need more knowledge and more practice.

Since you're on the subject of animation another amazing tool, specifically for pixel art, is asesprite. https://aseprite.org

Among many other features it has onion skinning, play controls per layer, and looping over custom-labeled set of frames.

I used it for my first game last year and it made everything so much more fun :)

Congrats on the release.

One point about the docs - you can cut down on the verbosity of those examples by using arrow functions (instead of .bind) and class properties instead of state initialization in constructors.

CSS Grid really helped me understand/wrangle z-index and stacking contexts. For example, within a grid you can use grid-row/grid-column to position an overlay over a grid item. The z-index will be scoped to that stacking context.

Modular CSS I think is a huge step forward - I totally agree that global scope is killer. As much as people love to hate on CSS-in-JS, I enjoy using styled-components a lot. I've noticed since using it I've been composing CSS instead of inheriting or overriding styles.

>> Since Tesla employees are unhappy, a lot of them are demonstrating flaws with Tesla's manufacturing process, potentially in an attempt to strongarm their bosses into getting better pay or unionization prospects

This seems like a pretty big/dangerous jump to make with little-to-no evidence.

>> In any case, Elon Musk's 20,000 Model 3 manufactured per month target for late 2017 is incredibly late (See: https://twitter.com/elonmusk/status/881757617416056832). A lot of Tesla bulls don't seem to care however and continue to throw money at the company.

I really hate that Musk publicly underestimates the amount of work and deadlines in this process. It's especially annoying for me because I've worked for people who publicly underestimate and it put way more ridiculous work on me and my coworkers.

That said, I also hate this "fraud-boy" FUD. I think Tesla could eventually pull this off. The ramp will obviously be slower than what Musk expects. I, like many bears, take what Elon says with a grain of salt. But cars are rolling off the production line. At this point, the Model 3 is now the best-selling EV in the US. (https://www.bloomberg.com/graphics/2018-tesla-tracker/). Tesla has proven itself with the Model S. People in general love the cars. Tesla will get there, and I think that's why bulls are holding.

I think nowadays they use Microsoft PowerBI for dashboards/reporting

Yeah this is weird. Maybe they meant "React Native-like reusable components". Flutter widgets take inspiration from React Native:

"Flutter widgets are built using a modern reactive-style framework which takes inspiration from React Native. " - https://flutter.io/flutter-for-react-native/#built-in-widget...

What's the use case for this? You can pretty easily do this already with React + styled-components + CSS grid and still keep it pretty DRY.

Would help if you added more/different examples to show what else it can do beyond that first example.

Building a game is a probably the best way to learn and apply state machines since a lot of it is all about how to manage state effectively since there are so many pieces of state and interactions between them.

Also, since Bob is too humble to say it - http://gameprogrammingpatterns.com is an amazing architecture resource for programmers in all disciplines, not just gamedevs.

He's got another book called http://craftinginterpreters.com/ that I've been eager to check out.

I learned about state machines, along with push-down automata and others but these were in a formal automata class where we learned things like the Church-Turing thesis and other similar theory.

So there's learning about state machines in that context and then there's learning about state machines by actually building them in complex pieces of software, or replacing spaghetti code with FSMs. That's when I personally realized how valuable they are.

That is something I never learned in school - and something I learned throughout a career of experimenting, making mistakes, reading from books like http://gameprogrammingpatterns.com, learning from peers, and reading articles like this.

They need to hit their immediate goal of 2,500/week by end of Q1 - see the last chart on that page. They didn't move this goal in the Q4 earnings call, which was surprising - but if this tracker is accurate the production curve seems to be on track.

They are also planning to bring in a fully automated assembly line being shipped from Europe, in March. Assuming nothing goes wrong there it is supposed to accelerate production even more.

Nah we need them for cross platform. But yes, learn Swift and Kotlin anyway!

For me, personally:

- One aggregated portfolio position over time would be enough for me i think

- Once per day is fine

- Given crypto volatility, 1 year would work.

Maybe a combo of image caching and time series caching would make this economical. Image caching for aggregated portfolio position - and if you're generating the image everyday (or eventually more frequently) for many portfolios then you could calculate and cache the individual coin time series and use that cache to aggregate and generate many charts.

Nice! A single server-generated multi-series chart would be nice but if it takes away from the simplicity then that's fine. If you haven't already seen it you can get volume/price/marketcap between a start/end date. https://graphs2.coinmarketcap.com/currencies/bitcoin/1487234...

>> Also note that CSS Grid does not deprecate Flexbox

I see this said a lot but in my experience (a) all the cases where I use flexbox eventually get replaced with grid with about the same verbosity but more flexibility and (b) I've noticed subtle bugs when using flexbox with grid that manifest only on some platforms (e.g. On iOS but not on Android, only on some versions, etc).

"Games can be compiled to iOS, Android and native apps via 3rd party tools"

Gonna need some explanation here... does it spit out native code? Where are the tools? And since it's HTML5 why can't I just run the thing in a native web view? Are there perf issues?

Thanks for sharing this.. when I was around 4 years old my parents, a relative, and I were in and out of a hospital.

We were going through a really tough time dealing with a life-altering diagnosis of one of my siblings. A lot of anger and sadness, especially from my parents.

But - the only thing I actually remember from the hospital was playing Galaga in the hospital game room with my relative. Since I was 4 years old, I always wondered (a) why it is such a vivid memory and (b) why I can't remember my family or myself being upset. Quite surreal to see that this specific scenario has been studied.

I've never really understood why people consider aging to be a problem. I'm not sure if we as a civilization have been able to deal with overpopulation, at least looking at currently-overpopulated areas.

Personally, I would rather have an optimal life - one where I don't have any diseases or ailments, so I can live life to the fullest, all the way up until death. So IMO, currently incurable or intractable things like cancer, Alzheimers, Parkinson's, dementia, are more important.

If fixing 'aging' can fix these issues, or if an aging fix is a side-effect of these issues (please enlighten me since I know nothing about aging research) then I would be fine with that - but would still be worried about overpopulation, whether it's the rich or both the rich and poor.

I'm pretty skeptical of design work that doesn't involve close dev interaction/iteration.

And especially for mobile apps there are things that are outside of just 'design' and I feel they would introduce a lot of variability in the amount of work involved per-project. How does a flat fee take that into account? Things like:

- responsive design: scaling to different phone/tablet sizes

- aligning to Android/iOS conventions (e.g. should not allow swipe-from-bottom on iOS)

- animations

- sound

- theming

Does this all come with every project as part of the fee for, example, the 'Startup' package? If none of this comes with any of the packages then I think the prices for each package should definitely be lower.

I like the idea though - the unlimited revisions part was pleasantly surprising. I'm not sure how that would scale for the business but it sounds nice :)