Frequently Asked Questions

The PSM I exam gives you 60 minutes for 80 questions, and you need 85% to pass. Using AI during the exam doesn't work: there is no time, and language models often give confident but wrong answers. Studying the Scrum Guide and doing the practice tests is what gets you through.

You get 60 minutes for 80 questions, which is about 45 seconds per question. Time management is a big part of the exam.

The passing score is 85%, which means at least 68 correct answers out of 80.

It doesn't help. With about 45 seconds per question, there is no time to ask a language model and check its answer, and models often give confident but wrong answers, even on simple questions like the typical size of a Scrum Team.

They give shallow, general answers, may rely on an outdated Scrum Guide, can make up answers when they don't understand a question and tend to fall for trap words. On an exam with an 85% passing score, even one such mistake hurts.

Telling similar terms apart, such as Increment and Definition of Done, sticking strictly to the Scrum Guide instead of habits from your company, long scenario questions and wrong options that look almost right.

Learn the Scrum Guide's exact wording, memorize the key concepts, take the Scrum.org practice tests until you score 100% several times in a row, keep your own notes and plan for about 45 seconds per question.

The second stop on the road to PSM I: a 15 hour Scrum training from ACM Agile. Working in twenty minute sprints over two days, we saw the cost of skipping the customer and of turning the Definition of Done into Mount Everest. The second half of the post covers the two books by our trainer Mehmet Yitmen and what they added to everyday work.

The 15 hour training covered the philosophy of Scrum, the roles, the events and the Definition of Done through hands on work. Participants worked on a sample project in twenty minute sprints and got feedback from the trainer at the end of every sprint.

A Definition of Done should be neither so long that it pushes developers harder than needed nor so short that it leaves holes in the software. The team should agree on a realistic list that guarantees the quality of the product without putting the Sprint Goal at risk.

No. Story Point, Velocity and Scrum Poker do not appear in the Scrum Guide. The trainer recommends avoiding them where possible and giving items a time estimate only if a measure is truly needed, because focusing too much on metrics can pull a team away from producing value.

It is not. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal, make the points where the team is stuck visible and coordinate on solutions. Meetings where everyone takes a turn reporting progress have drifted away from that purpose.

There are two. Scrum: Bir Dönüşüm Hikâyesi tells the story of a corporate company moving to Scrum. Scrum: Usta Sorulara Uzman Cevaplar answers fourteen frequently asked questions, covering fixed budgets, wearing two hats and retrospectives, with short and clear answers.

Scrum is a framework for managing complex work in short, fixed length Sprints. It rests on transparency, inspection and adaptation, and it is made up of three roles (Scrum Master, Product Owner, Developers), five events and three artifacts. This post walks through the basics of Scrum with notes from a PSM I certification journey, and compares Scrum with Kanban, Extreme Programming and Waterfall.

Scrum is a framework used to manage complex projects. It is not a rigid method but a structure that guides teams; it is built on transparency, inspection and adaptation, and it aims to deliver value to the customer as early as possible.

A Scrum team is made up of one Scrum Master, one Product Owner and the Developers. The Scrum Master owns the process and the removal of impediments, the Product Owner owns the value of the product, and the Developers commit to producing a usable Increment every Sprint.

Scrum defines five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Sprints are fixed length and last one month or less; the other events happen inside the Sprint and create chances to inspect and adapt.

Scrum runs on fixed length Sprints and defined roles, while Kanban focuses on continuous flow and defines neither a mandatory planning event nor distinct roles. The signature tool of Kanban is the WIP limit, which caps how many items are worked on at once.

PSM I is the Professional Scrum Master certificate issued by scrum.org. It shows that you understand and apply the roles, events and artifacts in the Scrum Guide correctly, and the exam process also helps you spot habits that quietly drifted away from Scrum.

Yarış Radarı is a Turkish running race calendar, built in two months from July 18, 2026. The post shares real visit numbers, the 18 tools that were built, and honest lessons from the SEO, AEO and GEO work. The most meaningful number was 78 clicks on race registration links.

Yarış Radarı is a Turkish running race calendar at yarisradari.com. It helps runners find races: they can look at events, plan their season and open registration links. The domain was registered on July 18, 2026.

The work covers two months, from July 18 to September 18, 2026. The post uses the on-site numbers from September 19, 2026.

Next to the race calendar, the site has a scraper that collects race data and 18 tools built in two months. One of the sections with the most work in it is called Technical Meeting.

The most meaningful number is 78 clicks on race registration links. It shows that people did not only read the pages; they went on to sign up for races.

Two separate Google counters were compared and the totals matched, so the tracking looks correct. In the post, the SEO side is described as everything looking fine on screen.

Yes. More than one Yarış Radarı page was used in an answer to a "2026 race calendar" question, on an account that is not the writer’s. People started to come to the site from that source card.

AEO means Answer Engine Optimization. In the post, sometimes the whole thing came down to two words: writing the right words in the right way changed the answer people got.

Yes. The post talks about a Yandex surprise, traffic from Bing and results from the English pages. So the site reached people outside its main Turkish readers too.

The site is for different kinds of runners: people who search for a 2026 race calendar, people who look at races in Istanbul, and people who try to pick their first half marathon.

The post has its own section about the things that did not go well, and the writer shares them openly next to the good results.

The post ends with a section about the third month goals. The plan is to listen to runners more and to build on the SEO, AEO and GEO lessons from the first two months.

A young teacher transferred from Kazancık visited all 25 households to ask for their blessing before leaving. He later learned a villager had bet a ram that he could corrupt the teacher — and lost. The teacher left with his integrity and everyone's goodwill intact.

A long-term national teacher training course caused his official post to be transferred to Kınıklı village in Denizli. Short courses didn't affect postings, but this one ran long enough to trigger a formal transfer.

Going door to door through the village to ask forgiveness and receive goodwill before departing — a traditional farewell practice. The teacher and Özdamar visited all 25 households in Kazancık before leaving.

Uncle Haydar told a gathering he trusted the teacher completely with life, property, and honor. A skeptic claimed a bachelor has no morals and could be led astray, so Haydar wagered a ram that the teacher would not do anything wrong. The skeptic lost.

He consistently refused, telling the man he came to the village to teach, not to fool around. He also stated that whatever the Quran says is the path he follows, and he never once acted as the man wanted.

He felt responsible for the repeated pressure the teacher faced, because his public bet had given the skeptic a reason to keep approaching the teacher and testing his character. He asked the teacher's forgiveness for his part in it.

Brother Seyfettin challenged the teacher to finish an entire plate of freshly drawn comb honey in exchange for not charging him for honey he had already bought. The teacher accepted the contest.

Warm, freshly drawn honey hits quickly and the teacher felt it was about to overwhelm him with only a few spoonfuls left. Two spoonfuls of yogurt helped him finish the plate and win the bet.

When Seyfettin tried to stop his wife from bringing yogurt, the teacher invoked the cultural bond of treating her like a sister, saying a man cannot refuse his own sister's kindness. Seyfettin had no answer to that and backed down.

Özdamar was a fellow teacher and close friend the narrator described as a precious friend. The transfer meant leaving both his students and this valued colleague behind, which caused him real grief even though there was no time to dwell on it.

Uncle Haydar was the brother of the village headman Ramazan, and his house was the main gathering spot where villagers sat and talked. He was also an expert in the livestock trade, having bought and sold animals all across Turkey.

This guide walks through adding Firebase Cloud Messaging (FCM) push notifications to a Vue.js and Quasar mobile app using Capacitor. It covers Firebase project setup, token management, notification configuration options, and sending notifications from a backend using the Firebase Admin SDK.

You need Vue.js, Quasar, Capacitor, and Firebase. Capacitor bridges the web app to native iOS and Android functionality, while Firebase Cloud Messaging handles the delivery of push notifications.

You add Capacitor to the project using Quasar's CLI, then add Capacitor's Device API, configure platform-specific settings for iOS and Android, and synchronize changes before opening the Android directory in a terminal.

Create a new project in the Firebase Console, enable Firebase Cloud Messaging (FCM), and register your iOS and Android apps. You then retrieve the Firebase SDK configuration and API keys for use in your app.

The app obtains a Firebase device token using specific code, then sends that token to the backend so the backend can target the correct device for notifications. The app can also subscribe or unsubscribe to specific notification topics.

Yes. The guide covers subscribing and unsubscribing devices to specific notification topics, which allows you to send notifications to groups of users rather than targeting individual device tokens.

You can configure notification categories, priority levels, silent notifications, custom sounds and ringtones, images and icons, delivery timing and delays, frequency management, multi-language support, and dismissible or recurring notifications.

Silent notifications are push messages delivered to a device without alerting the user with a sound or visible alert. They are useful for triggering background data syncs or app updates without interrupting the user.

The guide covers in-app notification handling, which lets you define how notifications are displayed or processed when the app is already running in the foreground rather than in the background.

The backend uses the Firebase Admin SDK, configured with a Firebase Service Account. Once set up, the backend can send targeted notifications to specific device tokens or topics through the FCM API.

Yes. The guide includes platform configurations for both iOS and Android, and Firebase Cloud Messaging supports push notifications on both platforms through Capacitor.

Yes. The guide covers multi-language support (localization) as part of the notification feature configuration, allowing notification content to be delivered in the user's preferred language.

On March 20, 2026, four popular AI tools — Lovable, Claude, Gemini, and Cursor — were given the exact same blog prompt in a live test. Their outputs were evaluated against defined technical and design criteria. The experiment was streamed on YouTube to keep the comparison transparent and convincing.

The four AI tools tested were Lovable, Claude, Gemini, and Cursor. Each received the same blog prompt and was evaluated on technical and design quality.

A blog was chosen as the test subject because it involves both design and technical decisions, making it a practical format to compare AI outputs across multiple criteria.

The author treated the prompt as a 'Software Task Description' rather than a simple prompt, making it more structured and precise to get production-quality outputs from each AI.

Architectural Nationalism refers to the author's preference for 'Model Classes' and the JavaScript ecosystem when structuring AI-generated code — it was a deliberate design philosophy baked into the prompt.

GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) are future SEO strategies focused on making content appealing to AI search engines. The author included these as criteria when evaluating the AI-generated blog outputs.

The comparison was conducted as a live broadcast and published on YouTube, so viewers could watch the results unfold in real time rather than take the author's word for it.

The post evaluates all four based on defined technical and design criteria, but the full results and winner are detailed in the technical evaluation section and the live broadcast summary.

The AIs were judged on technical and design criteria defined before the test began, ensuring the evaluation was structured and not subjective. Specific criteria details are covered in the technical evaluation section.

The comparison was written and conducted on March 20, 2026, reflecting the state of the mentioned AI tools at that specific point in time.

The bonus section notes that the first commit was completed and frames it as just the beginning — implying that further development or refinement of the AI-generated blog continues beyond the initial output.

98% of Fortune 500 companies use ATS systems that screen resumes before a human sees them, and recruiters spend only 7 seconds reviewing each one. To get called for an interview, your resume must use clean formatting, exact keywords from the job posting, and measurable achievements — plus your LinkedIn and GitHub must match what your resume claims.

An Applicant Tracking System (ATS) is an automated screening tool used by 98% of Fortune 500 companies to filter resumes before a recruiter ever sees them. If your resume isn't formatted and worded correctly, it gets eliminated before any human reviews it.

Use standard fonts like Times New Roman, Arial, or Calibri at 11–12 point size. Save your resume as a PDF and name the file simply, like surname_firstname.pdf. Avoid graphics, icons, and logos, as they can confuse ATS systems.

Use the exact job title from the posting, such as 'Software Engineer,' and list technical skills with standard terminology like React, Kotlin, or SwiftUI. Always spell out acronyms — for example, write 'CI/CD (Continuous Integration/Continuous Delivery)' rather than just the abbreviation.

