Why code in Node.js often get rejected by SoundCloud

•

25 recomendaciones•8,293 vistas

From: http://gotocon.com/aarhus-2013/presentation/Why%20code%20in%20Node.js%20often%20gets%20rejected%20by%20SoundCloud At SoundCloud we ask candidates to send us some code before inviting them in for interviews. Candidates can use whatever language they want, and over the past years we saw a massive rise on the number of submissions using server-side JavaScript. Unfortunately, too many submissions are asynchronous blobs of procedural code. JavaScript is a fairly functional language, and over the past decades Functional Programming developed interesting solutions for many of the problems we face when writing Node.js and regular JavaScript. Let's talk about how to leverage good old Functional Programming techniques to make code less coupled and more readable!

Tecnología

Why code in Node.js
often get rejected by
SoundCloud
Phil Calçado - SoundCloud
@pcalcado
http://philcalcado.com
Tuesday, October 1, 13

2011: Phil zieht nach Berlin
Tuesday, October 1, 13

~ 200 million users / month
> 11 hours of audio
uploaded every minute
Tuesday, October 1, 13

http://bit.ly/15DToNK
hiring @ SoundCloud
Tuesday, October 1, 13

Phone
Code Review
Interviews
Offer
Tuesday, October 1, 13

challenge until late 2012
Tuesday, October 1, 13

you can choose any language.
0
10
20
30
40
Ruby Java JavaScript (Node.js) C Clojure Scala
% of submissions ~2011-2012
Tuesday, October 1, 13

you can choose any language.
0
10
20
30
40
Ruby Java JavaScript (Node.js) C Clojure Scala
rejected before interview invited for inverview
Tuesday, October 1, 13

you can choose any language.
0
7.5
15
22.5
30
Ruby Java JavaScript (Node.js) Go Clojure Scala
% of submissions on the past ~1 year
Tuesday, October 1, 13

you can choose any language.
0
7.5
15
22.5
30
Ruby Java JavaScript (Node.js) Go Clojure Scala
rejected before interview invited for inverview
Tuesday, October 1, 13

you can choose any language.
0
7.5
15
22.5
30
Ruby Java JavaScript (Node.js) Go Clojure Scala
rejected before interview invited for inverview
WTF?
Tuesday, October 1, 13

http://bit.ly/J1aLNn
don’t get me wrong
we are all hipsters
Tuesday, October 1, 13

Not OO, not Functional...
Just (bad) Procedural code.
Tuesday, October 1, 13

http://bit.ly/JiECRp
Tuesday, October 1, 13

we don’t need this complicated stuff.
this is not java, you know.
Tuesday, October 1, 13

http://bit.ly/JiFSnq
so how do we structure our app?
Tuesday, October 1, 13

what to use?
(decent)
procedures?
Tuesday, October 1, 13

what to use?
objects?
Tuesday, October 1, 13

what to use?
...functions?
Tuesday, October 1, 13

http://bit.ly/JFbZt8
Tuesday, October 1, 13

http://bit.ly/JFbZt8
“SICP and some of the Sussman & Steele "Lambda
the ..." papers made a big impression on me years
before, although I did not understand their full
meaning then.
Remember, I was recruited to "do Scheme" [...] My
interest in languages such as Self informed a
subversive agenda [...]. Likewise with ﬁrst-class
functions, which were inspired by Scheme [...]”
Tuesday, October 1, 13

http://bit.ly/JiEQYM
Tuesday, October 1, 13

http://bit.ly/JiF7ef
going old school
Tuesday, October 1, 13

e.g. passing functions around
Tuesday, October 1, 13

we see a lot of this
Tuesday, October 1, 13

1st, we extract what is common
Tuesday, October 1, 13

then we refactor our functions
Tuesday, October 1, 13

and we send them as arguments
Tuesday, October 1, 13

e.g. closures not only for objects
Tuesday, October 1, 13

we can keep writeComment as it is
Tuesday, October 1, 13

and we add a function with two closures
Tuesday, October 1, 13

and we add a function with two closures
immutable
Tuesday, October 1, 13

