Scribe saves you 20+ hours a month in explaining, training & answering “quick" questions. Scribe auto-generates step-by-step guides, complete with text and screenshots. Share what you know without losing another minute. Just click record then go through your process. Scribe creates your guide in seconds. (Yep… it’s REALLY that easy!) Are you ready to… ✅ Save time: Document your processes 15x faster. No more writing steps or uploading screenshots. ✅ Spread knowledge: Find answers to your questions 67% faster. ✅ Increase success: Boost your team’s productivity by 25%. Your colleagues, customers, friends… grandparents (you get the picture 😉) have questions. Show them how it’s done while getting things done.

Scribe

One of the greatest strong points of Kotlin can also be its weakness. When we talk about data classes today, and in the same way java records, we tend to focus, at least many people I know do, on the complete elimination of the boilerplate code. Boilerplate code has been something that has been annoying developers for ages. It exists not only in Java, but other languages have that as well. If we think about creating data access objects any way, it doesn’t really matter if we do it in Kotlin or Java or any other language. Frequently we repeat the same process: repository creation, service and controller. A lot of what we do is boilerplate any way still. However boilerplate code may have been a part of the decision to create data classes or java records, a more important paradigm of software engineering was the actual focal point of creating these types of data structures. It all boils down to immutability or in any case the possibility thereof.Let’s rollback the time and go back to 1995 where we started at some point to create data structures where we would specify different things. We would define the fields, the getters, the setters, the properties, the accessors, the attributes and the parameters in a way to be able to pass our arguments to either the methods, the functions or the contructors.Fot this part we will have some fun programming using the characters of the mid-80’s series: The Golden Girls. Having said this, let’s see how a class would look like for about 15 years: public class GoldenGirlsJava {

    public String goldenGirl1;
    private final String goldenGirl2;
    private final String goldenGirl3;
    private final String goldenGirl4;


    public GoldenGirlsJava() {
        this.goldenGirl1 = "Dorothy Zbornak";
        this.goldenGirl2 = "Rose Nylund";
        this.goldenGirl3 = "Blanche Devereaux";
        this.goldenGirl4 = "Sophia Petrillo";

    }

    public GoldenGirlsJava(
            String goldenGirl1,
            String goldenGirl2,
            String goldenGirl3,
            String goldenGirl4
    ) {
        this.goldenGirl1 = goldenGirl1;
        this.goldenGirl2 = goldenGirl2;
        this.goldenGirl3 = goldenGirl3;
        this.goldenGirl4 = goldenGirl4;
    }

    public String getGoldenGirl1() {
        return goldenGirl1;
    }

    public void setGoldenGirl1(String goldenGirl1) {
        this.goldenGirl1 = goldenGirl1;
    }

    public String getGoldenGirl2() {
        return goldenGirl2;
    }

    public String getGoldenGirl3() {
        return goldenGirl3;
    }

    public String getGoldenGirl4() {
        return goldenGirl4;
    }

    @Override
    public String toString() {
        return "GoldenGirlsJava{" +
                "goldenGirl1='" + goldenGirl1 + '\'' +
                ", goldenGirl2='" + goldenGirl2 + '\'' +
                ", goldenGirl3='" + goldenGirl3 + '\'' +
                ", goldenGirl4='" + goldenGirl4 + '\'' +
                '}';
    }
} This was a tremendous amount of code to type in only to create two contructors. Although the hashcode and equals weren’t necessarily a must in all occasions, we almost always had to implememt a no arguments contructor next to a more generalistic constructor. The good thing about creating all of this boilerplate code is that we knew very clearly how everything would look like after compiling to bytecode. However, and in any case, boilerplate code was always a contentious issue for many developers and so in 2009, lombok came along and revolutionized the way we create data structures. It introduced the concept of using an annotation processor and interpreting specific annotations that would give the qualities we needed for our classes and so a lombok annotated class would look like this: @Getter
@Setter
@AllArgsConstructor
@ToString
public class GoldenGirlsLombok {
    public String goldenGirl1;
    private final String goldenGirl2;
    private final String goldenGirl3;
    private final String goldenGirl4;

