What’s your favorite chocolate chip cookie recipe? I bet you could ask that question to 5 different people and get 5 totally different recipes… brown sugar vs white sugar, cake flour vs all purpose, dark chocolate vs milk chocolate. All of these recipes result in a chocolate chip cookie but the process by which we get there is a matter of personal preference. If you were to ask multiple developers to solve a problem, it’s doubtful that any two developers write identical code. It’s not that any one solution is necessarily better than the others… the resulting code is likely just a matter of personal preference.
Grio has adapted the Agile methodology to our consulting business; and one of our most valued “ceremonies” is the retrospective. We keep these meetings open to all, and the notes from these meetings are in a shared folder for everyone at Grio to read.
Despite having access, I found them “gathering dust” so to speak, and decided to dig through the entire folder to track Grio’s ability to implement the changes proposed and avoid the pitfalls of previous projects. We’re genuinely asking ourselves, “Are we serious about learning from mistakes?”
I’ve explored the overall process of my research here, and have presented the findings in depth to our entire team. There’s some good news, and some work to do; but we’re happy to see that our efforts have created tangible benefits to our team, our clients, and our bottom line.
We’re asking ourselves:
“Are we serious about learning from mistakes?”
The term “Quantum Computing” is surfacing popular science and media outlets more and more. So what are Quantum Computers? What does quantum mean? How are companies tackling quantum computing research? This post will introduce quantum computing, quantum mechanical phenomena and the status of the quantum computing industry today.
There has recently been much discussion about getting more women into computer programming roles – the case of the Google manifesto shows that what many us think of as outdated gender stereotypes about programmers are still alive and well in some circles. However, it wasn’t always the case that computer programming was considered a ‘male’ field. Early computer programming was dominated by women, and it was women who were seen as uniquely capable of being computer programmers. Among early computer pioneers were many women who made important contributions to computer science and programming and invented many of the concepts & models we continue to use today.
Throughout my continuing journey as a designer I have started to notice several companies are creating what they call design systems. Some people also like to refer to them as design languages, visual languages, or human interface guidelines. Google has Material Design, Apple has created their Human Interface Guidelines, last year Salesforce put together their Lightning Design System, and Airbnb has recently put together a visual design language for their design team. I became curious as what a design system is and why these companies have started to create and document them. Below I’ve broken down my research into a few sections: what is a design system, what are the benefits, and when it is and isn’t beneficial to create one.
A spate of applications have popped/cropped up in recent years with slogans like “Make Anything Art.” They purport to transfer the style of one image and render the content of another image in that style. In the sets of images below, the small inset image is the source of the “style” which is transferred to the larger image. It’s an impressive trick, although I don’t know that it accurately represents what we mean by ‘style’.
I’ve partnered with my client, Texture, for more than two years, and I am still continually learning in all aspects of design. I’ve been lucky enough to pick up two software programs in the last year; Sketch and Principle. I’d like to give a quick review of Principle and share my pros and cons as a new user
Have you ever heard the term “esoteric programming language” and not known exactly what it was referring to? If so, this blog is for you, and hopefully an entertaining jaunt if not.
Esoteric programming languages are a unique class of programming languages that are generally NOT designed for everyday use on projects such as a website or phone app. Instead,
they are designed with a goal in mind, such as being a difficult as possible to program in, or to layout the code into a physical space that has meaning. Amusingly enough, even though they are often rather crazy, they also tend to be Turing complete which is quite impressive considering they weren’t necessarily designed with that goal in mind.
Kotlin is a JVM language that hit version 1.0 about a year ago (February 2016).
It is developed by JetBrains, the same people who make my favorite suite of
IDEs. The language itself is open-source under the Apache License 2.0 and is
developed as a community project over at kotlinlang.org. Kotlin is something
that I have become rather excited about over the past year. This post’s goal is
not to teach you Kotlin but to get you excited about it!
There are a lot of APIs out there, a lot of networking layers, a lot of abstractions, I’m going to offer just one way to start building Swift models backed by a RESTful API. Out of personal preference, PromiseKit will be used instead of callbacks and ObjectMapper will be used to convert between JSON and Swift objects.