and we add a function with two closures
immutablemutable
Tuesday, October 1, 13

now we don’t need to pass in the kitchen sink
Tuesday, October 1, 13

e.g. functions all the way down
Tuesday, October 1, 13

ﬁrst we extract common protocol
Tuesday, October 1, 13

then we clean up our functions
Tuesday, October 1, 13

then we use them.
Tuesday, October 1, 13

then we use them. redundant?
Tuesday, October 1, 13

http://bit.ly/JiETnd
Tuesday, October 1, 13

our “framework”:
1 - Extract protocol in
“combinators”
2 - Keep mutable state in
closures
Tuesday, October 1, 13

no scary monads required
Tuesday, October 1, 13

there is plenty to learn from
Tuesday, October 1, 13

in the javascript community too
Tuesday, October 1, 13

phil calçado
http://philcalcado.com
@pcalcado
www.soundcloud.com
Tuesday, October 1, 13

How to Design Programs - http://bit.ly/K0BfrL
Structure and Interpretation of Computer
Programs - http://bit.ly/K0BjYm
The Art of the Metaobject Protocol
http://amzn.to/K0BqU1
Purely Functional Data Structures
http://amzn.to/JFn4KG
Let Over Lambda - http://amzn.to/IMMkNO
An Introduction to Lambda Calculi for Computer
Scientists - http://amzn.to/IX8d1B
All drawings are available as t-shirts from the
awesome Diesel Sweeties -
http://dieselsweeties.com/
Tuesday, October 1, 13

Más contenido relacionado

Destacado

SoundCloud's microservice architecture is built mostly in Scala, using Finagle as its distributed systems workhorse. Finagle is an RPC system for the JVM, and it is based on a pipes-and-filters architecture that maps very nicely to functional programming concepts of higher-order functions and combinators. Over the past few years we have found that it is extremely useful to go even a step further and think of microservices as functions themselves. In this talk let's explore how SoundCloud uses Scala and Finagle, and how we started thinking of a microservices architecture as a special case of a functional system.

ScalaItaly 2015 - Your Microservice as a Function

Phil Calçado

SoundCloud is the largest repository of audio on the web, used by more than 200 million people every month, who upload more than 11 hours of audio every minute. Like so many others, we have migrated from a typical monolithic architecture to microservices. While the benefits brought by this style of SOA to our productivity and reliability are clear, the architecture required some non-obvious changes in the way we operate systems, and a way to tackle the overhead associated with having hundreds of small moving parts to serve every request. In this talk we’ll share the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable. What do we do about the operations overhead? How to spread devops skills across teams to support the “you build it, you run it” vision? How to deal with breaking changes and asynchronous behaviours? How to deal with chatty interactions? Which protocol? How do I even get a diagram telling me how all this stuff is put together?

Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015

Phil Calçado

Rhein-Main Scala Enthusiasts — Your microservice as a Function

Phil Calçado

A arquitetura de micro-serviços é fundamentada na explosão de uma aplicação grande e monolítica em um conjunto de APIs e componentes muito pequenos, com baixíssima capacidade funcional, visando independência e autonomia dessas pequenas partes. Nessa palestra vamos explorar alguns casos de uso desse estilo arquitetural, as motivações para a utilização da arquitetura de micro-serviços, comparando-a com as abordagens tradicionais de SOA e arquiteturas monolíticas. Veremos também quais os benefícios e desafios na composição das equipes de projetos, na comunicação entre os serviços e no gerenciamento dos dados. Apresentação realizada em 2014 no QCon Rio.

Vida longa para SOA com microservices

Fábio Rosato

Microservices - Quebrando gigantes em pequenos

Vinícius Krolow

Amadurecendo Equipes com Microservices

sanchez_ivan

Um pequeno estudo sobre a microsoft

Diego Eis

Integração utilizando REST API e Microservices

Denis Santos

Flexbox and Grid Layout: How you will structure layouts tomorrow.

Diego Eis

Microservices

Diego Pacheco

DOM, CSSOM e RenderThree - Introdução ao Browser Render Path

Diego Eis

Introdução à Microservices

André Faria Gomes

