Wednesday, 9 September 2015

Announcing a Non-fiction Book on Polish Aviation Pioneers, Brothers Joe and Ben Adamowicz

Across the Atlantic: The Adamowicz Brothers, Polish Aviation Pioneers
by Zofia Reklewska-Braun and Kazimierz Braun
Moonrise Press, September 2015 
ISBN 978-0-9963981-2-1, paperback, 240 pages, 
with 56 illustrations, a selected bibliography, and an index, $20.00
ISBN 978-0-9963981-3-8, e-Book (ePub format),  download, 4.97MB, $10.00

During the summer of 1934, two Polish amateur-pilots, Joe (Józef) and Ben (Bolesław) Adamowicz, who immigrated to the US more than twenty years earlier, flew over the Atlantic on a single-engine plane Bellanca. Their trip took them from New York to Warsaw; they were the first Poles to do so. They became instant celebrities, favorites of the journalists, photographers, and the public on both sides of the Atlantic. Alas, their triumph was short-lived, followed by a fall from grace, to imprisonment and bankruptcy. This richly illustrated book brings to life their forgotten story. Written by a historian, journalist and educator Zofia Reklewska-Braun and director, writer, scholar, and author of over 50 books, Dr. Kazimierz Braun, this book was originally published in Poland in 2011.



FROM THE INTRODUCTION

In this volume, we present our readers with the very first, comprehensive history of the lives and deeds of the Adamowicz brothers, Polish-American aviation pioneers. Across the Atlantic is the only comprehensive history of the lives and deeds of Joe and Ben Adamowicz – aviation heroes forgotten by time and the first amateurs, to have crossed the Atlantic by air.  We examine their victories and defeats, years of hard work, crowning achievements,  short-lived  celebrity,  and  their  illicit  business ventures leading to imprisonment and bankruptcy.  At the time, in Europe Hitler rose to power and was mobilizing to invade Poland. In America, Prohibition had only recently been revoked.

During the summer of 1934, two Polish amateur-pilots, Joseph (Józef) and Benjamin (Bolesław) Adamowicz, who immigrated to the United States of America more than twenty years earlier, accomplished an extraordinary feat. While using exclusively their own resources, skills, brains, cleverness, and diligence, and while taking an enormous risk, they flew over the North Atlantic on a single-engine Bellanca aircraft. Their  trip took them from New York to Warsaw.

Their arrival incited euphoria in Poland. Enthusiastic crowds shouting  their  names  met  them  as  they  landed  at  Warsaw’s airport, and then dozens of times during their triumphant tour of their  native  land.  The  highest  dignitaries  of  the  Republic  of Poland received them with honors: President Ignacy Mościcki, Prime Minister Leon Kozłowski, members of the government, mayors of the cities, and generals. During theatrical spectacles actors presented tributes that they designed and rehearsed especially for them. The pilots were amply honored and decorated; both received the “Cavalier Cross of the Order of the Resurrected Poland.” The two pilots were transformed into icons of both   resilient Polish patriots  and  successful  emigrants.  They  became  instant celebrities, favorites of the journalists, photographers, and the public on both sides of the Atlantic. [...]


After the initial enthusiasm, the Adamowiczes adopted country, the United Stated of America, treated them harshly. As non-professionals in the aviation world, distant from the elite pilots of their times, the flights by these Polish-Americans were not included in the registers of major achievements of American pilots. Similarly, the general history of aviation neglected to include them in its annals. When it did so, the Adamowicz brothers received only marginal recognition and were mentioned in a context diminishing their achievement. Lies distorted their real story and fun was made of them.

In fact, they were treated as a curiosity. Americans ironically looked upon the figures of two brothers, uneducated Poles, speaking in broken English, with a heavy foreign accent. These pilots were inexperienced in giving interviews, lacked manners, and did not know how to boast and brag about their feats. To make things worse, the disgrace which they carelessly brought upon themselves resulted in almost complete absence of coverage of their lives after their transatlantic journey. Many publications as well as internet files end their story just after their successful landing in Warsaw and the ten-week-long visit to Poland. Frequently, these incomplete accounts conclude with a variant of a remark:“Their further fate remains unknown.”