    public GoldenGirlsLombok() {
        this.goldenGirl1 = "Dorothy Zbornak";
        this.goldenGirl2 = "Rose Nylund";
        this.goldenGirl3 = "Blanche Devereaux";
        this.goldenGirl4 = "Sophia Petrillo";
    }
} And for a while, people were very happy about Lombok! Finally the weight of having to create all of that boilerplate code was gone. But that felling endured for about 7 years, when a new player arrived and this time it was something the software development industry didn’t expected. It was called Kotlin and in 2016 it debuted with the immediate introduction of data classes. Our golden girls implementation in Kotlin would now look like this: data class GoldenGirls(
    var goldenGirl1: String = "Dorothy Zbornak",
    private val goldenGirl2: String = "Rose Nylund",
    private val goldenGirl3: String = "Blanche Devereaux",
    private val goldenGirl4: String = "Sophia Petrillo"
) Although Kotlin slowly started gathering fans, Java on the other hand realized that something else was in the market and some developments on that side started gaining some steam like project Loom which had been in the making but also left in the back burner for a while. That is why, with the release of Java 14 in 20202, Java introduced java records, and data structures in Java would now look like this: public record GoldenGirlsRecord(
        String goldenGirl1,
        String goldenGirl2,
        String goldenGirl3,
        String goldenGirl4
) {
    public GoldenGirlsRecord() {
        this(
                "Dorothy Zbornak",
                "Rose Nylund",
                "Blanche Devereaux",
                "Sophia Petrillo"
        );
    }
} And to this day code simplification and code reduction seems only to continue. However with the reduction of the boilerplate code, the concepts of fields, getters, setters, properties, accessors, attributes and parameters became far less visual and less easy to map in our minds. Whether we like it or not those concepts are still how the JVM works and organizes code with the bytecode.But code oversimplification is really about making code easier to read and in the case of data classes and java records the idea is also to create data structures that are immutable or partially immutable. Java records are truly immutable in the sense that all values it contains or references it contains cannot be modified. Kotlin data classes can be also truly immutable for the same reasons but they don’t have to which in a way gives permission to developers to create complicated and worst of all, mutable code anyway.In any case this is all good until we then need to work with frameworks like the Spring Framework, which rely heavily on annotations. Here is an example: @Entity
@Table(name = "shelf_case")
data class Case(
    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE)
    val id: Long?,
    var designation: String?,
    var weight: Long?
) {
    constructor() : this(0L, null, null)

    override fun toString(): String {
        return super.toString()
    }
} This example works fine. To the unsuspecting eye, there isn’t a lot special going on here. This works in Kotlin, just in the same way as it would work in Java. But now let’s have a look at a similar example, but this time with Jackson annotations: data class AccountNumbersPassiveDto(
    @NotNull
    val accountNumberLong: Long?,
    val accountNumberNullable: Long?,
    @DecimalMax(value = "10")
    @DecimalMin(value = "5")
    val accountNumber: BigDecimal,
    val accountNumberEven: Int,
    val accountNumberOdd: Int,
    @Positive
    val accountNumberPositive: Int,
    @Negative
    val accountNumberNegative: Int,
    @DecimalMax(value = "5", groups =  [LowProfile::class])
    @DecimalMax(value = "10", groups = [MiddleProfile::class])
    @DecimalMax(value = "15", groups = [HighProfile::class])
    @DecimalMax(value = "20")
    val accountNumberMaxList:Int
) This example will fail and the reason for that is that in Kotlin, there is no way to tell the compiler where exactly do we want our annotation to be applied to. In the previous example with annotation , which is a jakarta persistence annotation, the annotations are applied correctly to the fields. If we decompile` that code we’ll find this: @Entity public final class Case {
   @Id
   @GeneratedValue(
      strategy = GenerationType.SEQUENCE
   )
   @Nullable
   private final Long id;
   @Nullable
   private String designation;
   @Nullable
   private Long weight; But for the latter, which is a jakarta validation example, we find this: public final class AccountNumbersPassiveDto {
   @Nullable
   private final Long accountNumberLong;
   @Nullable
   private final Long accountNumberNullable;
   @NotNull
   private final BigDecimal accountNumber;
   private final int accountNumberEven;
   private final int accountNumberOdd; This means that has not been affected by those annotations on its fields. We were just lucky in the first example. It might have actually also failed.In order to specify where our annotation needs to go to, Kotlin gives us the possibility to use use-site targets as prefix to any annotation. The requirement is of course that conditions are met. In this case, one way to fix this is to prefix all of the annotations with like this: AccountNumbersDto @field data class AccountNumbersPassiveDto(
    @field:NotNull
    val accountNumberLong: Long?,
    val accountNumberNullable: Long?,
    @field:DecimalMax(value = "10")
    @field:DecimalMin(value = "5")
    val accountNumber: BigDecimal,
    val accountNumberEven: Int,
    val accountNumberOdd: Int,
    @field:Positive
    val accountNumberPositive: Int,
    @field:Negative
    val accountNumberNegative: Int,
    @field:DecimalMax(value = "5", groups =  [LowProfile::class])
    @field:DecimalMax(value = "10", groups = [MiddleProfile::class])
    @field:DecimalMax(value = "15", groups = [HighProfile::class])
    @field:DecimalMax(value = "20")
    val accountNumberMaxList:Int
) If we now try to decompile the resulting bytecode using IntelliJ, we’ll find that it results in this code in Java: public final class AccountNumbersPassiveDto {
   @NotNull
   @Nullable
   private final Long accountNumberLong;
   @Nullable
   private final Long accountNumberNullable;
   @DecimalMax("10")
   @DecimalMin("5")
   @org.jetbrains.annotations.NotNull This means that the annotations have been applied to field and that our code works as it is supposed to. You can probably imagine at this point that people who have been working on Java for a long time, will have no problem in adapting to Kotlin because we all know what fields, parameters, properties, etc, are. What we observe today and I witness that too, is that it seems like the code simplification has a potential to backfire. There have been quite a few occasions where I have become aware of the time spent in projects trying to figure how why in some projects or modules, the annotations just don’t seem to work. And it all seems to boil down to not making use of the use-site targets. My theory on what is  most likely, is that new generations of developers will probably look at things that my generation didn’t think was complicated and learned out of instinct, as really complicated material. Such is the case with use-site targets. These used to be things that we could very easily visualize. However in current times, the generated confusion with this seems to be delaying projects from being developed on time in some occasions. I wouldn’t be able to generalize of course but there is potential for good and there is potential for bad with java records and data classes. How data classes and records will shape our future is hard to tell, but one thing that is clear is that because of this problematic, other frameworks are betting on going completely annotation free as is the case with Ktor. I have created documentation about this on Scribed: also on slide-share: . Fields-in-Java-and-Kotlin-and-What-to-Expectand fields-in-java-and-kotlin-and-what-to-expect You can also find the examples I’ve given on GitHub. The golden girls example can be found here: and the jakarta persistence and validation annotations examples can be found here: . jeorg-kotlin-test-drives https://github.com/jesperancinha/jeorg-spring-master-test-drives Finally I also created a video about this on YouTube that you can have a look at right over here: https://youtu.be/rTCjlyGVDGE?embedable=true Also published . here

How to Fix Kotln Problems When Dealing With Use-site Targets

ব্যবহার-সাইট টার্গেট নিয়ে কাজ করার সময় Kotln সমস্যাগুলি কীভাবে ঠিক করবেন

So beheben Sie Kotln-Probleme beim Umgang mit Use-Site-Zielen

Cómo solucionar problemas de Kotln al tratar con objetivos de sitios de uso

Comment résoudre les problèmes de Kotln lors du traitement des cibles de site d'utilisation

उपयोग-साइट लक्ष्यों से निपटने के दौरान कोटलन समस्याओं को कैसे ठीक करें

使用サイトターゲットを扱う際の Kotln の問題を修正する方法

사용 사이트 대상을 처리할 때 Kotln 문제를 해결하는 방법

Como corrigir problemas de Kotln ao lidar com alvos de uso de sites

Как исправить проблемы Kotln при работе с целями использования сайта

Kullanım Sitesi Hedefleriyle Başa Çıkırken Kotln Sorunları Nasıl Düzeltilir

Cách khắc phục sự cố Kotln khi xử lý các mục tiêu trang web sử dụng

如何解决处理使用站点目标时的 Kotln 问题

JavaScript Objects: From Fundamentals to Advanced Techniques

জাভাস্ক্রিপ্ট অবজেক্ট: ফান্ডামেন্টাল থেকে অ্যাডভান্সড টেকনিক

JavaScript-Objekte: Von den Grundlagen zu fortgeschrittenen Techniken

Objetos JavaScript: de los fundamentos a las técnicas avanzadas

Objets JavaScript : des fondamentaux aux techniques avancées

जावास्क्रिप्ट ऑब्जेक्ट: बुनियादी बातों से लेकर उन्नत तकनीकों तक

JavaScript オブジェクト: 基本から高度なテクニックまで

JavaScript 객체: 기초부터 고급 기술까지

Objetos JavaScript: dos fundamentos às técnicas avançadas

Объекты JavaScript: от основ к продвинутым методам

JavaScript Nesneleri: Temellerden İleri Tekniklere

Đối tượng JavaScript: Từ cơ bản đến kỹ thuật nâng cao

JavaScript 对象：从基础知识到高级技术

236 Stories To Learn About Ux

99 Stories To Learn About Ui

Crack Long-Form Blogs: Complete Guide & Experts' Insights 

ADVANTAGES OF THE BABCOCK & WILCOX BOILER

From the widely discussed Helpful Content Update (HCU) to the Search Generative Experience (SGE), 2022 was not the year for rest nor relaxation for most SEOs and content professionals. Google has seen more changes in the last year than in the last decade. I recently shared my experience of using for the first time. And how the AI overviews differ for different keywords and queries. Search Generative Experience (SGE) I have also been ringing the bells around Google’s visibly changing SERPs, and how it’s . killing organic reach A visual summary below 👀 Source Notice how ‘above the fold’ now comprises an AI overview, a couple of organic links, and a whole bunch of SERP elements (knowledge panels, People Also Ask, etc.). This is the beginning of a new Googleverse and a potential loss of your organic traffic. The antidote? I have five. 5 Ways to Stop the Potential Loss of Traffic to SGE and Grow Your Audience Like every other content professional, while I’m excited about SGE, I can’t help but wonder how SEO will change as SGE evolves. I’m sure you’re brimming with questions too. But at the moment, it will be a waste of time to worry about that. After all, SGE is still in the infancy stage. Over time, there are going to be many iterations and improvements to the model. So, what can you do? Other than creating valuable content, here are five ways your organic content can shine without SEO: Create content for native consumption Produce content with original research Build and document a distribution strategy Use executive branding for audience building Experiment with content formats (video, interactive product tours, webinars, podcasts, and more) Let’s explore each one in detail below. Build and document a distribution strategy Google has been cannibalizing clicks even before SGE was a thing. This happened in the form of a zero-click search. However, such zero-click responses were only relegated to straightforward queries like ‘ . What is content marketing?’ But with SGE in the picture, it’s different. You’re not just competing against the SERP elements like featured snippets or knowledge panels, but with the comprehensive AI overviews as well. This is why having a distribution strategy pays off. Instead of trying to optimize for SGE/SEO and waiting to be discovered, build a distribution system that lets you share and promote content in places where your target audience hangs out. Published a research report? Promote it via newsletter sponsorship. Released a new podcast episode? Share short clips on YouTube and Instagram. Wrote a new blog post? Share the juicy bits with a link on LinkedIn. You get the drift. Create content for native consumption Speaking of a distribution strategy, I have to mention the most abused content distribution and promotion practice: link dumping. Back when Facebook was in its prime, you could dump a blog post link and get a steady stream of traffic. Today? You’ll be happy to get a CTR of at least 1%. That’s because nobody likes moving away from the platform they’re engaged with. If someone is scrolling through LinkedIn, they want to read and engage with the content on LinkedIn instead of clicking away. By creating content for native consumption, you can keep your audience engaged and interested in learning more. And if you want to promote your content on social sites, be a little more creative. Rather than dumping the link as is, you should: Share the juiciest bit of information to compel the readers into clicking. Turn the key takeaways from the eBook to create a carousel. Visualize the data with graphs and charts. Ask the readers how they relate to the numbers. Pick a controversial or thought-provoking excerpt and get the conversation going in the comments. The key to a good content distribution (promotion) strategy is having a good repurposing strategy. Source original research and data When you think “Inbound Marketing”, you think HubSpot. When you think “zero-click search”, you think SparkToro. And when you think “sales intelligence”, you think of Gong. This is the power of brand recall. When you produce original, data-driven content, you get to shine in a sea of sameness (including SGE’s blandness) and build a loyal fanbase. One of my favorite examples of brands using content as a differentiating factor is Gong. Despite having roughly 1000+ sales tech solutions as competitors, they have managed to build a higher brand recall thanks to the original content. You’ll rarely find their company blog ranking high on SERPs, but ask any sales professional and they’ll tell you that Gong has the best sales content. These are a few reasons why. They use data sourced from real sales conversations to craft blog posts. You won’t find the information they provide elsewhere. Source: Gong Blog All their content is created for a clearly defined audience: sales leaders, AEs, and managers in tech companies. They write in a conversational, non-boring tone while providing actionable advice. Use executive branding for audience building Mark Schaefer, , shares in his why personal branding is essential in a post-SEO era: best-selling author and renowned marketer blog post “The ability to benefit from SEO depends on a special set of circumstances, and increasingly SEO isn’t going to create a return. The other option is to create content that establishes authority through thought leadership. In this way, you can earn attention and an audience without depending on search engines and ads.” Even great content gets buried between the many SERP folds. But if you’ve managed to build a trustworthy personal brand, you will have people waiting (eagerly) and going back to your opinions, values, and content. This is something SGE cannot replace. Here are a few ways to get started with executive branding. Build a following on social media. It costs nothing to get on platforms like LinkedIn, X, or Medium and share your entrepreneurial journey, what you’re building, or validate the idea for your next launch. Invest in digital PR to boost your digital footprint. It will also help shape your public image, and by extension, your brand’s. This could mean giving interviews, joining podcasts, guesting on webinars, or writing guest posts. The last tactic was how initially. Buffer’s Co-founder Leo Widrich grew the number of app users from 0 to 100000 Connect with journalists and content professionals through Help a B2B Writer (HaBw) and Help a Reporter Out (HARO). Share responses and quotes occasionally. This is a simple method of getting a mention on authoritative websites and scoring a backlink free of cost. Experiment with content formats Is a majority of your content efforts concentrated around blogging? Does your audience or reading the blog posts? Think about it. want like It makes sense for a company like Zapier or Scribe to publish 50+ blog posts every month. Since they sell a horizontal product catering to varying personas, Search is one of the best content marketing channels for them to target. This, however, would make zero sense for a company like Freshpaint, a healthcare data privacy platform, which sells to busy healthcare professionals and organizations. As their Head of Content, Mark Rogers, explains in the , SEO isn’t a priority for his team because their customers take advice from peers, not Google. Content, Briefly podcast Another example is Ahrefs. They created a ‘Blogging for Business’ video course to promote Ahrefs and , as Tim Soulo shares in his blog post. managed to snatch 500k+ views while bringing mid-five figures in revenue There’s no dearth of content formats to try – from podcasts, and webinars to seminars and more, you can dip your toes into a variety of’em. It gives you the benefit of meeting your audience where they hang out (perhaps on Instagram?) and provides the experience and content SGE cannot. So, find out what resonates with your audience and stick to it. Final Thoughts SEO has never been a passive strategy. While it’s too soon to conclusively say anything about the impact SGE will have on organic traffic, there are ways to win beyond SEO. As outlined above, methods like personal branding or doubling down on content distribution can ensure your content is consumed by the right people at the right time. Once we have more data about SGE and its impact, we’ll be able to devise better ways for sure.

How to Stop the Potential Loss of Traffic in the Era of AI-Powered Search

এআই-চালিত অনুসন্ধানের যুগে ট্র্যাফিকের সম্ভাব্য ক্ষতি কীভাবে থামানো যায়

So stoppen Sie den potenziellen Traffic-Verlust im Zeitalter der KI-gestützten Suche

Cómo detener la posible pérdida de tráfico en la era de la búsqueda impulsada por la IA

Comment arrêter la perte potentielle de trafic à l'ère de la recherche basée sur l'IA

एआई-संचालित खोज के युग में ट्रैफ़िक के संभावित नुकसान को कैसे रोकें

AI を活用した検索の時代に潜在的なトラフィック損失を阻止する方法

AI 기반 검색 시대에 트래픽 손실 가능성을 막는 방법

Como impedir a perda potencial de tráfego na era da pesquisa baseada em IA

Как остановить потенциальную потерю трафика в эпоху поиска на основе искусственного интеллекта

Yapay Zeka Destekli Arama Çağında Potansiyel Trafik Kaybı Nasıl Durdurulur

Cách ngăn chặn khả năng mất lưu lượng truy cập trong kỷ nguyên tìm kiếm được hỗ trợ bởi AI

如何阻止人工智能搜索时代潜在的流量损失

How Jesus appeared ofttimes to his disciples; and how, after many days, he ascended up to heaven.

Scribe

scribehow.com

51-200 employees

Since 2019

COMPANY RANKING

SCRIBE

EVERGREEN INDEX #10000

Scribe WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

Scribe

scribehow.com

51-200 employees

Since 2019

COMPANY RANKING

SCRIBE

EVERGREEN INDEX #10000

RELATED COMPANIESRANK

STORIES ABOUT SCRIBE

Scribe WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!