Tag Archives: developer

Podcast – Baruch Sadogursky on Pipeline, Immutability, and Edge

Posted on by
Reply

Joining us this week is Baruch Sadogursky, Head of Developer Relations at JFrog. Baruch is an industry veteran in management of complex software and is a fantastic event speaker; I highly recommend attending his sessions at a future event. Short promotion for JFrog Swamp Up (May 16 – 18, 2018)

Highlights

  • Short overview of JFrog and its relationship to CI/CD pipelines
  • Discussion of immutability (shifting left) in deployment paradigms
  • Metadata and the impact of scale (Toyota Manufacturing Model)
  • How can I update software components with confidence?
  • Distributed programming and impact of edge computing

Topic                                                                                        Time (Minutes.Seconds)

Introduction                                                                            0.0 – 2.17
JFrog Artifactory                                                                    2.17 – 3.26
Pipeline (Starting)                                                                  3.26 – 7.53
Immutability (Shifting Left)                                                  7.53 – 11.51
Metadata (Surrounds the Artifact)                                     11.51 – 16.45
Impact of Scale (Excessive File Names)                           16.45 – 23.30 (Toyota Model)
Updating Software Components                                       23.30 – 28.32 (Pain is Instructional)
Edge Computing (IoT is Next Frontier)                              28.32 – 38.01
Wrap Up                                                                                 38.01 – END

Podcast Guest: Baruch Sadogursky

Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 17 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people and how they work, or more precisely, don’t work together.

He is a CNCF ambassador, Developer Champion, and a professional conference speaker on DevOps, Java and Groovy topics, and is a regular at the industry’s most prestigious events including JavaOne (where he was awarded a Rock Star award), DockerCon, Devoxx, DevOps Days, OSCON, Qcon and many others. His full speaker history is available on Lanyrd: http://lanyrd.com/profile/jbaruch/sessions/

You can follow him @jbaruch on Twitter.

Podcast – Jim Plamondon tells history of developer evangelism and so much more

Posted on by
Reply

Coming direct from Cambodia is a rare podcast with Jim Plamondon, the creator of how software platforms were built at Microsoft via APIs and developer evangelism. In this podcast, he talks about the early history of developer evangelism at Apple and Microsoft, the current state of open source, and the upcoming competitive industry coming from China and its roots in the third world.

Highlights

  • Soviet Agriculture and Technology Market Comparison
  • Why NeXT and Apple Failed with Software Industry but iPhone Succeeded
  • China Industry Takeover is Coming: Product Price Points

Books referenced in the podcast (links to Amazon, we have no agreement with them based on your click/purchase):

Note – If you are easily offended by language please consider skipping this podcast J

Topic                                                       Time (Minutes.Seconds)

Introduction                                           0.0 –  0.33
Creator of Developer Evangelism      0.33 – 4.58
Plamondon Files                                   4.58 – 5.53
Working with Hostile Community      5.53 – 7.02
Android vs iOS Platform                       7.02 – 7.46
Study: Apple vs Windows                    7.46 – 9.13
PC Industry – Mostly All Alive            9.13 – 10.00
Open Source has same Struggles     10.00 – 12.21 (Focus on individual not yechnology)
Cargo Cult & Hype Cycle                     12.21 – 16.11 (VR and AI are on version 3; not new at all)
Security Breach                                     16.11 – 17.01
Back to Hype Cycle                              17.01 – 19.03 (Markets find a solution that makes profits)
Latest thoughts on Open Source       19.03 – 23.25 (Zipf’s Law)
Time Buying Strategy                           23.25 – 25.07 (e.g. IBM Server response to Amazon S3)
Microsoft Anti-Trust & Apple Mgmt    25.07 – 28.45 (NeXT Failure)
iPhone walled Garden Worked           28.45 – 31.10
Android will defeat iPhone                   31.10 – 32.33
Internet Competition dead?                 32.33 – 36.07 (Here comes China)
Alibaba moves West                              36.07 – 39.45 (Take over 3rd world then US/Europe)
Per Capita Income Averages                39.45 – 43.55 (Own tiny consumer market than move up)
China and Open Source                        43.55 –  47.18
Western vs Asian Gov’ts                       47.18 – 49.50 (Go learn Mandarin)
Wrap Up                                                  49.50 – END

 

Podcast Guest: Jim Plamondon
Jim Plamondon is a retired Technology Evangelist, noted for formalizing Microsoft’s Technology Evangelism practices in the 1990’s.

 

 

 

Update a pull request from git command line

Posted on by
2

Hand up

Sometimes we just need to feed the SEO gods… in this case, I could not find the simple git command line to update a pull request that I had in flight.

I was looking for the following:

git push -f personal HEAD:[pull branch]

Github.com happily gave me instructions from the pull branch but not the CLI version of the command.  The trick is that you need to know your remote (git remote) for the command so it’s not perfectly generic.  In the example above, my personal repo is named “personal”.

Deconstructing the command: you are pushing your to your personal clone from the local HEAD commit against the branch created for the pull request.  That’s because the pull request creates a branch from your clone to be pulled into the upstream repo.  That’s why it’s a PULL request not a push.

Ultimately, this is pretty basic git.  My experience with git is that the definition of “pretty basic” is a binary function.  Once you know how git works, everything in git is pretty basic.  Until then it’s completely opaque.

Side note: this is my 301st post on this blog!

8/1/2013 Post Script from Crowbar Contributor Adam Spiers

He noticed that I should include the -f in the git push instruction.  Read more at about that on his blog.