In  this  book,  we  break  the  curtain  and  narrate  both  the known and the unknown parts of the Adamowicz brothers’ story. These events deserve to be recalled. The brothers deserve that their true story be told accurately, with attention paid to the historical   detail   ─   not   filled   with   journalistic   gibberish, unconfirmed gossip, or deliberately fabricated lies.

The Adamowicz brothers accomplished something really significant. They conquered the North Atlantic only seven years after Charles Lindbergh. They were the first Poles to fly over the ocean. They were the very first aviators to fly from New York to Warsaw. It is imperative to give them justice and worthwhile to understand their motives. Why would two simple boys from a small village somewhere in eastern Poland who became laborers in Brooklyn find in their hearts such dedication and summon up enough courage and perseverance to do what they did?


ABOUT THE AUTHORS

Zofia Reklewska-Braun is literature and theatre historian, journalist, and educator. She studied Polish Literature at the Warsaw  University,  earning  Master  of  Letters  degree.  She worked as editor at the State Scholarly Publishing House in Warsaw  and  as  literary  manager  at  the  Osterwa  Theatre  in Lublin. She was teaching polish language and literature in Polish and   American   high   schools,   Buffalo   State   College,   and University at Buffalo. She wrote a book,  How It Really Was (about the martial law in Poland) and co-authored, with her husband   Kazimierz   Braun,   a   monograph,   Director   Teofil Trzciński    and  a  historical  book  Good  Priests.  With  theatre scholar and critic, Konstanty Puzyna she wrote a study Jacques Copeau’s “Bare Stage.” She published several articles in literary, religious, sociological, and theatre journals in Poland, and she collaborated  with  Nowe  Życie  in  Wrocław,  White  Eagle  in Boston, Am-Pol Eagle in Buffalo, and New Daily in New York, as well as with Polish radio stations in Chicago, New Jersey, and New York. She was active as an Instructor of Girl Scouts in Poland and as an adviser in various organizations and Roman Catholic parishes in Poland and the USA. Her memoires I Was Born in Between, (Norbertinum, Lublin, 2009) was a bestselling book in Poland. For her merits and achievements in teaching and promoting Polish history, literature, and language she was decorated with  the Cavalier Cross of  the Order of Merit of the Polish Republic by President Lech Kaczyński.

Kazimierz Braun is director, writer,  and  scholar.  He received his Ph. D. in Letters and Ph. D. in Theatre at the Poznań University, Poland, as well as M.F.A. and Ph.D. in Directing  at  the  National School of Drama in Warsaw. He holds the Professor’s title in both Poland and the USA. He was artistic director and general manager of pro- fessional theaters in Poland, including The Contemporary Theater in Wrocław. He directed more than 150 productions, both professionally and academically, in Poland, the United States, Canada, Germany, Ireland, and other countries. He taught both at Polish and at American  universities,  including  Wrocław  University,  Poznań University, New York University, City University of New York, Notre Dame University, University of California Santa Cruz, and University  at  Buffalo.  He  published  more  than  50  books  in Polish, English, and Czech languages, including scholarly works, novels, and plays, which were produced in Poland, Canada, the United States, Ireland, and Russia. He also published extensively in Polish and American literary and theatre journals, as well as in encyclopedias. He received several prizes for theater, literature, and scholarship, including the awards of the Guggenheim, the Fulbright, the Turzańskis, and the Japanese Foundations. He is member of the International PEN Club, International Theater Institute, Polish Writers Association, and Polish Actors Union.

Zofia Reklewska and Kazimierz Braun married in 1962. They have three children: Monika, Grzegorz and Justyna, as well as five granddaughters: Anna, Joanna, Aniela, Zofia and Elżbieta.



