Podcasts about CPAN

For a country that boasts of its digital public goods infrastructure like Aadhar and UPI, it is a wonder why telecom has been so ignored. After nearly 1500 crore rupees of was reportedly lost to digital fraud in the financial year 2024, the govt's TRAI is finally scrambling to catch up with CPAN or the Calling Name Presentation (CNAP) service, its own version of Truecaller.  Truecaller, the Swedish call-screening company, meanwhile, has been holding the fort for a while now. Users count on it to save them from spam and fraud calls.  While TrueCaller maybe looking like a hero in this situation, it is a private company after all. It is using this opportunity to make money from both users and businesses. But its success in India is also built partially on how inadequate privacy laws are in India. The company has been accused of breaching data privacy norms in the past.  Can TRAI replace Truecaller?  Tune in.(This episode was first published in July, 2024)DAYBREAK UNWIND RECOMMENDATIONS for "coming of age"Rahel: Big Mouth, NetflixSnigdha: The Lives of Girls and Women by Alice Munro and Lady Bird (2017)Atish Deore: The works of PL Deshpande, a Marathi author and playwright Shubhangi: Derry Girls (2018)Brijesh: Where The Crawdads Sing by Delia Owens   Daybreak is now on WhatsApp at +918971108379. For next Thursday's Unwind, send us your recommendations to us as texts or voice notes. The theme is "favourite translated books."              

For a country that boasts of its digital public goods infrastructure like Aadhar and UPI, it is a wonder why telecom has been so ignored. After nearly 1500 crore rupees of was reportedly lost to digital fraud in the financial year 2024, the govt's TRAI is finally scrambling to catch up with CPAN or the Calling Name Presentation (CNAP) service, its own version of Truecaller.Truecaller, the Swedish call-screening company, meanwhile, has been holding the fort for a while now. Users count on it to save them from spam and fraud calls. While TrueCaller maybe looking like a hero in this situation, it is a private company after all. It is  using this opportunity to make money from both users and businesses. But its success in India is also built partially on how inadequate privacy laws are in India. It company has been accused of breaching data privacy norms in the past.Can TRAI replace Truecaller?Tune in.Daybreak is produced from the newsroom of The Ken, India's first subscriber-only business news platform. Subscribe for more exclusive, deeply-reported, and analytical business stories.

Norton Healthcare's Plugged in to Nursing is the podcast that celebrates and informs the profession of nursing.   Episode 35: The Orchestra of Surgical Nursing Care Summary: In May's episode of Plugged In To Nursing, hear Kirsten McCoy Dietrich, RN, and Jessica Massouda, MSN, RN, CCRN, CPAN, CNOR, system nurse educator, discuss Surgical Services and the nurse's impact through its many phases of care. Jessica's description highlights the orchestra of teamwork and collaboration for successful surgeries. Listen to learn why being organized, having strong communication skills, and leading with compassion are essential traits for surgical nurses. Speakers: Kirsten McCoy Dietrich, RN Norton Audubon Hospital Jessica Massouda, MSN, RN, CCRN, CPAN, CNOR System Nurse Educator   Show Notes: ‘UofL' is University of Louisville ‘PACU' is post anesthesia care unit ‘PCA' is patient care assistant ‘CCRN' is Critical Care Registered Nurse ‘EP Lab' is Electrophysiology Lab ‘ERAS' is enhanced recovery after surgery ‘SCIP' is surgical care improvement project Job shadow interest, https://nortonhealthcare.com/careers/students-in-healthcare/job-shadowing/ Email address: Jessica.Massouda@nortonhealthcare.org   About Norton Healthcare's Center for Nursing PracticeNorton Healthcare's Center for Nursing Practice is responsible for readying student nurses for practice and transitioning new graduate nurses into practice.  Our team is committed to serving the profession of nursing, meeting people where they are and taking them to where they want to be. Contact Information:  PluggedInToNursing@nortonhealthcare.org     Audio Editing and Production:  www.unmuteaudio.com 

Can we manage pain and anxiety without medication? In today's interview, we sit down with Jessica Hovland, DNP, RN, CPAN, NE-BC, PMGT-BC, registered nurse and the Senior Director for UT Health Austin's Ambulatory Surgery Center, to answer this question! Tune in to discover how Jessica's DNP research blended multimodal analgesia and virtual reality to offer surgical patients a non-opioid treatment option for postoperative pain. We'll learn about her research, we'll discuss what she learned, and we'll uncover the unexpected benefits that she found for using virtual reality. Stay tuned! Love our show? Download our First Case mobile app on:

CME link:          https://cmetracker.net/UTHSCSA/Publisher?page=pubOpen#/getCertificate/10095275 ADHD Update: When Will the Drug Shortage End? What to Do FACULTY: Giancarlo Ferruzzi, MD, Associate Clinical Professor of Psychiatry and Behavioral Sciences at the University of Texas Health Science Center. He's been a child psychiatrist for 30 years.    OVERVIEW: Pediatrics Now Podcast host Holly Wayment interviews Giancarlo Ferruzzi, MD about the ADHD drug shortage and solutions for pediatric practitioners and their patients. Dr. Ferrruzzi and Wayment also talk about CPAN, plus the reason for an uptick in adolescents with facial tics. Don't forget to tell your patients about our new podcast for parents! Pediatrics Now for Parents: Health News in Small Bites for the Busy Parent.  One less topic you have to cover in the exam room! www.pediatricsnowforparents.com     DISCLOSURES: Giancarlo Ferruzzi, MD has no financial relationships with ineligible companies to disclose.   The Pediatric Grand Rounds Planning Committee (Deepak Kamat, MD, PhD, Steven Seidner, MD, Daniel Ranch, MD and Elizabeth Hanson, MD) has no financial relationships with ineligible companies to disclose.    The UT Health Science Center San Antonio and Deepak Kamat, MD course director and content reviewer for the activity, have reviewed all financial disclosure information for all speakers, facilitators, and planning committee members; and determined and resolved all conflicts of interests.   CONTINUING MEDICAL EDUCATION STATEMENTS: The UT Health Science Center San Antonio is accredited by the Accreditation Council for Continuing Medical Education to provide continuing medical education for physicians.   The UT Health Science Center San Antonio designates this live activity up to a maximum of 1.00 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.   CREDITS: AMA PRA Category 1 Credits™ (1.00) Non-Physician Participation Credit (1.00)    

Lately, school safety has been top-of-mind for growing numbers of parents, from Denver Public Schools and beyond. John Castillo and Colorado Parent Advocacy Network founder Lori Gimelshteyn return to discuss the importance of strengthening school safety and CPAN's powerful upcoming School Safety Summit, which will feature inspiring panels of school shooting survivors and experts.See omnystudio.com/listener for privacy information.

Lately, school safety has been top-of-mind for growing numbers of parents, from Denver Public Schools and beyond. John Castillo and Colorado Parent Advocacy Network founder Lori Gimelshteyn return to discuss the importance of strengthening school safety and CPAN's powerful upcoming School Safety Summit, which will feature inspiring panels of school shooting survivors and experts.See omnystudio.com/listener for privacy information.

112: Brian Daniel is the founder of The Celebrity Personal Assistant Network, a headhunting firm for celebrities, high-net-worth families, and billionaires. As a former personal assistant, chief of staff, and confidant to some of the world's wealthiest families, Brian knows firsthand what it takes to make it in the private service industry. Since its inception, http://FindCelebrityJobs.com has been featured in dozens of high-profile media outlets worldwide and has been visited tens of millions of times. In addition to household staffing, CPAN also offers resources for those in private service, including but not limited to career coaching and B2B consulting for small business owners in the luxury markets. Links: www.findcelebrityjobs.com www.linkedin.com/in/headhunter3/

Tim Hoste who is the President of CPAN joins the show to talk about Michigan Court Upholding Critical Benefits