Workshop soa, microservices e devops

Diego Pacheco

Microservices é um estilo arquitetural que têm revolucionado o desenvolvimento de aplicações através de pequenos serviços, desacoplados e com foco em executar uma tarefa específica comunicando-se através de Web APis ou mensagens assíncronas. Nesta palestra será apresentado como microservices é capaz de solucionar seus problemas no desenvolvimento de sistemas robustos e escaláveis. Serão abordadas as principais características deste paradigma, quais as vantagens e desvantagens em comparação a arquiteturas monolíticas, exemplos e situações de uso.

Microservices: uma abordagem para arquitetura de aplicações (Devcamp 2015)

Tiago Marchetti Dolphine

O que você precisa saber para se tornar um dev front-end

Diego Eis

A demanda cada vez maior por agilidade, inovação e escalabilidade das soluções digitais tem impulsionado a adoção da arquitetura baseada em microservices. Os benefícios desta abordagem são reais e significativos, mas esse estilo arquitetural traz uma série de novos desafios. Nesta apresentação, vamos fazer um mergulho profundo a partir de exemplos detalhados sobre as vantagens e desvantagens dessa abordagem arquitetural, como por exemplo: Explorar como realizar a decomposição funcional e como definir taxonomias e granularidades adequadas para os microservices; Como solucionar problemas arquiteturais como Client-side service discovery e Server-side service discovery, invocação, logging e monitoramento; Definir protocolos de comunicação (HTTP, AMQP e Websocket) de forma minimizar a latência e lidar com outros requisitos não funcionais; Como atacar questões de replicação de dados e regras de negócio e dados; Design Patterns para problemas arquiteturais recorrentes; Como conduzir a operação e evolução de um sistema nesta abordagem.

Vantagens e desvantagens de uma arquitetura microservices

Fábio Rosato

UX, Front-end and Back-end: How front-end can help these guys?

Diego Eis

O básico sobre Web Semântica, JSON-LD e Linked Data

Diego Eis

Destacado (18)

ScalaItaly 2015 - Your Microservice as a Function

Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015

Rhein-Main Scala Enthusiasts — Your microservice as a Function

Vida longa para SOA com microservices

Microservices - Quebrando gigantes em pequenos

Amadurecendo Equipes com Microservices

Um pequeno estudo sobre a microsoft

Integração utilizando REST API e Microservices

Flexbox and Grid Layout: How you will structure layouts tomorrow.

Microservices

DOM, CSSOM e RenderThree - Introdução ao Browser Render Path

Introdução à Microservices

Workshop soa, microservices e devops

Microservices: uma abordagem para arquitetura de aplicações (Devcamp 2015)

O que você precisa saber para se tornar um dev front-end

Vantagens e desvantagens de uma arquitetura microservices

UX, Front-end and Back-end: How front-end can help these guys?

O básico sobre Web Semântica, JSON-LD e Linked Data

Más de Phil Calçado

PicPay is the largest digital wallet in Latin America. We offer peer-to-peer payments, BNPL, credit cards, personal loans, insurance, investing, trading, and other financial products to 60 million people and 5 million merchants, processing over $20 billion yearly. But just three years ago, in 2019, PicPay was 30 engineers in a small office working on a single product for a few million users. Growing our product portfolio, team size, and the number of transactions by several orders of magnitude so quickly was as chaotic as you might imagine—but we've done it! Our approach gave teams and engineers radical autonomy to choose the best tool, process, and technology for their area. This strategy was invaluable in handling hypergrowth, but as we stabilize as a business and product, we have realized that what took us here isn't what will keep us moving forward. In this talk, let's explore the consequences of how we dealt with our hypergrowth phase and what are the changes and initiatives we have put in place to make sure that we keep growing and pushing the envelope—but at a manageable pace this time around. Phil Calçado is the Global CTO at PicPay. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, leading the team that built the live events platform used by 44 million people worldwide. He has also led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in adopting Microservices architectures. https://plus.qconferences.com/plus2022/presentation/afterparty-refactoring-after-100x-hypergrowth

the afterparty: refactoring after 100x hypergrowth