HR specialists spend an average of just 7 seconds scanning each resume. This makes it critical to use bold text for key skills, lead with your strongest achievements, and avoid long paragraphs that slow down readability.

Always use bullet points instead of long paragraphs. Long blocks of text are intimidating and HR specialists may skip right over them. Each bullet should be clear, concise, and ideally tied to a measurable result.

Back up every achievement with specific numbers instead of vague claims. For example, write 'I achieved a 35% performance increase in the XYZ project' rather than 'I contributed to the project.' Numerical data impresses both ATS systems and human reviewers.

List work experience in reverse-chronological order, placing your most recent job at the top. If a role from 20 years ago is irrelevant to the position you're applying for, move it toward the bottom so recent, relevant experience stands out.

STAR stands for Situation, Task, Action, Result. Applying it to your resume means framing accomplishments with context and outcome — for example, 'Led the team's transition to a microservices architecture; improved API response times by 50%.'

Recruiters now cross-check your resume against your digital presence. If your LinkedIn profile, GitHub account, or platforms like Kaggle don't align with what your resume claims, it raises red flags and can cost you the interview call.

Yes. Adding links to LinkedIn and GitHub lets HR specialists verify your technical background and see real projects. Some ATS platforms can pull in these profiles, but critical keywords must still appear within the resume text itself.

No. A riot of colors, cluttered blocks, and overly creative formats often backfire. Focus on readability and simplicity — a clean design helps both ATS systems parse your content and HR specialists scan it quickly.

Asimov's The End of Eternity and Orwell's 1984 both explore how powerful institutions control reality — one through time manipulation, the other through mind control. While 1984 ends in crushing despair, The End of Eternity offers hope: one person's choices can rewrite history and open a better future. Both novels use love as the spark of rebellion against cold, bureaucratic systems.

Published in 1955, The End of Eternity is one of Asimov's most philosophical and romantic works. It follows an organization called Eternity that travels through time to make 'Micro-Changes' to history, optimizing humanity's path — but at the cost of human freedom and potential.

The events in The End of Eternity are presented as a precondition for the creation of the Foundation universe. The novel ends with the line 'The end of Eternity is the beginning of Infinity,' signaling this transition.

Both novels feature cold, bureaucratic institutions that control reality — one manipulates time and history, the other manipulates minds and facts. They both use love as a form of awakening against the system, and both explore how knowledge and language are restricted to maintain power.

In 1984, control is enforced through surveillance, psychological manipulation, and rewriting records. In The End of Eternity, control is more refined — societies and historical events are physically altered through time travel, making the manipulation structural rather than personal.

In both novels, a romantic relationship becomes the character's first act of defiance against an oppressive system. Love gives the protagonist someone to act with and think alongside — a human connection the institution tries to eliminate.

1984 ends in total defeat and is designed to feel hopeless and cautionary. The End of Eternity carries a spark of hope — one person's actions can rewrite history and unlock a future full of possibilities, making it more philosophical and even romantic in tone.

In 1984, technology is purely a tool of oppression — surveillance and control. In The End of Eternity, technology like time travel is portrayed as fascinating but morally complex, raising questions rather than simply serving power.

Micro-Change Theory is the method Eternity uses to alter history — making small, calculated adjustments to events in order to steer humanity toward statistically 'better' outcomes, without people in the timeline ever knowing changes were made.

Asimov's loudest question is: if everything is already planned and optimized, what is the point of being human? The novel challenges whether a safe, managed existence is worth sacrificing genuine human agency and potential.

The novel features concepts like Physiotime, Time Kettles, Human Computers, and the Institution of Eternity itself. It also includes a moment where a character meets themselves — the closest the book comes to a classic time paradox.

In 1984, the protagonist's rebellion is ultimately crushed and changes nothing. In The End of Eternity, one person's choices genuinely rewrite history and open up a new future, giving individual action real weight and consequence.

Daniel Pink's Drive argues that traditional reward-and-punishment systems often backfire. True motivation comes from Autonomy (freedom to choose how you work), Mastery (getting better at things), and Purpose (doing work that matters). Money and external rewards can actually reduce performance and creativity.

Pink outlines Motivation 1.0 (primitive survival), Motivation 2.0 (industrial-era reward-and-punishment), and Motivation 3.0 (inner, intrinsic motivation). He argues we need to move beyond 2.0 to thrive in modern work environments.

Pink identifies Autonomy (the freedom to make your own choices), Mastery (the desire to keep improving at something), and Purpose (feeling that your work genuinely matters). Together these form the core of Motivation 3.0.

Pink lists seven reasons: rewards undermine intrinsic motivation, reduce performance, crush creativity, encourage unethical behavior, promote cheating and shortcuts, can become addictive, and push people toward short-term thinking rather than long-term goals.

The Soma Puzzle experiment is a key piece of research Pink references to show that external rewards can actually undermine intrinsic motivation. When people were paid to solve puzzles they previously enjoyed for free, they became less motivated to continue once the reward was removed.

Type X individuals are extrinsically motivated — driven mainly by external rewards like money or status. Type I individuals are intrinsically motivated — driven by genuine interest, growth, and purpose. Pink argues Type I behavior tends to produce better long-term results.

According to Pink's framework in Drive, yes — the shift from Type X to Type I is possible. It's not a fixed personality trait but a behavioral pattern that can change given the right environment, management style, and conditions.

Drive is highly relevant for managers because it challenges the common use of bonuses and penalties to drive performance. Pink suggests that good management focuses on giving people autonomy, helping them develop mastery, and connecting them to a meaningful purpose.

Pink doesn't say money is irrelevant — he acknowledges it needs to be fair and sufficient. But once basic compensation needs are met, additional monetary rewards often fail to boost motivation and can even harm intrinsic drive and creativity.

Vibe coding lets experienced developers turn ideas into working software fast by combining AI tools with lightweight planning, task tracking, and code quality principles. The key is writing a minimal analysis document, using a simple Kanban board, trusting UX intuition, and cleaning up AI-generated code with layered architecture. Speed matters, but sustainable products still need a touch of developer expertise.

MVP stands for Minimum Viable Product — the smallest version of your idea that actually works. In vibe coding, 'minimum' is emphasized so you stay focused and ship fast instead of over-engineering from the start.

A vibe coder's analysis document doesn't need banking-app-level detail. It should cover practical choices like which AI tools to use, key constraints, and essential decisions like whether a user agreement is needed — enough to guide development without slowing you down.

Use a simple Kanban board with a maximum of 4 columns to track progress. Keep task cards short and speed-focused so you can maintain momentum without getting buried in project management overhead.

Not deeply. The post recommends spending just 15 minutes training your eye for design rather than hours learning it formally. Trusting your intuition and using AI design tools is enough to keep pace with vibe coding's fast rhythm.

AI code often needs cleanup — the post calls this 'garbage sorting.' The real work begins after AI gives you a working idea, and you should separate code into data, presentation, and logic layers to keep it maintainable.

Separating a monolith into data, presentation, and logic layers means your codebase stays organized as it grows. AI tends to generate tangled code, so applying this structure manually is what makes a vibe-coded product sustainable.

The post raises SOLID principles as relevant to vibe coding quality. While vibe coding prioritizes speed, understanding SOLID helps experienced developers clean up and structure AI-generated code properly over time.

The post addresses non-coders directly, suggesting vibe coding tools lower the barrier significantly. However, it emphasizes that developer expertise is what makes a vibe-coded product truly sustainable beyond the initial build.

The core motto is: focus on what's done, not what's perfect. This mindset keeps you shipping rather than endlessly refining, which is central to vibe coding philosophy.

According to the post, vibe coding can help you lay the product foundation in about an hour. What comes after — quality, sustainability, and real usability — requires additional developer investment and expertise.

Buying a new watch or gadget to feel motivated is a form of 'pretending to start' — the excitement is real but temporary because it's external. True motivation comes from within and is built through repeated behavior, not purchases. Identity is formed by habits, not by owning objects.

It's shopping not to actually use something, but to experience the excitement of imagining a 'new you.' You feel motivated at purchase, but the feeling fades quickly because it depends on the product, not on internal drive. It's a cycle of dreaming, buying, barely using, feeling guilty, and repeating.

Because the motivation is external — it's tied to the object, not to you. Once the novelty wears off, there's nothing sustaining the behavior. Real, lasting motivation has to come from within and is built through consistent action over time.

Not necessarily. If you run in a group, use a phone with GPS, have no specific performance goals, or just run for fun or fitness, a dedicated running watch isn't essential. However, for trail running, long races, accurate measurements, or battery conservation, a watch becomes genuinely useful.

You likely need one if you do long trail runs requiring route loading, need precise data like altitude or heart rate zones, have a phone with poor GPS, or want to track health metrics like sleep and daily calories. If none of those apply, your phone may be enough.

People tell themselves 'I bought a running watch, so I'm a runner' or 'I bought a planner, so I'm organized.' But identity isn't built by possessing objects — it's built by making behaviors habitual through repeated action. The object alone doesn't make you the person you want to be.

The cycle goes: dream about a new version of yourself, buy something to feel motivated, use it briefly or not at all, lose motivation, feel guilty, then find a new enthusiasm and repeat. Each loop feels like a fresh start but rarely leads to lasting change.

Phone GPS receivers are designed for car-level navigation, not the precise, step-by-step tracking that running requires. This makes them less accurate for measuring running pace and distance compared to a dedicated running watch with a purpose-built GPS.

A genuine need is tied to specific limitations — like a watch battery dying mid-race or a phone draining during a long run. An excuse is when the upgrade is driven by excitement or the idea that new gear will somehow create discipline you don't currently have.

The author canceled their $20 ChatGPT Plus subscription after applying 7 honest self-audit questions to evaluate real usage, productivity gains, and value for money. These same questions work for any recurring subscription, like Office 365, Spotify, or Netflix, helping you cut what no longer earns its cost.

After honestly evaluating their usage patterns and productivity gains, the author concluded ChatGPT Plus no longer justified its $20/month cost. The seven self-audit questions revealed the subscription had become more habit than necessity.

Ask yourself how often you actually use the product and for what purpose. This forces you to confront whether your usage is meaningful or just occasional.

Question two asks whether the product genuinely improves your productivity or has simply become a habit. If you can't point to concrete outcomes, it may be a habit rather than a real tool.

Weigh the benefits you actually receive against both the money and time you invest. If the benefits don't clearly outweigh the cost, the subscription likely isn't earning its place.

Yes — question four asks whether a more affordable alternative could do the same job. If a free or lower-cost option covers your real needs, the premium tier isn't justified.

Question five asks what would genuinely be missing from your life without the product. If the honest answer is 'not much,' that's a strong signal to cancel.

It's one of the most clarifying questions in the framework. Seeing the product with fresh eyes removes the sunk-cost bias and reveals whether you'd still choose to pay for it.

Yes, the author explicitly applies the same seven questions to Office 365 and notes they work for any recurring subscription, including Spotify and Netflix.

The post suggests subscriptions often survive on habit rather than genuine value. People forget to revisit the original reason they subscribed, so outdated purchases keep renewing automatically.

Question seven asks why you bought the paid version in the first place and whether that reason is still relevant. Circumstances change, and a once-valid reason may no longer apply.

Short-form video platforms like Reels and Shorts are engineered with dopamine bait — repetitive, clickbait content designed to keep you scrolling. When you start feeling bored or disgusted by it, that's a sign your brain is waking up, not breaking down. The problem is the content, not you.

Algorithms serve content optimized for clicks and watch time, not originality. This creates a loop of recycled titles, formats, and hooks that start feeling identical after enough exposure. Your brain eventually stops finding novelty in content that was never truly novel to begin with.

Dopamine bait refers to content designed to trigger a quick reward response — clickbait titles, dramatic hooks, and shallow payoffs — that keeps users scrolling without delivering real value. It exploits the brain's reward system rather than offering genuine information or entertainment.

Yes, and the post frames it as a positive sign. Feeling burnt out on repetitive short-form content suggests your pattern recognition has caught up to the manipulation. It means you're no longer easily fooled by the same recycled hooks.

The post implies that people who consume a high volume of Reels and Shorts are the most prone to this fatigue. Heavy users eventually recognize the patterns — the same title structures, the same product plugs, the same 'life-changing' promises — and disengage.

According to the post, the problem is the content, not the viewer. Platforms and creators optimize for engagement metrics, which incentivizes repetitive, low-effort dopamine bait rather than meaningful or surprising content.

It means the content has become formulaic enough that your brain has internalized the pattern. When titles like 'This will totally change how we eat' or 'Buy it first, then make it' all blur together, the novelty that drives engagement has worn off completely.

The post suggests recognizing the feeling as meaningful rather than ignoring it. The author's response is to stop forcing consumption and question what genuinely surprising or valuable content even looks like anymore — treating the numbness as a signal to change habits.

Algorithms prioritize content that maximizes clicks and watch time, which rewards creators who use proven hooks and formats over those who take creative risks. This feedback loop floods feeds with similar content, accelerating viewer fatigue.

A developer reflects on 2024 as a transformative year marked by an eight-year career pivot, new tech skills, and first-time leadership experiences. Every challenge — personal or professional — became a learning opportunity. The post sets intentions for deeper specialization, leadership growth, and expanded writing in 2025.

The author made a significant career pivot after eight years, marking it as one of the biggest turning points of their professional life. The change was difficult but ultimately worth it, bringing both challenges and growth.

The author experienced first-time leadership responsibilities and discovered the importance and joy of building a strong team. These lessons shaped their goals for taking on new leadership horizons in 2025.

The author treated problems as learning opportunities, driven by a love for challenges. Both positive and negative experiences were embraced as part of personal and professional transformation.

The author discovered that writing feels like talking to themselves — a form of self-reflection. They also set a goal to expand their blog's reach in 2025, indicating writing became a meaningful habit.

The author's 2025 goals include investing in themselves, diving deeper into specialization, growing in leadership, expanding their blog's reach, and pursuing their sci-fi passion further.

The author made sports and health a part of their 2024 journey, recognizing the importance of physical well-being alongside professional development.

The author found that every new step — whether personal or professional — required courage to take. Facing uncertainty and discomfort in a major career pivot and leadership role reinforced this belief throughout 2024.

The post references gaining new tech skills as part of the career pivot, with plans to dive deeper and specialize further in 2025, though specific technologies are not detailed in the excerpt.

A soldier on army night duty read Pet Sematary, sent by a friend named Nare, and got so scared he fell off his chair. The book's deep horror and psychological weight made solo late-night reading genuinely terrifying. He describes it as one of King's most profound and frightening novels.

Louis Creed moves with his wife Rachel and two children to a small town seeking a peaceful life. A neighbor introduces them to a hidden Pet Sematary with a darker history than any ordinary cemetery. When the family cat dies, Louis buries it there with the neighbor's reluctant guidance.

The author considers it perhaps one of King's deepest and most terrifying novels. It stands out not just for horror but for its profound psychological impact, touching on humanity's darkest emotions.

He was so frightened during his night duty reading session that he fell off his chair with a loud crash. He described seeing a pair of glowing green eyes staring straight at him as part of the scare.

He read thirty books during four months of army service. Pet Sematary was among them, sent to him by a friend named Nare.

A friend named Nare sent him Pet Sematary, apparently to help cure boredom during army duty. The plan backfired when reading it alone at night proved genuinely terrifying.

Based on the soldier's experience, Pet Sematary is gripping enough to hook readers quickly, with strong opening lines that signal the book has a lot to offer. However, its psychological depth and horror make it intense, especially when read alone at night.

Higher-order functions in Kotlin let you pass functions as parameters or return them from other functions. This reduces code duplication by letting one function handle multiple similar operations. In Android development, this is especially useful when the same logic runs in different screens with only minor variations.

A higher-order function is a function that can accept other functions as parameters or return a function. In Kotlin, functions are treated like any other type such as String or Int, so they can be passed around freely without being tied to a class.

You declare the parameter with a function type, for example `function: () -> Unit`. You can then call it using `function()` inside the body. At the call site you can pass a lambda, a trailing lambda, or a function reference using `::functionName`.

Copy-pasting similar code across Activities, Fragments, and classes leads to redundant code that is hard to maintain. Higher-order functions let you write the shared logic once and pass only the part that differs — such as a specific API call — as a parameter.

In a Leave Management app, the actions of approving, declining, and deleting a leave all shared the same flow: dismiss a dialog, show a confirmation alert, then call a backend function. A single `showAlertAndOperate` function handled all three by accepting the differing backend call as a function parameter.

The `@StringRes` annotation on an Int parameter signals that the integer must be a valid Android string resource ID, such as `R.string.some_text`. It is a compile-time hint that helps avoid passing arbitrary integers where a string resource is expected.

Unlike Java, Kotlin does not require functions to be defined inside a class. This freedom is what enables true higher-order functions. Java can simulate this with interfaces and lambdas, but it is more verbose and not a native language feature in the same way.

At Google I/O 2017, Google declared Kotlin the official language for Android development. This followed years of legal conflict between Oracle and Google over Java, making a move to a non-Java language strategically and legally advantageous.

Yes. In Kotlin, functions can be stored in variables and data structures just like any other value. This is part of what makes Kotlin a language with functional programming features.

You can pass a trailing lambda outside the parentheses, a lambda inside the parentheses, a lambda with an explicit parameter name, or a function reference using the `::` syntax. All four styles are valid and produce the same result.

A Git Submodule lets you maintain a shared Android library as a separate Git repository and include it in multiple projects. This avoids copy-paste duplication, supports the DRY principle, and keeps the shared code in one place: a fix is a single commit in the library repository, and every app picks it up when it bumps its submodule pointer. It is better than JAR or AAR files when the library changes alongside your main projects.

JAR files can't include Android SDK classes like Activity or SharedPreferences. AAR files require you to rebuild and re-import the file every time you make a change, which is painful during active development. A Git Submodule lets the library evolve alongside your main project without that overhead.

A Git Submodule is a Git repository embedded inside another Git repository. In Android development, it lets you maintain a shared library as its own project and reference it from multiple main projects, so all apps automatically benefit from updates made to the library.

It makes sense when multiple projects share identical or near-identical features — like a login screen, theme settings, language selection, or common utility functions. Without a shared library, you end up copy-pasting code across projects and making the same bugfix or refactor in every one of them.

Any bug fix, service change, or refactor must be repeated manually in every forked project. The post describes working across 8–10 projects forked from each other, where every small change meant doing the same work over and over — which violates DRY and the Open/Closed Principle.

No. An Android library project cannot have a launcher Activity. You must remove or comment out the intent-filter with the MAIN action and LAUNCHER category from the AndroidManifest file before the project can function as a library.

The Open/Closed Principle, the Don't Repeat Yourself (DRY) principle, and SOLID principles all support library-based code reuse. The post explicitly states that copy-paste coding contradicts these principles and is not healthy development practice.

The main project must also reside within Git. Since Git Submodule is a Git feature, both the library and the consuming project need to be Git repositories for the submodule relationship to work.

According to the post, the library should be flexible, adaptable to constant change without causing developer friction, compliant with the Open/Closed Principle, and work directly from a Git-based source control system like VSTS or similar.

The author trained for and completed multiple ultra races, including a 63K in Cappadocia, by combining a clear goal, a structured training program from a coach, and consistent self-discipline practices. Key lessons: keeping your goal top of mind, setting rewards, and planning a realistic path — not just having a goal — are what sustain discipline long-term.

The author discovered that a goal without a clear path to achieve it falls short. Without a structured training program, he missed sessions even when motivated. The route to the goal is just as important as the goal itself.

Never let the goal slip from your mind and always prioritize it. Cut back on time-wasters like social media, say no to distractions, and keep the goal present — like something quietly nudging your conscience in the background.

Write your goal and the rewards you'll earn on colorful paper and hang it somewhere visible. This constant visual reminder keeps you motivated. The author keeps race medals on his work desk as a motivational tool.

No — overly rigid schedules can actually backfire and distance you from discipline. The author recommends approximately planning your path rather than micromanaging every minute, like a high-school study timetable.

A well-designed training program removes guesswork and gives you a clear path to follow. The author credits a program built by ultra-trail coach Özgür Tetik as the key reason he stayed on track and finished the 63K race.

At the Uludağ Ultra, he got leg cramps three times and finished in 6 hours — a sign of under-preparation. This reinforced that missing training sessions has direct consequences on race-day performance.

Start small and consistent — go to the gym before work or during lunch, or exercise at home with a resistance band. The key is not skipping sessions, no matter how short they are.

Pick a thin book you're genuinely curious about and read just 10 minutes a day at a time that suits you. Set alarms and, when they go off, drop what you're doing and start reading — no skipping allowed.

The author closes with advice from his mother: don't be lazy, don't procrastinate, and don't give up. These three principles underpin everything else discussed in the post.

Yes — the author injured his ankle at the 36 km mark of the 63K Cappadocia race and had to walk the rest. He still crossed the finish line in 10 hours, showing that persistence matters even when plans fall apart.

A former Android developer explains how to run Vue.js Quasar projects on real Android devices using ADB and Capacitor, with or without Android Studio. The post covers USB debugging setup, build and sync steps, real-time debugging via Chrome DevTools, and how Android development habits translate to Vue.js workflows.

Device Mode in the browser is described as 'just an illusion' — it simulates screen sizes but doesn't replicate real device behavior. Testing on an actual Android device reveals true performance, touch behavior, and hardware-specific issues that the browser cannot reproduce.

The post covers enabling Developer Mode and USB Debugging as a prerequisite for connecting an Android device for testing. These settings allow ADB to communicate with the device from your development machine.

You build the project with Quasar CLI, synchronize the build with Capacitor, connect the Android device via ADB, then install and run the app directly on the device. This workflow avoids needing Android Studio entirely.

After setting up the Capacitor sync, you open the project in Android Studio and deploy it to the connected device. You can then use Logcat for real-time monitoring and the Android Profiler for performance analysis.

Connect the device through Chrome's remote debugging tools, select your app, and you can view console.log messages, errors, and perform real-time debugging just like you would in a desktop browser.

Capacitor is used to synchronize the Quasar build output so it can be packaged and run as a native Android app. It bridges the web project and the native Android runtime.

The post compares Android's application-level lifecycle to Vue.js's component-based structure, noting differences in context, state management, asynchronous operations, and memory management between the two paradigms.

Vue.js uses Hot Module Replacement (HMR) in the browser, which live-reloads changes instantly during development — similar in purpose to live reload in an Android emulator but faster and browser-based.