ABOUT THIS BOOK

The Adamowicz brothers flew over the Atlantic on a single-engine plane Bellanca. Their trip took them from New York to Warsaw; they were the first Poles to do so. They became instant celebrities, favorites of the journalists, photographers, and the public on both sides of the Atlantic. Alas, their triumph was short-lived, followed by a fall from grace, to imprisonment and bankruptcy. This richly illustrated book brings to life their forgotten story. ~ Maja Trochimczyk, Ph.D., Moonrise Press

Intriguing and diligently researched, Across the Atlantic is a must-read for enthusiasts of aviation history, as well as those interested in Polish American history. The story of the Adamowicz brothers and their deft flight is a story of triumph and disappointment, victory and defeat, fame and oblivion. The authors are giving those aviation pioneers their second chance in history. ~ Anna D. Jaroszynska-Kirchmann, Professor of History

Zofia Reklewska-Braun and Kazimierz Braun’s book narrates the many entanglements and paradoxes of brothers Adamowicz life and achievements, as well the history of their times. Only seven years after Lindbergh, they were the first Poles, to cross the North Atlantic on a tiny Bellanca aircraft. The book is written with passion, care for the details, and perfectly documented; it is based on years’ lasting research in archives and on comparative analysis of various sources. All in all it is a fascinating story of the career, ascent, and catastrophe. ~ G. Eberhardt, author of "The World is Normal Anyway," 2014.



Wednesday, 19 August 2015

Happy RakshaBandhan Whatsapp Status Message For Brothers And Sisters



Sis is Someone Who is Caring N Sharing. Sis Can Understand Things u Never Said. She Can Understand Pain, Witch is not visible to anyone. I love u sis! Happy Raksha Bandhan

May this auspicious occasion bring you all the prosperity and good luck in your way of life.
Happy Raksha bandhan Sister…

Here a Rakhi to Say…  Bhaiya Tum jiyo hazaaron saal… Mile success tumhe har bar… Khushiyon ki ho tumpe bauchar… Yehi dua hum karte hain  …

Thanks dear Bhaiya for your warmth affection
&
ur understanding , May our bond of love remain forever.

The loving occasion of Raksha Bandhan
is the best time Brother, to
reminisce fondly the wonderful moment
we have spent together,sharing each
others joys and sorrows… Thanks for
spreading smiles everywhere and
making life so beautiful, meaningful
and Happy… My Dear Brother .

Har Ladki apke liye bekarar He
Har ladki ko aap ka Intezar He
Ye aap ka koi kamaal nhi
Aaj Rakhi Ka Tyohar He

Dear brother,today is rakhsha bandan and u r not here by my side..
but we r close in each others thought and my love will always be with u.

You know that you are the most precious stone in the collection of my secret treasure..
Wishing you very Happy Rakhi and best of luck for every thing.

“God could not take care for the whole world
so he has given mothers to each family.
In the same way mother could not take care
for the whole part of our life, so she had given brothers.
Thanks for being my brother.” Happy Raksha Bandhan

God sent in my life a beautiful Angel in
your guise, Sister. In good times or bad
ones, you’re ready to extend your help and
support. Thanks for all you do.”

"You are the person who holds me in my bad times,
you are the person who dances with me in my happiness.
I can't recall even a single day when you were absent from my life.
I really love you."
Happy Rakhi Bro

I want 2 tell u,during the times when we fought,
my love was in a different mood.Happy Raksha Bandhan sweety!

Khuda kare tujhe khushiyan hazaar mile
Mujhse bhi achcha yaar mile
Meri girlfriend tujhe bandhe RAKHI
Aur ek AUR behan ka pyaar mile…
Happy RAKSHA BANDHAN

Phoolon ka taron ka sabka kehna hai,Duniya me sobse achha mere Bhaiya hai...
luv u always.Happy Rakhi..

