Bitbucket Require Pull Request Reviews Before Merging
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Download Resume
Oji Udezue http://www.linkedin.com/in/ojiudezue . +1 425-829-9520 SUMMARY: EXPERIENCED PRODUCT, DESIGN & TECHNOLOGY EXECUTIVE I’m a product-led growth expert. A multi-disciplinary tech exec with strong product, design and engineering leadership skills. I have had stints in marketing and sales which provide a well - rounded experience of key business functions. In addition, I have startup experience and a track record advising several great startups. I have a talent for new product strategy and the practical leadership to innovate and execute with conviction. I am passionate about early stage product development and entrepreneurship in organizations. My strongest skill sets are product vision, lean product management; strategy & planning, people management and talent development. Professional Experience CALENDLY VP of Product (2018 – Present) Lead Technology, Product, Design and Content Strategy • Under my tenure, Calendly is sustaining 100% year on year growth in ARR and MAU • Drive key engineering investments and a high-performance engineering culture • Set product vision, mission and goals for business • Drive ongoing, high velocity innovation • Manage overall user experience and delivery of value to customers • Manage team health, product craft excellence and talent acquisition • Drive clear and actionable business metrics and management of business to those metrics • Drive acquisition strategy; review and approve potential acquisition deals • Manage growth program and virality initiatives to increase audience share ATLASSIAN Head -
Atlassian, a Devops Leader, Partners with Protiviti to Deliver Cutting-Edge IT Controls Across Its Environment
CLIENT STORY Atlassian, a DevOps leader, partners with Protiviti to deliver cutting-edge IT controls across its environment Technology companies compete on their ability to quickly develop, deliver and update quality systems and software. This need for speed has led solution providers to abandon the traditional “waterfall” software development Keys to Success methodology in favor of Agile and DevOps, a faster and more collaborative approach that ultimately aims to enable faster time to market and a more reliable product. However, many organizations have struggled to apply Change requested traditional IT control frameworks within an Agile/DevOps environment, and the Embed control activities into Agile two are often misconceived as being incompatible. processes without compromising speed of delivery Atlassian, a global software development company responsible for creating Change envisioned team collaboration and productivity tools — including Jira, Confluence, Trello, Stride and BitBucket, among others — recognizes that trust is Combine Protiviti’s IT, risk and increasingly at the forefront of customer adoption considerations, and that compliance expertise with Atlassian’s key to demonstrating trustworthiness is being transparent with compliance. culture of innovation to design In addition, when it listed on the NASDAQ market in the United States in best-in-class controls in a DevOps December 2015, Atlassian needed to be in a position to demonstrate effective environment controls to its investors. Change achieved Embedded, automated controls -
TEAM Q4-2019 Shareholder Letter
Shareholder Letter Q4 FY19 and Fiscal 2019 | July 25, 2019 From the CEOs Fellow shareholders, Fiscal 2019 was another outstanding year for Atlassian. We surpassed 150,000 customers and vaulted past the $1 billion revenue mark for the first time in a fiscal year. This year also saw a number of important advances in our products aimed to better serve our customers: Trello Trello reinforced its status as a go-to collaboration tool in the workplace, serving more than 80% of the Fortune 500. In Okta's 2019 Businesses @ Work report, Trello was cited as the most widely adopted project management app at work. We introduced powerful organization-wide features for Trello Enterprise and made automation a more integral part of Trello with the addition of Butler for Trello. Jira family We improved the overall user experience of our Jira product family by simplifying the interface for new users and enhancing features for more advanced users. This combination of simplicity and power keeps Jira Software the industry standard for managing work in software teams. Cloud for We introduced an early access program for large enterprises, expanding enterprises support from 5,000 to 10,000 users. Cloud We introduced an early access program for Cloud Premium Editions of Jira Premium Software and Confluence targeting more sophisticated and larger customers. These new editions combine advanced end-user features with additional platform capabilities around uptime, service levels and data storage. Access We saw continued momentum from one of our newest products, Atlassian Access. Access provides company-wide security and policy administration across multiple Atlassian products, and already supports hundreds of thousands of users in its first year. -
A Microsoft Office for Software Development with a Growing Moat, Large TAM and High-Quality Management
Company: Atlassian (NasdaqGS: TEAM) Rainbow Chik Recommendation: Long [email protected] Price Target: $422 (79% upside/ 21% 3-yr IRR) A Microsoft Office for software development with a growing moat, large TAM and high-quality management KEY STATISTICS TRADING CHART EXECUTIVE SUMMARY Atlassian is a high-quality SaaS market leader that offers mission critical workplace collaboration and Application Development software. It is analogous to Microsoft Office for software development and is the oil that powers software development from planning, coding, deployment, support and collaboration. I believe TEAM is undervalued as the market (1) underappreciates TEAM’s moat expansion as a result of cloud migration, (2) underestimates TEAM’s strong network effect expanding in the large knowledge worker TAM, (3) overlooks management quality being long-term owner- operator and prudent capital allocator. The recently announced migration from perpetual licenses to cloud subscription presents a unique window to invest. Investors are concerned about the short-term revenue headwind and churn risk as a result of cloud migration, but my research suggests that it masked the better business potential given it leads to higher pricing power in a win-win situation and much stickier customers in the long-term. My base case valuation suggests a 79% upside from its current valuation at $236 ($423 target price). This is based upon sustained strong customer growth and subscription revenue per customer growth during and post-cloud-migration from my research. In addition, my bull/ bear case analysis suggests an attractive 3.5x upside/ downside ratio. COMPANY OVERVIEW Atlassian = Microsoft Office for software development Founded in 2002, Atlassian is an Australian SaaS market leader. -
A Threat Modelling Approach to Analyze and Mitigate Botnet Attacks in Smart Home Use Case
A Threat Modelling Approach to Analyze and Mitigate Botnet Attacks in Smart Home Use Case Syed Ghazanfar Abbas, Shahzaib Zahid Faisal Hussain Ghalib A. Shah, Muhammad Husnain Al-Khawarizmi Institute of Computer Al-Khawarizmi Institute of Computer Al-Khawarizmi Institute of Computer Science (KICS) Lahore, Pakistan Science (KICS) Lahore, Pakistan Science (KICS) Lahore, Pakistan [email protected] [email protected] [email protected] [email protected] [email protected] Abstract—Despite the surging development and utilization of hardcoded, or guessable passwords, lack of security updates, IoT devices, the security of IoT devices is still in infancy. The etc. [5]. The attackers first exploit these vulnerabilities, then security pitfalls of IoT devices have made it easy for hackers bypass the user’s privacy and information and finally use the to take over IoT devices and use them for malicious activities like botnet attacks. With the rampant emergence of IoT devices, victim IoT device to perform different malicious activities botnet attacks are surging. The botnet attacks are not only ranging from shutting down service to control over end devices catastrophic for IoT device users but also for the rest of the world. [6]. Therefore, there is a crucial need to identify and mitigate the The rampant emergence of IoT devices caused the ignorance possible threats in IoT devices during the design phase. Threat of security threats to large extent [6]. The security pitfalls modelling is a technique that is used to identify the threats in the earlier stages of the system design activity. -
How Bad Can It Git? Characterizing Secret Leakage in Public Github Repositories
How Bad Can It Git? Characterizing Secret Leakage in Public GitHub Repositories Michael Meli Matthew R. McNiece Bradley Reaves North Carolina State University North Carolina State University North Carolina State University [email protected] Cisco Systems, Inc. [email protected] [email protected] Abstract—GitHub and similar platforms have made public leaked in this way have been exploited before [4], [8], [21], [25], collaborative development of software commonplace. However, a [41], [46]. While this problem is known, it remains unknown to problem arises when this public code must manage authentication what extent secrets are leaked and how attackers can efficiently secrets, such as API keys or cryptographic secrets. These secrets and effectively extract these secrets. must be kept private for security, yet common development practices like adding these secrets to code make accidental leakage In this paper, we present the first comprehensive, longi- frequent. In this paper, we present the first large-scale and tudinal analysis of secret leakage on GitHub. We build and longitudinal analysis of secret leakage on GitHub. We examine evaluate two different approaches for mining secrets: one is able billions of files collected using two complementary approaches: a to discover 99% of newly committed files containing secrets in nearly six-month scan of real-time public GitHub commits and a public snapshot covering 13% of open-source repositories. We real time, while the other leverages a large snapshot covering focus on private key files and 11 high-impact platforms with 13% of all public repositories, some dating to GitHub’s creation. distinctive API key formats. This focus allows us to develop We examine millions of repositories and billions of files to conservative detection techniques that we manually and automat- recover hundreds of thousands of secrets targeting 11 different ically evaluate to ensure accurate results. -
Github Pull Request Review
Github Pull Request Review Archaic and delegable Pierre prenotifying her longboat reactivating while Hartley reflow some intercross fadelessly. Narratable and thickhydropathic when Pincus Francois emerged reintegrate his timing. her bedchambers filigree or deactivate tamely. Unlearned and chiromantic Bearnard never outmeasuring There is merged soon, optimize this can request review status becomes quite clear based on their code management repositories that we would react to uninstall the pros and By dzone contributors, required for projects have fixed by everyone who can. In this palace, the toolbar will show why green Checks donut, a grey Changes revision, and grey zero counters in the remaining boxes. For this page with each other process, critical security expert from empirical and. Do at production data obtained from visual studio code review so that you if you want you selected, you a pull request that bad practice. Github will see? In github pull request review your first was this. Program readability: procedures versus comments. If any change on changes in progress and effective code coverage changes in that all pull request? Stripe is not have made for other reviewers are. Haacked is a blog about Technology, Software, Management, and fast Source. Even if there is in github or bandwidth costs go read way you can be detected by submitting are changes into new posts in github pull request review time for agility, requiring signed out. Rbac rules and code and more hunting down a nice aspect of incoming pr will update it more merge methods to! Review apps will spend some changes might require a pull reminders for. -
Assessing the Security of Android Dating Apps Värdering Av
DEGREE PROJECT IN COMPUTER ENGINEERING, FIRST CYCLE, 15 CREDITS STOCKHOLM, SWEDEN 2020 Assessing the Security of Android Dating Apps Värdering av säkerheten i dating- appar för Android HAMPUS HAUFFMAN ADAM MEYER KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ENGINEERING SCIENCES IN CHEMISTRY, BIOTECHNOLOGY AND HEALTH Assessing the Security of Android Dating Apps HAMPUS HAUFFMAN, ADAM MEYER Degree Programme in Computer Engineering Date: June 7, 2020 Supervisor: Shahid Raza Examiner: Ibrahim Orhan School of Engineering Sciences in Chemistry, Biotechnology and Health Swedish title: Värdering av säkerheten i dating-appar för Android iii Abstract Dating apps are continuously becoming a larger part of the social media mar- ket. Like any social media app, dating apps utilize a large amount of personal data. This thesis analyzes two dating apps and how they handle personal infor- mation from a security and privacy standpoint. This was done by conceptual- izing a threat model and then validating the threat through penetration testing on both of the apps in an attempt to find security vulnerabilities. This analysis proves that there is a substantial difference in whether or not app developers take security seriously or not. It was found that in one of the two apps analyzed, gaining access to personal data was particularly more trivial than expected, as TLS or other encryption were not implemented and server-side authorization was lacking in important app features like the one-to-one user chat. Keywords – Penetration testing, ethical hacking, dating apps, Android, reverse engineering, threat modeling, risk rating iv Sammanfattning Dating-appar blir kontinuerligt en större del av moderna sociala medier. -
Moving Your Team from Hipchat to Slack: Part One
Moving Your Team from HipChat to Slack: Part One In late July 2018, Atlassian announced it would be entering a “strategic partnership” with Slack. HipChat will shut down for good on February 15, 2019, which means that businesses using the service must be fully transitioned to Slack (or another collaboration platform) before that date. This news came as quite a shock to HipChat users, given Atlassian’s stated commitment to carving out its own corner of the busy real-time team communications market (the company released Stride, a new workplace communications product, just a few months ago). But Atlassian’s sudden and dramatic about-face was an inevitable reaction to the pressures of its chosen marketplace. Image: Slack’s Twitter announcement [email protected] 1 www.teampay.co Why Slack won Unlike Atlassian, Slack has been gaining market share at a remarkable rate: the company boasted in May that it had reached over eight million daily users and that 65% of the Fortune 100 companies were now paid Slack subscribers. Source: Slack Slack’s impressively broad integration options are a core component of its success; users of InVision, Trello, GitHub, Salesforce and many other popular SaaS platforms can install plug-and-play apps to link these platforms with Slack. That makes it a much “stickier” team collaboration option than, say, HipChat (which has a far smaller pool of available integrations) and greatly reduces customer churn. Whatever commercial software products and platforms you work with, there’s likely to be an app for that in Slack’s App Directory. Even direct competitors Google and Microsoft have worked with Slack to develop integration apps for their products. -
TEAM Q2-2018 Shareholder Letter
From the CEOs Fellow shareholders, We closed out calendar year 2017 with another strong quarter of fnancial, customer and product growth. Revenue for the quarter was $212.6 million, up 43% year-over-year, with free cash fow of $67.8 million. As of December 31, 2017 we counted 112,571 companies as customers, 4,825 of whom were added in the quarter. This is the most net new customers we've ever added in a single quarter and another milestone on our way to unleashing the potential of every team. We saw solid demand across all our deployment options—Cloud, Server, and Data Center. We continue to land and expand with customers of all sizes, and across numerous industries and geographies. Of course, results like these don't “just happen.” They're driven by product innovations that make our customers more productive, the incredible ecosystem of vendors that partner with us, and the vibrant community of users we connect with through events like the upcoming Team Tour—all of which you’ll hear more about below. We'll also touch on our expanding U.S. footprint and the newest member of our executive team. Jira Service Desk embedded portals: coming to a site near you No matter what business you're in, whether your customers are internal or external, they're demanding easier access to service. That's why Jira Service Desk users can now embed a mini help portal that lets their customers raise service requests from any web page on their website or intranet, without having to navigate to a separate page on a diferent part of the site. -
Veni, Vidi, Vici
Code Review: Veni, ViDI, Vici Yuriy Tymchuk, Andrea Mocci, Michele Lanza REVEAL @ Faculty of Informatics - University of Lugano, Switzerland Abstract—Modern software development sees code review as For example many of them leverage static code analysis a crucial part of the process, because not only does it facilitate techniques, like the ones provided by FindBugs [5], to spot the sharing of knowledge about the system at hand, but it may implementation problems. However, the results from such also lead to the early detection of defects, ultimately improving techniques are poorly integrated in a code review process, as the quality of the produced software. Although supported by we will see later. numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of We propose an approach to augment code review by inte- shortcomings in the state of the art. grating software quality evaluation, and more general design We present a critical analysis of the state of the art of code assessment, not only as a first class citizen, but as the core review tools and techniques, extracting a set of desired features concern of code review. Our approach, called Visual Design that code review tools should possess. We then present our vision Inspection (ViDI), uses visualization techniques to drive the and initial implementation of a novel code review approach quality assessment of the reviewed system, exploiting data named Visual Design Inspection (ViDI), illustrated through a set obtained through static code analysis. ViDI enables intuitive of usage scenarios. ViDI is based on a combination of visualization and easy defect fixing, personalized annotations, and review techniques, design heuristics, and static code analysis techniques. -
How to Trust Auto-Generated Code Patches? a Developer Survey And
How to trust auto-generated code patches? A developer survey and empirical assessment of existing program repair tools Yannic Noller∗ Ridwan Shariffdeen∗ National University of Singapore National University of Singapore Singapore Singapore [email protected] [email protected] Xiang Gao Abhik Roychoudhury National University of Singapore National University of Singapore Singapore Singapore [email protected] [email protected] ABSTRACT works on generating multi-line fixes [12, 29], or on transplanting Automated program repair is an emerging technology that seeks patches from one version to another [37] — to cover various use to automatically rectify bugs and vulnerabilities using learning, cases or scenarios of program repair. search, and semantic analysis. Trust in automatically generated Surprisingly, there is very little literature or systematic study patches is necessary for achieving greater adoption of program from either academia or industry — on the developer trust in pro- repair. Towards this goal, we survey more than 100 software practi- gram repair. In particular, what changes do we need to bring into tioners to understand the artifacts and setups needed to enhance the program repair process so that it becomes viable to have conver- trust in automatically generated patches. Based on the feedback sations on its wide-scale adoption? Part of the gulf in terms of lack from the survey on developer preferences, we quantitatively evalu- of trust comes from a lack of specifications — since the intended ate existing test-suite based program repair tools. We find that they behavior of the program is not formally documented, it is hard to cannot produce high-quality patches within a top-10 ranking and trust that the automatically generated patches meet this intended an acceptable time period of 1 hour.