"engineering" entries

Four short links: 3 August 2015

Four short links: 3 August 2015

Engineering Management, Smartphone Holograms, Multi-Protocol Server, and Collaborative CS

  1. A Conversation with Michael LoppMy job is to my get myself out of a job. I’m aggressively pushing things I think I could be really good at and should actually maybe own to someone else who’s gonna get a B at it, but they’re gonna get the opportunity to go do that. […] Delegation is helping someone else to learn. I’m all about the humans. If I don’t have happy, productive, growing engineers, I have exactly no job. That investment in the growth, in the happiness, the engineers being productive, that’s like my primary job.
  2. 3D Hologram Projector for Smartphone (BoingBoing) — is in hardware hack stage now, but OKYOUWIN maybe it’s the future.
  3. serve2dserve2 allows you to serve multiple protocols on a single socket. Example handlers include proxy, HTTP, TLS (through which HTTPS is handled), ECHO and DISCARD. More can easily be added, as long as the protocol sends some data that can be recognized. The proxy handler allows you to redirect the connection to external services, such as OpenSSH or Nginx, in case you don’t want or can’t use a Go implementation.
  4. GitXivIn recent years, a highly interesting pattern has emerged: Computer scientists release new research findings on arXiv and just days later, developers release an open-source implementation on GitHub. This pattern is immensely powerful. One could call it collaborative open computer science (COCS). GitXiv is a space to share collaborative open computer science projects. Countless Github and arXiv links are floating around the Web. It’s hard to keep track of these gems. GitXiv attempts to solve this problem by offering a collaboratively curated feed of projects. Each project is conveniently presented as arXiv + Github + Links + Discussion
Comments Off on Four short links: 3 August 2015
Four short links: 31 March 2015

Four short links: 31 March 2015

Boring Technology, Psychology Memes, Engineering Ladder, and Flatpack Refugee Shelters

  1. Choose Boring Technology (Dan McKinley) — Adding technology to your company comes with a cost. As an abstract statement this is obvious: if we’re already using Ruby, adding Python to the mix doesn’t feel sensible because the resulting complexity would outweigh Python’s marginal utility. But somehow when we’re talking about Python and Scala or MySQL and Redis, people lose their minds, discard all constraints, and start raving about using the best tool for the job.
  2. Dunning-Kruger and Other Memes — a reality check on the popsci conception of some psych research.
  3. Sharing our Engineering LadderIn addition to the ladder causing problems inside of my team, we were having a hard time evaluating candidates during interviews and determining what level to hire them into. Particularly at the more senior levels, it wasn’t clear what the criteria for success really looked like. So, together with my tech leads and engineering managers, we rewrote the ladder to be more specific. It has been very helpful both for the process of reviews and promotion committees as well as for the process of hiring.
  4. Ikea’s flat-pack refugee shelter is entering production (The Verge) — The UNHCR has agreed to buy 10,000 of the shelters, and will begin providing them to refugee families this summer. […] Measuring about 188 square feet, each shelter accommodates five people and includes a rooftop solar panel that powers a built-in lamp and USB outlet. The structure ships just like any other piece of Ikea furniture, with insulated, lightweight polymer panels, pipes, and wires packed into a cardboard box. According to Ikea, it only takes about four hours to assemble.
Comments Off on Four short links: 31 March 2015

It’s time for a “commitment escalation”

Mikey Dickerson on why he moved from Google to the West Wing, and where we need to be allocating our engineering resources.

In a keynote address at Velocity New York 2014, Mikey Dickerson described his journey from working for Google to working in the West Wing of the White House, leading the US Digital Services group. He told the story of how a three-day review turned into a nine-week “herculean effort” by a team working 17 hours per day, 7 days per week to get HealthCare.gov up and running. The challenges, he stressed, boiled down to a few big, though basic, things — building a monitoring system, creating a war room to provide development direction and organization, and establishing a sense of urgency to get the problems fixed. “This very formidable obstacle, when you pushed on it even a little bit, fell apart; it was made out of sand,” he said. “Nothing we did was that hard; it was labor intensive, but it was not hard.”

Read more…

Comments Off on It’s time for a “commitment escalation”
Four short links: 26 September 2011

Four short links: 26 September 2011

Design and Engineering Culture, Homemade Love, Code Tools, and Cyberbullying

  1. BERG London Week 328we’re a design company, with a design culture built over 6 years, yet we’re having to cultivate a new engineering culture that sits within it and alongside it, and the two have different crystal grains. It’s good that they do—engineering through a design process can feel harried and for some projects that does not lead to good outcomes. And vice versa. But it throws up all kinds of questions for me: do we really want two domains of engineering and design; what is the common protocol—the common language—of engineering culture, and indeed of our design culture; how do these lattices touch and interact where they meet; how do we go from an unthought process to one chosen deliberately; how is change (the group understanding of, and agreement with a common language) to be brought about, and what will it feel like as it happens. I think more and more businesses will have to explicitly confront the challenge of reconciling design with engineering, novelty with constancy, innovation with repetition. Science is doing something once in a way that others might able to reproduce, however long it takes. Business is doing it the same way a million times, as fast as possible.
  2. Why We Love The Things We Build — psychological research to look at people valuing the things they build. Lots of interesting findings: participants thought others would value their origami creations highly, despite assigning little value to the amateur creations of others and incomplete items were not valued as highly as completed items. (via BoingBoing)
  3. Gut Flora Social Network (New Scientist) — although there’s real science behind it, I think it’s mostly a callous play to get web journalists to say “this social network is a bit shit”. (via Dave Moskowitz)
  4. The Unintended Consequences of Cyberbullying Rhetoric (danah boyd) — actual research on bullying and cyberbullying, indicating that those involved in cyberbullying don’t think of what they’re involved in as bullying, because that implies power relationships they don’t want to acknowledge. Instead it’s all part of the “drama” of high-school.
Comments Off on Four short links: 26 September 2011

The boffins and the luvvies

The names may change, but the friction between science and art goes back centuries.

Whether we're discussing ancients vs. moderns, scientists vs. poets, or the latest variant, computer science vs. humanities, the debate between science and art is persistent and quite old.

Comments: 4

Marc Bohlen: Finding the Intersection of Art and Technology

Artist-Engineer Marc Bohlen uses some fairly advanced technology to express his artistic visions. It's not often you find an artist with a degree from CMU in robotics, or an engineer with an Masters in Art History. Bohlen's projects explore how people and technology interact, ranging from the bickering robots Amy and Klara, to his latest project, the Glass Bottom Float. In advance of his appearance at the E-Tech conference in March, Bohlen talked to us about how he approaches art, and just what art is.

Comments Off on Marc Bohlen: Finding the Intersection of Art and Technology
Four short links: 11.5 Feb 2009

Four short links: 11.5 Feb 2009

This second Feb 11 post was brought to you by the intersection of timezones and technology. If there’s a third Feb 11 post, I’m changing my name to Bill Murray.

  1. Hacking the Earth — an environmental futurist looks at “geoengineering”, deliberately interfering with the Earth’s systems to terraform the planet. Radical solution to global warming, unwise hubris and immoral act of the highest folly, or all of the above? (via Matt Jones)
  2. Reinvention Draws Near for Newsweek — fascinating look at how Newsweek are refocusing their magazine. “If we don’t have something original to say, we won’t. The drill of chasing the week’s news to add a couple of hard-fought new details is not sustainable.” gives me hope. Newsweek are hoping to target fewer but richer advertisers, essentially a business strategy of tapping existing customers for more. This feels like they’re ceding the contested parts of their business (commodity news stories) and doubling down on the bits that nobody else is fighting for yet (their columnists, pictures, whitespace). What else could they do? Possibly nothing (see Innovator’s Dilemma), but the alternative is figuring out something new that people want and giving them that. Easy to say, hard for anyone to do.
  3. Tinkerkit – a physical computing kit for designers. Arduino-compatible components for rapid prototyping. Sweet!
  4. Stanford University YouTube Channel — short interesting talks by Stanford researchers. Brains on chips, stem cells to fight deafness, and brain imagery are some of the first up there. The talks aren’t condescending or vague, they’re aimed at “a bright and curious audience”, as the Mind Hacks blog post about them put it.
Comments: 4