Good morning! (at Riksbron)

Photoset

wastholm.tumblr.com/post/114938107422/waffles, posted 29 Mar by peter

Waffles.

Profiling data can be thousands of lines long, and difficult to comprehend. Flame graphs are a visualization for sampled stack traces, which data allows hot code-paths to be identified quickly. See the Flame Graphs main page for uses of this visualization other than CPU profiling.

Flame Graphs can work with any CPU profiler on any operating system. My examples here use Linux perf_events, DTrace, SystemTap, and ktap. See the Updates list for other profiler examples, and github for the flame graph software.

My goal in this guide is both to answer these questions, and, more importantly, provide an overall framework you can use to think about how to answer these questions.

RT @_youhadonejob: Resistance is futile. http://t.co/yEjRQma5ef

The LedBorg provides a tri-colour LED controllable from the Raspberry Pis GPIO header. Using simple on / off logic it can provide a total of seven colours as well as off. Using software based pulse width modulation (PWM) it is capable of many more colours, around a million in fact.

One of the hardest parts of building for Android is making your app work well on all phones. While device fragmentation often brings forth concerns on design, the bigger struggle will be behind the scenes in managing memory, rendering smooth graphics, and maintaining battery life.

The German city of Hamburg has announced plans to become car-free within the next two decades. It is an ambitious idea, but city officials obviously feel that the personal motorcar does not fulfill a function that walking, biking and taking public transport cannot.

The goal of Hamburg’s project is to replace roads with a “gruenes netz” or a green network of interconnected open areas covering 40% of the city. According to the official website, parks, playgrounds, sports fields, allotments and cemeteries will be connected to form a network, which will allow people to navigate through the city without the use of cars.

So, why don’t we use git-flow at GitHub? Well, the main issue is that we deploy all the time. The git-flow process is designed largely around the “release”. We don’t really have “releases” because we deploy to production every day - often several times a day. We can do so through our chat room robot, which is the same place our CI results are displayed. We try to make the process of testing and shipping as simple as possible so that every employee feels comfortable doing it.

There are a number of advantages to deploying so regularly. If you deploy every few hours, it’s almost impossible to introduce large numbers of big bugs. Little issues can be introduced, but then they can be fixed and redeployed very quickly. Normally you would have to do a ‘hotfix’ or something outside of the normal process, but it’s simply part of our normal process - there is no difference in the GitHub flow between a hotfix and a very small feature.

Vårtecken: började käka allergimedicin i dag.

1–10 (2948)   Next >   Last >|