# Hadi Hariri

Hadi Hariri's Web Site

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Advocacy and your personal brand

DevFeed: [Advocacy and your personal brand](<https://devfeed.tech/articles/advocacy-and-your-personal-brand-41879.md>)

Original publisher: [Read original article](<http://hadihariri.com/2022/01/07/advocacy-and-your-personal-brand/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2022-01-06T23:00:00Z

Content type: opinion

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [jetbrains](<https://devfeed.tech/topics/jetbrains.md>), [integrity](<https://devfeed.tech/topics/integrity.md>)

Tags: [advocacy](<https://devfeed.tech/tags/advocacy.md>), [brand](<https://devfeed.tech/tags/brand.md>), [career](<https://devfeed.tech/tags/career.md>), [developer](<https://devfeed.tech/tags/developer.md>), [me](<https://devfeed.tech/tags/me.md>), [product](<https://devfeed.tech/tags/product.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

An opinion article about building a credible personal brand in developer advocacy. It emphasizes believing in the product, maintaining hands-on experience through projects or open source work, communicating internally, supporting product teams, and accepting honest feedback.

### Source excerpt

There are many aspects that contribute to being successful in Developer Advocacy. Branding is probably one of the most important elements of a successful advocacy career. During my years as an Advocate, there are some collected wisdoms I've learned which I'd like to share: Believe in what you do This may seem quite obvious, but if you don't believe in the product that you're advocating for, it's going to be very difficult for you to project any confidence to people when you're talking about it. Not only will it be hard, but it negatively damages your own brand. People can sense your sincerity. Practice what you preach Every single person that I've interviewed, and I've asked why they want to join advocacy, tell me that it's because they've been doing "advocacy on the side" and have so much knowledge they want to write and speak about it. They say they love the idea of being able to do it full time. Forgetting for a moment that advocacy isn't just about content (in any form), one of the greatest challenges in Advocacy is continuing to have that input stream of "stuff" to talk about. See, when you're a full time developer or consultant, you're constantly faced with interesting challenges that sprout new ideas in your head. When you're a full time advocate, this no longer happens. Once the well of ideas you brought with you dries up, what's next? That's when you risk becoming a pundit, and consequently damaging your brand. This is why it's critical that you continue to do "stuff", not just talk about it. Whether it's internal projects, whether it's working on OSS, or helping customers with issues, having hands-on experience is key to keeping your brand credible. Work on your brand internally As an advocate, our primary goals (at least at JetBrains) are to educate folks and provide feedback to product teams to improve our products. As important as it is to work on your brand externally, it's also important to do so internally. Make sure that your colleagues understand t

## Applying for Developer Advocacy

DevFeed: [Applying for Developer Advocacy](<https://devfeed.tech/articles/applying-for-developer-advocacy-41878.md>)

Original publisher: [Read original article](<http://hadihariri.com/2022/01/03/applying-for-developer-advocacy/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2022-01-02T23:00:00Z

Content type: article

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [jetbrains](<https://devfeed.tech/topics/jetbrains.md>)

Tags: [advocacy](<https://devfeed.tech/tags/advocacy.md>), [applying](<https://devfeed.tech/tags/applying.md>), [communication](<https://devfeed.tech/tags/communication.md>), [communication-skills](<https://devfeed.tech/tags/communication-skills.md>), [community](<https://devfeed.tech/tags/community.md>), [cv](<https://devfeed.tech/tags/cv.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-advocate](<https://devfeed.tech/tags/developer-advocate.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [development](<https://devfeed.tech/tags/development.md>), [events](<https://devfeed.tech/tags/events.md>), [experience](<https://devfeed.tech/tags/experience.md>), [github](<https://devfeed.tech/tags/github.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [speaking](<https://devfeed.tech/tags/speaking.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tools](<https://devfeed.tech/tags/tools.md>), [using](<https://devfeed.tech/tags/using.md>), [you-re](<https://devfeed.tech/tags/you-re.md>)

### AI overview

For JetBrains Developer Advocacy roles, real-world software development experience is the key requirement: advocates help developers and product teams, and applicants should highlight their development background. The text also recommends showing familiarity with JetBrains tools and a genuine interest in improving them, communication skills, community activities or online presence, and teaching through formats such as talks, screencasts, or writing. Community prominence is helpful but not essential, and applicants need not be equally strong in every area; the team encourages building weaker skills over time.

### Source excerpt

We have a few positions open for Developer Advocacy at JetBrains, and for the past several months I've been going through CVs. I usually look for specific things that stand-out for the role and thought it might be worth sharing these. Developer Experience Developer Advocacy is first and foremost about Software Development. You are someone that will be helping developers. You are someone that will be helping the product teams make a better product. Both of these are hard to accomplish if you don't have the experience and war-stories. Highlight your experience as a developer in your CV. In the 12 years I've been involved in Advocacy, only on a couple of occasions did we hire someone with little real-world developer experience, but these were justified for other reasons. Experience with JetBrains Tools We want folks that join JetBrains to believe in what we're doing, and enjoy using our products. If you don't, then you probably won't be happy at your job. If you use our products, make sure you point it out. You don't need to be an expert, but believing in them and wanting to help improve them is important. We are strongly against hiring shills. Communication Skills Communicating is critical in the role. Whether it's talking to a customer at a booth, or talking to developers inside the company, it must be something that you're not only good at but enjoy doing. As such, highlighting communication skills is important when applying for the role. Community Presence As a Developer Advocate, having a community presence is important. Provide information about your community activities and/or online presence, whether it's speaking, organising events, social media accounts, GitHub or other repository accounts. Note however that while community presence is important, it's not critical. You don't have to be a micro-celebrity in your community to get a job as a Developer Advocate at JetBrains. We're not particularly looking for big names. We're looking for people that are aligned w

## A few words on Git.

DevFeed: [A few words on Git.](<https://devfeed.tech/articles/a-few-words-on-git-41876.md>)

Original publisher: [Read original article](<http://hadihariri.com/2020/10/14/a-few-words-on-git/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2020-10-13T22:00:00Z

Content type: opinion

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [distributed](<https://devfeed.tech/tags/distributed.md>), [failure](<https://devfeed.tech/tags/failure.md>), [git](<https://devfeed.tech/tags/git.md>), [hacker-news](<https://devfeed.tech/tags/hacker-news.md>), [reddit](<https://devfeed.tech/tags/reddit.md>), [system](<https://devfeed.tech/tags/system.md>), [twitter](<https://devfeed.tech/tags/twitter.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The author distinguishes Git's widespread adoption from success at delivering a good distributed version control experience. They argue that users should not need deep knowledge of Git's internals or memorized command sequences to avoid mistakes and manage branches. Their desired system would protect work from easy-to-make errors and remember or guide branching and collaboration workflows while hiding unnecessary complexity. They note that a graphical interface alone does not solve broader usability problems, and that Git being better than earlier tools or widely used does not rule out better alternatives. The excerpt presents these as the author's opinions and does not specify a concrete replacement.

### Source excerpt

I tweeted something about Git. Do I regret it? A little bit. Why? Because it had a grammar mistake. Git is not a success story. Git is a failure as a system with a crap user experience that forces you to learn more about the tool you're using that about getting your work done. -- Hadi Hariri (@hhariri) October 8, 2020 The tweet made some rounds and died off. Then someone posted it on Hacker News, and it made more rounds, and then it died. Then someone posted it on Reddit, and the damn thing just doesn't die off! The feedback The replies to the tweet can be grouped in two: Folks that agree Those that don't agree (and some are very angry) I want to address the second group because it seems many of them don't seem to get my point, and I keep repeating myself in replies to the tweet. Of course, it's wishful thinking if anyone reads this post because at times, I find folks often don't even read Twitter threads. Having said that, let's try and categorize the responses: You're an idiot for saying it's not successful. It's used everywhere! Let's first address what I mean by success. If we're talking about reach, Git is successful, yes. It's probably the most used Version Control system. If we're talking about people being frustrated and banging their heads to the wall because of Git, I'd say it probably is also successful. Jokes aside though, the success I was talking about is actually in the context of the tweet - it is not (remember, this is my opinion) successful at its job of being a distributed version control system, because it fails at the user experience. More on why later. So let's put success into context - especially on Twitter. Remember we only read single tweets. You're a professional. Learn the tool or GTFO. I suck at Git. But let's say for a moment that I didn't suck at Git. The response of "learn the tool" is not only assuming that you know my knowledge about Git, but also implying that everything is wonderful, and the problem lies only in that we, as users,

## From Zero to Lambda with Kotless

DevFeed: [From Zero to Lambda with Kotless](<https://devfeed.tech/articles/from-zero-to-lambda-with-kotless-41875.md>)

Original publisher: [Read original article](<http://hadihariri.com/2020/05/12/from-zero-to-lamda-with-kotless/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2020-05-11T22:00:00Z

Content type: tutorial

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [Code](<https://devfeed.tech/topics/code.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [code](<https://devfeed.tech/tags/code.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

A tutorial on using Kotless to deploy Kotlin functions to AWS without writing Terraform files. It covers AWS account and credential setup, serverless functions, and how Kotless derives infrastructure configuration from application code.

### Source excerpt

I know, the title is cringeworthy. In fact the only thing worse is using a subtitle "with only one line of code" But allow me to indulge somewhat, because it really is accurate if one were to consider my knowledge of AWS Lambdas, Terraform, and AWS in general as somewhat zero. I mean sure, I know what they are, but I've not really played with them that much in the past. Today, I managed to create a new AWS account, set up my credentials, write a function in Kotlin and deploy it to AWS without even having to open up a single Terraform file. And all with Kotless. In this post I'm going to walk you through the process. Using Kotless and deploying is in fact the smallest part of the entire thing. Most of this post is about setting up an AWS account and credentials, as well as my very superficial explanation of serverless. If you know all that, just skip right ahead to Writing our function. What is Serverless? I'm pretty sure Wikipedia will offer you a much better definition than I can, but in its simplest form, imagine you want to run a function in the cloud without the overhead of having to have an HTTP application or set-up Docker, or anything else. You just want to run a simple Kotlin function, something like: fun sayHello() = "Say Hello!" which would respond to an endpoint /hello. Different technologies allow you to do that, including AWS Lambdas, Google Cloud Functions, as well as Azure Functions. And with the majority of them you can use their web control panel to write some function and deploy it. But we all know that in real-world applications, you're not using GUIs to write and deploy apps! Terraform Galore So what do you do in the real world? You write Terraform files to deploy your functions. And you don't just write one, you write a lot! And the more functions, the more you need. The more resources you use (databases, files, etc.), the more complex these become. But what's more, if you look through most of these configurations, they're somewhat defining thin

## Routing in Ktor

DevFeed: [Routing in Ktor](<https://devfeed.tech/articles/routing-in-ktor-41872.md>)

Original publisher: [Read original article](<http://hadihariri.com/2020/04/02/Routing-in-Ktor/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2020-04-01T22:00:00Z

Content type: article

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Ktor](<https://devfeed.tech/topics/ktor.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>)

Tags: [2020](<https://devfeed.tech/tags/2020.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [extension](<https://devfeed.tech/tags/extension.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [function](<https://devfeed.tech/tags/function.md>), [hadi-hariri](<https://devfeed.tech/tags/hadi-hariri.md>), [ktor](<https://devfeed.tech/tags/ktor.md>), [order](<https://devfeed.tech/tags/order.md>), [orders](<https://devfeed.tech/tags/orders.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [shipment](<https://devfeed.tech/tags/shipment.md>), [structure](<https://devfeed.tech/tags/structure.md>), [twitter](<https://devfeed.tech/tags/twitter.md>)

### AI overview

Ktor allows routes to be defined by HTTP verb and path, nested under URL groups, and split into `Route` extension functions. The excerpt presents several organization choices: group related routes in files such as `CustomerRoutes.kt`; expose per-file `Application` extensions so startup calls `customerRoutes()` and `orderRoutes()`; split routes into folders or packages, which can make long handlers easier to navigate but may create package and filename clutter; or group code by feature rather than technical layer. Feature-based grouping can complicate server-side templates, especially with FreeMarker, whose loader expects particular locations; the example uses `MultiTemplateLoader` to load templates from multiple directories. The author notes that installing a feature twice raises `DuplicateApplicationFeatureException`, and that grouping routes in objects offers no performance or memory benefit over top-level functions. The excerpt recommends choosing a structure suited to the application.

### Source excerpt

One of Ktor's strong points is in the flexibility it offers in terms of structuring your application. Different to many other server-side frameworks, it doesn't force you into a specific pattern such as having to place all cohesive routes in a single class name {XZY}Controller for instance. Of course, not being forced into using a specific pattern also has its downsides. How am I meant to structure my app? What's the best convention to follow? I recently asked the same question on Twitter If you're using Ktor for server-side, how do you organise your routes? If other, please feel free to reply below. Also RT appreciated. -- Hadi Hariri (@hhariri) March 27, 2020 and the results were somewhat surprising - didn't expect 25.3% of folks to put them all into a single routing function. For anything beyond a simple application this could get quite ugly quite quickly. But it did get me thinking in that maybe it would be good to provide some different samples of how one could structure an application. For our example we're going to assume that our application deals with Customers and Orders. Defining routes Before we talk about how we can group routes, let's first discuss ways in which we can define them. Something which is again quite flexible in Ktor. Generally routes are defined using the routing function. We can then create routes using verbs and paths routing { get("/customer/{id}") { } post("/customer") { } get("/order/{id}") { } } or we can group routes by URL routing { route("/customer") { get { } post { } } } and of course we can also have sub-routes routing { route("/order") { route("/shipment") { get { } post { } } } } Using Route Extension Functions A common pattern is to use extension functions on Route to define the actual routes, allowing us easy access to the verbs, and remove clutter of having all routes in a single routing function. We can apply this pattern independently of how we decide to group routes. As such, the first example could be represented in a c

## Making a habit of giving feedback

DevFeed: [Making a habit of giving feedback](<https://devfeed.tech/articles/making-a-habit-of-giving-feedback-41871.md>)

Original publisher: [Read original article](<http://hadihariri.com/2020/01/31/making-a-habit-of-giving-feedback/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2020-01-30T23:00:00Z

Content type: article

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [jetbrains space](<https://devfeed.tech/topics/jetbrains-space.md>)

Tags: [advocacy](<https://devfeed.tech/tags/advocacy.md>), [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bot](<https://devfeed.tech/tags/bot.md>), [channel](<https://devfeed.tech/tags/channel.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [constructive-criticism](<https://devfeed.tech/tags/constructive-criticism.md>), [cron](<https://devfeed.tech/tags/cron.md>), [data-class](<https://devfeed.tech/tags/data-class.md>), [developer](<https://devfeed.tech/tags/developer.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [manager](<https://devfeed.tech/tags/manager.md>), [peer-to-peer](<https://devfeed.tech/tags/peer-to-peer.md>), [review](<https://devfeed.tech/tags/review.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

JetBrains' Developer Advocacy team introduced a weekly peer feedback routine to make feedback less likely to be forgotten: each person reviews a colleague's work and gives feedback. A Space bot uses the HTTP API to fetch team members, randomly pairs them, and posts the pairs to a feedback channel every Monday morning. With an odd-sized team, one person is paired twice. The authors say it is too early to know whether the routine will be effective or continue; the bot currently serves to assign pairs and send reminders.

### Source excerpt

How many times have you heard yourself or someone else say "We should give more feedback" I'm pretty sure it's too many to count. When it comes to feedback however, we usually think about it in terms of hierarchy; that is, I should receive feedback from my manager, and hopefully also give them feedback. The reality at times though is that we often forget to give feedback to our managers. In her book Radical Candor Kim Scott highlights this point and places emphasis on how important it is for managers to also be recipients of feedback. However, she also talks about another important aspect which is peer-to-peer feedback. This is certainly something we don't do as often as we should. Well, actually! The last sentence isn't entirely correct. Sometimes we're actually quite good at giving feedback to colleagues, very quickly highlighting issues we see. We call it constructive criticism, albeit sometimes it's far from constructive, even if we have no ill-intent. In a recent research by Marcus Buckingham and Ashley Goodall, they wrote about The Feedback Fallacy and how not everything we perceive about feedback is what it seems. But the article also points out, much like Kim does in her book, that feedback can help. As individuals, we strive to improve. Often times the line of work we do doesn't provide us with enough data to know whether we're on the right path. Having external folks guide you can be very beneficial. And of course positive reinforcement is also extremely important as it can help motivate and inspire us to continue to do what we do. I'd love to give feedback, I just don't always remember to Many of us have good intentions and want to give feedback. Yet, we're all busy doing our thing and often de-prioritize this task. On the Developer Advocacy team at JetBrains, we decided to try and put our feedback where our mouth is (sorry...) and do something about it that wouldn't just end up in words. We decided to make it a rule that every person has to review the work

## Your privacy, your control.

DevFeed: [Your privacy, your control.](<https://devfeed.tech/articles/your-privacy-your-control-41870.md>)

Original publisher: [Read original article](<http://hadihariri.com/2019/11/17/your-privacy-your-control/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2019-11-16T23:00:00Z

Content type: opinion

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [online privacy](<https://devfeed.tech/topics/online-privacy.md>), [interface](<https://devfeed.tech/topics/interface.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [advertising](<https://devfeed.tech/tags/advertising.md>), [communications](<https://devfeed.tech/tags/communications.md>), [control](<https://devfeed.tech/tags/control.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [data](<https://devfeed.tech/tags/data.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [options](<https://devfeed.tech/tags/options.md>), [personal](<https://devfeed.tech/tags/personal.md>), [personal-information](<https://devfeed.tech/tags/personal-information.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [privacy-settings](<https://devfeed.tech/tags/privacy-settings.md>), [settings](<https://devfeed.tech/tags/settings.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [simple](<https://devfeed.tech/tags/simple.md>), [simplicity](<https://devfeed.tech/tags/simplicity.md>), [transparent](<https://devfeed.tech/tags/transparent.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

The author argues that complex privacy controls can make user choice misleading: LinkedIn's settings are spread across Privacy, Advertising, and Communications, and even a privacy-conscious user may find them burdensome to configure. Most users may therefore rely on defaults that, the author says, can favor data monetization over privacy. The proposed approach is simpler controls and defaults that share as little as possible. The author criticizes the broader industry trend toward fine-grained settings, including cookie choices, as a way to claim transparency while still collecting personal information.

### Source excerpt

I'm sure you've probably heard Mark Zuckerberg talk about how they are giving their users the choice when it comes to privacy. That they're putting privacy in the hands of you, the user. That you're in control of what you want to share and with whom you want to share it. It's a lie. Lie is harsh? Fair enough. Let's call it misleading. Control Center I'm on LinkedIn and recently I decided to go through the privacy options for my account... And these were just about Privacy. Then we have an entire tab for Advertising, and one more for Communications I'd consider myself a tech-savy person who cares about their privacy, so I probably would take the time to go through all this and try to configure everything. Do you think though that that is something that your everyday user would do? Most likey not, which leaves them in the vulnerable position of relying on what the default options are. And guess what? At times these aren't trying to favour your privacy but maximise the return on your data. And just so it's clear, I'm not singling out LinkedIn. Fortunately I deleted my Facebook account years ago, but I'm guessing that it's somewhat in the same league. We should be favouring simplicity Giving users a command center which at times feels more complex than an plane's cockpit, allowing them to toggle 50 different options to indicate exactly what data they want to share, is not the way we should be defining interfaces if we truly care about our users privacy. We should be making it extremely simple for them to do this, and defaulting to sharing as little as possible. And yet what we're seeing in the industry is a move to more fine-grained control of what exactly we want to be exposed to as a user, whether this is privacy settings or the cookies we want to receive. We disguise this under the pretext of being transparent, yet what we're really trying to do is harvest as much personal information as possible and then tell users (or authorities if they come knocking), that you're i

## Getting Started with Kotlin for .NET Developers

DevFeed: [Getting Started with Kotlin for .NET Developers](<https://devfeed.tech/articles/getting-started-with-kotlin-for-net-developers-41869.md>)

Original publisher: [Read original article](<http://hadihariri.com/2019/08/16/getting-started-with-kotlin-for-net-developers/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2019-08-15T22:00:00Z

Content type: article

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [.NET](<https://devfeed.tech/topics/net.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [blog](<https://devfeed.tech/tags/blog.md>), [book](<https://devfeed.tech/tags/book.md>), [course](<https://devfeed.tech/tags/course.md>), [courses](<https://devfeed.tech/tags/courses.md>), [guides](<https://devfeed.tech/tags/guides.md>), [intellij-idea](<https://devfeed.tech/tags/intellij-idea.md>), [ios](<https://devfeed.tech/tags/ios.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-js](<https://devfeed.tech/tags/kotlin-js.md>), [kotlin-native](<https://devfeed.tech/tags/kotlin-native.md>), [learning](<https://devfeed.tech/tags/learning.md>), [macos](<https://devfeed.tech/tags/macos.md>), [material](<https://devfeed.tech/tags/material.md>), [native](<https://devfeed.tech/tags/native.md>), [net](<https://devfeed.tech/tags/net.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Kotlin now targets the JVM, JavaScript, and native platforms including iOS, macOS, and Windows, as well as Android. Because much documentation and training still assumes Java and JVM familiarity, the excerpt recommends starting with JVM and IntelliJ IDEA guides written from a .NET developer's perspective, then choosing Kotlin instruction by background: Atomic Kotlin assumes no Java or programming experience; the author's introductory and advanced O'Reilly courses aim to accommodate learners without Java experience; Kotlin for Java Developers assumes Java knowledge. Kotlin in Action is also recommended for explanations of the language's rationale and workings. The excerpt says these resources can lead into areas such as mobile, server-side, or native development.

### Source excerpt

I've been asked quite a few times by .NET Developers (as well as those not familiar with Java/JVM), what material to use to get started with Kotlin coming from a non-Java background. As such, I feel it's probably more efficient to have this outlined in a blog post as opposed to a series of tweets. Kotlin was Kotlin/JVM. It no longer is. When we first started Kotlin, the only platform it supported was the JVM. Today we have Kotlin/JS and Kotlin/Native, which opens up possibility to many targets such as iOS, macOS, Windows, etc. And of course Android. But it's no secret that originating on the JVM, there's a heavy influence of this in the documentation, learning material and available courses, most of them assuming that you know some Java and are familiar with the JVM. The good news is that we're working on improving all this, but as with anything, it takes time. In the meantime, hopefully you'll find some of following useful. Getting up to speed with the JVM and the tooling I wrote the following guides when I first came to Kotlin and the JVM, so they very much are from the perspective of a .NET developer. JVM Minimal Survival Guide IntelliJ IDEA Minimal Survival Guide They're mostly still relevant and a good starting point to get you up to speed with the JVM and also IntelliJ IDEA. While there are a lot of comparisons with .NET, obviously any developer can read it and hopefully it will be useful. Also, if you want to learn a bit more about IntelliJ IDEA, there's my IntelliJ IDEA 42 Tips and Tricks talk Getting up to speed with Kotlin If you're completely new to Kotlin, there are quite a few courses available to get you up to speed Atomic Kotlin by Sveta Isakova and Bruce Eckel. This one assume not only zero knowledge of Java, but also of programming. My Intro to Kotlin O'Reilly Course and Advanced one. I've tried to keep this one mostly assuming you may not have a background in Java. Kotlin for Java Developers by Sveta. It does assume some background knowledge of Jav

## Slack and the false sense of urgency

DevFeed: [Slack and the false sense of urgency](<https://devfeed.tech/articles/slack-and-the-false-sense-of-urgency-41868.md>)

Original publisher: [Read original article](<http://hadihariri.com/2018/12/17/slack-and-the-false-sense-of-urgency/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2018-12-16T23:00:00Z

Content type: opinion

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Slack](<https://devfeed.tech/topics/slack.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [email](<https://devfeed.tech/tags/email.md>), [issue-tracker](<https://devfeed.tech/tags/issue-tracker.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [remote](<https://devfeed.tech/tags/remote.md>), [slack](<https://devfeed.tech/tags/slack.md>), [youtrack](<https://devfeed.tech/tags/youtrack.md>)

### AI overview

The author argues that Slack reduced internal email at JetBrains and helped remote coworkers feel connected, but frequent direct pings can interrupt work and cause productivity-harming context switches. Their rule is to use direct Slack messages or small private groups only for urgent matters. For non-urgent discussions or requests to schedule a chat, they recommend email; for bugs and issues needing attention, an issue tracker such as YouTrack, which they say supports ongoing participation and documentation. They reserve channel questions for urgent matters or when they do not know who can help. The goal is to stay available for important Slack conversations without treating every notification as requiring an immediate response. These points come from the supplied excerpt.

### Source excerpt

Slack brought us the promise of reducing emails and having all the knowledge of your company in one place, searchable. While I still feel it's completely failed to deliver on the latter, on the former it most definitely has delivered. Internal emails at JetBrains have been significantly reduced. At least in my case. But I personally feel that it's come at a cost; that of productivity. As a remote person, I very much advocated and encouraged the use of Slack at JetBrains, and I believe that it has greatly benefited our company. In fact, most of our team is remote and we have a channel on Slack which is esssentially the same as a watercooler; giving us a sense of working together and constantly being in touch. Much the same way, it has contributed positively to non-remote workers too. But Slack has also given us the feeling that we can reach out to anyone at any time for anything. The consequence of this however is that frequent interruptions can often lead to context switches which in turn, much like with threads, can impact performance. Now of course, many may say - don't blame the tool but how you use it. And that's OK. In fact many times I've used the same argument, and this post isn't about me "rage-quiting Slack". Instead it's about changing the way I'm now using Slack. A simple rule This change is reduced to a very simple rule: Unless it is urgent, I do not ping a person or a group of people (understanding by this a group DM or small private channel) directly. Instead use email or issue tracker I've moved(ing) back to making use of the right tool at the right moment, as opposed to believing Slack should be used for everything, i.e.: Email or issue tracker for non-urgent discussions or issues that need attention. At JetBrains we make heavy use of YouTrack, not just as a software project management tool, but for many things including organising shows, trips, payments, etc. We also at times use it to have discussions and make decisions. The benefits over email are

## Public Speaking - Questions

DevFeed: [Public Speaking - Questions](<https://devfeed.tech/articles/public-speaking-questions-41864.md>)

Original publisher: [Read original article](<http://hadihariri.com/2018/08/24/public-speaking-questions/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2018-08-23T22:00:00Z

Content type: article

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [recording](<https://devfeed.tech/topics/recording.md>)

Tags: [conference](<https://devfeed.tech/tags/conference.md>), [keynote](<https://devfeed.tech/tags/keynote.md>), [public-speaking](<https://devfeed.tech/tags/public-speaking.md>), [q-a](<https://devfeed.tech/tags/q-a.md>), [questions](<https://devfeed.tech/tags/questions.md>), [recording](<https://devfeed.tech/tags/recording.md>), [series](<https://devfeed.tech/tags/series.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

A public-speaking series installment offers practical advice on handling audience questions during talks, including when to allow questions, whether to defer them, repeating each question, and admitting when an answer is unknown.

### Source excerpt

This is part 5 of a multi-post series on public speaking Dealing with nerves Talk Structure Slides Timing Questions Speaking Should I speak? This post is about dealing with questions, and to be honest there isn't much to share in this area. Nonetheless, I'll cover some of the most common sense aspects of it. Questions? The first question of course should be...should I allow questions? My rule of thumb is yes except if keynotes. And even with keynotes there are exceptions to the rule. If it's a non-technical keynote, then very rarely is there place for questions and most topics I talk about are probably better discussed one on one. As such, a better place to address these types of enquiries and comments is after the talk. If it's a technical keynote, and if there is time after the talk then sure, a few questions are fine. However, never during the talk itself. If it's not a keynote, then I'm good with questions and I'm fine with people to ask it during the talk as opposed to piling it all up at the end. Ironically most conference organisers keep telling speakers that a session should be X minutes with Y minutes Q&A to end the session. I disagree for two reasons: If someone has a question which is not addressed, their mind may start to wander and as a consequence, they can get lost. This is even more so when it's a technical talk and knowledge is built on as the session progresses. If someone has a question, you're pretty certain that at least someone else has the same question. I can't prove it scientifically but it's happened to me so often that there's a high probability it's the case. The flip side of it is that often someone's question will be answered by yourself during the talk at some later point, and you'd save everyone the trouble by avoiding interruptions. However, it's up to you to decide whether saying "we'll get to that" is worth the balance of not allowing questions during your talk. Repeat the question Always repeat the question. It serves two main purpo

## Public Speaking - Talk Structure

DevFeed: [Public Speaking - Talk Structure](<https://devfeed.tech/articles/public-speaking-talk-structure-41861.md>)

Original publisher: [Read original article](<http://hadihariri.com/2018/08/19/public-speaking-talk-structure/>)

Author: Hadi Hariri (mail@hadihariri.com)

Published: 2018-08-18T22:00:00Z

Content type: tutorial

Language: en

Sources: [Hadi Hariri](<https://devfeed.tech/sources/hadi-hariri.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [about-you](<https://devfeed.tech/tags/about-you.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [coherent](<https://devfeed.tech/tags/coherent.md>), [contents](<https://devfeed.tech/tags/contents.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [public-speaking](<https://devfeed.tech/tags/public-speaking.md>), [slides](<https://devfeed.tech/tags/slides.md>), [speaker](<https://devfeed.tech/tags/speaker.md>), [speaking](<https://devfeed.tech/tags/speaking.md>), [structure](<https://devfeed.tech/tags/structure.md>), [summary](<https://devfeed.tech/tags/summary.md>), [talk](<https://devfeed.tech/tags/talk.md>), [talks](<https://devfeed.tech/tags/talks.md>), [technical](<https://devfeed.tech/tags/technical.md>), [the-abstract](<https://devfeed.tech/tags/the-abstract.md>), [time](<https://devfeed.tech/tags/time.md>), [timing](<https://devfeed.tech/tags/timing.md>), [want](<https://devfeed.tech/tags/want.md>)

### AI overview

The article recommends structuring a talk around an introduction, focused and coherent content, and a summary. Keep the introduction under a minute, set expectations, and skip agenda and "About Me" slides; some keynotes or soft-skill talks may not need an introduction. In the main section, limit material and use a central theme to connect ideas. Build technical talks from foundational concepts toward more advanced ones; for less technical talks, the author describes arranging rough slides in Keynote's Light Table view, then reviewing the order and murmuring through each slide to check the flow. Treat the summary as both a final quality check--too many points or difficulty writing it may signal structural problems--and a way to reinforce the talk's message and end clearly.

### Source excerpt

This is part 2 of a multi-post series on public speaking Dealing with nerves Talk Structure Slides Timing Questions Speaking Should I speak? A talk usually consists of three parts: The Intro The Contents The Summary The Intro The intro should give the audience a brief overview of what it is they're going to be hearing, and more importantly set expectations. If it's a technical talk, tell them the level of coverage for instance. Use it as a way to make sure everyone has read the abstract (assuming you've done a good job writing it) and are on the same page. It's also a good way for those that are in the wrong talk, to apply the law of two feet. It should be short though, not more than a minute. Agenda I personally dislike agenda slides. I think they're boring and useless. People often spend a good two to three minutes going over, point by point everything they're going to cover in a talk. For what? Do you believe members of the audience are going to remember the agenda? You think they're going to take a picture of it and reproach you later on if you didn't exactly cover what you mentioned? It's also rare that anyone would come to a talk just because they want to make sure one or two specific items will be covered in it, which an agenda highlights. If you're going into that level of detail in your agenda slide, then you're already spending way too much time on it. Th abstract along with an intro should be more than enough to set the tone for the talk. About me If there's something I dislike more than an agenda slide, it's an "About Me". If you want my opinion (and given you're reading this blog I assume you do), drop it. Completely get rid of any slides that are about you. Time and time again I witness talks where the speaker spends a good couple of minutes talking about themselves, their cats, dogs, kids, what they've done or haven't done with their life. And all of this is usually following a disclaimer of "I don't normally talk about myself"....but here's 20 minutes