Aaj Din Bahut Khaas Hai,
Behan KE Liye Kuch Mere Paas Hai,
Uske Sukun Ki Khaatir O Behnaa..
Tera Bhaiya Hamesha Tere Aas-Paas Hai !!
Happy Rakhsha Bandhan

“Yes, you are so cute,
smart. My mother also likes you very
much. My father is ready to take up
our relationship seriously. So please
don’t say no to my proposal. Accept
me as your dearest, loveliest younger
sister.” Happy Raksha Bandhan

You are the person who holds me in my
bad times, you are the person who dances
with me in my happiness. I can’t recall
even a single day when you were absent
from my life. I really love you sweet Bro.”

Dear brother,
today is rakhsha bandan
and u r not here by my side..
but we r close in each others thought
and my love will always be with u.

Wednesday, 5 August 2015

What is Flow Debt?

+Daniel Vacanti's excellent treatise on Actionable Agile Metrics [vaca] introduces a term that may be unfamiliar, even to those with an interest and experience in managing flow systems. The term is Flow Debt - for a definition and explanation read on.

My own particular interest in flow systems is the management of agile software development teams, usually using some variant of Scrum and/or Kanban, and other agile practices such as test-driven (or automated-test intensive) build-test-deploy processes. However the discussion is relevant in many other domains, such as one I've recently been involved in discussing, the flow of patients through diagnosis, treatment and convalescence in healthcare systems.

In managing these systems we need ways to look at the mass of data that emerges from them to focus on the useful information rather than the noise; information in particular that indicates when intervention is appropriate to improve flow, and when the attempt would be as futile as trying to smooth the waves on an ocean. Flow systems in knowledge work contain variability. That variability, within certain bounds (much wider bounds than in manufacturing for example), is desirable to allow innovation, responsiveness and minimising wasteful planning activities.

In this context Flow Debt is a measure that provides a view of what is happening inside our system. This is in contrast with other important measures such as Throughput (Th) and the time an item stays in the process (I call this "Time in Process", TiP [macc], though other terms may be used). These measures provide information only after items have left the system, which may be too late to avoid problems accumulating.

Having Flow Debt roughly translates as: delivering more quickly now at the cost of slower times later. It is calculated by comparing the time since the number of arrivals into the systems was equal to the current number of deliveries with the average time in the process for the most recent deliveries. It is easiest to visualise this on a Cumulative Flow Diagram.
At the point highlighted in the the diagram it is a little over 2 weeks since the cumulative number of items entering the system equalled the cumulative number of deliveries on that date. If the items were delivered in the precise order they arrived, and if all the items were delivered (neither assumption is true!), then we would be able to say that the time the last item spent in the process was also a little over 2 weeks. Furthermore if arrivals and deliveries were smooth over the period, the Average Time in Process for the items would also be this same time.

What was the actual Average Time in Process though? Well you can't read this off the diagram. You have to look at the average TiP for the items delivered in the recent period. Each one has a known TiP, so take the average of them. Exactly how long the period you select for this average is up to you - a day or a week seems reasonable. The shorter the period you take the more noise there will be in the signal. Take too long a period though and there is insufficient time to act on the information. 

With this information we can calculate Flow Debt using Dan's method[vaca]:
Flow Debt = (Time since number of arrivals equalled deliveries) - Average TiP
If you plot this quantity for the data above you get a graph like this. Note I've reversed the sign on this graph to show Flow Debt as negative.
The plot of Flow Debt in this case is quite normal showing a fluctuation around zero and maxima and minima of around the value of the average TiP for the whole period. If you plotted the same data with a monthly average, most of this fluctuation would disappear. I certainly wouldn't want managers rushing down to this team to radically change their process!