The post draws a parallel between Gradle (Android's build tool) and Quasar CLI, noting that Quasar CLI handles the build process for Vue.js projects in a comparable role, allowing developers to build and serve the app from the command line.

Android developers use XML files to define UI layouts, while Vue.js uses single-file component templates with HTML-like syntax. The post covers adjustments needed when transitioning from XML-based UI design to Vue.js templates.

You configure a launch.json file in VS Code with a Chrome launch configuration pointing to localhost:8080, enabling source maps and breakpoints. The post provides a ready-to-use launch.json snippet for this setup.

The author says it can seem intimidating at first but becomes faster over time. Their Android background actually added useful habits around device testing, debugging, and lifecycle thinking that transferred well to Vue.js.

A Computer Engineering team built an indoor navigation app for shopping malls using Wi-Fi modem signals instead of GPS or beacons. They used the Free Space Path Loss formula to calculate distance from signal strength, then mapped modem positions relative to stores to determine user location and route them to their destination. The project was selected as the university's best graduation project.

GPS signals don't work reliably inside enclosed buildings like shopping malls, airports, and hospitals. The team had to find an alternative method — Wi-Fi modem signals — to determine a user's location indoors.

Beacons cost $5–$10 each and required one per every 5–6 square meters, making them expensive for a student project. The university didn't fund the cost, and the shopping mall agreement fell through, so the team used existing Wi-Fi modems instead.

They used the Free Space Path Loss (FSPL) formula, which calculates distance from signal strength measured in decibels. The formula uses signal strength (dB), frequency (Hz), and a constant of 32.44 to estimate the distance between the device and the modem in meters.

Testing in the dormitory showed the formula was accurate about 60–70% of the time. Signal strength variability meant a true 5-meter distance could read as 4 meters or sometimes as little as 2 meters.

They used Android's WiFiManager, ScanResult, and ConnectivityManager classes to collect information about nearby modems, including each modem's unique MAC address and signal strength.

The app was written in Java, since Kotlin was not yet the official Android language at the time the project was developed (2015–2016).

In 2015–2016, there were virtually no working indoor navigation apps for enclosed spaces. Google was working on an airport navigation project, but it was only at the commercial stage and was later cancelled. Only theoretical academic papers existed at the time.

The app was designed to help visitors navigate large indoor spaces like shopping malls. Users select a destination store, the app determines their current location via Wi-Fi signals, and then calculates the shortest route to that store.

A literature review is the first stage of a graduation project where students research existing similar projects, academic papers, and prior solutions. The findings are then presented to the supervising professor to establish the project's context and novelty.

Almost a decade after the project, several indoor navigation solutions now exist, including Google Indoor Maps, InMapz, Path Guide, Situm Mapping Tool, Anyplace, Indoor Service, and IndoorAtlas. The field has grown significantly since 2015–2016.

A developer launched yarisradari.com on Saturday and had ChatGPT citing it as a source by Wednesday, just 3 days later. The site went live with server-side rendering, Schema.org structured data, an llms.txt file, Bing Webmaster Tools and AI crawlers explicitly allowed in robots.txt; a single case cannot show how much each of those contributed. The site had zero backlinks and zero promotion at the time.

GEO stands for Generative Engine Optimization — getting AI tools like ChatGPT, Perplexity, and Google AI to cite your site as a source when answering questions. It differs from classic SEO, which focuses on ranking in blue-link search results.

AEO stands for Answer Engine Optimization, which is about making your content the direct answer that AI-powered engines serve to users. It overlaps heavily with GEO and is contrasted with traditional SEO focused on click-through rankings.

AI crawlers need to read your content directly from HTML without executing JavaScript. SSR ensures your content is fully present in the raw HTML response, making it immediately readable by bots like GPTBot and PerplexityBot.

The author recommends running curl tests with AI bot user-agent strings, for example using `curl -A GPTBot`, to confirm Cloudflare or other services aren't blocking those crawlers.

To get cited by AI engines, you should explicitly allow them. The author recommends permitting GPTBot, ClaudeBot, PerplexityBot, and OAI-SearchBot in your robots.txt file.

llms.txt is a file you add to your site to help large language models understand your content structure. The author included it but cautions not to expect miracles — it's a supporting signal, not a magic fix.

ChatGPT's web search feature feeds from Bing's index. Signing up for Bing Webmaster Tools helps ensure your site is indexed by Bing, which increases the chance ChatGPT will find and cite your pages.

The author considers it essential — but only when generated from real data and matched to visible page content. He warns that 'ghost markup' (structured data not reflected in visible content) is penalized.

The author focused on data no one else was keeping in a structured, accessible way — a unified race calendar for Turkey. Being the sole authoritative source for a specific niche, rather than competing on broad queries, was the core strategy.

The author recommends checking the Bing AI Performance report in Bing Webmaster Tools and periodically asking ChatGPT questions as a real user would to see if your site appears as a cited source.

The author opened the repository on Saturday evening and ChatGPT was citing the site by Wednesday — roughly 3 days. He used Claude Code to accelerate development of the scraper, site, SEO, and GEO layers.

Yes, according to this case study. Yarış Radarı had a brand new domain, zero backlinks, and zero promotion when ChatGPT first cited it on day three. The author attributes this to technical GEO decisions made from the start.

A computer engineering student shares how their graduation project was selected as the best of their term at Ankara Yıldırım Beyazıt University. They offer practical tips on picking the right project, managing time, working in teams, and leveraging internships to maximize career impact.

Choosing an innovative idea not previously tried in the market or academia helps your project gain recognition. A working, finished project with a well-written report matters more than perfect code quality for a graduation project.

Internships are very important — they help you learn real-world technologies you can apply directly to your project. The author learned ASP.Net MVC 5 during internships and used that experience as the foundation for their graduation project.

Working in a team is strongly recommended. Team members can discuss progress, motivate each other, and being able to say 'we did this as a team' in job interviews demonstrates that you are a team player.

Pick a topic you are passionate about and genuinely enjoy, so you stay motivated during long hours of work. It should also align with your long-term career goals and offer the opportunity to learn new technologies.

The project's difficulty should be just above your current skill level. This challenges you to grow your problem-solving skills without being so hard or so easy that it hurts your learning experience.

No one — not professors or hiring companies — expects perfect or clean code from a student or junior developer. Finishing the project and writing a careful report are far more important than code quality.

Graduation projects are usually selected in September and span a 6–8 month work period. Students must balance this with other ongoing courses, so choosing a project that is completable within that timeframe is essential.

Yes, significantly. The author mentions that across 400–500 interviews, no manager ever failed to show respect or interest in their graduation project, regardless of the company's size.

Projects with real-world impact increase your motivation and raise the visibility of your work. Software or systems that address genuine problems are also more impressive to potential employers.

Yes, and it is actually a positive sign. A well-known industry principle says a good programmer should look at code they wrote six months ago and cringe — if they don't, it means they are not learning fast enough.

ADB (Android Debug Bridge) is a command-line tool that lets developers connect to Android devices, install apps, transfer files, and monitor performance metrics like CPU, GPU, memory, battery, and network. It is essential for Android development and debugging. Setting it up requires enabling Developer Mode and USB Debugging on your device.

ADB stands for Android Debug Bridge. It is a command-line tool that allows developers to communicate with Android devices or emulators to install apps, debug issues, transfer files, and run device management commands.

ADB is used for device connection and management, app installation and testing, debugging, file transfer, command-line device management, and running or stopping apps. It covers most tasks a developer needs when working with an Android device.

To set up ADB, you need to install the ADB tools on your computer and enable Developer Mode on your Android device. Once Developer Mode is on, you enable USB Debugging so your device can accept ADB commands over a USB connection.

Developer Mode is typically enabled by tapping the Build Number in your device's About Phone settings multiple times. After that, USB Debugging can be turned on inside the Developer Options menu.

ADB provides command-line commands that let developers monitor real-time CPU usage on a connected Android device. This helps identify performance bottlenecks and CPU-intensive processes in an app.

Yes, ADB includes commands for monitoring GPU usage on Android devices. This is useful for developers optimizing graphics-heavy apps or games to ensure smooth rendering performance.

ADB provides commands to query memory usage on a connected device, allowing developers to track how much RAM their app consumes and detect potential memory leaks.

Yes, ADB has commands to monitor battery performance, helping developers understand how much battery their app drains under different usage conditions.

ADB commands can be used to track network activity and performance on an Android device, which helps developers diagnose slow network calls or excessive data usage in their apps.

Systrace is a profiling tool that can be triggered through ADB commands. It captures detailed system-level data about app and device performance, helping developers identify rendering delays and other bottlenecks.

Yes, ADB allows developers to install APK files directly onto a connected Android device or emulator using a simple command. This is useful for testing builds without going through the Play Store.

ADB includes push and pull commands that let developers transfer files between a computer and a connected Android device. This is helpful for loading test assets or retrieving log files from the device.

Vuex is a centralized state management library for Vue.js that lets all components share and update a single source of truth. It is built on five design patterns: Observer, Singleton, Module, Façade, and Command. These patterns make large Vue.js projects scalable, consistent, and easier to maintain.

Vuex is a state management library designed for Vue.js applications. It provides a centralized store shared across all components and enforces specific rules for how state can be read and changed.

The core concepts are State (where app-wide data lives), Mutations (the only place state can be changed, and only synchronously), Actions (which commit mutations), Getters (computed values from state), and Modules (for splitting the store in large apps).

As applications grow, sharing data between many components becomes complex and error-prone. Vuex solves this by managing all state from a single centralized place, making data sharing easier and ensuring consistency across the app.

Vuex uses five design patterns: Observer, Singleton, Module, Façade, and Command. Developers apply these patterns automatically just by working with Vuex, even without realizing it.

Vuex provides reactive state management, meaning components automatically react to state changes. When state updates, any component watching that state (via computed properties or watchers) is notified and re-renders accordingly.

The Vuex store is created as a single instance shared across the entire application. All components access and modify state through this one instance, preventing duplicate or conflicting stores.

In large-scale applications, Vuex allows the store to be split into modules. Each module can have its own state, mutations, actions, and getters, making the codebase more organized and manageable.

Vuex acts as a simplified interface between Vue components and the underlying state management complexity. Components interact with state through Vuex without needing to know the internal details of how state is managed.

In Vuex, actions serve as commands that trigger mutations to modify the state. This separates the instruction to change state from the actual change, keeping logic organized and traceable.

The Observer pattern is highlighted as the most popular and frequently asked about in job interviews. It underpins Vuex's reactive state management, where components automatically respond to state changes.

You create a store using createStore() with state, mutations, actions, and getters defined inside it. You then register the store in the app's boot or entry file, and access state in components using mapState or the Vuex composable APIs.

Vuex guarantees data consistency, simplifies data sharing between components, and makes projects scalable. Its built-in design patterns provide a solid architectural foundation that benefits both individual developers and teams.

Manga frequently features science fiction elements like superpowers, dystopian societies, alternate histories, space and time travel, genetic engineering, robots, AI, and virtual reality. Series like One-Punch Man, Attack on Titan, Fullmetal Alchemist, and Pluto are prime examples. These themes make manga a rich genre for sci-fi storytelling.

Manga is a genre of comic books originating from Japan. It is characterized by black-and-white illustrations, distinctive stylistic features, and is typically read from right to left.

Common sci-fi elements in manga include superpowers, dystopian and alternate worlds, alternate history, space travel, time travel, genetic engineering, virtual reality, and robots with artificial intelligence.

Fullmetal Alchemist features automails as one of the best-executed science fiction elements in manga. Automails are mechanical limbs that represent a fusion of engineering and the series' unique alchemy-based world.

Attack on Titan is highlighted as a manga that features strong dystopian and alternate world sci-fi elements. It is one of several series used as examples in exploring how manga handles these themes.

Yes, robots and artificial intelligence are listed as a key sci-fi element in manga. Pluto is cited as one example of a manga that explores these themes in a compelling way.

Yes, superpowers and special abilities are treated as a core science fiction element in manga. One-Punch Man is one of the series mentioned as a strong example of this theme.

Time travel is listed as one of the science fiction elements frequently featured in manga. It is part of a broader range of sci-fi themes the medium regularly explores.

Genetic engineering and biotechnology are included among the key sci-fi elements found in manga. This reflects manga's willingness to engage with complex and speculative scientific concepts.

Alternate history and parallel universes are listed as a distinct sci-fi element in manga. The post highlights this as one of the exciting ways manga engages with speculative fiction.

Virtual reality and games are cited as a notable science fiction element in manga. This theme reflects how manga incorporates modern and futuristic technology into its storytelling.

Video games can build real skills beyond entertainment. Story-driven games grow empathy, hard games teach patience and resilience, and team or strategy games sharpen leadership and planning. The lessons learned from a keyboard or console often carry directly into everyday life.

Video games can teach patience, empathy, leadership, decision-making, and strategic thinking. Different genres build different skills — hard games build resilience, story games grow emotional intelligence, and team games develop communication and leadership.

Souls-like games like Dark Souls and Sekiro teach patience through repeated failure and learning. Survival games like The Long Dark and slow-paced games like Stardew Valley also reward long-term thinking and waiting for the right moment.

Story-driven games put you in someone else's shoes and show how your choices affect others. Games like Undertale, Detroit: Become Human, Hellblade, and Disco Elysium help players understand different perspectives, mental health struggles, and moral complexity.

Yes. Research by Nick Yee from Palo Alto Research Center found that players of online group games report stronger leadership, motivation, and conflict-resolution skills. Leading a raid in World of Warcraft or coordinating a team in League of Legends directly practices real leadership.

Studies show students who performed well in Civilization scored higher on planning and problem-solving tests. Games like StarCraft, SimCity, and Football Manager require managing resources, thinking multiple steps ahead, and making complex decisions under pressure.

This War of Mine puts you in control of civilians surviving a war zone. Every decision carries serious consequences, teaching patience, moral weight, and the cost of choices. The game is noted as highly emotional and a strong teacher of real-world empathy.

Unlike most RPGs, Undertale lets you talk to enemies instead of fighting them. If you choose violence, you face the consequences. This design forces players to ask whether they had another choice, making empathy a core mechanic rather than a side effect.

Hellblade: Senua's Sacrifice is specifically designed to simulate psychosis. Players hear voices and experience distorted reality, giving them a first-hand feel for what mental illness can be like. The game is widely recognized for building genuine understanding of mental health.

The post argues they are not, citing player experiences and research. The right games build mental, emotional, and practical skills. Even games bought just for fun can teach communication, decision-making, and forward thinking.

In Papers, Please, you play a border officer where every person crossing has a human story. Breaking rules costs you money; following them may harm innocent people. This creates daily moral dilemmas that mirror real-life ethical conflicts between rules and compassion.

The author describes two personal rituals: reading people's stories from airplane windows by observing the buildings below, and noticing hidden lives while driving through the Sakar Pass between Muğla city center and the coastal towns. Both moments of transit spark quiet, unexpected reflection on the lives unfolding around us.

The Sakar Pass is a route in Turkey connecting Muğla city center to the coastal towns. The author drives through it regularly and uses the journey as a moment for quiet observation.

During flights, the author looks out at the buildings below and imagines the hidden lives unfolding inside them. It's a personal habit of finding human stories from above.

At the gate, the author tries to read stories on the tired faces of fellow travelers. The busy airport environment — announcements, engine roars, rushing people — sets the scene for this people-watching ritual.

Both involve moving through a landscape and pausing to notice the unseen lives of others. Despite being very different settings, they share a spirit of quiet, thoughtful observation.

The author trained for 5 months to run a 63km ultra-trail race in Cappadocia, finishing in 10 hours 9 minutes. He later reflected that his discipline came from clear goals, community support, and a structured weekly routine — factors that became harder to replicate during the COVID-19 pandemic.

He trained 6 days a week for 5 months: gym strength work on Mondays, a group run of 6–10km on Tuesdays, light endurance lifting on Wednesdays, HIIT on Thursdays, lighter gym work on Fridays, and a 25–40km forest run starting at 4:30 AM on Saturdays. Sundays were rest days.

The author completed the 63.4km race on October 19, 2019, in 10 hours and 9 minutes. It was his first long-distance race, and he described crossing the finish line feeling exhausted but deeply accomplished.

The author ran weekly with Runarchy Running Club, which provided structured accountability and social motivation. Having a crew to run with on Tuesdays was a built-in commitment that helped sustain his training over five months.

He identifies the COVID-19 pandemic as a major disrupting factor — gyms posed health risks, races were canceled, and the uncertainty made sustained motivation much harder. The external conditions and goal clarity that drove him in 2019 were no longer the same.

He found the answer by comparing what was present in his life during the successful training year versus what was absent later. Self-discipline appears tied to clear goals, supportive community, structured routines, and stable external conditions — not willpower alone.

After a speech at Karabük University in March 2020, a Computer Science student asked the author how he sustained months of intense training. He didn't have a clear answer at the time, and spent over a year reflecting before writing this article.

He encouraged students to read widely, open GitHub accounts to store even small projects, contribute to open-source work, and prioritize physical exercise — sharing lessons he wished he had heard during his own university years.

The author worked as an Android App Developer from 8:00 to 17:00 throughout his training period. He notes that he maintained the pace without much conscious thought, suggesting that strong goal commitment can coexist with a demanding work schedule.

After three months of blogging and publishing 15 posts, the author earned $46.54 in total. Despite slow early growth, they kept writing and focused on lessons like keyword research, reading more blogs, and consuming more books to improve their content strategy.

The blogger earned $46.54 over three months of blogging. This came after a first month that brought in around $10, showing gradual but real growth.

The author published fifteen posts over the three-month period from April to June 2024. Consistency was a key part of their approach.

The author explicitly did not want to join what they called the 'graveyard of quitting writers.' They stayed motivated by a long-term mindset rather than expecting quick financial returns.

Key lessons included the importance of keyword hunting, reading more blogs in their niche, and reading more books to fuel content ideas. These were framed as ongoing homework to improve reach and readership.

Keyword hunting means researching terms people are actively searching for and building content around them. The blogger identified this as a critical step to getting more reads and organic traffic.

According to the author, yes — reading more blogs was listed as a direct action item to grow as a writer. It helps you understand what works, spot trends, and improve your own content quality.

The post frames it as honest, incremental progress rather than a failure. The author treats it as proof the effort is working and worth continuing, not a reason to quit.

Based on the post, the biggest mistake is quitting too early. The author specifically mentions a pattern of writers giving up, and positions persistence as the main differentiator.

This guide walks frontend developers through publishing an iOS app using Vue.js 3, Quasar, and Capacitor — from setup and browser testing to syncing native files, debugging real errors, and submitting to the App Store. It also applies to Angular and React apps using Capacitor as the native bridge.

You need a Mac with Xcode, VSCode, and Git installed. Pull your project via Git, open it in VSCode, and install Vue.js and Quasar dependencies using npm i.

Run npx cap add ios in your project directory. This creates the src-capacitor/ios folder with all necessary iOS files. Only run it once — repeating it can cause errors.

Run npm install -g @capacitor/cli to install or update it globally. You can check the installed version with npx cap --version.

Testing with quasar dev in the browser first lets you catch and fix Vue.js or API errors early. It's faster to debug at this stage than to chase down issues on the iOS side.

Navigate to src-capacitor, run npm i, then run npx cap sync ios. This syncs your latest web build and plugin changes into the native iOS project.

After syncing, navigate to src-capacitor/ios and run pod install --repo-update. This installs or updates native iOS dependencies and prevents common Xcode build errors.

Use quasar dev -m capacitor -T ios --livereload --external to run on a simulator. For a real device, run npx cap open ios, select your device in Xcode, and press the Run button.

Yes. Since Capacitor is a framework-agnostic native bridge, most errors and solutions described here apply to Angular, React, Next.js, and other JS frameworks. Each framework may have its own Capacitor adapter package, but core issues are largely the same.

Capacitor wraps your web app in a native WebView, so Xcode sees the iOS project directory (src-capacitor/ios) rather than the Vue.js source files. It acts as the middleware between your frontend code and the native platform.

Try running npm install --force or npm ci. These commands can resolve stubborn dependency issues that a standard npm i might miss.

Evgeny Grinko, a Russian minimalist pianist born in 1984, performed in Istanbul on July 3rd, blending his signature piano style with Turkish melodies. The two-hour concert won over at least one self-described skeptic, leaving the audience with a memorable musical experience.

Evgeny Grinko is a Russian musician born in 1984, often called the 'silent genius of music.' He is known for his minimalist piano compositions that blend delicate melodies with emotional depth.

Evgeny Grinko performed in Istanbul on July 3rd. The concert lasted approximately two hours and left a strong impression on attendees.

Yes, Grinko blended his minimalist piano style with Turkish melodies during the Istanbul concert, creating a unique fusion that resonated with the local audience.

Based on firsthand experience in the post, even a self-described skeptic was turned into a genuine admirer after the concert. The blend of his minimalist style with Turkish influences made it accessible and moving.

A native Android developer with 8 years of experience tried Quasar Framework after burning out on Android development. Quasar, built on Vue.js, lets you build web and mobile apps from a single codebase. He found it familiar, fun, and fast — and built a working movie app within weeks.

The author says it felt like meeting aliens at first, but he adapted quickly. Quasar's Material Design components felt familiar to an Android dev, and the Vue.js syntax was clean and easy to pick up. Within weeks he shipped a working app.

Yes. Quasar lets you write one codebase and deploy it as a web app, Android app, or other platforms. The author, a former native Android developer, used it to build a mobile app and describes it as a game changer for cross-platform development.

Quasar is a cross-platform framework, not a native Android tool, but it can target Android. The author notes some occasional friction with platform-specific features, but overall found it productive and enjoyable compared to native-only development.

Quasar is built on Vue.js. The author highlights Vue's readable syntax, good performance, and large community as reasons the combination works well for developers coming from other backgrounds.

Native Android requires platform-specific code, while Quasar lets you target multiple platforms from one codebase. The author found Quasar faster for shipping projects and more fun, though he acknowledges some platform-specific quirks can slow you down.

Through Quasar, Vue.js can be used to build cross-platform apps including mobile. The author praises Vue's understandable syntax and strong community support, saying it makes coding enjoyable without sacrificing performance.

The ING Turkey banking app used Hilt for dependency injection, MVVM with StateFlow and two-way binding, Clean Architecture split into feature modules, a single-activity multi-fragment structure, and Mockito for unit testing. It launched on Google Play Store in 2023.

A Turkish school principal recalls his time teaching in Kazancık, a remote Sivas village in the early 1980s. He describes harsh winters with no road access, stunning white Pur cliffs, partridge calls, and deep bonds with villagers and students. Years later, an unexpected reunion at a bus station brought those memories back to life.

The principal lived in a house with a wooden reverse ceiling and no mud insulation, so snow would blow inside even when the stove was lit. Winter roads closed until early March, cutting off the village entirely from outside access.

The Pur Rocks are shiny, snow-white cliffs across from Kazancık village, described as almost glass-like in appearance but not marble. They are not used commercially and the principal visited them often out of pure admiration for their beauty.

Students would arrive each morning carrying bags with dung cakes to heat the classroom. The principal felt it was morally wrong to warm himself using fuel those children carried in, so he bought firewood from the village at his own expense instead.

No. Although he had a hunter's instinct and spotted hares and partridges regularly, he never fired a single shot. The sound of partridges calling in the early morning was so harmonious that he chose never to disturb it.

There was no coffeehouse, so villagers gathered in private rooms in the evenings for tea and conversation. The teachers joined these gatherings and found the talk enjoyable. They also watched Turkey's basketball matches on one of the village's few black-and-white televisions.

Villagers held teachers in very high regard, seating them in the place of honor above elders. Headman Uncle Ramazan and his brother Uncle Haydar were particularly generous and respectful toward the principal and his colleague.

The principal acknowledged having personal political views, but chose to set them aside entirely. He believed his duty was to educate children and not betray the salary paid by the state, so he focused all spare time on his students rather than politics.

There were no resources at home — no encyclopedias, no educated family members to help. So when the principal assigned homework, he and his colleague Mehmet Bey would help the children complete it themselves, keeping busy with students even in their free time.

The post was established by order of Atatürk and could not be removed. The village had a Chechen population, and the post provided security for all the surrounding villages in the area.

The village had a health house with midwives and nurses, but no resident doctor. In winter, the doctor could not reach the village due to closed roads, and would only visit during open months using the Health Directorate's vehicle.

Quasar is a web-based UI framework that targets multiple platforms, while Android XML is native to Android development. Both share surprising similarities in component structure, modularity, and documentation quality. Your best choice depends on whether you need cross-platform reach or native Android performance.

Quasar is a web and mobile UI framework that lets you build cross-platform apps from a single codebase. Android XML is Android's native UI system, tightly integrated with the Android platform. The key difference is that Quasar targets multiple platforms while Android XML is optimized specifically for Android.

Android XML generally has an edge in raw performance since it is native to the Android platform and compiled closer to the hardware. Quasar, being web-based, may introduce some overhead, but modern optimization techniques can make the difference minimal for most use cases.

Android XML can be complex for beginners due to its tight coupling with the Android ecosystem and Java or Kotlin requirements. Quasar uses web technologies like Vue.js, which many developers already know, potentially making it easier to pick up for those with a web background.

Yes, according to the author's 7 years of Android experience, the switch is not as difficult as expected. Quasar shares similarities with Android XML in component structure, modularity, documentation quality, and development paradigms, making the transition relatively smooth.

Both share similar development paradigms, UI component structures, modular and flexible architectures, and strong documentation and community support. Programming language patterns also show parallels, helping developers transfer knowledge between the two.

Quasar is the clear winner for cross-platform development since it can target web, mobile, and desktop from a single codebase. Android XML is limited to Android devices and is not designed for cross-platform use.

Android XML development relies on Android Studio, which is a mature and powerful IDE tailored for Android. Quasar uses web-based tooling built around Vue.js and the Quasar CLI, which is flexible and familiar to web developers but may feel different to native Android developers.

Android XML is better suited for Android-only apps because it is native, deeply integrated with Android APIs, and typically delivers superior performance and access to device features. Quasar is a stronger choice when cross-platform support is a priority.

Both technologies have solid documentation and active communities. Android XML benefits from Google's extensive official documentation and a large developer base. Quasar has well-maintained docs and a growing community supported by its Vue.js ecosystem.

Android XML pairs with Java or Kotlin for logic and behavior. Quasar uses JavaScript or TypeScript alongside Vue.js for component logic. Both approaches separate UI markup from programming logic in comparable ways.

The golden ratio (1.618, or phi φ) is a mathematical proportion found in nature, art, and architecture that makes things look visually pleasing. Designers and developers use it — often without knowing — to set spacing, typography, card sizes, and layouts in mobile apps. When applied intentionally, it creates interfaces that feel balanced and professional without users being able to explain why.

The golden ratio is the proportion 1.618, known mathematically as phi (φ). In design, it's used as a guide for spacing, sizing, and layout so that visual elements feel naturally balanced and pleasing to the eye.

It was noticed across different cultures and eras — from the Great Pyramid of Giza to ancient Greek math. Euclid formally defined it around 300 BC in his book Elements as the 'extreme and mean ratio.' During the Renaissance, Luca Pacioli popularized it as the 'Divine Proportion,' with drawings by Leonardo da Vinci.

Yes, intentionally. Da Vinci applied the golden ratio in works like the Vitruvian Man, The Last Supper, and the Mona Lisa. He collaborated closely with mathematician Luca Pacioli, who wrote the landmark book De Divina Proportione in the 1490s.

Yes. Seashells, sunflower seed patterns, pinecones, and pineapples all grow following the golden ratio through the Fibonacci sequence. Plants place seeds at roughly a 137.5° golden angle to maximize sunlight exposure.

The proportions of the human face, finger joints, and even the ratio of belly-button height to total height are all close to 1.618. The human body is described in the post as 'almost a perfect guide when it comes to symmetry and ratio.'

It influences spacing between components, card dimensions, text size hierarchies, and constraint-based layouts. Whether using Jetpack Compose or XML, applying the golden ratio produces designs that are visually comfortable and don't tire the user.

The post states that the golden ratio quietly works in the background of modern UI kits, even if it isn't explicitly labeled. It underlies spacing scales, typography ratios, and component proportions that frameworks ship by default.

Natural patterns like sunflower seeds and pinecones grow using the Fibonacci sequence, and the ratio between consecutive Fibonacci numbers converges toward 1.618 — the golden ratio. The post describes this as the mechanism plants use to achieve optimal growth.

The rule of thirds is a photography composition guideline where the frame is divided into a 3×3 grid. The post describes it as a simplified version of the golden ratio, used to create visually balanced and professional-looking images.

Understanding the golden ratio lets developers move beyond just making things that work to making things that look good. The post argues that connecting beauty and logic marks growth from a regular coder to a craftsman, improving overall UI/UX quality.

Yes. The post emphasizes that the golden ratio is a learnable visual language — not exclusive to artists. Once understood, developers can intentionally apply it in spacing, sizing, and layout decisions within their existing tools and frameworks.

A developer skipped adding Dagger dependency injection to a small Android project, then regretted it when the app grew to handle three different backend services. With Hilt, you can use @Qualifier annotations to manage multiple OkHttpClient and Retrofit instances cleanly without tangled code.

Small projects can grow unexpectedly. In this case, a simple tablet app eventually needed to integrate with a valet QR system, an Oracle hotel database, and the original API — three separate backends. Adding DI from the start would have made that growth much easier to manage.

You create custom @Qualifier annotations — one for each base URL and its corresponding OkHttpClient and Retrofit instance. In your NetworkModule, you provide each separately and annotate injection sites with the right qualifier so Hilt knows which client to inject.

@Qualifier annotations let you distinguish between multiple bindings of the same type. When you have three Retrofit instances for three different APIs, Hilt needs qualifiers like @BaseRetrofit, @ValeRetrofit, and @HotelRetrofit to know which one to inject where.

Dagger is the original dependency injection framework for Android, but setting it up was complex and error-prone. Hilt is built on top of Dagger and simplifies the setup significantly, providing standard components like SingletonComponent out of the box.

Without DI, each new service integration forces you to manually manage object creation and pass dependencies through constructors or globals. The codebase becomes harder to maintain, test, and extend — exactly what happened in this project when two unexpected backend integrations were added.

SingletonComponent is a Hilt component that lives for the entire lifetime of the application. Modules installed in it with @InstallIn(SingletonComponent::class) provide dependencies as app-wide singletons, which is ideal for network clients and Retrofit instances.

The post notes this project started in Java because Kotlin support was not yet announced for Android at the time. Today the industry has largely moved to Kotlin, and the author suspects the app was later rewritten in Kotlin based on clues from the Play Store.

This project builds a RAG (retrieval-augmented generation) system for legal documents that only answers from uploaded files, cites every source, and explicitly says it doesn't know when the answer isn't in the documents. It was tested on Turkish legal texts using Claude Haiku 4.5, Gemma 4, and DeepSeek-R1, with no fine-tuning required.

Fine-tuning pushes information into model weights in a fuzzy, unverifiable way and leaves no checkable source behind each sentence, which is exactly what this project needed, so it was not chosen. RAG keeps documents outside the model in a searchable archive, so sources stay checkable, adding a new document takes seconds, and no retraining is needed.

The system constrains the model instead of trusting it: a strict system prompt with temperature set to 0 tells it to use only the provided document chunks, never fall back on general knowledge, and answer exactly 'I could not find this information in the provided documents.' when the answer is not there. An instruction is not a guarantee of compliance; in the five-question comparison run here all three models did refuse, which is an observation from a small test rather than a proof.

The system uses BAAI/bge-m3, which produces 1024-dimension vectors. It was chosen because it's multilingual (handles Turkish well), performs strongly on long text, and runs locally on CPU or MPS without needing a second API key or paid service.

Both pypdf and pdfplumber dropped the Turkish letter 'İ' due to a broken ToUnicode/CMap font map inside the PDF — they trusted the broken map and produced corrupted text. pypdfium2 uses Google's PDFium engine, which resolves characters from the glyph itself, correctly preserving Turkish characters.

Text is cleaned first with regex to remove page numbers, date headers, URLs, and portal noise. It's then split at sentence boundaries (not raw character counts), targeting around 1200 characters per chunk with roughly 200 characters of overlap between chunks, so rules spanning chunk edges aren't cut off and lose context.

No. At the current scale, all vectors are stored in a single NumPy array and searched using cosine similarity, which with normalized vectors equals a simple dot product. This keeps the setup simple and avoids external dependencies for smaller document collections.

The system computes cosine similarity scores between the query vector and all chunk vectors, then returns the top-K highest-scoring chunks. A MIN_SIMILARITY cutoff of 0.35 filters out irrelevant chunks. In testing, relevant legal chunks scored 0.60–0.72 while unrelated ones scored 0.42–0.46.

Yes. The top-K retrieved chunks can come from different documents in the archive. All are passed to the model together, and the model attributes each piece of information to its correct source document, allowing answers that combine definitions from one file and examples from another.

The model will not use its internal training knowledge to fill the gap. In a test asking about employment notice periods, the models all responded that they could not find the information in the provided documents — even though they likely knew the answer from general training data.

The system supports .txt, .docx, and text-based .pdf files. Scanned or image-based PDFs require a separate OCR step, which was not implemented in this project since the test documents were text-based PDFs.

Three models were tested on Turkish legal texts: Claude Haiku 4.5, Gemma 4, and DeepSeek-R1. In the five-question comparison all three refused to answer when the relevant information was not present in the provided documents.

In early 1981, a newly appointed teacher traveled through heavy snow and freezing cold to reach Kazancık village in Sivas, Turkey. With roads completely blocked, he walked the final stretch nearly frozen, slept in the school's principal office, and survived on eggs and stale bread. Despite the hardship, his passion for teaching kept him going.

He received a Ministry of National Education letter in January 1981 directing him to Sivas. He participated in a district-by-district lottery and ended up assigned to Kazancık village in Şarkışla district after no schools were left in his preferred district of Gemerek.

Kazancık is a high-mountain village, and heavy blizzards had completely closed the roads. Even the District Governor's official jeep couldn't get through, and no taxis or minibuses were operating on that route.

A driver named Osman Abi took him as far as his Renault could go, but the final stretch was blocked by a blizzard. The teacher walked the last two kilometers alone in freezing temperatures, arriving at the village nearly frozen.

Yes — he knew that three teacher colleagues had recently frozen to death on similar roads in the Zara and İmranlı areas. Despite this fear, he said his ambition to be a teacher overcame even his fear of death.

He wrote a petition with help from the District Governor, which was signed after some back and forth with the District National Education Director. He was granted twelve days' leave to return home to Develi for the February holiday.

He initially stayed as a guest in a village home but felt uncomfortable with the different local customs. The resident teacher, Mehmet Özdamarlar, offered to convert the principal's office into a bedroom, where he stayed until spring.

Not knowing how to cook and unable to rely on others for food, he lived almost entirely on eggs — soft-boiled in the morning, boiled at noon, and fried in the evening — along with bread that had gone hard as firewood in the dry, freezing air.

A teacher named Mehmet Özdamarlar, who was on his second posting at the village, welcomed him warmly. He lit the stove, gave him a room to warm up, and organized the students to retrieve the teacher's belongings from the road.

A senior developer with 10 years of experience tried vibe coding using Lovable and Gemini for a hobby project. He found it fast for prototyping but raised serious concerns about code security, lack of understanding, and hidden risks like mining agents. He concluded that experienced developers should stay in the architect role, not hand over full control.

Vibe coding means using AI tools like Lovable or Gemini to generate code or designs quickly without writing every line yourself. For an Android developer, it can speed up prototyping but skips the deep code understanding that experienced developers rely on.

The main issue flagged is security — vibe coding tools prioritize speed over code quality and safety. The developer also warns that AI-generated code can contain hidden risks like mining agents that run on your device without your knowledge.

According to this developer, no — not without reading every line yourself. He did not even commit Lovable's output to GitHub and planned to rewrite it from scratch after analysis. A developer needs to understand not just the code but the intent behind it.

It can be useful for rapid prototyping and design, but experienced developers should treat AI as a grunt worker, not the architect. Handing over full control is described as 'professional suicide' in the post.

He used Lovable for visual design and code generation, and Gemini as an AI assistant. The project started with a written brief before moving into the vibe coding tools.

The post warns that vibe coding tools can embed mining agents into generated code, which run on your device and silently benefit the tool's owner. This could expose banking information, passwords, and other sensitive data.

The developer's current advice is to learn Java if your university taught it, but switch to Kotlin immediately for Android development. Java has never died and remains widely used in backend and frontend, but Kotlin is the modern standard for Android.

Earlier no-code website and app builders existed but were far less capable. The developer notes that modern vibe coding tools backed by large language models are significantly more powerful than those older platforms.

The author reflects on his father, a deeply respected school principal in Develi, Kayseri for 35 years. Despite his father's strength and public presence, their relationship was complex and deepened gradually over time. The piece explores distance, admiration, and the quiet ways a father leaves a lasting mark.

He is a man born in Develi, Kayseri in 1954 who worked as a teacher before becoming a school principal. He served as a principal for thirty-five years and is widely known, respected, and loved throughout the Develi district.

He knew virtually everyone connected to education in the region — school principals, teachers, and national education directorate staff. Walking with him meant constant greetings and chance encounters at every corner.

The author says his father was not just a school principal — he touched every life and left a mark. His influence extended far beyond his professional duties into the personal lives of those around him.

The tone is one of deep admiration mixed with reflection on emotional distance. The author acknowledges his father's strength and public warmth while hinting that their personal relationship took time to deepen.

A new blogger earned $10 in their first month on a blogging platform. They joined a partner program, built an early readership, and received encouraging engagement through reads, claps, and comments. The experience motivated them to keep growing as a creative writer.

The blogger earned $10 during their first month of blogging. While modest, the earnings came alongside meaningful engagement from readers in the form of claps and comments.

Their writing journey began in high school, contributing to a school newspaper. They described their early articles as striking, confident, and overly self-assured.

The interest, support, and engagement they received from readers in a short time excited them greatly. Seeing claps, reads, and comments gave them encouragement to continue growing as a creative writer.

Yes, joining a partner program was part of their first-month blogging journey, which contributed to their ability to earn money from their writing.

Headaches can be relieved naturally through self-affirmation, breathwork, and mindfulness techniques. These methods are backed by scientific research and offer an alternative to painkillers. Managing stress and practicing relaxation can reduce headache frequency and intensity.

Self-affirmation, relaxation techniques, breathwork, and mindfulness are highlighted as effective natural approaches. These methods target the stress and tension that often trigger headaches.

Yes, the post supports self-affirmation as a tool for headache relief, citing scientific research. Positive self-talk can help reduce stress responses that contribute to headache onset.

Breathwork promotes relaxation by calming the nervous system, which can ease tension-related headaches. It is one of the core techniques recommended in the post as a painkiller alternative.

Mindfulness is presented as a scientifically backed technique for headache management. By increasing awareness and reducing stress, it can help prevent and alleviate headache symptoms.

The post points to the pressures of modern life — including emotional burdens, traumas, and lack of social support — as key contributors to stress-related headaches. These pressures can manifest physically as head pain.

An experienced Android developer stepped outside their comfort zone in 2024 to build a Golang backend for a real running club app. They implemented REST APIs and Firebase authentication, tackling backend development from a frontend perspective for the first time.

The developer recognized that frontend work is useless without backend services and APIs. After years of Android development, they wanted to understand the backend side, especially since collaborating with backend developers unfamiliar with mobile teams can be challenging.

The developer used Golang to build the backend, implementing REST APIs and Firebase authentication. This was for a real-world running club application.

The developer pursued Android development from around 2016 until January 2024, meaning they had roughly eight years of Android experience before tackling a Golang backend.

Frontend development depends entirely on backend web services and APIs to function. Understanding the backend also helps frontend developers collaborate more effectively with backend teams, especially those with no prior mobile experience.

The Golang backend was built for a running club app, giving the developer a practical, real-world scenario to apply their new backend skills rather than just a tutorial exercise.

Declarative UI is a programming paradigm where developers describe what the UI should look like, and the framework handles how to render it. This contrasts with imperative UI, where developers manually control every step. Popular frameworks include React, Flutter, SwiftUI, and Jetpack Compose.

Declarative UI is a programming paradigm that defines the desired end state of a user interface without detailing the control flow. Developers specify what the UI should look like, and the framework handles creating and managing transitions automatically.

In imperative UI, you manually create objects and set their properties step by step. In declarative UI, you simply describe what an object should look like and the framework takes care of the rest, requiring less code overall.

Key features include state-based rendering, simplicity and readability, a component-based architecture, and memory efficiency. Modern declarative frameworks update the UI only when necessary, improving performance.

The main challenges are a steeper learning curve for developers used to imperative programming and limited low-level control over the rendering process. This abstraction can be a disadvantage for projects requiring fine-tuned optimizations.

Popular declarative UI frameworks include React (a JavaScript library by Facebook), Flutter, SwiftUI, and Jetpack Compose. React and Flutter are often the first examples that come to mind when discussing declarative UI.

In declarative UI, the interface is rendered based on the application's current state. When the state changes, the framework automatically updates the UI to reflect the new state without the developer manually managing each transition.

Modern declarative UI frameworks are designed to update the UI only when necessary and minimally, which improves performance and makes them more memory friendly compared to traditional imperative approaches.

Science strongly supports discipline as a key driver of success, citing studies like the Stanford Marshmallow Experiment and Angela Duckworth's Grit research. However, figures like Salvador Dalí and Steve Jobs show that passion, vision, and flexibility can also lead to extraordinary achievement. The truth likely lies between strict discipline and creative freedom.

Multiple studies support discipline as a major success factor. The Stanford Marshmallow Experiment linked self-control in children to better life outcomes, Angela Duckworth's Grit research found the most successful people were the most disciplined and persistent, and Ericsson's 10,000-hour rule showed that deliberate, consistent practice — not just talent — leads to mastery.

Yes, some highly successful people operated without strict discipline. Salvador Dalí worked on instinct and irregular hours, while Steve Jobs was known for disorganization and constantly changing his mind. Their success was driven more by passion, vision, and flexibility than by structured routines.

In 1972, psychologist Walter Mischel gave children a marshmallow and told them they could get a second one if they waited 15 minutes. Children who waited — showing self-control — went on to have better academic careers, higher income, and lower stress as adults. The study suggests self-discipline has a significant impact on long-term success.

Duckworth's 2007 research found that the most successful people — including West Point cadets, corporate executives, and elite athletes — were not necessarily the most intelligent, but the most disciplined and persistent. She called this quality 'grit': passion and perseverance toward long-term goals.

Psychologist K. Anders Ericsson developed this concept in 1993 after studying pianists, chess masters, and athletes. He found that top performers averaged around 10,000 hours of deliberate, conscious practice. The key wasn't just time spent, but the quality and intentionality of practice.

Steve Jobs didn't follow strict working hours, frequently changed his mind, and could be impatient or withdraw for weeks at a time. Despite this disorganization, he built Apple into one of the world's most valuable companies by prioritizing vision and flexibility over rigid discipline.

Dalí worked on instinct rather than a plan — sometimes working for days, then doing nothing for hours. His creative process was spontaneous and intuition-driven. Yet his works ended up in the world's most valuable art collections, suggesting that passion can sometimes substitute for structured discipline.

According to the research cited in the post, discipline consistently outweighs raw talent. Duckworth's grit study and Ericsson's deliberate practice research both found that persistent, disciplined effort matters more than innate ability. However, examples like Dalí show that intense passion can also drive success.

Grit, as defined by psychologist Angela Duckworth, is the combination of passion and perseverance toward long-term goals. Her research showed it was a stronger predictor of success than intelligence or talent alone, making it one of the most important psychological traits for achievement.

This post covers integrating mobile push notifications into a Quasar and Vue.js app using Capacitor and Firebase Cloud Messaging (FCM). The author, an experienced Android developer, shares real pitfalls encountered — especially around retrieving device identifiers — and links to a detailed step-by-step guide.

Yes. The author rebuilt a Flutter-based mobile app using Quasar and Vue.js, including full push notification support. Capacitor is used as the bridge to access native device features like FCM registration.

A major time sink was correctly retrieving the Android/iOS device identifier. The author missed something in the documentation that caused significant wasted time before the issue was resolved.

The post highlights this as a key challenge and dedicates a section to it. The detailed method is covered in the author's full linked guide on Firebase push notification integration with Quasar.

Yes, the implementation targets both Android and iOS devices, as the app being rebuilt needed to support both platforms previously handled by Flutter.

Firebase Cloud Messaging (FCM) is used to handle push notification delivery. The FCM registration steps are part of the detailed guide linked from this post.

Not necessarily — the author had no prior Vue.js or Flutter experience when starting this project. The articles are written from the perspective of someone learning on the job.

This post begins a memoir series about a respected school principal's 35-year career. Through real stories, it shows how he handled conflicts between teachers and parents, supported staff through personal crises, and treated his school community like family. The goal is to preserve these lessons and eventually turn them into a book.

He treated both teachers and parents like family, stepping in personally during hardships — including visiting a child in the hospital before surgery. He handled conflicts calmly and privately, protecting his teachers' dignity while still holding them accountable.

When a parent was rude to a teacher in the schoolyard, the principal stopped the teacher's husband from intervening and took charge himself. He brought the parent to his office, understood the real problem (an upcoming child surgery), and resolved it respectfully for everyone involved.

Instead of demanding an explanation, he welcomed the teacher warmly, offered tea, and acknowledged that something serious must have happened since the teacher had never been late before. He created a safe space for the teacher to open up rather than jumping to discipline.

After resolving a dispute with parents whose child needed surgery, the principal visited the hospital, helped with paperwork, brought gifts for the child, and gave them his home phone number. He told them, 'Your parents aren't in town — here, I'm your mother and father,' showing that genuine care builds deeper trust than authority alone.

He publicly defended his teachers from unfair treatment while privately coaching them on better responses. For example, after protecting the teacher's husband from a costly fight, he later called him in and asked whether throwing away years of hard work over one moment was worth it.

The post briefly mentions a previous story about how Evgeny Grinko got inspired by Aşık Veysel as part of the author's earlier writing. No further details about the album or that story are provided in this post.

SwiftUI (iOS) and Jetpack Compose (Android) are both modern declarative UI frameworks with many similarities in syntax and structure. A developer with 6 months of Android experience shares firsthand observations switching between the two platforms, covering UI building, syntax patterns, and practical challenges.

Yes, SwiftUI and Jetpack Compose share many similarities as both are declarative UI frameworks. Developers familiar with one can often pick up the other more quickly than learning a completely different paradigm.

The main differences lie in the programming language (Swift vs Kotlin), platform ecosystem (iOS vs Android), and some syntax conventions. Each framework also has platform-specific UI components and design guidelines.

An Android developer experienced with Jetpack Compose can leverage that knowledge when learning SwiftUI, since both use declarative UI patterns. However, there are still language and platform-specific challenges to overcome.

Both frameworks are considered beginner-friendly compared to their older counterparts (UIKit and XML layouts). The best choice depends on whether you're targeting iOS or Android development.

The post mentions resources for both SwiftUI and Jetpack Compose, though specific titles are referenced in the full article. Official documentation and community tutorials are typically the go-to starting points for both frameworks.

Dune is a 1965 sci-fi epic set on the desert planet Arrakis, following Paul Atreides as he rises to power through political betrayal and alliance with the native Fremen. While praised for its world-building and themes, some readers find it overly fantasy-like, with predictable plot beats, jarring time jumps, and underdeveloped character arcs.

Dune follows young Paul Atreides after his family is betrayed and his father killed on the desert planet Arrakis. Paul escapes into the desert, joins the native Fremen people, and eventually leads them to defeat the Harkonnens and the Emperor to take control of Arrakis.

Spice, found only on Arrakis, is the most valuable substance in the universe. It extends human life, expands consciousness, and makes interstellar space travel possible, making control of Arrakis a massive political prize.

The key characters include Paul Atreides, his father Duke Leto, his mother Lady Jessica (a Bene Gesserit), the villain Baron Vladimir Harkonnen, and Stilgar, leader of the desert-dwelling Fremen who take Paul and Jessica in.

Dune explores power and political control, the ecology and environment of a desert world, the messianic concept of a chosen one, and the limits of human potential through Bene Gesserit training and evolution.

Despite being marketed as sci-fi, Dune leans heavily into fantasy elements like prophecies, genetic manipulation by the Bene Gesserit, and special powers. Sci-fi elements like ornithopters and Fremen suits exist, but they don't dominate the story.

Common criticisms include frequent time jumps that disrupt story flow, a predictable 'chosen one' hero arc, lack of detail around space travel, and Paul's inconsistent portrayal as both god-like and helpless across the two books.

After escaping into the desert following his father's death, Paul and his mother Jessica are reluctantly accepted by the Fremen. Paul quickly earns their trust, takes the name Muad'Dib, and uses superior combat techniques to unite them against their enemies.

Dune Messiah shows a sharp decline for Paul, who displays increasing helplessness and weakness despite his earlier god-like promise. The abrupt tonal shift and underdeveloped character arcs in the sequel left some readers feeling disconnected.

Dune was rejected by around 20 publishers because the sci-fi trend at the time favored shorter, more impactful stories. The book was considered too long and was often turned down without being fully read.

The Bene Gesserit is a secretive sisterhood that practices genetic manipulation and trains members in advanced mental and physical abilities. Paul's mother Lady Jessica is a member and trains Paul in their ways.

You can sleep in longer by doing most morning tasks the night before — packing your bag, laying out clothes, and prepping food. Better sleep quality through good bedding and pre-sleep routines also helps you wake up later feeling rested. Small time savings add up to an extra 15–30 minutes of sleep.

Prepare as much as possible the night before — pack your bag, lay out your clothes, and prep your food. This can free up 20–30 minutes in the morning so you can sleep in and still get out the door on time.

Front-load your morning prep into the evening. Packing your bag, ironing clothes, and setting out breakfast ingredients the night before eliminates decisions and tasks that eat into sleep time.

Protect the quality of the hours you do get. A good bed and pillow, a pitch-dark room, a sleep mask or earplugs, and brushing your teeth as a wind-down signal all make a short night more restorative. Put your phone in airplane mode so group chats and good-morning messages do not cut the little sleep you have even shorter.

The post suggests skipping breakfast or eating just two meals a day can free up meaningful morning time for sleep. The author notes no negative impact on energy or productivity, though a minimal pre-prepped breakfast is offered as an alternative.

The post reframes laziness as motivation — doing prep work the night before is itself a lazy strategy to avoid morning stress. Making mornings effortless makes it easier to get out of bed quickly.

A quality bed and pillow improve sleep quality so you wake up feeling more refreshed. Better rest means you're less likely to have your sleep disrupted, effectively letting you sleep longer.

Brushing your teeth signals your brain it's time to sleep and improves sleep quality. The post also recommends meditation or relaxation exercises, a dark room, sleep masks, or earplugs to reduce disruptions and deepen sleep.

Shorten the morning, not the sleep. If your bag is packed, your clothes are laid out and breakfast is either skipped or waiting in the fridge, you can be out the door 20 to 30 minutes after the alarm instead of an hour. Those minutes come straight back as sleep, which is the whole difference between waking up early and waking up early exhausted.

The author began running in 2017 during a period of loneliness and aimlessness, starting with garden sprints alongside his dog Şeker. Over time, running became a source of mental clarity, personal growth, and connection with others, eventually leading him to complete multiple ultramarathons.

The author began running in 2017 while living in Istanbul during a difficult, directionless period of his life. He started with short sprints in a small garden alongside his Russian Spaniel, Şeker, and gradually built up to longer solo laps when the dog wasn't in the mood to run.

For the author, yes — running emerged during a time when he felt alone, empty, and without purpose. The physical routine of exhaustion, sweat, and recovery gave him something concrete and rewarding to hold onto when little else did.

He started with 6 garden laps a day, gradually increasing to 8, 10, 12, and 14 without formal knowledge of pace or running form. Over years, that habit evolved into completing races like the Cappadocia Ultra (63 km, twice) and the Uludağ Ultra (30 km, twice).

He has completed the Cappadocia Ultra (63 km) twice, the Uludağ Ultra (30 km) twice, and the Dağyenice Ultra (35 km) once. He is also eyeing the Uludağ Ultra 66 km race.

The author quotes Dean Karnazes: 'There is a magic in misery.' The idea is that intense physical effort heightens awareness and consciousness in a way comfort never can. For the author, the fatigue and sweat were genuinely enjoyable from the very start.

For the author, running indirectly helped. As he worked on communication skills and opened up to colleagues, he discovered a coworker who ran races — a connection that helped draw him deeper into the running community.

The author started with zero knowledge of pace, speed, running form, or training zones. He simply timed his laps and focused on completing them without stopping, showing that beginners can make real progress without technical knowledge.

Yes — the post frames running as a journey toward freedom, mental clarity, and inner peace. The author describes it as something that cuts through emptiness and gives a sense of direction, both literally and emotionally.

The author attended two Haluk Levent concerts at Kuruçeşme in 2021 and 2022. The first was a rainy but unforgettable night where no one left despite getting soaked. The second featured a VIP spot, custom Haluk Levent photo T-shirts, and an emotional, up-close experience with the legendary Turkish rock artist.

Haluk Levent's concerts are high-energy, intimate events where he mingles with the audience and performs improvisations. At Kuruçeşme, he walked among the crowd, and even when rain soaked the audience, no one left — which visibly surprised him.

The author shares photos taken at two Kuruçeşme concerts in 2021 and 2022, including crowd shots in the rain and images of custom Haluk Levent photo T-shirts fans wore. Getting a personal photo with Haluk Levent proved difficult even at close range.

His band includes Göktuğ Şenkal on electric guitar, Elvan Kızılay and Feray Tekşahin on violin, Mert Alkaya on drums, Burak Kulaksızoğlu on bass, Aslıhan Parlak on cello, and Erdi Arslan on wind instruments. Haluk Levent himself praised the orchestra for handling unrehearsed songs and his improvisations.

The concerts described in this post were both held at Kuruçeşme, a venue by the sea in Istanbul. The seaside setting added to the atmosphere, especially during the emotional cello performance of 'Anlasana.'

The author and a friend couldn't find ready-made Haluk Levent photo T-shirts for sale, so they found a high-quality old photograph of him and had T-shirts custom printed themselves. No official merchandise store for such items is mentioned in the post.

The author mentions singing along to many of Haluk Levent's songs, including 'Anlasana,' which featured a standout cello solo. The setlist appeared to cover a wide range of his catalog, including songs about breakups and longing.

According to the post, Haluk Levent himself said, 'I've been a rocker for 40 years, and I'm still adjusting my pants,' suggesting a career spanning at least four decades.

Haluk Levent founded Ahbap, a charitable organization. The post notes this, along with other good deeds like starring in a cryptocurrency exchange commercial and donating the proceeds to students, as reasons the author deeply respects him.

Opening massive HTML documents (11M+ characters) in a mobile WebView crashes the main thread. The solution is virtual chunking: parsing the HTML into safe segments at block-level boundaries, then rendering only the visible chunk in the DOM while keeping the rest out of memory.

When a WebView loads HTML, it keeps the entire document in memory and recalculates the full layout tree on every scroll or interaction. An 11 million character document with hundreds of nested tables, divs, and definitions causes layout thrashing and locks the main thread, making the app unresponsive and the device hot.

Virtual chunking is an adaptation of the 'virtual scrolling' or 'windowing' technique applied to large HTML documents. Instead of loading the entire document into the DOM, only the portion visible on screen is rendered, keeping invisible content outside the DOM to reduce memory usage and main thread load.

TBT is the time the browser's main thread is blocked and unable to respond to user input. Loading 11 million characters into the DOM all at once can lock the main thread for minutes. Breaking the process into smaller chunks frees up the main thread and keeps the app responsive.

Splitting HTML at arbitrary character positions or with simple regex risks cutting through open tags, leaving unclosed tables or broken div hierarchies that crash the browser. HTML's deeply nested and often poorly formed structure makes safe splitting with regex extremely difficult at scale.

Documents exceeding 1.5 million characters were identified as risky. There were 227 documents in the system that exceeded this threshold, with the worst cases reaching over 11 million characters.

The sales team reported that opening documents outside the mobile application was unacceptable to customers. The product requirement was that all documents must open within the app, ruling out the simpler browser-redirect approach.

Reddit migrated from raw HTML to a JSON-based content format in the early 2010s. The common philosophy across major platforms is to render only what is visible on screen and keep invisible content outside the DOM, which is the same principle behind virtual scrolling.

Layout thrashing happens when the browser repeatedly recalculates the positions and sizes of elements in a large DOM tree. On mobile devices, this causes physically noticeable sluggishness with every scroll or touch interaction, especially in documents with complex nested structures.

The post indicates cuts must be made at safe block-level boundaries rather than at arbitrary character positions. Cutting mid-tag or inside nested structures like tables or divs creates broken HTML that the browser cannot render correctly.

The application was built with Vue.js and Capacitor, running as a native wrapper around a WebView on mobile devices.

Science fiction explores scientific and technological innovations, social questions, and alternative futures. Its key traits include advanced technology, philosophical depth, alternative realities, and strong character development. It acts as a mirror for humanity's hopes and fears about the future.

Science fiction has four core traits: scientific and technological innovations (like AI or space travel), social and philosophical questions about human nature, alternative realities and future scenarios, and strong narrative with deep character development. Together these make sci-fi both entertaining and thought-provoking.

Science fiction explores scientific and technological possibilities through stories set in the future or alternative universes. It examines philosophical questions about human nature and society while reflecting our hopes and fears for the future. It's not just escapism — it's a mirror held up to the present.

Sci-fi explores themes like artificial intelligence, space travel, genetic engineering, social structures, identity, and the impact of scientific progress on humanity. Works like Asimov's Foundation and Philip K. Dick's Do Androids Dream of Electric Sheep? tackle sociopolitical evolution and what it means to be human.

Good starting points include H.G. Wells's War of the Worlds and The Time Machine, which replaced magic with science-driven storytelling. Richard K. Morgan's Altered Carbon is a standout cyberpunk entry, and Frank Herbert's Dune is considered a landmark of the genre.

No — while technology is a common element, sci-fi also digs into deep philosophical and social questions. Asimov's Foundation examines sociopolitical structures, and Philip K. Dick's work questions reality and human identity. Technology is often just the backdrop for exploring human nature.

According to the post, H.G. Wells moved sci-fi closer to positive sciences by replacing magic, spells, and supernatural events with human or alien-made machines. Fantasy relies on those supernatural elements, while sci-fi grounds its impossible ideas in scientific or technological reasoning.

War of the Worlds is a satire of British colonialism, and The Time Machine is a satire of Victorian social class differences. Many readers, including the post's author, don't catch this subtext on first read, which shows how sci-fi layers entertainment with deeper social criticism.