Introduction I have occasionally been using a tool called ack for a few years now. It's billed as “an alternative to grep for programmers”. There are several features I find particularly useful: It can restrict text searches to files of a particular type It uses Perl regular expressions which may be the most powerful and feature rich types of RE's available at present You can limit the search area within a file if desired It is a very comprehensive and useful tool, though maybe quite complex to use. Personally I use it in special cases where I need its power, and otherwise use the usual grep. In this episode I will give you the flavour of its capabilities and otherwise leave you to research more if it sounds interesting. Installing ack The tool can be found in repositories. I use Debian, and ack is in the Debian repo and can be installed with: sudo apt install ack Installing it this way the version I have (and am describing here) is 3.6.0. There is a new version, 3.7.0 available from the website. The documentation on the website suggests installing it as a Perl module using CPAN, which is something I will do soon I think. Perl regular expressions These are very sophisticated. A project to convert the Perl regular expression capabilities into a portable library form was undertaken by Philip Hazel of Cambridge University in 1997, and was called Perl Compatible Regular Expressions or PCRE. Philip Hazel was the originator of the exim mail transfer agent (MTA, or mail server), and wanted to use PCRE within it. Since then PCRE (and later PCRE2) is the way regular expressions are implemented in a lot of other software, which shows how widespread use of the Perl RE has become. The ack documentation refers to the Perl manual for details of this type of regular expression, and to a tutorial, if you wish to gain a deeper understanding. It should be noted that GNU grep can use Perl compatible regular expressions when matching lines in files, but this feature is marked as experimental. File types The ack command has rules for recognising file types. It does this by looking at the name extensions ('.html' or '.py' for example), and in some cases by examining their contents. The complete list of types can be found by running: ack --help-types … or, for a more detailed but less readable list: ack --dump Some examples are: cc for C files haskell for Haskell files lua for Lua files python for Python files shell for Bash, and other shell command files These names can be used with the options -t TYPE and --type=TYPE and also by simply preceding them with two dashes (--TYPE). There are also ways of requesting files not of a given type: -T TYPE, --type=noTYPE and --noTYPE. To check files in the current directory of type shell an ack command like the following might be used and the following type of output produced: $ ack --shell declare Bash_snippet__using_coproc_with_SQLite/examples/coproc_test.sh 11:declare -a com=('date +%F' 'whoami' 'id' 'echo "$BASH_VERSION"' Note that ack reports the file path and numbered lines within it that match. You can add your own file types to ack. There is a configuration file called .ackrc in which new types can be declared. See below for more information. The file type feature is one that makes me use ack again and again. The .ackrc file This file contains “command-line options that are prepended to the command line before processing”. It's a useful way to add new types (or even modify existing ones). It can be located in a number of places. Mine is ~/.ackrc with other configuration files in my home directory. It's possible to generate a new .ackrc with the option --create-ackrc. This saves all the default settings in the file which makes it simple to adjust anything you need to change. As an example of a change, I have Markdown files with the extension .mkd. However, by default ack only recognises .md, and .markdown. To add .mkd to the list I can add one of the following to the .ackrc: # Either add `.mkd` to the list --type-add=markdown:ext:mkd # or replace the list with a new one --type-set=markdown:ext:md,mkd,markdown Note that lines beginning with # are comments. Note also that --type-add and --type-set have to be followed by an = sign, not a space in this file. If you examine the settings with ack --dump you will see the default command and the one you have added. If you use ack --help-types you will see the new extension added to the default list. markdown .md .markdown; .mkd If I use this to search files in the directory where I keep my HPR episodes I see: $ ack --markdown 'inner ear' Hacking_my_inner_ear/hpr2109_full_shownotes.mkd 24:became fascinated by the structure of the human [inner ear][2], and studied it 28:The human inner ear performs two major functions: . . . Quick review of selected ack options Usage The ack command is designed to be similar in as many respects as possible to grep. The command is used in general as follows: ack [OPTION]... PATTERN [FILES OR DIRECTORIES] The [OPTION] part denotes any options (some discussed below) and PATTERN is the PCRE search pattern. There are some cases where this must be omitted - such as when files of a particular type are being listed. See example 1 below for such a case. In some cases a particular file is being searched, or all files in certain directories, and that is what [FILES OR DIRECTORIES] denotes. The full documentation for ack can be seen with the usual man ack command, and also using ack --man. There is also an option --help which gives a summary of all of the available options. Options There are many options specific to ack and some in common with grep, and we'll look at just a few here: -i - like grep this makes the matched pattern case insensitive. -f - Only print the files that would be searched, without actually doing any searching. See example 1 below. -g - Same as -f, but only select files whose names match PATTERN. This interacts with file type searches like --html, so beware. -l - reports the file names which contain matches for a given pattern -L - reports the file names which do not contain matches for a given pattern -c - reports file names and the number of matches; used on its own it reports all files, those that match and those that do not. If used with -l then you only see the names of file that have matches, as well as a count of matches. See example 2 below. -w - forces the search pattern to match only whole words. See example 3 below. (Note: there is an equivalent in GNU grep, which I had not checked when I recorded the audio). Examples 1. Find all Markdown files in a directory Using the -f option: $ ack --markdown -f Nitecore_Tube_torch/ Nitecore_Tube_torch/README.mkd Nitecore_Tube_torch/container.mkd Nitecore_Tube_torch/index.mkd Nitecore_Tube_torch/shownotes.mkd Using the -g option: $ ack -g '\.mkd$' Nitecore_Tube_torch/ Nitecore_Tube_torch/README.mkd Nitecore_Tube_torch/container.mkd Nitecore_Tube_torch/index.mkd Nitecore_Tube_torch/shownotes.mkd 2. Names of files that contain a match, with a match count Using the -l and -c options: $ ack --markdown -lci '\bear\b' Hacking_my_inner_ear/hpr2109_full_shownotes.mkd:11 Hacking_my_inner_ear/shownotes.mkd:3 An_overview_of_the_ack_command/shownotes.mkd:6 The sequence '\b' in Perl regular expressions is a boundary such as a word boundary. So the pattern is looking for the word 'ear' as opposed to the characters 'ear' (as in 'pearl' for example). Note how the single-letter options -l, -c and -i can be concatenated. 3. Searching for words in a simpler way In example 2 the \b boundaries ensured the pattern matched words rather than letter sequences. This can be simplified by using the -w option: $ ack --markdown -lci -w 'ear' Hacking_my_inner_ear/hpr2109_full_shownotes.mkd:11 Hacking_my_inner_ear/shownotes.mkd:3 An_overview_of_the_ack_command/shownotes.mkd:6 Links The ack website: ack! Perl regular expressions: RE reference manual RE tutorial PCRE: Perl Compatible Regular Expressions: Wikipedia article on PCRE Wikipedia article on Philip Hazel

This short clip can explain the ex CPAN girlfriend.. https://fb.watch/lF1GLlY1kN/

About Malekeh Amini:Malekeh Amini is a veteran in the healthcare industry with more than 25 years in digital health services and a proven track record in entrepreneurship, strategy, business development, fundraising, and operations. Malekeh founded Trayt to help shift the paradigm in how mental healthcare is accessed, delivered, and supported in the United States due to her own experience attempting to navigate the healthcare system. Malekeh brings extensive entrepreneurial, fundraising, P&L, business development, operations, and strategic advisory experience to Trayt, including experience with both SaaS and big data applications with a focus on scalability, and capitalizing on new business opportunities with deep knowledge of the healthcare industry and a strong national network of connections for strategic partnerships. At Trayt, Malekeh serves as Founder and CEO.Prior to Trayt, Malekeh was the Senior Vice President of Product & Business Development at Base Health, where she provided the vision connecting new breakthroughs in medical science to the needs of healthcare organizations and consumers. A former consultant with the Boston Consulting Group (BCG) and the Parthenon Group, Malekeh advised companies in the pharmaceutical, biotech, health insurance, and hospital industries. Malekeh also sat on the fundraising Board of Baylor College of Medicine in Houston, Texas, is the Fund Chair for her class at the Harvard Business School, and is Chairman of the Board at Wings Learning Center, a Non-Public School for students with autism and other neurodevelopmental disabilities.Malekeh earned multiple bachelor's degrees and a master's degree at USC, as well as an MBA from Harvard University.About Laurel Williams:Laurel L. Williams, DO is a Professor in the Menninger Department of Psychiatry and Behavioral Science at Baylor College of Medicine. Dr. Williams is the Medical Director for the Centralized Operational Support Hub for the Texas Child Mental Health Care Consortium coordinating the implementation of a state-wide child psychiatry access network and tele-mental health to youth in schools. Dr. Williams is also the Training Director for Child and Adolescent Psychiatry at Baylor. Dr. Williams completed both her fellowship and residency training at Baylor College of Medicine in 2004 upon graduation from the University of North Texas School of Osteopathic Medicine in 1999. She graduated with a BS in Psychobiology and a Minor in Fine Arts at the University of Southern California in 1994. In 2020, Dr. Williams received a Women of Excellence Award and a Norton Rose Educational Leadership Faculty Excellence Award at Baylor College of Medicine. In 2021, Greater Houston NAMI presented Dr. Williams with one of the “Heroes and Hope Across Greater Houston awards.” Dr. Williams has special expertise in working with youth who have suicidal and self-injurious behaviors and pregnant and post-partum adolescents.Things You'll Learn:Early intervention in childhood is crucial for addressing mental health disorders and can have a significant impact on long-term outcomes.The Texas Child Mental Health Consortium shows the power of collaboration and coordination among various stakeholders to enhance access to healthcare and training.Over 10,000 providers in the state of Texas have enrolled in CPAN.Over 500 school districts are currently enrolled in TCHATT with over 2000 campuses.Technology plays a pivotal role in improving access to care, streamlining workflows, and collecting valuable data for informed decision-making in children's mental health.The success of the Texas Consortium's initiatives illustrates the potential for nationwide implementation of similar programs to enhance mental health support for children.Building and maintaining connections among healthcare professionals, patients, and their families are essential for delivering effective mental healthcare services for children.Resources:Connect with and follow Malekeh Amini on LinkedIn.Follow Trayt on LinkedIn.Explore the Trayt Website.Connect with and follow Laurel Williams on LinkedIn.Follow Baylor College of Medicine on LinkedIn.Explore the Baylor College of Medicine Website.

There is ALWAYS a narcissist be hide the narcissist we was with. And that is usually there mothers , as most of the time mothers are the parent who bring up the child . And from there is how narcissists are created . Sharon is a classic CPAN . And her mother most probably a venerable narcissist (a covert narcissist)

My ex CPAN said to me her and her (toxic narc family) are going to hurt me . Cold sobering words , from someone who said she loved me . These people do not see things like regular people they make up lies and stories to tie into their false self and then enabled by narc families…

Look out for the narcissist family , with no friends and always drama in their family. Racist and bigoted views . Once you know the traits you can see them . My ex CPAN lives with her narcissist, racist, bigot family in Motherwell . Be careful of them they lie to police and cheat and manipulate the justice system to get their vengeance on people

The CPAN had the most terrifying stare and a good many times she unleashed her narcissist stare , I had never felt so uncomfortable

CME link for the Episode 17:     https://cmetracker.net/UTHSCSA/Publisher?page=pubOpen#/getCertificate/10092800   Episode 17: After the Nashville School Shooting: How to Process, Cope, and Talk About Really Sad Things FACULTY: Dr. Jessica Sandoval is an assistant clinical professor for the Child and Adolescent Psychiatry Division at UT Health San Antonio. She is double board certified in adult and child psychiatry, with 13 years of experience in child and adolescent psychiatry. Dr. Sandoval has experience working in the community with underserved/underrepresented populations. Her clinical interests are in trauma/PTSD.   OVERVIEW: Host Holly Wayment talks to Dr. Jessica Sandoval on advice for practitioners on how to talk to parents/caregivers about how to talk to children about really sad things, and also how all of us working in the pediatric world can help ourselves during this heartbreaking time in light of the Nashville school shooting.  We'll also discuss new psychiatric/therapy resources for children. * CPAN, Child Psychiatry Access Network: 1-888-901-CPAN * TCHATT, Texas Child Health Access Through Telemedicine 210-567-5460 * Trauma Research study, Contact information for families: Email: TraumaStudy@UTHealthSA.org Or call: (210) 567-8016 Or, to reach the Program Director, Amy S. Garrett, Ph.D contact me:  garrettas@uthscsa.edu Details : We are providing cost-free therapy for teens, ages 10-17, who have experienced a trauma or significant life stress and are having difficulties such as trouble sleeping, upsetting memories, irritability, or other symptoms.   Therapy is provided for 18 weeks, by licensed clinicians who are specialized in treating traumatic stress.  The research aspect of the program is that we are using MRI scans to study how brain activity improves during therapy. MRI is a safe medical procedure that has NO radiation, blood draws, or injections.   Compensation is provided for the MRIs, questionnaires and interviews. * TCHATT, or Texas Child Health Access Through Telemedicine, provides FREE mental and behavioral health services for students year round! TCHATT is a telemedicine program to address the mental and behavioral health needs of youth throughout Texas. UT Health San Antonio TCHATT now offers specialty care in person in  three areas! TCHATT EXPANSION SERVICES: - School Refusal For youth (5 y/o & up) who have persistent school avoidance or attendance issues due to anxiety and emotional distress - Substance Use For youth (12 y/o & up) whose alcohol or drug use is causing impairment or family conflict - Trauma For youth (5 y/o & up) who have experienced a traumatic event or loss and are having emotional or behavioral consequences such as PTSD Contact us for more information, to make a referral, or to obtain service. Office: (210) 567-5460 Fax: (210) 450-2450 Email: TCHATT@uthscsa.edu TCHATT is administered by the Texas Child Mental Health Care Consortium (TCMHCC). DISCLOSURES: Jessica Sandoval, MD has no financial relationships with ineligible companies to disclose.   The Pediatric Grand Rounds Planning Committee (Deepak Kamat, MD, PhD, Daniel Ranch, MD and Elizabeth Hanson, MD) has no financial relationships with ineligible companies to disclose.  Planning Committee member Steven Seidner, MD has disclosed he receives funding from Draeger Medical for the Clinical Study to Evaluate the Safety and Effectiveness of the Infinity Acute Care System Workstation Neonatal Care Babylog VN500 Device in High-Frequency Oscillatory Ventilation (HFOV) Mode in Extremely Low Birth Weight (ELBW) Neonates for which he is a co-principal investigator. The relevant financial relationships noted for Dr. Seidner have been mitigated.     The UT Health Science Center San Antonio and Deepak Kamat, MD course director and content reviewer for the activity, have reviewed all financial disclosure information for all speakers, facilitators, and planning committee members; and determined and resolved all conflicts of interests.   CONTINUING EDUCATION STATEMENTS: The UT Health Science Center San Antonio is accredited by the Accreditation Council for Continuing Medical Education to provide continuing education for physicians.   The UT Health Science Center San Antonio designates this live activity up to a maximum of 0.50 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.   CREDITS: AMA PRA Category 1 Credits™ (0.50) Non-Physician Participation Credit (0.50)    

Sharon the CPAN will be in handcuffs for the lies in police statement and false allegations , and also for coresive control and order emotional and mental abuse . Women are also abusers , learnt because she comes and came from a toxic abusive , racist family

The CPAN makes us feel insecure during the relationship to confuse us and then use that insecurity they created to control our feelings and emotions and then that turns into controlling us . It happened to me with my ex CPAN girlfriend, and it happens to many victims/ survivors of narcissistic abuse

The Mental Health Crisis and the Blueprint for Youth Suicide Prevention: the Role of the Pediatrician If you're a practitioner, click here for free credit. https://cmetracker.net/UTHSCSA/Publisher?page=pubOpen#/getCertificate/10092730   FACULTY Hilda Loria, MD, MPH, FAAP is an Assistant Professor of Pediatrics in the Division of Developmental-Behavioral Pediatrics at UT-Southwestern Medical Center.   OVERVIEW Host Holly Wayment talks to Hilda Loria, MD, MPH, FAAP about the Blueprint for Youth Suicide Prevention:  The Role of the Pediatrician and The Mental Health Crisis.  To reach Dr. Loria, please email her: Hilda.Loria@utsouthwestern.edu 988 https://988lifeline.org/ TCHATT and CPAN https://lsom.uthscsa.edu/psychiatry/clinical-programs/cpan-tchatt/ National Institutes of Mental Health - https://www.nimh.nih.gov/health/find-help If a Patient in Your Practice Dies by Suicide: https://www.aap.org/en/patient-care/blueprint-for-youth-suicide-prevention/strategies-for-clinical-settings-for-youth-suicide-prevention/if-a-patient-in-your-practice-dies-by-suicide/     DISCLOSURES Hilda Loria, MD, MPH, FAAP has no financial relationships with ineligible companies to disclose.   The Pediatric Grand Rounds Planning Committee (Deepak Kamat, MD, PhD, Daniel Ranch, MD and Elizabeth Hanson, MD) has no financial relationships with ineligible companies to disclose.  Planning Committee member Steven Seidner, MD has disclosed he receives funding from Draeger Medical for the Clinical Study to Evaluate the Safety and Effectiveness of the Infinity Acute Care System Workstation Neonatal Care Babylog VN500 Device in High-Frequency Oscillatory Ventilation (HFOV) Mode in Extremely Low Birth Weight (ELBW) Neonates for which he is a co-principal investigator. The relevant financial relationships noted for Dr. Seidner have been mitigated.     The UT Health Science Center San Antonio and Deepak Kamat, MD course director and content reviewer for the activity, have reviewed all financial disclosure information for all speakers, facilitators, and planning committee members; and determined and resolved all conflicts of interests.   CONTINUING EDUCATION STATEMENTS The UT Health Science Center San Antonio is accredited by the Accreditation Council for Continuing Medical Education to provide continuing medical education for physicians. The UT Health Science Center San Antonio designates this live activity up to a maximum of 0.75 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.   CREDITS AMA PRA Category 1 Credits™ (0.75) Non-Physician Participation Credit (0.75) Texas Medical Board of Ethics credit (0.75)

Joe Biden spent Presidents' Day in Ukraine as East Palestine burns and is abandoned. Pedophilia on the rise in America but will parents do anything about it? --- Support this podcast: https://podcasters.spotify.com/pod/show/matthew-dark/support

And tell stories they believe to play the victim .

塊根植物の栽培とDIY温室、家庭菜園と害獣、クラシックなInstagramの使い方について話しました。Shownotes コーデックス … 塊根植物とも。名前の通り根っこや幹が膨らんでる。みためがかわいい GORE-TEX 塊根(かいこん)植物･コーデックスとは？特徴や育て方･代表的な種類も紹介します アデニウム … 学名：Adenium, その他の名前：砂漠のバラ 科名 / 属名：キョウチクトウ科 / アデニウム属 メガニウム … チコリータの最終進化系。ポケモン第二世代で登場。 ガジュマル 貧者の薔薇(ミニチュアローズ) … 人間の底すらない悪意(進化)を！！ ぷらんちゅ … “植物を同定して進める恋愛ゲームです!” 是非プレイしてください。 ぷらんちゅの配信 by Researchat.fm … “分子生物学者がプレイする「植物同定恋愛ゲーム ぷらんちゅ」ぷらんちゅの作成者のまいんさんをお呼びし、ポッドキャスト番組Researchat.fmのメンバーで実況プレイしました。” レッドリスト ワシントン条約 オペルプリカリア　パキプス　… コーデックスの一種 コーデックスの種 … いくつか買って種から育ててみた。なお収録中に言及した、実生が実際にレッドリストに登録されている植物に与える影響はcoelaの独自見解です。 DIY温室 … こちら(https://mkskblog.com/caudex-onsitu/)のサイトなどを参考に作成してみました SwitchBot　温湿度計 ドラセナ ドラコ … 樹液が赤いことから竜血樹とも呼ばれる。いちいち名前がかっこいい。 マンドラゴラ(マンドレイク) コミフォラカタフ … これに関しては正直ノリで種を買ってみたのでどんな植物か正直良くわかってない（coela) researchatのインスタグラム ユーフォルビアステラータ … 和名(でいいのか？園芸名?）だと飛龍 リオレウス … モンハンの代表的モンスター ユーフォルピアイネリウス … 和名（？）だと九頭龍 竜舌蘭 … アガベ ディオスコレア エレファンティペス … 和名だと亀甲竜 チューリングパターン 近藤滋 フィボナッチ数列 ガンダムのヒロインとトマト … ガンダムTVシリーズ最新作「水星の魔女」のヒロインがトマト育ててます（参考） フェノール入り -> フェノールフタレイン ツイン・ピークス … みんなコーヒー、ドーナッツ、ダイナーにあこがれたよな？ Instagram (Wikipedia) … インスタグラムは2010/10/06らしいので本当に多分石黒は古参とのことですが、確認したら最初のラーメン画像の投稿は、2011年3月21日でした。インスタの日本語サービスが2014年に始まる随分と前ですね。この頃はインスタ映えみたいな感じじゃなかったな。 yorufukuro 中吊り広告 … old media 根津のたい焼き屋 CPAN Editorial Notes かつて無いほどにアライグマが嫌いになりました (soh) いつまで続くか正直謎ですが、インスタグラムアカウントもよろしくおねがいします！！(coela) 植物に覆われていく…！(tadasu)

This is what I would say to my ex CPAN girlfriend . I am sorry you have a personality disorder, I wish you haven't, sorry you come from the family that you do, wish you didn't use and abuse me and blame me for what you did to me and you acted and played a victim . I understand what you are . Really wish you wasn't a covert passive aggressive narcissist

The female CPAN targeted me , used me and abused me. She would of done this before and since discarding me. These female narcissist are experts at playing a victim. So she can get control as she has none in her projected life. But behide closed doors it's another story

.

This is a message to my ex CPAN next victim , there will be another , she will tell you I was the “crazy” one , as narcissist do. You will see and hear the truth , something won't be right , you won't be able to put your finger on it. I have the truth for you , I am a survivor of who she is and her narcissist family.

Most narcissist are raised by narcissist and /or have narcissist family members. My ex CPAN girlfriend is no different she comes from a covert narcissist mother and two narcissist sisters

CPAN women , are some of the most dangerous, this is why

CPAN was the first open-source software module repository. And on this day, Aug 1st, in 1995, CPAN was first announced to a private group of PERL users. If you are building things today by pulling in various packages from various open source places – and really, who isn't – then the history of how this world came to be is essential. Episode Page Support The Show Subscribe To The Podcast Join The Newsletter

This is why a female CPAN will cheat with married men , and why they don't care about the women who are married to these men , they give themselves the lie that they are just “friends”

In this episode, Jillian explores the topics of incivility and workplace violence prevention with a panel of NPD experts—Connie Hardy Tabet, MSN, RN, CPAN, CAPA, FASPAN, Katie Ann Blanchard, MSN, RN, NPD-BC, CNE, CPP, CTM, and Katlyn Jackson, MN, RN. Join Jillian Russell, MSN, RN, NPD-BC for monthly episodes analyzing information gathered through environmental scanning and discussing NPD implications that you can apply to your daily practice.  Visit www.anpd.org for more information. #NPDsoundbites 

The con artist that is the female CPAN

.

About AmyAmy Tobey has worked in tech for more than 20 years at companies of every size, working with everything from kernel code to user interfaces. These days she spends her time building an innovative Site Reliability Engineering program at Equinix, where she is a principal engineer. When she's not working, she can be found with her nose in a book, watching anime with her son, making noise with electronics, or doing yoga poses in the sun.Links Referenced: Equinix Metal: https://metal.equinix.com Personal Twitter: https://twitter.com/MissAmyTobey Personal Blog: https://tobert.github.io/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning-fast processing power, courtesy of third-gen AMD EPYC processors without the IO or hardware limitations of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general-purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices and say goodbye to noisy neighbors and egregious egress forever. Vultr delivers the power of the cloud with none of the bloat. “Screaming in the Cloud” listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G-E-T-V-U-L-T-R dot com slash screaming. My thanks to them for sponsoring this ridiculous podcast.Corey: Finding skilled DevOps engineers is a pain in the neck! And if you need to deploy a secure and compliant application to AWS, forgettaboutit! But that's where DuploCloud can help. Their comprehensive no-code/low-code software platform guarantees a secure and compliant infrastructure in as little as two weeks, while automating the full DevSecOps lifestyle. Get started with DevOps-as-a-Service from DuploCloud so that your cloud configurations are done right the first time. Tell them I sent you and your first two months are free. To learn more visit: snark.cloud/duplo. Thats's snark.cloud/D-U-P-L-O-C-L-O-U-D.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Every once in a while I catch up with someone that it feels like I've known for ages, and I realize somehow I have never been able to line up getting them on this show as a guest. Today is just one of those days. And my guest is Amy Tobey who has been someone I've been talking to for ages, even in the before-times, if you can remember such a thing. Today, she's a Senior Principal Engineer at Equinix. Amy, thank you for finally giving in to my endless wheedling.Amy: Thanks for having me. You mentioned the before-times. Like, I remember it was, like, right before the pandemic we had beers in San Francisco wasn't it? There was Ian there—Corey: Yeah, I—Amy: —and a couple other people. It was a really great time. And then—Corey: I vaguely remember beer. Yeah. And then—Amy: And then the world ended.Corey: Oh, my God. Yes. It's still March of 2020, right?Amy: As far as I know. Like, I haven't checked in a couple years.Corey: So, you do an awful lot. And it's always a difficult question to ask someone, so can you encapsulate your entire existence in a paragraph? It's—Amy: [sigh].Corey: —awful, so I'd like to give a bit more structure to it. Let's start with the introduction: You are a Senior Principal Engineer. We know it's high level because of all the adjectives that get put in there, and none of those adjectives are ‘associate' or ‘beginner' or ‘junior,' or all the other diminutives that companies like to play games with to justify paying people less. And you're at Equinix, which is a company that is a bit unlike most of the, shall we say, traditional cloud providers. What do you do over there and both as a company, as a person?Amy: So, as a company Equinix, what most people know about is that we have a whole bunch of data centers all over the world. I think we have the most of any company. And what we do is we lease out space in that data center, and then we have a number of other products that people don't know as well, which one is Equinix Metal, which is what I specifically work on, where we rent you bare-metal servers. None of that fancy stuff that you get any other clouds on top of it, there's things you can get that are… partner things that you can add-on, like, you know, storage and other things like that, but we just deliver you bare-metal servers with really great networking. So, what I work on is the reliability of that whole system. All of the things that go into provisioning the servers, making them come up, making sure that they get delivered to the server, make sure the API works right, all of that stuff.Corey: So, you're on the Equinix cloud side of the world more so than you are on the building data centers by the sweat of your brow, as they say?Amy: Correct. Yeah, yeah. Software side.Corey: Excellent. I spent some time in data centers in the early part of my career before cloud ate that. That was sort of cotemporaneous with the discovery that I'm the hardware destruction bunny, and I should go to great pains to keep my aura from anything expensive and important, like, you know, the SAN. So—Amy: Right, yeah.Corey: Companies moving out of data centers, and me getting out was a great thing.Amy: But the thing about SANs though, is, like, it might not be you. They're just kind of cursed from the start, right? They just always were kind of fussy and easy to break.Corey: Oh, yeah. I used to think—and I kid you not—that I had a limited upside to my career in tech because I sometimes got sloppy and I was fairly slow at crimping ethernet cables.Amy: [laugh].Corey: That is very similar to growing up in third grade when it became apparent that I was going to have problems in my career because my handwriting was sloppy. Yeah, it turns out the future doesn't look like we predicted it would.Amy: Oh, gosh. Are we going to talk about, like, neurological development now or… [laugh] okay, that's a thing I struggle with, too right, is I started typing as soon as they would let—in fact, before they would let me. I remember in high school, I had teachers who would grade me down for typing a paper out. They want me to handwrite it and I would go, “Cool. Go ahead and take a grade off because if I handwrite it, you're going to take two grades off my handwriting, so I'm cool with this deal.”Corey: Yeah, it was pretty easy early on. I don't know when the actual shift was, but it became more and more apparent that more and more things are moving towards a world where you could type. And I was almost five when I started working on that stuff, and that really wound up changing a lot of aspects of how I started seeing things. One thing I think you're probably fairly well known for is incidents. I want to be clear when I say that you are not the root cause as—“So, why are things broken?” “It's Amy again. What's she gotten into this time?” Great.Amy: [laugh]. But it does happen, but not all the time.Corey: Exa—it's a learning experience.Amy: Right.Corey: You've also been deeply involved with SREcon and a number of—a lot of aspects of what I will term—and please don't yell at me for this—SRE culture—Amy: Yeah.Corey: Which is sometimes a challenging thing to wind up describing or putting a definition around. The one that I've always been somewhat partial to is, “SRE is DevOps, except you worked at Google for a while.” I don't know how necessarily accurate that is, but it does rile people up.Amy: Yeah, it does. Dave Stanke actually did a really great talk at SREcon San Francisco just a couple weeks ago, about the DORA report. And the new DORA report, they split SRE out into its own function and kind of is pushing against that old model, which actually comes from Liz Fong-Jones—I think it's from her, or older—about, like, class SRE implements DevOps, which is kind of this idea that, like, SREs make DevOps happen. Things have evolved, right, since then. Things have evolved since Google released those books, and we're all just figured out what works and what doesn't a little bit.And so, it's not that we're implementing DevOps so much. In fact, it's that ops stuff that kind of holds us back from the really high impact work that SREs, I think, should be doing, that aren't just, like, fixing the problems, the symptoms down at the bottom layer, right? Like what we did as sysadmins 20 years ago. You know, we'd go and a lot of people are SREs that came out of the sysadmin world and still think in that mode, where it's like, “Well, I set up the systems, and when things break, I go and I fix them.” And, “Why did the developers keep writing crappy code? Why do I have to always getting up in the middle of the night because this thing crashed?”And it turns out that the work we need to do to make things more reliable, there's a ceiling to how far away the platform can take us, right? Like, we can have the best platform in the world with redundancy, and, you know, nine-way replicated data storage and all this crazy stuff, and still if we put crappy software on top, it's going to be unreliable. So, how do we make less crappy software? And for most of my career, people would be, like, “Well, you should test it.” And so, we started doing that, and we still have crappy software, so what's going on here? We still have incidents.So, we write more tests, and we still have incidents. We had a QA group, we still have incidents. We send the developers to training, and we still have incidents. So like, what is the thing we need to do to make things more reliable? And it turns out, most of it is culture work.Corey: My perspective on this stems from being a grumpy old sysadmin. And at some point, I started calling myself a systems engineer or DevOps or production engineer, or SRE. It was all from my point of view, the same job, but you know, if you call yourself a sysadmin, you're just asking for a 40% pay cut off the top.Amy: [laugh].Corey: But I still tended to view the world through that lens. I tended to be very good at Linux systems internals, for example, understanding system calls and the rest, but increasingly, as the DevOps wave or SRE wave, or Google-isation of the internet wound up being more and more of a thing, I found myself increasingly in job interviews, where, “Great, now, can you go wind up implementing a sorting algorithm on the whiteboard?” “What on earth? No.” Like, my lingua franca is shitty Bash, and no one tends to write that without a bunch of tab completions and quick checking with manpages—die.net or whatnot—on the fly as you go down that path.And it was awful, and I felt… like my skill set was increasingly eroding. And it wasn't honestly until I started this place where I really got into writing a fair bit of code to do different things because it felt like an orthogonal skill set, but the fullness of time, it seems like it's not. And it's a reskilling. And it made me wonder, does this mean that the areas of technology that I focused on early in my career, was that all a waste? And the answer is not really. Sometimes, sure, in that I don't spend nearly as much time worrying about inodes—for example—as I once did. But every once in a while, I'll run into something and I looked like a wizard from the future, but instead, I'm a wizard from the past.Amy: Yeah, I find that a lot in my work, now. Sometimes things I did 20 years ago, come back, and it's like, oh, yeah, I remember I did all that threading work in 2002 in Perl, and I learned everything the very, very, very hard way. And then, you know, this January, did some threading work to fix some stability issues, and all of it came flooding back, right? Just that the experiences really, more than the code or the learning or the text and stuff; more just the, like, this feels like threads [BLEEP]-ery. Is a diagnostic thing that sometimes we have to say.And then people are like, “Can you prove it?” And I'm like, “Not really,” because it's literally thread [BLEEP]-ery. Like, the definition of it is that there's weird stuff happening that we can't figure out why it's happening. There's something acting in the system that isn't synchronized, that isn't connected to other things, that's happening out of order from what we expect, and if we had a clear signal, we would just fix it, but we don't. We just have, like, weird stuff happening over here and then over there and over there and over there.And, like, that tells me there's just something happening at that layer and then have to go and dig into that right, and like, just basically charge through. My colleagues are like, “Well, maybe you should look at this, and go look at the database,” the things that they're used to looking at and that their experiences inform, whereas then I bring that ancient toiling through the threading mines experiences back and go, “Oh, yeah. So, let's go find where this is happening, where people are doing dangerous things with threads, and see if we can spot something.” But that came from that experience.Corey: And there's so much that just repeats itself. And history rhymes. The challenge is that, do you have 20 years of experience, or do you have one year of experience repeated 20 times? And as the tide rises, doing the same task by hand, it really is just a matter of time before your full-time job winds up being something a piece of software does. An easy example is, “Oh, what's your job?” “I manually place containers onto specific hosts.” “Well, I've got news for you, and you're not going to like it at all.”Amy: Yeah, yeah. I think that we share a little bit. I'm allergic to repeated work. I don't know if allergic is the right word, but you know, if I sit and I do something once, fine. Like, I'll just crank it out, you know, it's this form, or it's a datafile I got to write and I'll—fine I'll type it in and do the manual labor.The second time, the difficulty goes up by ten, right? Like, just mentally, just to do it, be like, I've already done this once. Doing it again is anathema to everything that I am. And then sometimes I'll get through it, but after that, like, writing a program is so much easier because it's like exponential, almost, growth in difficulty. You know, the third time I have to do the same thing that's like just typing the same stuff—like, look over here, read this thing and type it over here—I'm out; I can't do it. You know, I got to find a way to automate. And I don't know, maybe normal people aren't driven to live this way, but it's kept me from getting stuck in those spots, too.Corey: It was weird because I spent a lot of time as a consultant going from place to place and it led to some weird changes. For example, “Oh, thank God, I don't have to think about that whole messaging queue thing.” Sure enough, next engagement, it's message queue time. Fantastic. I found that repeating myself drove me nuts, but you also have to be very sensitive not to wind up, you know, stealing IP from the people that you're working with.Amy: Right.Corey: But what I loved about the sysadmin side of the world is that the vast majority of stuff that I've taken with me, lives in my shell config. And what I mean by that is I'm not—there's nothing in there is proprietary, but when you have a weird problem with trying to figure out the best way to figure out which Ruby process is stealing all the CPU, great, turns out that you can chain seven or eight different shell commands together through a bunch of pipes. I don't want to remember that forever. So, that's the sort of thing I would wind up committing as I learned it. I don't remember what company I picked that up at, but it was one of those things that was super helpful.I have a sarcastic—it's a one-liner, except no sane editor setting is going to show it in any less than three—of a whole bunch of Perl, piped into du, piped into the rest, that tells you one of the largest consumers of files in a given part of the system. And it rates them with stars and it winds up doing some neat stuff. I would never sit down and reinvent something like that today, but the fact that it's there means that I can do all kinds of neat tricks when I need to. It's making sure that as you move through your career, on some level, you're picking up skills that are repeatable and applicable beyond one company.Amy: Skills and tooling—Corey: Yeah.Amy: —right? Like, you just described the tool. Another SREcon talk was John Allspaw and Dr. Richard Cook talking about above the line; below the line. And they started with these metaphors about tools, right, showing all the different kinds of hammers.And if you're a blacksmith, a lot of times you craft specialized hammers for very specific jobs. And that's one of the properties of a tool that they were trying to get people to think about, right, is that tools get crafted to the job. And what you just described as a bespoke tool that you had created on the fly, that kind of floated under the radar of intellectual property. [laugh].So, let's not tell the security or IP people right? Like, because there's probably billions and billions of dollars of technically, like, made-up IP value—I'm doing air quotes with my fingers—you know, that's just basically people's shell profiles. And my God, the Emacs automation that people have done. If you've ever really seen somebody who's amazing at Emacs and is 10, 20, 30, maybe 40 years of experience encoded in their emacs settings, it's a wonder to behold. Like, I look at it and I go, “Man, I wish I could do that.”It's like listening to a really great guitar player and be like, “Wow, I wish I could play like them.” You see them just flying through stuff. But all that IP in there is both that person's collection of wisdom and experience and working with that code, but also encodes that stuff like you described, right? It's just all these little systems tricks and little fiddly commands and things we don't want to remember and so we encode them into our toolset.Corey: Oh, yeah. Anything I wound up taking, I always would share it with people internally, too. I'd mention, “Yeah, I'm keeping this in my shell files.” Because I disclosed it, which solves a lot of the problem. And also, none of it was even close to proprietary or anything like that. I'm sorry, but the way that you wind up figuring out how much of a disk is being eaten up and where in a more pleasing way, is not a competitive advantage. It just isn't.Amy: It isn't to you or me, but, you know, back in the beginning of our careers, people thought it was worth money and should be proprietary. You know, like, oh, that disk-checking script as a competitive advantage for our company because there are only a few of us doing this work. Like, it was actually being able to, like, manage your—[laugh] actually manage your servers was a competitive advantage. Now, it's kind of commodity.Corey: Let's also be clear that the world has moved on. I wound up buying a DaisyDisk a while back for Mac, which I love. It is a fantastic, pretty effective, “Where's all the stuff on your disk going?” And it does a scan and you can drive and collect things and delete them when trying to clean things out. I was using it the other day, so it's top of mind at the moment.But it's way more polished than that crappy Perl three-liner. And I see both sides, truly I do. The trick also, for those wondering [unintelligible 00:15:45], like, “Where is the line?” It's super easy. Disclose it, what you're doing, in those scenarios in the event someone is no because they believe that finding the right man page section for something is somehow proprietary.Great. When you go home that evening in a completely separate environment, build it yourself from scratch to solve the problem, reimplement it and save that. And you're done. There are lots of ways to do this. Don't steal from your employer, but your employer employs you; they don't own you and the way that you think about these problems.Every person I've met who has had a career that's longer than 20 minutes has a giant doc somewhere on some system of all of the scripts that they wound up putting together, all of the one-liners, the notes on, “Next time you see this, this is the thing to check.”Amy: Yeah, the cheat sheet or the notebook with all the little commands, or again the Emacs config, sometimes for some people, or shell profiles. Yeah.Corey: Here's the awk one-liner that I put that automatically spits out from an Apache log file what—the httpd log file that just tells me what are the most frequent talkers, and what are the—Amy: You should probably let go of that one. You know, like, I think that one's lifetime is kind of past, Corey. Maybe you—Corey: I just have to get it working with Nginx, and we're good to go.Amy: Oh, yeah, there you go. [laugh].Corey: Or S3 access logs. Perish the thought. But yeah, like, what are the five most high-volume talkers, and what are those relative to each other? Huh, that one thing seems super crappy and it's coming from Russia. But that's—hmm, one starts to wonder; maybe it's time to dig back in.So, one of the things that I have found is that a lot of the people talking about SRE seem to have descended from an ivory tower somewhere. And they're talking about how some of the best-in-class companies out there, renowned for their technical cultures—at least externally—are doing these things. But there's a lot more folks who are not there. And honestly, I consider myself one of those people who is not there. I was a competent engineer, but never a terrific one.And looking at the way this was described, I often came away thinking, “Okay, it was the purpose of this conference talk just to reinforce how smart people are, and how I'm not,” and/or, “There are the 18 cultural changes you need to make to your company, and then you can do something kind of like we were just talking about on stage.” It feels like there's a combination of problems here. One is making this stuff more accessible to folks who are not themselves in those environments, and two, how to drive cultural change as an individual contributor if that's even possible. And I'm going to go out on a limb and guess you have thoughts on both aspects of that, and probably some more hit me, please.Amy: So, the ivory tower, right. Let's just be straight up, like, the ivory tower is Google. I mean, that's where it started. And we get it from the other large companies that, you know, want to do conference talks about what this stuff means and what it does. What I've kind of come around to in the last couple of years is that those talks don't really reach the vast majority of engineers, they don't really apply to a large swath of the enterprise especially, which is, like, where a lot of the—the bulk of our industry sits, right? We spend a lot of time talking about the darlings out here on the West Coast in high tech culture and startups and so on.But, like, we were talking about before we started the show, right, like, the interior of even just America, is filled with all these, like, insurance and banks and all of these companies that are cranking out tons of code and servers and stuff, and they're trying to figure out the same problems. But they're structured in companies where their tech arm is still, in most cases, considered a cost center, often is bundled under finance, for—that's a whole show of itself about that historical blunder. And so, the tech culture is tend to be very, very different from what we experience in—what do we call it anymore? Like, I don't even want to say West Coast anymore because we've gone remote, but, like, high tech culture we'll say. And so, like, thinking about how to make SRE and all this stuff more accessible comes down to, like, thinking about who those engineers are that are sitting at the computers, writing all the code that runs our banks, all the code that makes sure that—I'm trying to think of examples that are more enterprise-y right?Or shoot buying clothes online. You go to Macy's for example. They have a whole bunch of servers that run their online store and stuff. They have internal IT-ish people who keep all this stuff running and write that code and probably integrating open-source stuff much like we all do. But when you go to try to put in a reliability program that's based on the current SRE models, like SLOs; you put in SLOs and you start doing, like, this incident management program that's, like, you know, you have a form you fill out after every incident, and then you [unintelligible 00:20:25] retros.And it turns out that those things are very high-level skills, skills and capabilities in an organization. And so, when you have this kind of IT mindset or the enterprise mindset, bringing the culture together to make those things work often doesn't happen. Because, you know, they'll go with the prescriptive model and say, like, okay, we're going to implement SLOs, we're going to start measuring SLIs on all of the services, and we're going to hold you accountable for meeting those targets. If you just do that, right, you're just doing more gatekeeping and policing of your tech environment. My bet is, reliability almost never improves in those cases.And that's been my experience, too, and why I get charged up about this is, if you just go slam in these practices, people end up miserable, the practices then become tarnished because people experienced the worst version of them. And then—Corey: And with the remote explosion as well, it turns out that changing jobs basically means their company sends you a different Mac, and the next Monday, you wind up signing into a different Slack team.Amy: Yeah, so the culture really matters, right? You can't cover it over with foosball tables and great lunch. You actually have to deliver tools that developers want to use and you have to deliver a software engineering culture that brings out the best in developers instead of demanding the best from developers. I think that's a fundamental business shift that's kind of happening. If I'm putting on my wizard hat and looking into the future and dreaming about what might change in the world, right, is that there's kind of a change in how we do leadership and how we do business that's shifting more towards that model where we look at what people are capable of and we trust in our people, and we get more out of them, the knowledge work model.If we want more knowledge work, we need people to be happy and to feel engaged in their community. And suddenly we start to see these kind of generational, bigger-pie kind of things start to happen. But how do we get there? It's not SLOs. It maybe it's a little bit starting with incidents. That's where I've had the most success, and you asked me about that. So, getting practical, incident management is probably—Corey: Right. Well, as I see it, the problem with SLOs across the board is it feels like it's a very insular community so far, and communicating it to engineers seems to be the focus of where the community has been, but from my understanding of it, you absolutely need buy-in at significantly high executive levels, to at the very least by you air cover while you're doing these things and making these changes, but also to help drive that cultural shift. None of this is something I have the slightest clue how to do, let's be very clear. If I knew how to change a company's culture, I'd have a different job.Amy: Yeah. [laugh]. The biggest omission in the Google SRE books was [Ers 00:22:58]. There was a guy at Google named Ers who owns availability for Google, and when anything is, like, in dispute and bubbles up the management team, it goes to Ers, and he says, “Thou shalt…” right? Makes the call. And that's why it works, right?Like, it's not just that one person, but that system of management where the whole leadership team—there's a large, very well-funded team with a lot of power in the organization that can drive availability, and they can say, this is how you're going to do metrics for your service, and this is the system that you're in. And it's kind of, yeah, sure it works for them because they have all the organizational support in place. What I was saying to my team just the other day—because we're in the middle of our SLO rollout—is that really, I think an SLO program isn't [clear throat] about the engineers at all until late in the game. At the beginning of the game, it's really about getting the leadership team on board to say, “Hey, we want to put in SLIs and SLOs to start to understand the functioning of our software system.” But if they don't have that curiosity in the first place, that desire to understand how well their teams are doing, how healthy their teams are, don't do it. It's not going to work. It's just going to make everyone miserable.Corey: It feels like it's one of those difficult to sell problems as well, in that it requires some tooling changes, absolutely. It requires cultural change and buy-in and whatnot, but in order for that to happen, there has to be a painful problem that a company recognizes and is willing to pay to make go away. The problem with stuff like this is that once you pay, there's a lot of extra work that goes on top of it as well, that does not have a perception—rightly or wrongly—of contributing to feature velocity, of hitting the next milestone. It's, “Really? So, we're going to be spending how much money to make engineers happier? They should get paid an awful lot and they're still complaining and never seem happy. Why do I care if they're happy other than the pure mercenary perspective of otherwise they'll quit?” I'm not saying that it's not worth pursuing; it's not a worthy goal. I am saying that it becomes a very difficult thing to wind up selling as a product.Amy: Well, as a product for sure, right? Because—[sigh] gosh, I have friends in the space who work on these tools. And I want to be careful.Corey: Of course. Nothing but love for all of those people, let's be very clear.Amy: But a lot of them, you know, they're pulling metrics from existing monitoring systems, they are doing some interesting math on them, but what you get at the end is a nice service catalog and dashboard, which are things we've been trying to land as products in this industry for as long as I can remember, and—Corey: “We've got it this time, though. This time we'll crack the nut.” Yeah. Get off the island, Gilligan.Amy: And then the other, like, risky thing, right, is the other part that makes me uncomfortable about SLOs, and why I will often tell folks that I talk to out in the industry that are asking me about this, like, one-on-one, “Should I do it here?” And it's like, you can bring the tool in, and if you have a management team that's just looking to have metrics to drive productivity, instead of you know, trying to drive better knowledge work, what you get is just a fancier version of more Taylorism, right, which is basically scientific management, this idea that we can, like, drive workers to maximum efficiency by measuring random things about them and driving those numbers. It turns out, that doesn't really work very well, even in industrial scale, it just happened to work because, you know, we have a bloody enough society that we pushed people into it. But the reality is, if you implement SLOs badly, you get more really bad Taylorism that's bad for you developers. And my suspicion is that you will get worse availability out of it than you would if you just didn't do it at all.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: That is part of the problem is, in some cases, to drive some of these improvements, you have to go backwards to move forwards. And it's one of those, “Great, so we spent all this effort and money in the rest of now things are worse?” No, not necessarily, but suddenly are aware of things that were slipping through the cracks previously.Amy: Yeah. Yeah.Corey: Like, the most realistic thing about first The Phoenix Project and then The Unicorn Project, both by Gene Kim, has been the fact that companies have these problems and actively cared enough to change it. In my experience, that feels a little on the rare side.Amy: Yeah, and I think that's actually the key, right? It's for the culture change, and for, like, if you really looking to be, like, do I want to work at this company? Am I investing my myself in here? Is look at the leadership team and be, like, do these people actually give a crap? Are they looking just to punt another number down the road?That's the real question, right? Like, the technology and stuff, at the point where I'm at in my career, I just don't care that much anymore. [laugh]. Just… fine, use Kubernetes, use Postgres, [unintelligible 00:27:30], I don't care. I just don't. Like, Oracle, I might have to ask, you know, go to finance and be like, “Hey, can we spend 20 million for a database?” But like, nobody really asks for that anymore, so. [laugh].Corey: As one does. I will say that I mostly agree with you, but a technology that I found myself getting excited about, given the time of the recording on this is… fun, I spent a bit of time yesterday—from when we're recording this—teaching myself just enough Go to wind up being together a binary that I needed to do something actively ridiculous for my camera here. And I found myself coming away deeply impressed by a lot of things about it, how prescriptive it was for one, how self-contained for another. And after spending far too many years of my life writing shitty Perl, and shitty Bash, and worse Python, et cetera, et cetera, the prescriptiveness was great. The fact that it wound up giving me something I could just run, I could cross-compile for anything I need to run it on, and it just worked. It's been a while since I found a technology that got me this interested in exploring further.Amy: Go is great for that. You mentioned one of my two favorite features of Go. One is usually when a program compiles—at least the way I code in Go—it usually works. I've been working with Go since about 0.9, like, just a little bit before it was released as 1.0, and that's what I've noticed over the years of working with it is that most of the time, if you have a pretty good data structure design and you get the code to compile, usually it's going to work, unless you're doing weird stuff.The other thing I really love about Go and that maybe you'll discover over time is the malleability of it. And the reason why I think about that more than probably most folks is that I work on other people's code most of the time. And maybe this is something that you probably run into with your business, too, right, where you're working on other people's infrastructure. And the way that we encode business rules and things in the languages, in our programming language or our config syntax and stuff has a huge impact on folks like us and how quickly we can come into a situation, assess, figure out what's going on, figure out where things are laid out, and start making changes with confidence.Corey: Forget other people for a minute they're looking at what I built out three or four years ago here, myself, like, I look at past me, it's like, “What was that rat bastard thinking? This is awful.” And it's—forget other people's code; hell is your own code, on some level, too, once it's slipped out of the mental stack and you have to re-explore it and, “Oh, well thank God I defensively wound up not including any comments whatsoever explaining what the living hell this thing was.” It's terrible. But you're right, the other people's shell scripts are finicky and odd.I started poking around for help when I got stuck on something, by looking at GitHub, and a few bit of searching here and there. Even these large, complex, well-used projects started making sense to me in a way that I very rarely find. It's, “What the hell is that thing?” is my most common refrain when I'm looking at other people's code, and Go for whatever reason avoids that, I think because it is so prescriptive about formatting, about how things should be done, about the vision that it has. Maybe I'm romanticizing it and I'll hate it and a week from now, and I want to go back and remove this recording, but.Amy: The size of the language helps a lot.Corey: Yeah.Amy: But probably my favorite. It's more of a convention, which actually funny the way I'm going to talk about this because the two languages I work on the most right now are Ruby and Go. And I don't feel like two languages could really be more different.Syntax-wise, they share some things, but really, like, the mental models are so very, very different. Ruby is all the way in on object-oriented programming, and, like, the actual real kind of object-oriented with messaging and stuff, and, like, the whole language kind of springs from that. And it kind of requires you to understand all of these concepts very deeply to be effective in large programs. So, what I find is, when I approach Ruby codebase, I have to load all this crap into my head and remember, “Okay, so yeah, there's this convention, when you do this kind of thing in Ruby”—or especially Ruby on Rails is even worse because they go deep into convention over configuration. But what that's code for is, this code is accessible to people who have a lot of free cognitive capacity to load all this convention into their heads and keep it in their heads so that the code looks pretty, right?And so, that's the trade-off as you said, okay, my developers have to be these people with all these spare brain cycles to understand, like, why I would put the code here in this place versus this place? And all these, like, things that are in the code, like, very compact, dense concepts. And then you go to something like Go, which is, like, “Nah, we're not going to do Lambdas. Nah”—[laugh]—“We're not doing all this fancy stuff.” So, everything is there on the page.This drives some people crazy, right, is that there's all this boilerplate, boilerplate, boilerplate. But the reality is, I can read most Go files from top to the bottom and understand what the hell it's doing, whereas I can go sometimes look at, like, a Ruby thing, or sometimes Python and e—Perl is just [unintelligible 00:32:19] all the time, right, it's there's so much indirection. And it just be, like, “What the [BLEEP] is going on? This is so dense. I'm going to have to sit down and write it out in longhand so I can understand what the developer was even doing here.” And—Corey: Well, that's why I got the Mac Studio; for when I'm not doing A/V stuff with it, that means that I'll have one core that I can use for, you know, front-end processing and the rest, and the other 19 cores can be put to work failing to build Nokogiri in Ruby yet again.Amy: [laugh].Corey: I remember the travails of working with Ruby, and the problem—I have similar problems with Python, specifically in that—I don't know if I'm special like this—it feels like it's a SRE DevOps style of working, but I am grabbing random crap off a GitHub constantly and running it, like, small scripts other people have built. And let's be clear, I run them on my test AWS account that has nothing important because I'm not a fool that I read most of it before I run it, but I also—it wants a different version of Python every single time. It wants a whole bunch of other things, too. And okay, so I use ASDF as my version manager for these things, which for whatever reason, does not work for the way that I think about this ergonomically. Okay, great.And I wind up with detritus scattered throughout my system. It's, “Hey, can you make this reproducible on my machine?” “Almost certainly not, but thank you for asking.” It's like ‘Step 17: Master the Wolf' level of instructions.Amy: And I think Docker generally… papers over the worst of it, right, is when we built all this stuff in the aughts, you know, [CPAN 00:33:45]—Corey: Dev containers and VS Code are very nice.Amy: Yeah, yeah. You know, like, we had CPAN back in the day, I was doing chroots, I think in, like, '04 or '05, you know, to solve this problem, right, which is basically I just—screw it; I will compile an entire distro into a directory with a Perl and all of its dependencies so that I can isolate it from the other things I want to run on this machine and not screw up and not have these interactions. And I think that's kind of what you're talking about is, like, the old model, when we deployed servers, there was one of us sitting there and then we'd log into the server and be like, I'm going to install the Perl. You know, I'll compile it into, like, [/app/perl 558 00:34:21] whatever, and then I'll CPAN all this stuff in, and I'll give it over to the developer, tell them to set their shebang to that and everything just works. And now we're in a mode where it's like, okay, you got to set up a thousand of those. “Okay, well, I'll make a tarball.” [laugh]. But it's still like we had to just—Corey: DevOps, but [unintelligible 00:34:37] dev closer to ops. You're interrelating all the time. Yeah, then Docker comes along, and add dev is, like, “Well, here's the container. Good luck, asshole.” And it feels like it's been cast into your yard to worry about.Amy: Yeah, well, I mean, that's just kind of business, or just—Corey: Yeah. Yeah.Amy: I'm not sure if it's business or capitalism or something like that, but just the idea that, you know, if I can hand off the shitty work to some other poor schlub, why wouldn't I? I mean, that's most folks, right? Like, just be like, “Well”—Corey: Which is fair.Amy: —“I got it working. Like, my part is done, I did what I was supposed to do.” And now there's a lot of folks out there, that's how they work, right? “I hit done. I'm done. I shipped it. Sure. It's an old [unintelligible 00:35:16] Ubuntu. Sure, there's a bunch of shell scripts that rip through things. Sure”—you know, like, I've worked on repos where there's hundreds of things that need to be addressed.Corey: And passing to someone else is fine. I'm thrilled to do it. Where I run into problems with it is where people assume that well, my part was the hard part and anything you schlubs do is easy. I don't—Amy: Well, that's the underclass. Yeah. That's—Corey: Forget engineering for a second; I throw things to the people over in the finance group here at The Duckbill Group because those people are wizards at solving for this thing. And it's—Amy: Well, that's how we want to do things.Corey: Yeah, specialization works.Amy: But we have this—it's probably more cultural. I don't want to pick, like, capitalism to beat on because this is really, like, human cultural thing, and it's not even really particularly Western. Is the idea that, like, “If I have an underclass, why would I give a shit what their experience is?” And this is why I say, like, ops teams, like, get out of here because most ops teams, the extant ops teams are still called ops, and a lot of them have been renamed SRE—but they still do the same job—are an underclass. And I don't mean that those people are below us. People are treated as an underclass, and they shouldn't be. Absolutely not.Corey: Yes.Amy: Because the idea is that, like, well, I'm a fancy person who writes code at my ivory tower, and then it all flows down, and those people, just faceless people, do the deployment stuff that's beneath me. That attitude is the most toxic thing, I think, in tech orgs to address. Like, if you're trying to be like, “Well, our liability is bad, we have security problems, people won't fix their code.” And go look around and you will find people that are treated as an underclass that are given codes thrown over the wall at them and then they just have to toil through and make it work. I've worked on that a number of times in my career.And I think just like saying, underclass, right, or caste system, is what I found is the most effective way to get people actually thinking about what the hell is going on here. Because most people are just, like, “Well, that's just the way things are. It's just how we've always done it. The developers write to code, then give it to the sysadmins. The sysadmins deploy the code. Isn't that how it always works?”Corey: You'd really like to hope, wouldn't you?Amy: [laugh]. Not me. [laugh].Corey: Again, the way I see it is, in theory—in theory—sysadmins, ops, or that should not exist. People should theoretically be able to write code as developers that just works, the end. And write it correct the first time and never have to change it again. Yeah. There's a reason that I always like to call staging environments in places I work ‘theory' because it works in theory, but not in production, and that is fundamentally the—like, that entire job role is the difference between theory and practice.Amy: Yeah, yeah. Well, I think that's the problem with it. We're already so disconnected from the physical world, right? Like, you and I right now are talking over multiple strands of glass and digital transcodings and things right now, right? Like, we are detached from the physical reality.You mentioned earlier working in data centers, right? The thing I miss about it is, like, the physicality of it. Like, actually, like, I held a server in my arms and put it in the rack and slid it into the rails. I plugged into power myself; I pushed the power button myself. There's a server there. I physically touched it.Developers who don't work in production, we talked about empathy and stuff, but really, I think the big problem is when they work out in their idea space and just writing code, they write the unit tests, if we're very lucky, they'll write a functional test, and then they hand that wad off to some poor ops group. They're detached from the reality of operations. It's not even about accountability; it's about experience. The ability to see all of the weird crap we deal with, right? You know, like, “Well, we pushed the code to that server, but there were three bit flips, so we had to do it again. And then the other server, the disk failed. And on the other server…” You know? [laugh].It's just, there's all this weird crap that happens, these systems are so complex that they're always doing something weird. And if you're a developer that just spends all day in your IDE, you don't get to see that. And I can't really be mad at those folks, as individuals, for not understanding our world. I figure out how to help them, and the best thing we've come up with so far is, like, well, we start giving this—some responsibility in a production environment so that they can learn that. People do that, again, is another one that can be done wrong, where it turns into kind of a forced empathy.I actually really hate that mode, where it's like, “We're forcing all the developers online whether they like it or not. On-call whether they like it or not because they have to learn this.” And it's like, you know, maybe slow your roll a little buddy because the stuff is actually hard to learn. Again, minimizing how hard ops work is. “Oh, we'll just put the developers on it. They'll figure it out, right? They're software engineers. They're probably smarter than you sysadmins.” Is the unstated thing when we do that, right? When we throw them in the pit and be like, “Yeah, they'll get it.” [laugh].Corey: And that was my problem [unintelligible 00:39:49] the interview stuff. It was in the write code on a whiteboard. It's, “Look, I understood how the system fundamentally worked under the hood.” Being able to power my way through to get to an outcome even in language I don't know, was sort of part and parcel of the job. But this idea of doing it in artificially constrained environment, in a language I'm not super familiar with, off the top of my head, it took me years to get to a point of being able to do it with a Bash script because who ever starts with an empty editor and starts getting to work in a lot of these scenarios? Especially in an ops role where we're not building something from scratch.Amy: That's the interesting thing, right? In the majority of tech work today—maybe 20 years ago, we did it more because we were literally building the internet we have today. But today, most of the engineers out there working—most of us working stiffs—are working on stuff that already exists. We're making small incremental changes, which is great that's what we're doing. And we're dealing with old code.Corey: We're gluing APIs together, and that's fine. Ugh. I really want to thank you for taking so much time to talk to me about how you see all these things. If people want to learn more about what you're up to, where's the best place to find you?Amy: I'm on Twitter every once in a while as @MissAmyTobey, M-I-S-S-A-M-Y-T-O-B-E-Y. I have a blog I don't write on enough. And there's a couple things on the Equinix Metal blog that I've written, so if you're looking for that. Otherwise, mainly Twitter.Corey: And those links will of course be in the [show notes 00:41:08]. Thank you so much for your time. I appreciate it.Amy: I had fun. Thank you.Corey: As did I. Amy Tobey, Senior Principal Engineer at Equinix. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or on the YouTubes, smash the like and subscribe buttons, as the kids say. Whereas if you've hated this episode, same thing, five-star review all the platforms, smash the buttons, but also include an angry comment telling me that you're about to wind up subpoenaing a copy of my shell script because you're convinced that your intellectual property and secrets are buried within.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

On this episode of Melody and Friends, Melody speaks with author and speaker Debbie Mirza about covert passive aggressive narcissists and why they can be so difficult to detect in a relationship. Debbie shares her story of being married to a covert narcissist for almost 22 years and talks about her own healing as she went through a time of isolation. She and Melody discuss the signs to look for in someone who may be a covert narcissist, their different methods of manipulating their victims and what you can do to escape that relationship and begin your journey of healing and restoration. Our listeners can get in contact with Debbie and purchase her books including The Covert Passive Aggressive Narcissist on her website, debbiemirza.com Who is Debbie Mirza? Debbie is a best-selling author who is passionate about helping people heal after narcissistic abuse. She has personally experienced decades of covert narcissistic abuse and has a wealth of understanding on this topic stemming from her own life experience, education, and research. Debbie has been interviewed on several podcasts and online conferences. She has deep empathy for those who have dealt with this damaging form of narcissism.  She has created online courses to help with the healing process, one specifically on parenting when your ex is a covert narcissist, and one with helpful tips for starting your own in person support group. During her own healing, she went through a time of much isolation where she spent a lot of time in nature and at home taking care of her wounded heart. It was during this time that she wrote and recorded songs that would bring her and others calm, love, and tenderness. Things We Talked about in This Episode Debbie's experience with finding out her husband was a covert passive aggressive narcissist.  What it's like living with someone who has CPAN and how to identify some of the traits (well liked, well respected, but they are very chameleon-like). The differences between an overt and a covert narcissist. When you're with a covert narcissist there's always a question of “who are you really?”  How covert narcissists use silent rage rather than overt yelling and anger. The three stages a victim goes through in a relationship with a covert narcissist. Cover Narcissists ability to sabotage important days and them offering to “settle”.   Traits that are common in individuals that are missing from covert narcissists What gaslighting actually is in a relationship and what that looks like with covert narcissists How to escape those relationships and begin healing after that abuse.

Perl was started by Larry Wall in 1987. Unisys had just released the 2200 series and only a few years stopped using the name UNIVAC for any of their mainframes. They merged with Burroughs the year before to form Unisys. The 2200 was a continuation of the 36-bit UNIVAC 1107, which went all the way back to 1962. Wall was one of the 100,000 employees that helped bring in over 10 and a half billion in revenues, making Unisys the second largest computing company in the world at the time. They merged just in time for the mainframe market to start contracting. Wall had grown up in LA and Washington and went to grad school at the University of California at Berkeley. He went to the Jet Propulsion Laboratory after Grad School and then landed at System Development Corporation, which had spun out of the SAGE missile air defense system in 1955 and merged into Burroughs in 1986, becoming Unisys Defense Systems. The Cold War had been good to Burroughs after SDC built the timesharing components of the AN/FSQ-32 and the JOVIAL programming language. But changes were coming. Unix System V had been released in 1983 and by 1986 there was a rivalry with BSD, which had been spun out of UC - Berkeley where Wall went to school. And by then AT&T had built up the Unix System Development Laboratory, so Unix was no longer just a language for academics. Wall had some complicated text manipulation to program on these new Unix system and as many of us have run into, when we exceed a certain amount of code, awk becomes unwieldy - both from a sheer amount of impossible to read code and from a runtime perspective. Others were running into the same thing and so he got started on a new language he named Practical Extraction And Report Language, or Perl for short. Or maybe it stands for Pathologically Eclectic Rubbish Lister. Only Wall could know. The rise of personal computers gave way to the rise of newsgroups, and NNTP went to the IETF to become an Internet Draft in RFC 977. People were posting tools to this new medium and Wall posted his little Perl project to comp.sources.unix in 1988, quickly iterating to Perl 2 where he added the languages form of regular expressions. This is when Perl became one of the best programming languages for text processing and regular expressions available at the time. Another quick iteration came when more and more people were trying to write arbitrary data into objects with the rise of byte-oriented binary streams. This allowed us to not only read data from text streams, terminated by newline characters, but to read and write with any old characters we wanted to. And so the era of socket-based client-server technologies was upon us. And yet, Perl would become even more influential in the next wave of technology as it matured alongside the web. In the meantime, adoption was increasing and the only real resource to learn Perl was a the manual, or man, page. So Wall worked with Randal Schwartz to write Programming Perl for O'Reilly press in 1991. O'Reilly has always put animals on the front of their books and this one came with a Camel on it. And so it became known as “the pink camel” due to the fact that the art was pink and later the art was blue and so became just “the Camel book”. The book became the primary reference for Perl programmers and by then the web was on the rise. Yet perl was still more of a programming language for text manipulation. And yet most of what we did as programmers at the time was text manipulation. Linux came around in 1991 as well. Those working on these projects probably had no clue what kind of storm was coming with the web, written in 1990, Linux, written in 1991, php in 1994, and mysql written in 1995. It was an era of new languages to support new ways of programming. But this is about Perl - whose fate is somewhat intertwined. Perl 4 came in 1993. It was modular, so you could pull in external libraries of code. And so CPAN came along that year as well. It's a repository of modules written in Perl and then dropped into a location on a file system that was set at the time perl was compiled, like /usr/lib/perl5. CPAN covers far more libraries than just perl, but there are now over a quarter million packages available, with mirrors on every continent except Antartica. That second edition coincided with the release of Perl 5 and was published in 1996. The changes to the language had slowed down for a bit, but Perl 5 saw the addition of packages, objects, references, and the authors added Tom Christiansen to help with the ever-growing camel book. Perl 5 also brought the extension system we think of today - somewhat based off the module system in Linux. That meant we could load the base perl into memory and call those extensions. Meanwhile, the web had been on the rise and one aspect of the power of the web was that while there were front-ends that were stateless, cookies had come along to maintain a user state. Given the variety of systems html was able to talk to mod_perl came along in 1996, from Gisle Was and others started working on ways to embed perl into pages. Ken Coar chaired a working group in 1997 to formalize the concept of the Common Gateway Interface. Here, we'd have a common way to call external programs from web servers. The era of web interactivity was upon us. Pages that were constructed on the fly could call scripts. And much of what was being done was text manipulation. One of the powerful aspects of Perl was that you didn't have to compile. It was interpreted and yet dynamic. This meant a source control system could push changes to a site without uploading a new jar - as had to be done with a language like Java. And yet, object-oriented programming is weird in perl. We bless an object and then invoke them with arrow syntax, which is how Perl locates subroutines. That got fixed in Perl 6, but maybe 20 years too late to use a dot notation as is the case in Java and Python. Perl 5.6 was released in 2000 and the team rewrote the camel book from the ground up in the 3rd edition, adding Jon Orwant to the team. This is also when they began the design process for Perl 6. By then the web was huge and those mod_perl servlets or CGI scripts were, along with PHP and other ways of developing interactive sites, becoming common. And because of CGI, we didn't have to give the web server daemons access to too many local resources and could swap languages in and out. There are more modern ways now, but nearly every site needed CGI enabled back then. Perl wasn't just used in web programming. I've piped a lot of shell scripts out to perl over the years and used perl to do complicated regular expressions. Linux, Mac OS X, and other variants that followed Unix System V supported using perl in scripting and as an interpreter for stand-alone scripts. But I do that less and less these days as well. The rapid rise of the web mean that a lot of languages slowed in their development. There was too much going on, too much code being developed, too few developers to work on the open source or open standards for a project like Perl. Or is it that Python came along and represented a different approach with modules in python created to do much of what Perl had done before? Perl saw small slow changes. Python moved much more quickly. More modules came faster, and object-oriented programming techniques hadn't been retrofitted into the language. As the 2010s came to a close, machine learning was on the rise and many more modules were being developed for Python than for Perl. Either way, the fourth edition of the Camel Book came in 2012, when Unicode and multi-threading was added to Perl. Now with Brian Foy as a co-author. And yet, Perl 6 sat in a “it's coming so soon” or “it's right around the corner” or “it's imminent” for over a decade. Then 2019 saw Perl 6 finally released. It was renamed to Raku - given how big a change was involved. They'd opened up requests for comments all the way back in 2000. The aim was to remove what they considered historical warts, that the rest of us might call technical debt. Rather than a camel, they gave it a mascot called Camelia, the Raku Bug. Thing is, Perl had a solid 10% market share for languages around 20 years ago. It was a niche langue maybe, but that popularity has slowly fizzled out and appears to be on a short resurgence with the introduction of 6 - but one that might just be temporary. One aspect I've always loved about programming is the second we're done with anything, we think of it as technical debt. Maybe the language or server matures. Maybe the business logic matures. Maybe it's just our own skills. This means we're always rebuilding little pieces of our code - constantly refining as we go. If we're looking at Perl 6 today we have to look at whether we want to try and do something in Python 3 or another language - or try and just update Perl. If Perl isn't being used in very many micro-services then given the compliance requirements to use each tool in our stack, it becomes somewhat costly to think of improving our craft with Perl rather than looking to use possibly more expensive solutions at runtime, but less expensive to maintain. I hope Perl 6 grows and thrives and is everything we wanted it to be back in the early 2000s. It helped so much in an era and we owe the team that built it and all those modules so much. I'll certainly be watching adoption with fingers crossed that it doesn't fade away. Especially since I still have a few perl-based lamda functions out there that I'd have to rewrite. And I'd like to keep using Perl for them!

On this week's Word on Medicine, a great show for you on Surgical Care and Recovery: medical experts and a patient discuss the process of care before and after surgery. We hope you'll join our panelists Dr. Njeri Wainaina from the Department of Medicine, Dr. Chris Fadumiye from the Department of Anesthesiology, and Amy Miskelley (BSN, RN, PACU Manager), Sara Betthauser, (MSN, RN, NE-BC, Perioperative RN Manager, Procedure Arrival & Recovey), Lisa Acker (BSN, RN), and Terri Lakich (BSN, RN, CPAN, Educator POHA/PACU) along with a grateful patient who shared his story.

Dos Veteranos aos Calouros de Geografia - Cpan

The software development process, or software supply chain, is quite complex and involves a number of independent actors. Due to this ever-growing complexity has led to various software supply chain compromises: from XCodeGhost injecting malware on millions of apps, to the highly-publicized SolarWinds Compromise. In this talk, Santiago will introduce various research challenges, as well as attempts from both Open Source and Industry --- such as SigStore, CoSign and in-toto --- to protect millions of users across the globe. About the speaker: Dr. Torres-Arias' current research focuses on securing the software development life-cycle. Previously, his research focused on secure password storage mechanisms and update systems. He is the team lead of in-toto, a framework to secure the software development life-cycle, as well as PolyPasswordHasher, a password storage mechanism that's incredibly resilient to offline password cracking. He also contributes to The Update Framework (TUF), which is the software update system being integrated on a variety of projects like Docker, CPAN, and others.

00:00 The spiritual lessons of the Super Bowl 05:00 Eldritch Dennis Prager (feat. Dave Rubin), https://www.youtube.com/watch?v=sbwE5zLiWNY 10:00 Luke interviewed in 2015 about sex and Orthodox Jews, https://www.youtube.com/watch?v=uH7gHuh86l8 15:00 Dooovid joins, https://twitter.com/RebDoooovid 16:00 Dooovid on Week in Review breaks out his pimp hand, https://t.co/fhUCX8MbFu?amp=1 16:40 Abraham J. Twerski died, https://en.wikipedia.org/wiki/Abraham_J._Twerski https://greenwald.substack.com/p/the-journalistic-tattletale-and-censorship 18:00 New York Times obit on Abraham J. Twerski, https://www.nytimes.com/2021/02/06/science/abraham-j-twerski-dead-coronavirus.html 19:00 R. Abraham J. Twerski combined Hasidic Judaism with the 12 Steps, https://www.thefreelibrary.com/The+Americanization+of+Mussar%3A+Abraham+Twerski%27s+Twelve+Steps.-a059120281 27:30 Elias Davidsson: I Sued a Zionist Wikipedia Editor for Slander—and Won! 29:00 Many Jews look at Christianity as akin to QANON 29:30 The Noahide Covenant, Christianity and Idol Worship, https://www.youtube.com/watch?v=tHm_VSnqHts 33:00 Michael Cohen's Prison of Choice: Well-Known to Jewish Offenders, https://www.nytimes.com/2019/01/22/nyregion/michael-cohen-otisville-prison.html 34:00 Rabbi Pleads "Stupid" For Trying To Blackmail Steve Cohen Because He's "Rich" And "Jewish", https://www.businessinsider.com/rabbi-pleads-stupid-for-trying-to-blackmail-steve-cohen-because-hes-rich-and-jewish-2010-11 40:00 Trump Lawyer Asks to Pause Impeachment Trial if It Runs Into Sabbath, https://www.nytimes.com/2021/02/06/us/politics/trump-impeachment-trial.html 1:00:00 Greg Gutfeld commentary on column: What can you do about the Trumpites next door?, https://www.latimes.com/opinion/story/2021-02-05/trumpite-neighbor-unity-capitol-attack 1:08:00 Steve Sailer back from Twitter jail, https://twitter.com/Steve_Sailer/status/1358900796339884033 1:11:00 CPAN video of Luke in 2007 asking Christopher Hitchens a question about religion, https://lukeford.net/blog/?p=255 1:15:00 US-China relations, https://www.rollcall.com/podcasts/cq-future/cq-future-us-china-relations/ 1:31:00 Richard Spencer on Tom Brady being a god 1:36:20 Defying COVID restrictions | Thousands of Orthodox Jews attend rabbi funeral 1:44:00 What is the source of transcendent morality? 2:10:00 The Journalistic Tattletale and Censorship Industry Suffers Several Well-Deserved Blows, https://greenwald.substack.com/p/the-journalistic-tattletale-and-censorship 2:18:10 Mark Steyn on the new attempt to impeach Donald Trump 2:58:00 The Secret History of the Shadow Campaign That Saved the 2020 Election, https://time.com/5936036/secret-2020-election-campaign/ https://rumble.com/lukeford https://dlive.tv/lukefordlivestreams Listener Call In #: 1-310-997-4596 Superchat: https://entropystream.live/app/lukefordlive Bitchute: https://www.bitchute.com/channel/lukeford/ Soundcloud MP3s: https://soundcloud.com/luke-ford-666431593 Code of Conduct: https://lukeford.net/blog/?p=125692 https://www.patreon.com/lukeford http://lukeford.net Email me: lukeisback@gmail.com or DM me on Twitter.com/lukeford Support the show | https://www.streamlabs.com/lukeford, https://patreon.com/lukeford, https://PayPal.Me/lukeisback Facebook: http://facebook.com/lukecford Feel free to clip my videos. It's nice when you link back to the original.

Corinne est la créatrice de la WeekUp : la première Coupe menstruelle pliable et transportable dans un sa boite dédiée, pour toujours mieux vivre avec nos règles. De la grande distribution, à la comptabilité puis à la création de la Week Up, le parcours de Corinne est vraiment très inspirant. Théo et Faustin, ses fils, ont été des vraies sources d'inspiration dans son saut dans la vie entrepreneuriale : L'aspect polluant des tampons et protection periodiques classiques révolte Faustin et Théo est à l'origine du nom de la WeekUp Comme quoi, les menstruations sont un sujet dont on peut parler dès le plus jeune âge peu importe son genre et son sexe ! La Week Up ça fait 4 ans que Corinne est dedans, à fond, dont 2 ans de recherche et developpement. Elle nous parle de

Neste episódio a Ana conversa com a aluna de graduação Brenda Tomichá e com a Dra. Gecele Matos Paggi sobre as pesquisas desenvolvidas no laboratório de genética do CPAN e sobre como a genética se relaciona com a preservação da biodiversidade.

No quinto episódio do PantaCast, a Ana conversa com a aluna de mestrado Yasmin Pereira e o aluno de graduação Douglas Lucena sobre as pesquisas desenvolvidas no laboratório de zoologia do CPAN e contam algumas experiências vivenciadas nas pesquisas de campo. 

Brian D. Foy, author of many Perl books discusses what Perl 7 is, where it’s going, what you need to do to get ready and various pieces advice on making the most of your Perl and programming life.

The Child Psychiatry Access Network (CPAN) offers teleconferencing and telephonic consultations to primary care providers so they can easily connect with the behavioral health community and its experts in order to better serve the pediatric population facing mental, behavioral or developmental disorders.Dr. Mili Khandheria and Brittany Mumford, behavior health care manager, share their insight.

Because of a shortage of Shreveport Police Officers, as of September 1, 2020, the Shreveport Police will not be handling the following in person: Private Property Accidents, Parking Complaints, Ungovernable Juveniles, Animal Complaints, Message and Delivery, Complementary Rides, Civil Matters, Child Custody Disputes, Thefts under $1,000 of Property, Drug Related Complaints, and COVID Complaints.The Broken Window Theory, which was a major part policing in the 1990s and especially in New York City, indicated that as the appearance of a neighborhood deteriorates, the amount of crime will go up. This included both the condition of physical buildings and the activities within the neighborhood. Until about 2015, crime was on the decline in the major cities.Our American Mamas, Teri Netterland and Denise Arthur, discuss the Saints wearing the name of Jacob Blake on their helmets. But Jacob Blake has a warrant out for his arrest for domestic abuse and sexual assault. He also had a restraining order against him, and the woman who called the police was the one with the warrant. What is this really saying about the personal values of the professional football players?It now has been absolutely proven and the facts made public that neither President Trump nor the Trump Campaign colluded with the Russians to steal the 2016 election. So why won’t the Russian Collusion Scam go away? Stephen Parr and Louis Avallone explain why.CSPAN did a very good job of covering the conventions. It was the only place viewers could go and watch the speeches without anchors continually interrupting or the network completely cutting out. After the speeches were complete, CPAN has a call-in segment where viewers can call on a Democrat or Republican phone line and express their opinions. What was unusual were the number of Democrats calling in to say they were leaving the party and would be voting for Donald Trump.

Because of a shortage of Shreveport Police Officers, as of September 1, 2020, the Shreveport Police will not be handling the following in person: Private Property Accidents, Parking Complaints, Ungovernable Juveniles, Animal Complaints, Message and Delivery, Complementary Rides, Civil Matters, Child Custody Disputes, Thefts under $1,000 of Property, Drug Related Complaints, and COVID Complaints.The Broken Window Theory, which was a major part policing in the 1990s and especially in New York City, indicated that as the appearance of a neighborhood deteriorates, the amount of crime will go up. This included both the condition of physical buildings and the activities within the neighborhood. Until about 2015, crime was on the decline in the major cities.Our American Mamas, Teri Netterland and Denise Arthur, discuss the Saints wearing the name of Jacob Blake on their helmets. But Jacob Blake has a warrant out for his arrest for domestic abuse and sexual assault. He also had a restraining order against him, and the woman who called the police was the one with the warrant. What is this really saying about the personal values of the professional football players?It now has been absolutely proven and the facts made public that neither President Trump nor the Trump Campaign colluded with the Russians to steal the 2016 election. So why won’t the Russian Collusion Scam go away? Stephen Parr and Louis Avallone explain why.CSPAN did a very good job of covering the conventions. It was the only place viewers could go and watch the speeches without anchors continually interrupting or the network completely cutting out. After the speeches were complete, CPAN has a call-in segment where viewers can call on a Democrat or Republican phone line and express their opinions. What was unusual were the number of Democrats calling in to say they were leaving the party and would be voting for Donald Trump.

Picture this. It's 1983. The International Design Conference in Aspen has a special speaker: Steve Jobs from Apple. He's giving a talk called “The Future Isn't What It Used To Be.” He has a scraggly beard and really, really wants to recruit some industrial designers. In this talk, he talked about software. He talked about dealers. After watching the rise of small computer stores across the country and seeing them selling, and frequently helping people pirate, apps for their iconic Apple II, Steve Jobs predicts that the dealers were adept at selling computers, but not software. There weren't categories of software yet. But there were radio stations and television programs. And there were record stores. And he predicted we would transmit software electronically over the phone line. And that we'd pay for it with a credit card if we liked using it. If you haven't listened to the talk, it's fascinating. https://www.youtube.com/watch?v=KWwLJ_6BuJA In that talk, he parlayed Alan Kay's research into the DynaBook while he was at Xerox PARC to talk about what would later be called tablet computers and ebooks. Jobs thought Apple would do so in the 80s. And they did dabble with the Newton MessagePad in 1993, so he wasn't too far off. I guess the writers from Inspector Gadget were tuned into the same frequency as they gave Penny a book computer in 1983. Watching her use it with her watch changed my life. Or maybe they'd used GameLine, a service that let Atari 2600 owners rent video games using a cartridge with a phone connection. Either way, it took awhile, but Jobs would eventually ship the both the App Store and the iPad to the masses. He alluded to the rise of the local area network, email, the importance of design in computers, voice recognition, maps on devices (which came true with Google and then Apple Maps), maps with photos, DVDs (which he called video disks), the rise of object-oriented programming, and the ability to communicate with a portable device with a radio link. So flash forward to 1993. 10 years after that brilliant speech. Jobs is shown the Electronic AppWrapper at NextWORLD, built by Paget Press. Similar to the Whole Earth Catalog, EAW had begun life as a paper catalog of all software available for the NeXT computers but evolved into a CD-based tool and could later transmit software over the Internet. Social, legal, and logistical issues needed to be worked out. They built digital rights management. They would win the Content and Information Best of Breed award and there are even developers from that era still designing software in the modern era. That same year, we got Debian package managers and rpm. Most of this software was free and open source, but suddenly you could build a binary package and call it. By 1995 we had pan, the Comprehensive Perl Archive Network. An important repository for anyone that's worked with Linux. 1998 saw the rise of apt-get. But it was 10 years after Jobs saw the Electronic AppWrapper and 20 years after he had publicly discussed what we now call an App Store that Apple launched the iTunes Store in 2003, so people could buy songs to transfer from their Mac to their iPod, which had been released in 2001. Suddenly you could buy music like you used to in a record store, but on the Internet. Now, the first online repository of songs you could download had come about back in 93 and the first store to sell songs had come along in 98 - selling MP3 files. But the iTunes Store was primarily to facilitate those objects going to a mobile device. And so 2007 comes along and Jobs announces the first iPhone at the Apple Worldwide Developers Conference . A year later, Apple would release the App Store, the day before the iPhone 3G dropped, bringing apps to phones wirelessly in 2008, 25 years after Jobs had predicted it in 1983. It began with 500 apps. A few months later the Google Play store would ship as well, although it was originally called the Android Market. It's been a meteoric rise. 10 years later, in 2018, app revenue on the iOS App Store would hit 46.6 billion dollars. And revenue on the Google Play store would hit 24.8 billion with a combined haul between $71 billion and 101 billion according to where you look. And in 2019 we saw a continued 2 digit rise in revenues, likely topping $120 billion dollars. And a 3 digit rise in China. The global spend is expected to double by 2023, with Africa and South America expected to see a 400% rise in sales in that same time frame. There used to be shelves of software in boxes at places like Circuit City and Best Buy. The first piece of software I ever bought was Civilization. Those boxes at big box stores are mostly gone now. Kinda' like how I bought Civilization on the App Store and have never looked back. App developers used to sell a copy of a game, just like that purchase. But game makers don't just make money off of purchases any more. Now they make money off of in-app advertising and in-app purchases, many of which are for subscriptions. You can even buy a subscription for streaming media to your devices, obviating the need for buying music and sometimes video content. Everyone seems to be chasing that sweet, sweet monthly recurring revenue now. As with selling devices, Apple sells less but makes much, much more. Software development started democratically, with anyone that could learn a little BASIC, being able to write a tool or game that could make them millions. That dropped for awhile as software distribution channels matured but was again democratized with the release of the App Store. Those developers have received Operating systems, once distributed on floppies, have even moved over to the App Store - and with Apple and Google, the net result is that they're now free. And you can even buy physical things using in-app purchases, Apple Pay through an Apple credit card, and digital currency, closing the loop and fully obfuscating the virtual and the physical. And today any company looking to become a standard, or what we like to call in software, a platform, will have an App Store. Most follow the same type of release strategy. They begin with a catalog, move to facilitating the transactions, add a fee to do so, and ultimately facilitate subscription services. If a strategy aint broke, don't fix it. The innovations are countless. Amazon builds services for app developers and sells them a tie to wear at their pitches to angels and VCs. Since 1983, the economy has moved on from paying cash for a box of software. And we're able to conceptualize disrupting just about anything thanks to the innovations that sprang forth in that time where those early PCs were transitioning into the PC revolution. Maybe it was inevitable without Steve Jobs right in the thick of it. Technological determinism is impossible to quantify. Either way, app stores and the resultant business models have made our lives better. And for that we owe Apple and all of the other organizations and individuals that helped make them happen, our gratitude. Just as I owe you mine for tuning in, to yet another episode, of the history of computing podcast. We are so lucky to have you. Have a great day!

FORTRAN Welcome to the History of Computing Podcast, where we explore the history of information technology. Because by understanding the past, we're better prepared for the innovations of the future! Todays episode is on one of the oldest of the programming languages, FORTRAN - which has influenced most modern languages. We'll start this story with John Backus. This guy was smart. He went to med school and was diagnosed with a brain tumor. He didn't like the plate that was left behind in his head. So he designed a new one. He then moved to New York and started to work on radios while attending Columbia for first a bachelor's degree and then a master's degree in math. That's when he ended up arriving at IBM. He walked in one day definitely not wearing the standard IBM suit - and when he said he was a grad student in math they took him upstairs, played a little stump the chump, and hired him on the spot. He had not idea what a programmer was. By 1954 he was a trusted enough resource that he was allowed to start working on a new team, to define a language that could provide a better alternative to writing code in icky assembly language. This was meant to boost sales of the IBM 704 mainframe by making it easier to hire and train new software programmers. That language became FORTRAN, an acronym for Formula Translation. The team was comprised of 10 geniuses. Lois Haibt, probably one of the younger on the team said of this phase: "No one was worried about seeming stupid or possessive of his or her code. We were all just learning together." She built the arithmetic expression analyzer and helped with the first FORTRAN manual, which was released in 1956. Roy Nutt was also on that team. He wrote an assembler for the IBM 704 and was responsible for the format command which managed data as it came in and out of FORTRAN programs. He went on to be a co-founder of Computer Science Corporation, or CSC with Fletcher Jones in 1959, landing a huge contract with Honeywell. CSC grew quickly and went public in the 60s. They continued to prosper until 2017 when they merged with HP Enteprirse services, which had just merged with Silicon Graphics. Today they have a pending merger with Cray. David Sayre was also on that team. He discovered the Sayre crystallography equation, and molter moved on to pioneer electron beam lithography and push the envelope of X-ray microscopy. Harlan Herrick on the team invented the DO and GO TO commands and ran the first working FORTRAN program. Cuthbert Herd was recruited from the Atomic Energy Commission and invented the concept of a general purpose computer. Frances Allen was a math teacher that joined up with the group to help pay off college debts. She would go on to teach Fortran and in 1989 became the first female IBM Fellow Emeritus. Robert Nelson was a cryptographer who handled a lot of the technical typing and designing some of the more sophisticated sections of the compiler. Irving Ziller designed the methods for loops and arrays. Peter Sheridan, aside from having a fantastic mustache, invented much of the compiler code used for decades after. Sheldon Best optimized the use of index registers, along with Richard Goldberg. As Backus would note in his seminal paper, the History Of FORTRAN I, II, and III, the release of FORTRAN in 1957 changed the economics of programming. While still scientific in nature, the appearance of the first true high-level language using the first real compiler meant you didn't write in machine or assembly, which was hard to teach, hard to program, and hard to debug. Instead, you'd write machine independent code that could perform complex mathematical expressions and once compiled it would run maybe 20% slower, but development was 5 times faster. IBM loved this because customers needed to buy faster computers. But customers had a limit for how much they could spend and the mainframes at the time had a limit for how much they could process. To quote Backus “To this day I believe that our emphasis on object program efficiency rather than on language design was basically correct.” Basically they spent more time making the compiler efficient than they spent developing the programming language itself. As with the Constitution of the United States, simplicity was key. Much of the programming language pieces were designed by Herrick, Ziller, and Backus. The first release of FORTRAN had 32 statements that did things that might sound similar today like PRINT, READ, FORMAT, CONTINUE, GO TO, ASSIGN and of course IF. This was before terminals and disk files so programs were punched into 80 column cards. The first 72 columns were converted into 12 36 bit words. 1-5 were labels for control statements like PRINT, FORMAT, ASSIGN or put a C in column 1 to comment out the code. Column 6 was boolean where a 1 told it a new statement was coming or a 0 continued the statement from the previous card. Columns 7 through 72 were the statement, which ignored whitespace, and the other columns were ignored. FORTRAN II came onto the scene very shortly thereafter in 1958 and the SUBROUTINE, FUNCTION, END, CALL, RETURN, and COMMON statements were added. COMMON was important because it gave us global variables. FORTRAN III came in 1958 as well but was only available for specific computers and never shipped. 1401 FORTRAN then came for the 1401 mainframe. The compiler ran from tape and kept the whole program in memory, allowing for faster runtime. FORTRAN IV came in the early 60s and brought us into the era of the System/360. Here, we got booleans, logical IF instead of that used in arithmetic, the LOGICAL data type, and then came one of the most important versions, FORTRAN 66 - which merged all those dialects from IV into not quite a new version. Here, ANSI, or the American National Standards Institute stepped in and started to standardize. We sill use DO for loops, and every language has its own end of file statement, commenting structures, and logical IFs. Once things get standardized, they move slower. Especially where compiler theory is concerned. Dialects had emerged but FORTRAN 66 stayed put for 11 years. In 1968, the authors of BASIC were already calling FORTRAN old fashioned. A new version was started in 66 but wasn't completed until 1977 and formally approved in 1978. Here, we got END IF statements, the ever so important ELSE, with new types of I/O we also got OPEN and CLOSE, and persistent variable controls with SAVE. The Department of Defense also insisted on lexical comparison strings. And we actually removed things, which these days we call DEPRECATE. 77 also gave us new error handling methods, and programmatic ways to manage really big programs (because over the last 15 years some had grown pretty substantial in size). The next update took even longer. While FORTRAN 90 was released in 1991, we learned some FORTRAN 77 in classes at the University of Georgia. Fortran 90 changed the capitalization so you weren't yelling at people and added recursion, pointers, developer-controlled data types, object code for parallelization, better argument passing, 31 character identifiers, CASE, WHERE, and SELeCT statements, operator overloading, inline commenting, modules, POINTERs (however Ken Thompson felt about those didn't matter ‘cause he had long hair and a beard), dynamic memory allocation (malloc errors woohoo), END DO statements for loop terminations, and much more. They also deprecated arithmetic IF statements, PAUSE statements, branching END IF, the ASSIGN statement, statement functions, and a few others. Fortran 95 was a small revision, adding FORALL and ELEMENTAL procedures, as well as NULL pointers. But FORTRAN was not on the minds of many outside of the scientific communities. 1995 is an important year in computing. Mainframes hadn't been a thing for awhile. The Mac languished in the clone era just as Windows 95 had brought Microsoft to a place of parity with the Mac OS. The web was just starting to pop. The browser wars between Netscape and Microsoft were starting to heat up. C++ turned 10 years old. We got Voice over IP, HTML 2.0, PHP, Perl 5, the ATX mother board, Windows NT, the Opera browser, the card format, CD readers that cost less than a grand, the Pentium Pro, Java, JavaScript, SSL, the breakup of AT&T, IBM's DEEP BLUE, WebTV, Palm Pilot, CPAN, Classmates.com, the first Wiki, Cygwin, the Jazz drive, Firewire, Ruby, and NumPy kickstarted the modern machine learning era. Oh and Craigslist, Yahoo!, eBay, and Amazon.com. Audible was also established that year but they weren't owned by Amazon just yet. Even at IBM, they were buys buying Lotus and trying to figure out how they were going to beat Kasparov with Deep Blue. Hackers came out that year, and they were probably also trying to change their passwords from god. With all of this rapid innovation popping in a single year it's no wonder there was a backlash as can be seen in The Net, with Sandra Bullock, also from 1995. And as though they needed even more of a kick that this mainframe stuff was donezo, Konrad Zuse passed away in 1995. I was still in IT at the university watching all of this. Sometimes I wonder if it's good or bad that I wasn't 2 or 3 years older… Point of all of this is that many didn't notice when Fortran continued on becoming more of a niche language. At this point, programming wasn't just for math. Fortran 2003 brought object oriented enhancements, polymorphism, and interoperability with C. Fortran 2008 came and then Fortran 2018. Yes, you can still find good jobs in Fortran. Or COBOL for that matter. Fortran leaves behind a legacy (and a lot of legacy code) that established many of the control statements and structures we use today. Much as Grace Hopper pioneered the idea of a compiler, FORTRAN really took that concept and put it to the masses, or at least the masses of programmers of the day. John Backus and that team of 10 programmers increased the productivity of people who wrote programs by 20 fold in just a few years. These types of productivity gains are rare. You have the assembly line, the gutenberg press, the cotton gin, the spinning Jenny, the watt steam engine, and really because of the derivative works that resulted from all that compiled code from all those mainframes and since, you can credit that young, diverse, and brilliant team at IBM for kickstarting the golden age of the mainframe. Imagine if you will, Backus walks into IBM and they said “sorry, we don't have any headcount on our team.” You always make room for brilliant humans. Grace Hopper's dream would have resulted in COBOL, but without the might of IBM behind it, we might still be writing apps in machine language. Backus didn't fit in with the corporate culture at IBM. He rarely wore suits in an era where suit makers in Armonk were probably doing as well as senior management. They took a chance on a brilliant person. And they assembled a diverse team of brilliant people who weren't territorial or possessive, a team who authentically just wanted to learn. And sometimes that kind of a team lucks up and change sthe world. Who do you want to take a chance on? Mull over that until the next episode. Thank you so very much for tuning into another episode of the History of Computing Podcast. We're lucky to have you. Have a great day! The History of FORTRAN I, II, and III :: http://www.softwarepreservation.org/projects/FORTRAN/paper/p165-backus.pdf

Aaron Curtis was diagnosed with cutaneous polyarteritis nodosa (CPAN) in 2015. Like many people with rare diseases, his path to a diagnosis wasn’t routine. Once he finally had a diagnosis, he was left with the task of managing his painful flare-ups while working full-time and also pursuing a writing career. On this episode, Aaron and I talk about the adjustments he has made to help manage his illness, what prompted him to start writing about CPAN, and why the spoon theory resonates with him. Learn more about Aaron and check out the show notes here. Follow Made Visible on Instagram and Facebook. 

As a young mother, Rose Gerber faced a HER2-positive breast cancer diagnosis at an early stage in life – and during a time where this disease had poorer outcomes. Despite this feat, Rose used her personal experience, in combination with her professional skillset, to help other patients with cancer through the Community Oncology Alliance Patient Advocacy Network (CPAN). Since, Rose – who is the director of patient advocacy at CPAN – has met with legislators on Capitol Hill to discuss cancer policy issues and has also assisted in developing programs across the country. In this week’s episode of CURE Talks Cancer, we speak with Rose about her experience with breast cancer, how she became an advocate and how her journey helped her to see beyond the cancer experience. To learn more, visit the [CPAN site](https://www.curetoday.com/advocacy/coa-patient-advocacy-network) on curetoday.com.

Damian Conway is a computer scientist, a member of the Perl community and the author of several books. He is perhaps best known for his contributions to CPAN and Perl 6 language design, and his Perl programming training courses as well. He has won the Larry Wall Award three times for CPAN contributions. He worked with Larry Wall on Perl6 design for more than a decade.

Für einmal, zum ersten Mal in zehn Jahren, ist der Sendetermin genau auf den 1. April gefallen. Zeit für uns, auch ein paar Scherzkekse zu essen. Und weil man davon nicht satt wird, haben wir auch noch ein paar Ostereier gefunden. Trackliste Alle Tracks zu finden auf: Musikpiraten E.V. – We Love Sharing Zahlenfakt :: 113 ist das Kenzeichen von Micky Maus' Auto RFC April Fools :: Aprilscherz RFC Dokumente Monkey Island Film :: Casting-Aufruf von Amiga Joker im April 1993 Scherzberichte :: Gesammelte Aprilscherze aus deutschen Spielezeitschriften Heise 2016 :: Erpressungstrojaner fuer Autofahrer Heise 2017 :: Webcam scannt Firmenlogos und blendet passende Werbung ein Heise 2013 :: Fuzzy Passwords Windows Startknopf :: UNESCO erklaert Windows Startknopf zum Weltkulturerbe Heiser Online :: Heiser Online April 2005 :: Steve Jobs wechselt zu IKEA XM::Simpler :: Perlmodul XML::Simpler The Register 2017 :: Register Webseite finanziert sich per Bitcoin-Miner White Space :: White Space Programmiersprache apt-gentoo :: Emuliert eine vernuenftige Distribution auf Debian GNU/Linux Selbstfahrende Velos :: Selbstfahrend und autonom lenkende Velos Shrinter :: Shredder und Printer endlich vereint Sofia :: Sofia, das Smart-Sofa Synology Drinkstation :: Bier aus der Cloud Swim Desk :: Super ergonomischer Hipster Arbeitsplatz MH40C1 Concrete Overear :: Kopfhoerer aus Beton Selbstlenkende Mietautos :: Uebernehmen auch gleich die Urlaubsplanung Cinema Vertecal :: Filmfestival fuer Hochkant-Handyfilmer Netzpolitik April 2017 :: Netzpolitik.org Aprilausgabe (sehenswert!) CERN new corporate identity :: CERN wechselt Corporate identity zu Comic Sans CPAN :: CPAN wird zu Matt's Script Archive Ahmed's used Cars and Certs :: Add Honest Achmed's used cars and certificates to root CAs Debian Insider :: RFP: jidanni -- a natural intelligence to find many bugs Robo Shop :: Adobe Robo Shop Mett-Schokolade :: Ritter Sport Mett Internet wird abgeschaltet :: IPv4 Adressraum aufgebraucht Canned Unicorn Meat :: Einhornfleisch in der Dose NEAT :: Grab von Wilhelm Tell unter NEAT-Baustelle gefunden Sechselaeutenplatz :: Google wird Sponsor des Sechselaeutenplatzes in Zuerich Honda Hupen :: Honda akustische Hupen-Emojis Nokia 3310 Neuauflage :: 2017 wahr gewordener Scherz Parrot Python-Perl Crossover :: Parrot Python-Perl Crossover Programmiersprache Parrot VM :: Parrot Interpreter MacOS X fuer Intel :: 2004 wars noch ein Aprilscherz, 2006 hat Apple die Plattform gewechselt Hackintosh :: MacOS X auf dem PC installieren Aprilscherz :: Woher kommen die Aprilscherze eigentlich? Ostereier :: Ostereier in den Medien Adventure (1979) :: Vermutlich das erste Osterei in einem Videospiel Grand Theft Auto :: Ostereier in Grand Theft Auto Spielen Grand Theft Auto :: Ostereier in Grand Theft Auto Spielen Diablo 2 :: Der Kuh-Level in Diablo 2 Super Mario Brothers :: Die Negative-World in Super Mario Brothers IK+ Ostereier :: International Karate + fuer C64 und Amiga IK+ Codeliste :: Komplette Liste aller Codes in IK+ (samt Hosentrick!) Siemens S45 :: Osterei in der Siemens S45 Mobiltelefon Firmware PalmOS Taxi :: Das Taxi Osterei in PalmOS lp0 on fire :: Das Druckerinterface brennt! lp0 on fire source-code :: Auf Zeile 257 SparcStation IPX :: Die Katze auf dem Motherboard der IPX Amiga 1000 :: Unterschriften der Amiga-Entwickler in der oberen Plastikabdeckung File Download (170:52 min / 168 MB)

Für einmal, zum ersten Mal in zehn Jahren, ist der Sendetermin genau auf den 1. April gefallen. Zeit für uns, auch ein paar Scherzkekse zu essen. Und weil man davon nicht satt wird, haben wir auch noch ein paar Ostereier gefunden. Trackliste Alle Tracks zu finden auf: Musikpiraten E.V. – We Love Sharing Zahlenfakt :: 113 ist das Kenzeichen von Micky Maus' Auto RFC April Fools :: Aprilscherz RFC Dokumente Monkey Island Film :: Casting-Aufruf von Amiga Joker im April 1993 Scherzberichte :: Gesammelte Aprilscherze aus deutschen Spielezeitschriften Heise 2016 :: Erpressungstrojaner fuer Autofahrer Heise 2017 :: Webcam scannt Firmenlogos und blendet passende Werbung ein Heise 2013 :: Fuzzy Passwords Windows Startknopf :: UNESCO erklaert Windows Startknopf zum Weltkulturerbe Heiser Online :: Heiser Online April 2005 :: Steve Jobs wechselt zu IKEA XM::Simpler :: Perlmodul XML::Simpler The Register 2017 :: Register Webseite finanziert sich per Bitcoin-Miner White Space :: White Space Programmiersprache apt-gentoo :: Emuliert eine vernuenftige Distribution auf Debian GNU/Linux Selbstfahrende Velos :: Selbstfahrend und autonom lenkende Velos Shrinter :: Shredder und Printer endlich vereint Sofia :: Sofia, das Smart-Sofa Synology Drinkstation :: Bier aus der Cloud Swim Desk :: Super ergonomischer Hipster Arbeitsplatz MH40C1 Concrete Overear :: Kopfhoerer aus Beton Selbstlenkende Mietautos :: Uebernehmen auch gleich die Urlaubsplanung Cinema Vertecal :: Filmfestival fuer Hochkant-Handyfilmer Netzpolitik April 2017 :: Netzpolitik.org Aprilausgabe (sehenswert!) CERN new corporate identity :: CERN wechselt Corporate identity zu Comic Sans CPAN :: CPAN wird zu Matt's Script Archive Ahmed's used Cars and Certs :: Add Honest Achmed's used cars and certificates to root CAs Debian Insider :: RFP: jidanni -- a natural intelligence to find many bugs Robo Shop :: Adobe Robo Shop Mett-Schokolade :: Ritter Sport Mett Internet wird abgeschaltet :: IPv4 Adressraum aufgebraucht Canned Unicorn Meat :: Einhornfleisch in der Dose NEAT :: Grab von Wilhelm Tell unter NEAT-Baustelle gefunden Sechselaeutenplatz :: Google wird Sponsor des Sechselaeutenplatzes in Zuerich Honda Hupen :: Honda akustische Hupen-Emojis Nokia 3310 Neuauflage :: 2017 wahr gewordener Scherz Parrot Python-Perl Crossover :: Parrot Python-Perl Crossover Programmiersprache Parrot VM :: Parrot Interpreter MacOS X fuer Intel :: 2004 wars noch ein Aprilscherz, 2006 hat Apple die Plattform gewechselt Hackintosh :: MacOS X auf dem PC installieren Aprilscherz :: Woher kommen die Aprilscherze eigentlich? Ostereier :: Ostereier in den Medien Adventure (1979) :: Vermutlich das erste Osterei in einem Videospiel Grand Theft Auto :: Ostereier in Grand Theft Auto Spielen Grand Theft Auto :: Ostereier in Grand Theft Auto Spielen Diablo 2 :: Der Kuh-Level in Diablo 2 Super Mario Brothers :: Die Negative-World in Super Mario Brothers IK+ Ostereier :: International Karate + fuer C64 und Amiga IK+ Codeliste :: Komplette Liste aller Codes in IK+ (samt Hosentrick!) Siemens S45 :: Osterei in der Siemens S45 Mobiltelefon Firmware PalmOS Taxi :: Das Taxi Osterei in PalmOS lp0 on fire :: Das Druckerinterface brennt! lp0 on fire source-code :: Auf Zeile 257 SparcStation IPX :: Die Katze auf dem Motherboard der IPX Amiga 1000 :: Unterschriften der Amiga-Entwickler in der oberen Plastikabdeckung File Download (170:52 min / 168 MB)

Axel hat einen neuen Job, in dem er Phisher, Blackhats und so aufzuspüren und zu verfolgen versucht, und erzählt da ein bisschen davon am Hackerfunk, soweit es ihm moeglich ist. Trackliste Dirtyphonics – Anonymous Kepler – Melody Heydevils – AOHell Barcelona – I have the password to your Hav I been pwned :: Check if your account is compromised Geocreepy :: Geolocation OSINT Tool XKCD 936 :: Password strength Report Phishing :: Switch Phishing reporting form MELANI :: Antiphishing Meldestelle des BAKOM KOBIK :: Schweizerische Koordinationsstelle zur Bekämpfung der Internetkriminalität Google Safebrowsing :: Report malicious websites (Malware) to Google APWG :: Report Phishing Phishtank :: Report Phishing WHOIS :: Infos zu Domains abfragen Team CYMRU :: Internet Security Research and Insight Virus Total :: Verdaechtige Dateien zur Analyse melden Virusscan :: Jotti's Malware Scanner Email Headers :: Email Header Analyzer Email Blacklists :: Email Blacklist Checker Email Blacklists :: Mail-Blacklist-Überwachungs Scripte CPAN Modul Net::Abuse :: Perl-Modul Net::Abuse von CPAN Python-Modul :: Python-Modul zum Abuse-Handling DNS Diag :: DNS Diagnostics and Performance Measurement Tools Bruce Schneier :: Stop trying to fix the user! Response policy zone :: Response policy zone File Download (124:40 min / 123 MB)

Axel hat einen neuen Job, in dem er Phisher, Blackhats und so aufzuspüren und zu verfolgen versucht, und erzählt da ein bisschen davon am Hackerfunk, soweit es ihm moeglich ist. Trackliste Dirtyphonics – Anonymous Kepler – Melody Heydevils – AOHell Barcelona – I have the password to your Hav I been pwned :: Check if your account is compromised Geocreepy :: Geolocation OSINT Tool XKCD 936 :: Password strength Report Phishing :: Switch Phishing reporting form MELANI :: Antiphishing Meldestelle des BAKOM KOBIK :: Schweizerische Koordinationsstelle zur Bekämpfung der Internetkriminalität Google Safebrowsing :: Report malicious websites (Malware) to Google APWG :: Report Phishing Phishtank :: Report Phishing WHOIS :: Infos zu Domains abfragen Team CYMRU :: Internet Security Research and Insight Virus Total :: Verdaechtige Dateien zur Analyse melden Virusscan :: Jotti's Malware Scanner Email Headers :: Email Header Analyzer Email Blacklists :: Email Blacklist Checker Email Blacklists :: Mail-Blacklist-Überwachungs Scripte CPAN Modul Net::Abuse :: Perl-Modul Net::Abuse von CPAN Python-Modul :: Python-Modul zum Abuse-Handling DNS Diag :: DNS Diagnostics and Performance Measurement Tools Bruce Schneier :: Stop trying to fix the user! Response policy zone :: Response policy zone File Download (124:40 min / 123 MB)

Fredrik snackar med Erik Larkö om React, ramverk och att välja dem, att lära sig nya saker, händelser i typvärlden och mycket annat. Att lära sig tankesätten är kanske det viktigaste att ta med sig från alla ramverk som kommer och går, och kan vi se vad som kommer härnäst genom att titta en lagom bit bakåt? Har det blivit för svårt att skriva Javascript? Spännande Git-arbetsflöden, Gits inlärningskurva, grafiska Git-gränssnitt och att råka bli support för andra utvecklare. Autouppdatering. Och det osannolika i att NPM och alla paket där fortfarande inte funkar sämre än det gör. Snacket spelades in på ett lokalt café, och Fredrik vill be om så hemskt mycket om ursäkt för hur mycket bakgrundsmusiken hörs. Ett stort tack till Cloudnet som sponsrar vår VPS! Har du kommentarer, frågor eller tips? Vi är @kodsnack, @tobiashieta, @isallmaroon och @bjoreman på Twitter, har en sida på Facebook och epostas på info@kodsnack.se om du vill skriva längre. Vi läser allt som skickas. Gillar du Kodsnack får du hemskt gärna recensera oss i iTunes! Prova att rensa saker i centern. Lärdom: slå inte ihop till mono det första jag gör, det kan finnas information att rädda. Länkar Access MS SQL express Redux Dan Abramov Dan Abramovs kurs om Redux på Egghead React Europe - och talet där Dan Abramov visar tidsresor Mobx Annoteringar Java EE Object.observe() - en finess som aldrig dök upp i Javascript-standarden Knockout Java FX Elm Om Monader Eslint Jslint gofmt Typescript Create React app Webpack Babel Atom Flow Douglas Crockford Javascript the good parts Relay Graphql Lee Byron pratar bra om Graphql Flux-arkitekturen Hyperterm - terminal skapad i och med Javascript Bash Z shell Oh my ZSH Babel traverse Npm shrinkwrap Have we forgotten how to program? MIT-licensen CPAN - Perls paketsystem Nuget Artifactory Nexus Gitless XKCD om Git Detached head Git reflog Git på svenska Dunning-Kruger-effekten Impostor syndrome - känslan att man inte vet vad man gör och kan bli påkommen med det när som helst Firacode - teckensnitt med ligaturer som gör kod tydligare Clion Pycharm Netbeans Borderlayout Webstorm Gitkraken - visade sig finnas för Macos, Windows och Linux Tower - Git-klient för Macos Jgit Fedora Mono och .NET core Monodevelop och Xamarin studio Vi blir båda taggade av att lyssna på Tomas Cocoapods Stack overflows arkitektur Serverlösa arkitekturer Martin Fowler Leetspeek - i Malmö 15 oktober Jon Skeet Titlar Allt vi ville göra hamnade i en skarv Då vill de låna mitt skript Samtidigt vill man inte bli Debian Titta inte i node_modules Trolla i företagets DNS Krypterad malware Visst, det är malware, men jag kan verifiera att det är samma malware Du bygger högre och högre korthus Jag är precis så Jag sitter i detached head hela tiden Jag missbrukar ju Git Ett hatbrev till nästa person Jag brukar skriva kärleksbrev Git är ju sin commitgraf Är de ens en per server? Det räcker med datum och tid på en planet

02:28 - Ruby in a Polyglot Architecture (Panel Experience) 04:21 - Does Ruby do well or not in the microservices area? Is Ruby keeping up? 07:30 - What are areas where Ruby still beats other languages? Speed and Momentum Dependency Management CPAN Bundler npm 13:12 - Polyglotting Architecture if Only Using Ruby for Build Tools, Deployment Tools, etc.? “Deployment is part of the code.” Capistrano rake 16:09 - Error Messages 18:20 - Tradeoffs in a Polyglot Architecture (Negatives) Context Switching AWK DSLs 34:35 - Learning Programming Ruby as a First Language? What is a good language for beginners? Smalltalk Scheme Python 41:24 - Mixing Languages

02:28 - Ruby in a Polyglot Architecture (Panel Experience) 04:21 - Does Ruby do well or not in the microservices area? Is Ruby keeping up? 07:30 - What are areas where Ruby still beats other languages? Speed and Momentum Dependency Management CPAN Bundler npm 13:12 - Polyglotting Architecture if Only Using Ruby for Build Tools, Deployment Tools, etc.? “Deployment is part of the code.” Capistrano rake 16:09 - Error Messages 18:20 - Tradeoffs in a Polyglot Architecture (Negatives) Context Switching AWK DSLs 34:35 - Learning Programming Ruby as a First Language? What is a good language for beginners? Smalltalk Scheme Python 41:24 - Mixing Languages

02:28 - Ruby in a Polyglot Architecture (Panel Experience) 04:21 - Does Ruby do well or not in the microservices area? Is Ruby keeping up? 07:30 - What are areas where Ruby still beats other languages? Speed and Momentum Dependency Management CPAN Bundler npm 13:12 - Polyglotting Architecture if Only Using Ruby for Build Tools, Deployment Tools, etc.? “Deployment is part of the code.” Capistrano rake 16:09 - Error Messages 18:20 - Tradeoffs in a Polyglot Architecture (Negatives) Context Switching AWK DSLs 34:35 - Learning Programming Ruby as a First Language? What is a good language for beginners? Smalltalk Scheme Python 41:24 - Mixing Languages

 El físico Antonio Pich del CPAN nos explica qué se cuece en el LHC, el acelerador de partículas más grande del mundo, que ha reabierto sus puertas tras dos años de parón.Luego, nuestro particular cazador de sonidos de la naturaleza, Carlos de Hita, nos muestra cómo suena este florido y revolucionado mes de mayo.Escuchar audio

Ollie Charles, author of 24 Days of Hackage (and a number of Haskell libraries), gives us his perspectives on Haskell libraries and how they relate to Perl's CPAN. He shares how he began his transition from Perl to Haskell while working for MusicBrainz and how he came to work full-time on Haskell at Fynder. (Listen closely if you've wanted to write Haskell in your non-Haskell job.) We also chat briefly about developing in Haskell with Nix and a different take on equational reasoning.

Who advocates for advocates? At Community Oncology Alliance Patient Advocacy Network (CPAN), it's Rose Gerber, Dir. of Patient Advocacy. A survivor herself, Rose's experiences incl. meeting with legislators in Wash., D.C. on cancer policy issues. CPAN advocates may begin their journey thinking "I can't speak to the governor", only to find confidence through conviction (and their personal exp. with cancer) to say "I can" on behalf of all cancer patients and oncological professionals. Rose supports CPAN advocates through training, resources, and direction they need to facilitate critical changes in issues such as chemo drug shortages. Joni live M-F at 2:00 p.m. ET on www.W4CS.com. www.JoniAldrich.com

"Pa ciència, la nostra (VOS)" es un programa que repasa la actualidad científica con humor en su versión en castellano. En el programa de hoy tenemos el placer de conversar con Javier Armentia, un gran divulgador científico y director del Pamplonetario, el Planetario de Pamplona que cumple 20 años. En la actualidad: niños que no corren, oxitocina, la inversión del campo magnético terrestre y visones felices. En "A ti te encontré en el interné" felicitamos a cuentos-cuanticos.com por su mericidísimo premio CPAN (www.i-cpan.es)