Ask HN: Companies who adopted React Native over a year ago, do you regret it? | Hacker News
Some good discussion on Hacker News about adopting React Native. So good points against at, lots of terrible points against it, but mostly a strong :thumbsup: from those that have used it.
react  ReactNative  javascript  iOS  mobile  development  via:chriscain 
10 weeks ago
flav/php-docker-sandbox: Linux (E)nginx MySQL PHP - lemp stack sandbox
A nice Docker-based _development_ environment for PHP. The intent here is to replace a vagrant box with a docker container, but still give you the ability to tinker within that environment.
docker  development  php  via:flav  vagrant  github_repo 
11 weeks ago
iOS 11 Sucks
One of my sources at Apple recently told me the reason why things don’t seem to click the way they did in Steve Jobs’s era. It’s just a matter of scale: “We have been growing so fast so much that it is impossible to hire people that are excellent and obsessed with detail all the time.” There are so many teams and so much middle management and so much design by committee that it is impossible for them to keep the consistency they need to make not just a good OS, but the perfect OS that an obsessive Steve Jobs would have demanded back in the day.
ios  design  apple  entropy  scale  ios11 
12 weeks ago
On the Bottom Navigation Bar – Android UI Patterns – Medium
What happens when you press the back button now?

That damn back button…

This article shows how that persistent hardware button has inconsistent behavior.
design-navigation  usability  back-button  design  android  mobile 
12 weeks ago
The Problem with Saying “Don’t Bring Me Problems, Bring Me Solutions”
Require problem statements instead of complaints. Although you should want people to alert you to potential issues, they need to learn how to distinguish between raising a valid concern and simply complaining. Complaints are stated in absolutes, such as always and never, rather than in concrete facts. They lack accountability and often have villains (them) and heroes (us). And they often don’t look beyond the surface of the issue. For example, “Group Blue never hits their deadlines, and we’re always left holding the bag” is a complaint. It makes an absolute statement, identifies a villain, and doesn’t show any accountability on the part of the speaker.

Problem statements, on the other hand, provide objective facts, examine underlying factors and causes, and reveal everyone’s role in creating the problem, even the person presenting it. A problem statement for the same issue would be something like this: “In the past six months, Group Blue has missed deadlines four times, by an average of 6.5 days. In two cases we were also unprepared to meet the deadline. However, in the other two cases our group completed our part of the project on time, but we had to work weekends to integrate Blue’s late work so that it wouldn’t impact the customer.”

When the issue is presented in the form of a problem statement, it’s much easier to spot the pattern of repeated delays. Because the presenters acknowledge their part in the problem, you know they’re open to being part of solution, not just blaming others. This allows everyone to dig in deeper and identify the root cause of the issue. Perhaps Group Blue needs more resources or isn’t receiving the information they need to complete their work on time. Or maybe the way projects are scheduled fails to account for unexpected events.
team  hbr  business  management  leadership 
september 2017
Sketch Runner
Runner helps you to get around Sketch quicker by giving you an intuitive interface to supercharge your daily workflow. Stop searching through your menu & start running commands directly from your keyboard.
sketch  plugin  tools  design 
september 2017
nikitavoloboev/my-mac-os: 💻 a list of applications, alfred workflows and various tools that make my macOS experience even more amazing
a list of applications, alfred workflows and various tools that make my macOS experience even more amazing
mac  osx  macOS  apps  github_repo  tools 
september 2017
Offline Only
You must go offline to view this page.
Enable Airplane Mode.
inspiration  distraction  deep_work  cool 
august 2017
sstephenson/bats: Bash Automated Testing System
Writing tests in bash.

A good application is using `curl` to run integration tests on an HTTP endpoint, with the harness being these bash scripts.

Zach Holman has a good example here: https://zachholman.com/posts/integration-tests

A potentially simpler set up for Nutshell's Ruby+Cucumber-based HTTP API integration test suite.
github_repo  test  testing  unittesting  bash  cli  shell 
august 2017
I’m a White Man. Hear Me Out. - The New York Times
“You must understand my experience, and you can’t understand my experience.”
august 2017
Artificial Intelligence Is Stuck. Here’s How to Move It Forward.
To get computers to think like humans, we need a new A.I. paradigm, one that places “top down” and “bottom up” knowledge on equal footing. Bottom-up knowledge is the kind of raw information we get directly from our senses, like patterns of light falling on our retina. Top-down knowledge comprises cognitive models of the world and how it works.
ai  neural_network  opinion  deep_learning  artificial_intelligence 
july 2017
Complexity and Strategy – Hacker Noon
A high-level review of the convex curve of functionality vs. cost in software:
This reflects a model where new functionality gets _harder_ to add as a system gets more functional.
It does so by showing example from Microsoft with their development of FrontPage, Word, PowerPoint, OneNote, and how they all harnessed their complexity and document-format moat to go up against Google Apps.
In Fred Brooks’ terms, this was _essential_ complexity, not _accidental_ complexity. Features interact — intentionally — and that makes the cost of implementing the `N+1` feature closer to `N` than `1`.
For those closer to code, APIs, and open-source libraries, this passage is relevant:
What I found is that advocates for new technologies tended to confuse the productivity benefits of working on a small code base (small N essential complexity due to fewer feature interactions and small N cost for features that scale with size of codebase) with the benefits of the new technology itself — efforts using a new technology inherently start small so the benefits get conflated.
complexity  simplicity  software_engineering  programming  microsoft 
july 2017
RailsConf 2017: Keynote by Justin Searls - YouTube
An incredibly quotable talk, such as:
99% of the work that I've done as a professional programmer can be boiled down as, "a business person trying to get a spreadsheet onto the internet