Phil Calçado

Presented at LeadingEng New York 2022 (https://leaddev.com/leadingeng-new-york/video/dont-try-home-how-practice-self-improvement-senior-leader) -- Most of us have developed our expertise as engineers through a mix of literature and experimentation. The software industry moves at a higher speed than others because we can try and study complex, real-world systems in the comfort of our bedrooms and personal Github accounts. When you become a leader, especially one who leads other leaders, things get a little more complicated. There are books, but they tend to contain generic advice. There are patterns, but the nature of the job makes it harder to identify when and how to apply them. In this session, I want to walk through a few things that have worked for me when you don't have a lab to try things out. Let's explore processes, tools, and resources to continuously improve your skills and expertise when there is no StackOverflow and no coding dojos. Phil Calçado is Global CTO at PicPay, the largest digital wallet in Latin America. He leads a team of more than 1,500 engineers building financial products for 60 million users and processing over four billion dollars yearly. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, where he led the team that built the live events platform used by 44 million people worldwide. He also has led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in the adoption of Microservices architectures.

don't try this at home: self-improvement as a senior leader

Phil Calçado

The Economics of Microservices (redux)

Phil Calçado

From microservices to serverless - Chicago CTO Summit 2019

Phil Calçado

For the last ten years or so, many companies have focused on migrating from larger, monolithic systems and applications towards a specific style of Service-Oriented Architecture called Microservices. The promise was that these smaller, loosely-coupled, and independently developed components would increase productivity and safety for organizations, as large and complex business challenges can be broken down into smaller and simpler components. However, even before most organizations were able to fully migrate to this new architecture and enjoy its promised benefits, a new iteration of cloud computing has been made available in the shape of Serverless platforms such as AWS Lambda, and Google Cloud and Microsoft Azure Functions. Now lots of companies found themselves conflicted between abandoning their traditional microservices approach towards Serverless, often even before they have fully migrated to it from the legacy systems. After leading successful Microservices adoption at SoundCloud and DigitalOcean, recently at Meetup I have faced the challenge of pivoting from a traditional monolith-to-microservices migration to a cloud-native platform. In this talk, let's discuss the fundamental concepts, technologies, and practices behind Microservices and Serverless, and how a software architect used to distributed systems based on microservices needs to change their mindset and approach when adopting Serverless.

The Not-So-Straightforward Road From Microservices to Serverless

Phil Calçado

Ten Years of Failing Microservices

Phil Calçado

How are microservices in 2017 different from how we used to build them at the beginning of the decade? More traditional Service-Oriented Architectures were defined by protocols and standards published and curated by industry consortiums. Knowledge of the architectural style usually called "microservices", on the other hand, is often in the form of patterns, cautionary tales, and tools extracted from real-world reports and software made available by organisations that have adopted this style. Almost ten years since the first wave of such reports, the landscape has changed considerably. Many hard challenges from the past have been eased or completely solved, and a lot of the custom software created by the microservices pioneers have been made off-the-shelf open source software. In this talk, Phil Calçado will contrast what we first found in the first generation of microservices architectures against the current generation's landscape. Let's talk about which previous common knowledge and patterns are deprecated, which ones are still active, and introduce some of the ones that have been recently added to our toolbox.

The Next Generation of Microservices

Phil Calçado

The Next Generation of Microservices — YOW 2017 Brisbane

Phil Calçado

The Economics of Microservices (2017 CraftConf)

Phil Calçado

TALK #2: Microservices vs. The First Law of Object Design We've been breaking systems and application into smaller components for a long time now. From Component-Based Design to Distributed Objects to SOA to what is today's preferred golden hammer: microservices. One definition of microservices is that it is a flavor of SOA that emphasizes many specialize services versus a few more generalist ones. Often these microservices are so small that they take care of a single "object". Distributed objects aren't new to this industry, and in 2003, Martin Fowler wrote a classic article where he discusses several problems with this model, and proposes the First Law of Distributed Objects: "Objects have been around for a while, and sometimes it seems that ever since they were created, folks have wanted to distribute them. However, distribution of objects, or indeed of anything else, has a lot more pitfalls than many people realize, especially when they're under the influence of vendors' cozy brochures. This article is about some of these hard lessons-lessons I've seen many of my clients learn the hard way... my First Law of Distributed Object Design: Don’t distribute your objects!" Reinventing the wheel is nothing new in our field, but if microservices are meant to be small, how can we avoid the same problems from the past? What are the technologies, architectures, protocols, and practices we need in place to make sure that our microservices architecture isn't just the largest bowl of spaghetti this organization has ever cooked? SPEAKER: Phil Calçado, Director of Software Engineering at DigitalOcean Phil Calçado works at DigitalOcean, where he helps build the cloud for developers. Before that, he spent four years building the team and architecture behind SoundCloud's move from a monolith to microservices. He tweets at @pcalcado writes at http://philcalcado.com.

Microservices vs. The First Law of Distributed Objects - GOTO Nights Chicago ...

Phil Calçado

Finagle @ SoundCloud

Phil Calçado

A Brief Talk On High-Performing Organisations

Phil Calçado

Finagle-Based Microservices at SoundCloud

Phil Calçado

An example of Future composition in a real app

Phil Calçado

From a monolithic Ruby on Rails app to the JVM

Phil Calçado

Applying Evolutionary Architecture on a Popular API

Phil Calçado

SoundCloud Masterclass on Brazil

Phil Calçado

SpeakerConf: my findings in trying to use this functional programming busines...

Phil Calçado

[GOTO Copenhagen 2012] The Startup Hangover: Supporting 15 mil Users

Phil Calçado

When writing Object-Oriented software these days, few developers doubt the benefits of TDD. The Software Craftsmanship movement even goes one step further, and says that it is just plain irresponsible to write software without this tool. More and more projects are using Functional programming languages, though, and TDD is not so common in this side of the software development world. Maybe TDD doesn’t make sense outside Object-Oriented software? After experimenting with the TDD mindset and Functional languages in real-world projects, my experience is that those also benefit a lot from using tests as design aid. In this talk, let’s investigate what is generally accepted as good practices in Functional Programming and how to use TDD to take us there, with examples in Clojure.

(v2.0) Better Functional Design Through Test-Driven Development

Phil Calçado

Más de Phil Calçado (20)

the afterparty: refactoring after 100x hypergrowth

don't try this at home: self-improvement as a senior leader

The Economics of Microservices (redux)

From microservices to serverless - Chicago CTO Summit 2019

The Not-So-Straightforward Road From Microservices to Serverless

Ten Years of Failing Microservices

The Next Generation of Microservices

The Next Generation of Microservices — YOW 2017 Brisbane

The Economics of Microservices (2017 CraftConf)

Microservices vs. The First Law of Distributed Objects - GOTO Nights Chicago ...

Finagle @ SoundCloud

A Brief Talk On High-Performing Organisations

Finagle-Based Microservices at SoundCloud

An example of Future composition in a real app

From a monolithic Ruby on Rails app to the JVM

Applying Evolutionary Architecture on a Popular API

SoundCloud Masterclass on Brazil

SpeakerConf: my findings in trying to use this functional programming busines...

[GOTO Copenhagen 2012] The Startup Hangover: Supporting 15 mil Users

(v2.0) Better Functional Design Through Test-Driven Development

Último

MySQL Webinar, presented on the 25th of April, 2024. Summary: MySQL solutions enable the deployment of diverse Database Architectures tailored to specific needs, including High Availability, Disaster Recovery, and Read Scale-Out. With MySQL Shell's AdminAPI, administrators can seamlessly set up, manage, and monitor these solutions, ensuring efficiency and ease of use in their administration. MySQL Router, on the other hand, provides transparent routing from the application traffic to the backend servers in the architectures, requiring minimal configuration. Completely built in-house and supported by Oracle, these solutions have been adopted by enterprises of all sizes for their business-critical applications. In this presentation, we'll delve into various database architecture solutions to help you choose the right one based on your business requirements. Focusing on technical details and the latest features to maximize the potential of these solutions.

Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...

Miguel Araújo

Histor y of HAM Radio presentation slide

vu2urc

Developing An App To Navigate The Roads of Brazil

V3cube

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Scaling API-first – The story of a global engineering organization

Radu Cotescu

As privacy and data protection regulations evolve rapidly, organizations operating in multiple jurisdictions face mounting challenges to ensure compliance and safeguard customer data. With state-specific privacy laws coming up in multiple states this year, it is essential to understand what their unique data protection regulations will require clearly. How will data privacy evolve in the US in 2024? How to stay compliant? Our panellists will guide you through the intricacies of these states' specific data privacy laws, clarifying complex legal frameworks and compliance requirements. This webinar will review: - The essential aspects of each state's privacy landscape and the latest updates - Common compliance challenges faced by organizations operating in multiple states and best practices to achieve regulatory adherence - Valuable insights into potential changes to existing regulations and prepare your organization for the evolving landscape

TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments

TrustArc

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

GenCyber Cyber Security Day Presentation

Michael W. Hawkins

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

Handwritten Text Recognition for manuscripts and early printed texts

Maria Levchenko

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

Discord is a free app offering voice, video, and text chat functionalities, primarily catering to the gaming community. It serves as a hub for users to create and join servers tailored to their interests. Discord’s ecosystem comprises servers, each functioning as a distinct online community with its own channels dedicated to specific topics or activities. Users can engage in text-based discussions, voice calls, or video chats within these channels. Understanding Discord Servers Discord servers are virtual spaces where users congregate to interact, share content, and build communities. Servers may revolve around gaming, hobbies, interests, or fandoms, providing a platform for like-minded individuals to connect. Communication Features Discord offers a range of communication tools, including text channels for messaging, voice channels for real-time audio conversations, and video channels for face-to-face interactions. These features facilitate seamless communication and collaboration. What Does NSFW Mean? The acronym NSFW stands for “Not Safe For Work,” indicating content that may be inappropriate for professional or public settings. NSFW Content NSFW content encompasses material that is sexually explicit, violent, or otherwise graphic in nature. It often includes nudity, profanity, or depictions of sensitive topics.

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

UK Journal

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Tech Trends Report 2024 Future Today Institute.pdf

hans926745

Advantages of Hiring UIUX Design Service Providers for Your Business

Pixlogix Infotech

Why code in Node.js often get rejected by SoundCloud

1. Why code in Node.js often get rejected by SoundCloud Phil Calçado - SoundCloud @pcalcado http://philcalcado.com Tuesday, October 1, 13

2. 2011: Phil zieht nach Berlin Tuesday, October 1, 13

3. Tuesday, October 1, 13

4. ~ 200 million users / month > 11 hours of audio uploaded every minute Tuesday, October 1, 13

5. Tuesday, October 1, 13

6. http://bit.ly/15DToNK hiring @ SoundCloud Tuesday, October 1, 13

7. Phone Code Review Interviews Offer Tuesday, October 1, 13

8. Phone Code Review Interviews Offer Tuesday, October 1, 13

9. challenge until late 2012 Tuesday, October 1, 13

10. you can choose any language. 0 10 20 30 40 Ruby Java JavaScript (Node.js) C Clojure Scala % of submissions ~2011-2012 Tuesday, October 1, 13

11. you can choose any language. 0 10 20 30 40 Ruby Java JavaScript (Node.js) C Clojure Scala rejected before interview invited for inverview Tuesday, October 1, 13

12. new challenge Tuesday, October 1, 13

13. you can choose any language. 0 7.5 15 22.5 30 Ruby Java JavaScript (Node.js) Go Clojure Scala % of submissions on the past ~1 year Tuesday, October 1, 13

14. you can choose any language. 0 7.5 15 22.5 30 Ruby Java JavaScript (Node.js) Go Clojure Scala % of submissions on the past ~1 year Tuesday, October 1, 13

15. you can choose any language. 0 7.5 15 22.5 30 Ruby Java JavaScript (Node.js) Go Clojure Scala rejected before interview invited for inverview Tuesday, October 1, 13

16. you can choose any language. 0 7.5 15 22.5 30 Ruby Java JavaScript (Node.js) Go Clojure Scala rejected before interview invited for inverview WTF? Tuesday, October 1, 13

17. http://bit.ly/J1aLNn don’t get me wrong we are all hipsters Tuesday, October 1, 13

18. Tuesday, October 1, 13

19. Not OO, not Functional... Just (bad) Procedural code. Tuesday, October 1, 13

20. http://bit.ly/JiECRp Tuesday, October 1, 13

21. we don’t need this complicated stuff. this is not java, you know. Tuesday, October 1, 13

22. http://bit.ly/JiFSnq so how do we structure our app? Tuesday, October 1, 13

23. what to use? (decent) procedures? Tuesday, October 1, 13

24. Tuesday, October 1, 13

25. Tuesday, October 1, 13

26. what to use? objects? Tuesday, October 1, 13

27. Tuesday, October 1, 13

28. what to use? ...functions? Tuesday, October 1, 13

29. http://bit.ly/JFbZt8 Tuesday, October 1, 13

30. http://bit.ly/JFbZt8 “SICP and some of the Sussman & Steele "Lambda the ..." papers made a big impression on me years before, although I did not understand their full meaning then. Remember, I was recruited to "do Scheme" [...] My interest in languages such as Self informed a subversive agenda [...]. Likewise with ﬁrst-class functions, which were inspired by Scheme [...]” Tuesday, October 1, 13

31. http://bit.ly/JiEQYM Tuesday, October 1, 13

32. Tuesday, October 1, 13

33. Tuesday, October 1, 13

34. Tuesday, October 1, 13

35. Tuesday, October 1, 13

36. Tuesday, October 1, 13

37. http://bit.ly/JiF7ef going old school Tuesday, October 1, 13

38. e.g. passing functions around Tuesday, October 1, 13

39. we see a lot of this Tuesday, October 1, 13

40. 1st, we extract what is common Tuesday, October 1, 13

41. then we refactor our functions Tuesday, October 1, 13

42. and we send them as arguments Tuesday, October 1, 13

43. e.g. closures not only for objects Tuesday, October 1, 13

44. we see a lot of this Tuesday, October 1, 13

45. we can keep writeComment as it is Tuesday, October 1, 13

46. and we add a function with two closures Tuesday, October 1, 13

47. and we add a function with two closures immutable Tuesday, October 1, 13

48. and we add a function with two closures immutablemutable Tuesday, October 1, 13

49. now we don’t need to pass in the kitchen sink Tuesday, October 1, 13

50. e.g. functions all the way down Tuesday, October 1, 13

51. we see a lot of this Tuesday, October 1, 13

52. ﬁrst we extract common protocol Tuesday, October 1, 13

53. then we clean up our functions Tuesday, October 1, 13

54. then we use them. Tuesday, October 1, 13

55. then we use them. redundant? Tuesday, October 1, 13

56. http://bit.ly/JiETnd Tuesday, October 1, 13

57. our “framework”: 1 - Extract protocol in “combinators” 2 - Keep mutable state in closures Tuesday, October 1, 13

58. no scary monads required Tuesday, October 1, 13

59. there is plenty to learn from Tuesday, October 1, 13

60. in the javascript community too Tuesday, October 1, 13

61. phil calçado http://philcalcado.com @pcalcado www.soundcloud.com Tuesday, October 1, 13

62. How to Design Programs - http://bit.ly/K0BfrL Structure and Interpretation of Computer Programs - http://bit.ly/K0BjYm The Art of the Metaobject Protocol http://amzn.to/K0BqU1 Purely Functional Data Structures http://amzn.to/JFn4KG Let Over Lambda - http://amzn.to/IMMkNO An Introduction to Lambda Calculi for Computer Scientists - http://amzn.to/IX8d1B All drawings are available as t-shirts from the awesome Diesel Sweeties - http://dieselsweeties.com/ Tuesday, October 1, 13

Why code in Node.js often get rejected by SoundCloud

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (18)

Más de Phil Calçado

Más de Phil Calçado (20)

Último

Último (20)

Why code in Node.js often get rejected by SoundCloud