There is one point highlighted which is interesting, where the Flow Debt goes from highest debt to highest credit in a few days. What do you think is going on here? Well, if you go back to the informal definition of Flow Debt (delivering more quickly now at the cost of slower times later), we should surmise that before this point the delivered items had been in the process for only a short time. Those delivered at or after this point had a longer time in the process. That's exactly what happened, as the Control Chart below shows.
Another useful indicator here is the "average age" of the work in progress. Here is the plot of that and you can see the significant drop in this metric at the same point.
Just by way of balance let's look at another data set of a team delivering software much less frequently, where their work in progress is increasing over the process, and where the items are not being delivered in age order. All these factors are likely to effect the efficiency and predictability of the flow system... and this is borne out by their plot of Flow Debt.
Seeing a plot like this is a indication to management (and flow management specialists in particular) to take a much closer look at the process being used here.

References

Wednesday, 29 July 2015

Beyond Control Charts and Cumulative Flow Diagrams

Control Charts (CCs) and Cumulative Flow Diagrams (CFDs) are powerful ways to display information about a flow system, such as a Scrum or Kanban development process. Unfortunately the very fact that the charts display so much information means that it is often difficult to extract specific information from them. That is why it's useful to also plot some of the key attributes of the systems on their own - this allows us to look at these aspects specifically, alongside the rawer view of the data that you get from CCs and CFDs.

The graphic on the right shows a number of diagrams all of which were derived from very simple data about each item that flowed through this system:
  • when it arrived into the system; 
  • when it departed the system; and
  • whether the item was "delivered" or "discarded".
Note: I use the term "discard" here as a general term to include an exit from the system at any point in the system and for any reason. It includes aborting/abandoning the item after commitment, as well as postponing the item by moving it back to a part of the process upstream from the system under study. For the definition of this and other terms used here please see this Glossary.
The first diagrams in the graphic is the Control Chart - actually this is simply a scatter plot of the time each item stays in the system under study. I refer to this as "Time in Process - TiP - or alternatively "Time in _______" where the blank stands for whatever the process or part of the process is under study. For example it could be the Time in Preparation, Time in Development, Time in Acceptance, etc. The scatter plot highlights (in orange) the items which were not "delivered".

Below it is the CFD. Unlike some very stripy versions, this one has only 3 bands (as limited by the input data), corresponding to arrivals, all departures (including discards), and deliveries.

The remaining diagrams all highlight one or more aspects of the same data. Firstly the terms from Little's Law:
  1. Average Delivery Rate. This is measured in items per week, and the average is taken over 1 week. Note this only shows actually delivered items. Alternatively a plot of "Throughput" could have been used which includes all items that have passed through the system.
  2. Average Time in Process (TiP). This is measured in weeks and again the average is taken over 1 week.
  3. Average Work in Progress (WiP). This is measured in number of items, again averaged over one week. Care must be taken when calculating average WiP for a day, particularly on days when an item arrives in or departs from the system, to ensure that it is consistent with the calculations of average TiP.
In addition to these standard quantities from Little's Law a number of flow balance metrics are shown. These are:
  1. Net Flow. Simply the difference between the number arriving and departing over the previous week.
  2. Delivery Bias. This is a measure of the degree to which Delivery Rate is higher or lower than would be predicted by Little's Law for the given period (1 week in this case). If it is non-zero it indicates away from stability. Further discussion of this quantity is found here.
  3. Flow Debt/Credit. This is a measure of the degree to which the average TiP varies from that predicted by the CFD. This also indicates a degree of instability if it varies significantly from zero. See Dan Vacanti's book [vaca] for further discussion.
  4. Age of WiP Indicator. This compares the average age of the WiP with half the average Tip. It is another indicator of imbalance.
Recently I have been discussing these four quantities with colleagues and with Troy Magennis and Dan Vacanti as they show promise for predicting significant changes in the TiP, a very important aspect of the effectiveness of the system.

A spreadsheet containing the means to generate these diagrams from your data will shortly be made available from gitHub. Watch this space!

References
  • [vaca] Vacanti, Daniel S. "Actionable Agile Metrics for Predictability: An Introduction". LeanPub. (2015)