Introduces [a personality profile][1] for the type of programmer.

[1]: https://docs.google.com/forms/d/e/1FAIpQLSfHlw_qQLPcZTE4_oSlSxdivJQEJQ30jL7E8FFusUdqqHUbEw/viewform
presentation  rails  railsconf  goos  testing  programming  inspiration 
july 2017
Reducers - Chris Eidhof
Building up a Redux-like pattern of reducers in Swift and iOS's `UIViewController`.

Swift's enums and structs make this really nice.
swift_lang  redux  swift  UIKit  elm  enum 
july 2017
Stop waiting for perfection and learn from your mistakes - All Things Distributed
2. Make due with incomplete information

German companies have a tradition of being thorough and perfectionist. In the digital world, however, you need to loosen those principles a bit. Technology is changing so fast; you need to be fast too. Make decisions even if the information you have is not as complete as you would like.Jeff Bezos put his finger on that when he wrote in his most recent letter to shareholders that "most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you're probably being slow. Plus, either way, you need to be good at quickly recognizing and correcting bad decisions. If you're good at course correcting, being wrong may be less costly than you think, whereas being slow is going to be expensive for sure."
decision_making  inspiration  failure  experimentation  mistakes  development  product_management 
july 2017
How To Make Use Of Weekly Design Meetings – Smashing Magazine
In a nutshell, The Design Kiosk consists of:

10 minutes for going through our current tasks and our top priorities for the company’s objectives and key results (OKR);
15 minutes for sharing the latest articles we’ve read, links we’ve found and other useful resources we’ve discovered (up to three for each member);
5 minutes for sharing a quick design tip that we learned in the past week (Photoshop, Sketch or other); for example, pressing “Alt” in a Photoshop panel displays the “Reset” button — Yipee!;
25 minutes for the main topic to be discussed (this could consist of how to adopt the latest design trends, or how to improve our presentation skills, or how to organize the style guide for our agency’s website);
5 minutes for wrapping things up, writing clear actions to be taken and deciding on the main topic for next week.
management  design  projectmanagement  team  meetings 
july 2017
The rise of the McModern
Like modern art, many seem to think they can design a “modern” house—it’s just a box made up of smaller box-like shapes, right? To look at the simplicity of Philip Johnson’s Glass House and say, “I could design that” is—though flawed—relatively understandable: To the casual observer, it is a box made of windows sandwiched between a roof and a floor. Just as Jackson Pollock’s paintings are merely “paint splatters,” modern houses are merely “boxes.”
mcmansion  modernism  architecture  midcentury_modern 
july 2017
Developer experience is the ball game · Justin Duke
there’s a difference between What approach produces the best software for users? and What is the best approach for producing software for users?
native-vs-web  mac  javascript  native  development  ReactNative  electron 
april 2017
IBM's Carbon Design System
A component atomic design system and toolkit from IBM
design  sketch  ibm  design_system  atomic_design 
april 2017
The Unnecessary Fragmentation of Design Jobs
We skip most of the formal process stuff, and our Designers do everything: writing, visuals, code, project management, whatever it takes.

We’re living proof that this approach works well. We support hundreds of thousands of customers, plus multiple platforms and products, with a design team of 10 people.

We pull that off specifically because we don’t assign one designer to UX, and another to UI, and another to writing, and another to code.

Think this sounds too hard? Like there’s no way you could possibly be good at all of that?

Take a step back for a second. We’re only talking about making software.

Yes it’s hard…but in the grand scheme of things it’s not THAT hard.
design  team  product_management 
march 2017
in which four pieces are placed in a row
Lovely little write up and building a connect 4 app with your kids. Makes me look forward to those days :-)
emacs  games  lua  programming  kids 
february 2017
jasonrudolph/keyboard: Toward a more useful keyboard
A set of Karabiner-Elements + Hammerspoon configurations to set up my desired keyboard on macOS Sierra.
macos  osx  sierra  keyboard  github_repo 
january 2017
minimaxir/big-list-of-naughty-strings
The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.
github  github_repo  testing  tools 
january 2017
The Semantic Versioning Anti-Pattern
My preference is just to use something that intentionally does not look like a semantic version—this is the important step—as it helps to signal that you are simplifying the version message. I have found a simple way to do this with CD looks like:

```
YYMM.xxxx
```

Where you have a two digit year, a two digit month, followed by a zero padded incremented build number, reset as the date stamp changes. Ideally, you would not do more than 10k builds in a given month. With this you can know what build you are on, and you can also easily support continuous delivery systems. A few examples of what this might look like:
library  software_engineering  semantic_versioning  software  api  versioning 
january 2017
A crazy, better kind of roadmap – Basecamp
It's hard to have a consensus about the state of the product because we all track different issues and different feature ideas in different places and different ways. We solved this issue when we do feature development by making a map of the scopes and tracking them in lists. Is there a way we could have a kind of "canonical reference" that is an overview of the whole product as we see it right now, with pain points and opportunities called out?

A crazy idea came to mind that I had to spike. I imagined the whole product projected onto a map, with pins stuck in the areas where we need to fix something or want to change something.
roadmap  product_management  development 
december 2016
10 Things that Immediately Happen when Real Leadership Shows Up – The Mission
An obsessive focus on the nuts and bolts (the fundamentals) creates an expectation of ensuing success

It’s all about the fundamentals. The better you get at the basics, the more confident you will be.

You don’t have to worry about the outcome when you master the nuts and bolts. Success takes care of itself. You just do work that’s so good it can’t be ignored. You focus on becoming a true professional in every sense of the word.
december 2016
Multitouch is a Red Herring
After all this time, after all this waiting and lying to myself, I think multi-touch has been a big red herring. I’ve always looked at it and seen potential, like, this is the year of the multitouch desktop but it’s never materialized.
productivity  multitasking  computing  ios  multitouch 
december 2016
Management theory is becoming a compendium of dead ideas
The theorists’ third ruling idea is that business is getting faster. There is some truth in this. Internet firms can acquire hundreds of millions of customers in a few years. But in some ways this is less impressive than earlier roll-outs: well over half of American households had motor cars just two decades after Henry Ford introduced the first moving assembly line in 1913. And in many respects business is slowing down. Firms often waste months or years checking decisions with various departments (audit, legal, compliance, privacy and so on) or dealing with governments’ ever-expanding bureaucracies. The internet takes away with one hand what it gives with the other. Now that it is so easy to acquire information and consult with everybody (including suppliers and customers), organisations frequently dither endlessly.
management  productivity  business  theory 
december 2016
Optimistic UI
Optimistic UIs can make your app more fluent, straightforward and enjoyable for a user.
design  ux  errors  via:cdzombak 
december 2016
« earlier      
aaron_swartz actormodel aeropress afnetworking alternativeto amazon analytics android andyfowler animation annarbor api apple arc architecture autolayout backup bdd bestpractices blocks book bunny business c c++ chrissalzman chrome ci clang cli clojure clothing cocoa cocoapods codeoptional coffee collaboration complexity concurrency cool coreanimation coredata coregraphics couchdb css cucumber culture data database debugger design designpattern development documentation dokku dropbox dsl dynamiclanguage dzombak editor education elixir email encryption engineering erlang facebook falsedichotomy focus font fonts formobject framework from:dribbble frp functional functionalprogramming futures gcd gif git github_repo golang google goos graphql gtd guide guitar hardware hateoas health heroku home http humor hypermedia iconography icons ifttt innovation inspiration instagram interface ios ios7 ios8 ipad iphone java javascript javascriptcore jenkins jmsto json jsonapi jvm kvo layout library lisp llvm mac machine_learning management markdown material_design math memorymanagement mobile mutability mvc mvvm native-vs-web networking nsa nsfetchedresultscontroller nsmanagedobjectcontext objective-c office omnifocus onethingwell oop osx performance photography php podcast presentation privacy product_management productivity programming projectmanagement promises prototyping quote rails rails4 react reactive reactivecocoa reactiveprogramming reactjs reactnative recipe redux reference resources rest reveal-controller review rss ruby rubymotion rust_lang rxjava rxjs scala search security simplicity sketch smalltalk software software_engineering srp ssl startups static_analysis statictyping storyboard struct swift swift_lang swiftlang sync tdd team testing tool tools tshirt tutorial types typography ui uicollectionview uiimage uikit uitableview uiview uiviewcontroller ux valueobject via:androidweekly via:andyfowler via:cdzombak via:github via:henrik via:iosdevweekly via:mikelinington video web wishlist writing xcode

Copy this bookmark:



description:


tags: