Beginning to suspect that my philosophy that ‘the only two real writing tips you need are to read a lot and write a lot’ is missing a third secret component, being that the reading benefits from being both fiction and nonfiction, regardless of what you’re writing. Long meandering musings below cut expand at own risk

I best refrain from using second person because this is I suppose a matter of personal taste and how I’ve realised my brain works, as a tragically uncreative person, but reading theory–which consists of attempts to light and taxonomise the abstract shadows beneath the water, the quintessence of all writing–teaches me how to organise and develop my ideas. My writing is becoming more coherent than before. It’s easier to figure out exactly what I’m trying to say in a given piece of writing. This also makes writer’s block so much less torturous. It does sometimes slow down, but mostly to give way for problem solving. I can work from abstraction into concrete, which prevents me from getting stuck on events unfolding in a certain way, and from being reluctant to scrap scenes, as they’ve served their purpose in the sense that failing to argue for something teaches you more about your position. Cool plot or worldbuilding ideas fall flat for me without a strong thesis. Making it exist isn’t enough, I have to prove why it matters. Otherwise why are you reading, why am I writing? Because it’s new? Things are unique as often as they are the same. I don’t want to make things for the sake of a novelty-induced dopamine kick, that is a grind with no discernible goal or endpoint. (That’s part of the reason I quit graphic design/marketing, actually, aside from being unable to settle in the cognitive dissonance of being a mercenary, and the particularly blatant vampirism of the industry, which is being committed by one toward customers and peers, and onto one by peers and employers. Nearly every field is a burnout machine now, but nonetheless. I hate that one in particular with the sort of intensity you have to convert wistfulness into after failed experience). And if theory and philosophy help me figure out what I’m saying, history helps me figure out how to say it. This may be a consequence of me, again, being an unfortunately uncreative person, but I struggle there. Helen Hindpere once gave a fantastic interview for the Platypus Affiliated Society (truly excellent interviewing, too) that is very meaningful to me, and one of the most igniting things she says with regards to writing is this:

All of my writing is inspired by history. I sometimes say that I don’t make things up, I just take them from history and then put them in another context so people pay them more attention. That’s how the entire world of Elysium was created. We just took things out of their contexts, freeing them of the conscious notions and subconscious associations attached to them by applying different names and aesthetics. The hope was that people could see them in a new light, and that is what I usually say I do. But I’m not just writing for myself; I’m writing to communicate ideas. These come from history, about which Kurvitz and I read a lot.

I think she put words to a place I’ve been trying to reach as long as I’ve been writing, and in the way of all excellent writing, she shone a light onto a shadow here, to make you go 'of course! This is, obviously, what it’s been all along!’ I think so much of the success of DE, not commercially but creatively, communicatively, is down to its writers being drawn to theory: a desire to truly engage with and understand, and versed in theory: having this internal framework for how to structure ideas both individually and then among themselves. (The thought cabinet being a from-scratch invention still blows my mind, and the way the skills are constructed and expressed is one of my favourite parts. Rhetoric is my favourite: the remark that being able to argue for something is separate from being correct, and that always striving to be correct stunts you.)

That, the understanding and engagement, is the difference between copying established canon in a way that legitimises you by proxy, and being able to build on it in a way that contributes something to the canon. (Some of the vampirism I mentioned earlier was this: creativity can get so incestuous. You can make a moodboard with unique and intriguing visual references and the visual you will end up creating is nothing more interesting than 'something that fits harmonically within this moodboard’. Are you making or copying? Is realism/believability creativity or merely a skill? Funnily, in uni we didn’t read Baudrillard, we read works that referenced and summarised Baudrillard. Writes itself.)

The difference between art as an attempt to subtly rephrase something somebody said before you that everyone agreed with lest you seem stupid when the conversation reaches your turn, and art as an attempt to engage with the conversation out of true interest, is at the core of improved writing. You can read endlessly and write endlessly but without the third, essential component, understanding, you risk turning yourself into a copy machine. And I think theory forces one to think in a way that is optional in a lot of other writing.

has anyone completely bald done sideburns with no other facial hair before. i’m brainstorming new untainted perversions

some stupid bullshit i’ve been doing lately is to bust a move every time i feel myself succumbing to the void. you can freak out and hit the rasputin simultaneously but it’s harder

What is Customer Segmentation and Why It Matters

You know your product is good. Your customers know it too—the ones who’ve found you. But reaching everyone else? That’s the challenge that keeps business owners up at night.

Quick Answer:

Customer segmentation in marketing is the process of dividing your customer base into distinct groups based on shared characteristics such as demographics, behavior, or preferences. This allows you to create personalized marketing strategies that resonate more deeply with each segment, improving engagement and conversion rates.

What is Customer Segmentation and Why It Matters

Customer segmentation is the practice of categorizing a business’s audience into smaller groups that exhibit similar traits, such as age, buying behavior, location, or interests. These segments enable marketers to tailor messages and offers specifically to each group, rather than using a one-size-fits-all approach.

Why is this important? According to a study by

MarketingCharts

, segmented email campaigns can result in a 760% increase in revenue. Personalization doesn’t just feel nicer to customers; it drives significant business impact.

From my experience working with various brands, companies that invest time in refining their customer segments often see higher open rates, improved customer loyalty, and stronger brand affinity. Yet many businesses struggle to identify the right segments or lack the tools to implement segmentation effectively.

Main Types of Customer Segmentation

Understanding the different types of segmentation is key to building effective groups that truly reflect your audience:

Demographic Segmentation:

Based on age, gender, income, education, or occupation.

Geographic Segmentation:

Dividing customers by location—country, city, climate, or urban/rural.

Psychographic Segmentation:

Focuses on lifestyle, values, interests, and personality traits.

Behavioral Segmentation:

Groups customers by purchasing habits, brand loyalty, usage frequency, or online behavior.

Each type offers unique insights, and combining them often yields the most precise targeting. For example, targeting young urban professionals (demographic + geographic) who frequently shop online (behavioral) can guide you to craft highly relevant promotions.

heated rivalry on the 6 o clock news

i was eating me dinner and thought let me watch the news for a second. I went online and heated rivalry was being spoken about in my country. I was like what? Following the floods in Spain haha. Did not see that coming🤭 every day heated rivalry! Yeah!

Top 10 Segmentation Fault Errors in C and How to Crush Them Fast

Segmentation faults—those dreaded “Segmentation fault (core dumped)” messages—can halt your C programs in their tracks. If you’ve ever wondered what causes a segmentation fault in C, you’re not alone. They stem from accessing memory you’re not allowed to touch, like invalid pointers or array overflows.

In this post, we’ll dive into the top 10 segmentation fault errors in C, complete with segmentation fault in C example code snippets and quick fixes. Whether you’re debugging segment fault in c or hunting for how to solve segmentation fault in C tips, these strategies will help you crush them fast. Let’s get coding!

1. Dereferencing NULL Pointers

The classic newbie trap: forgetting to check if a pointer is NULL before using it.

Example:

c

int *ptr = NULL; *ptr = 10; // Boom! Segfault.

Quick Fix: Always validate pointers.

c

if (ptr != NULL) { *ptr = 10; }

Use gdb to inspect: gdb ./program, then run and bt for the backtrace. Pro tip: Initialize pointers to NULL.

2. Array Out-of-Bounds Access

Accessing beyond an array’s limits is like reaching into someone else’s fridge.

Example:

c

int arr[5]; arr[10] = 42; // Segfault on small arrays.

Quick Fix: Bounds-check with loops or sizeof.

c

for (int i = 0; i < 5; i++) { // Safe access }

Tools like Valgrind (valgrind ./program) spot these instantly.

3. Uninitialized Pointers

Pointers with garbage values point to random memory, inviting chaos.

Example:

c

int *ptr; // Uninitialized! *ptr = 5; // Random segfault.

Quick Fix: Zero them out.

c

int *ptr = NULL;

Compile with -Wall -Wextra for warnings. Static analyzers like Clang Static Analyzer catch this early.

4. Dangling Pointers After Free

Freeing memory but still using the pointer—zombie code!

Example:

c

int *ptr = malloc(sizeof(int)); free(ptr); *ptr = 10; // Dangling! Segfault likely.

Quick Fix: Set to NULL post-free.

c

free(ptr); ptr = NULL;

Adopt RAII-like habits or use smart pointers in C++ wrappers.

5. Stack Overflow from Recursion

Infinite recursion eats your stack like Pac-Man.

Example:

c

void recurse() { recurse(); } // Endless loop, segfault. int main() { recurse(); return 0; }

Quick Fix: Add a base case.

c

void recurse(int depth) { if (depth > 100) return; recurse(depth + 1); }

Monitor stack size with ulimit -s.

6. Writing to Read-Only Memory

String literals are in read-only segments—don’t touch!

Example:

c

char *str = “hello”; str[0] = ‘H’; // Segfault!

Quick Fix: Use char arrays.

c

char str[] = “hello”; // Mutable copy. str[0] = 'H’;

For strings, prefer strdup or malloc.

7. Function Pointer Mishaps

Calling uninitialized or wrong-type function pointers.

Example:

c

int (*func)() = NULL; func(); // Segfault city.

Quick Fix: Initialize properly.

c

int foo() { return 42; } int (*func)() = foo; func();

Validate with if (func) func();.

8. Off-by-One Errors in Loops

Sneaky loops that overshoot by one.

Example:

c

int arr[5]; for (int i = 0; i <= 5; i++) { // <= is the killer. arr[i] = i; }

Quick Fix: Use < for zero-based arrays.

c

for (int i = 0; i < 5; i++) { arr[i] = i; }

sizeof(arr)/sizeof(arr[0]) automates bounds.

9. Mismatched malloc/free Sizes

Allocating small, freeing large (or vice versa).

Example:

c

int *ptr = malloc(sizeof(char)); // Too small! free(ptr); // Might segfault on cleanup.

Quick Fix: Match types exactly.

c

int *ptr = malloc(sizeof(*ptr)); // Portable!

Always free what you malloc.

10. Multithreading Race Conditions

Threads clashing on shared memory without locks.

Example:

c

int *shared = malloc(sizeof(int)); void *thread_func(void *arg) { (*shared)++; // Race! Potential segfault. }

Quick Fix: Use mutexes.

c

pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER; pthread_mutex_lock(&lock); (*shared)++; pthread_mutex_unlock(&lock);

Test with ThreadSanitizer (-fsanitize=thread).

Pro Tips: How to fix segmentation fault Like a Boss

• Debuggers: GDB or LLDB for core dumps.
• Sanitizers: -fsanitize=address in GCC/Clang flags undefined behavior.
• Valgrind: Catches leaks and invalid reads/writes.
• Prevention: Static analysis (Coverity, cppcheck) and code reviews.

Master these, and segment fault in c with example scenarios won’t slow you down. Happy coding—may your pointers always point true!

(WIP) Process of the expression test of Ava, my moth OC! This is only the positive half of the expressions, plus I still need to add her wingsss

gonna be a balkan year

On a scientific level, pre-typing a message in the notes app basically imbues the text with a good aura that will make it of the correct texture for the recipient; this is because words of a message are swaths of discrepant ants which first need to be raised and bonded in a tranquil environment, and sometimes their developmental needs outright demand a larger enclosure than the message input field, so that they can practice their collaborative skills in a more open and low-stress environment before having to be compacted flawlessly into the text message

Isms of the year:

Determinism

Impressionism

Exorcism

Isms of next year:

Dialectical materialism

Homoeroticism

Kineticism

arch

carnival

facade

ruin

spire

window

Post-war / 1945–1980

video:

POST WWII HOME MOVIES OF COLOGNE GERMANY COLOGNE CATHEDRAL REBUILDING OF GERMANY 28152 : Free Download, Borrow, and Streaming : Internet Arc

“ THE TRUE GLORY ” 1945 ACADEMY AWARD WINNING WWII DOCUMENTARY D-DAY TO V-E DAY PART 2 22374 : PeriscopeFilm : Free Download, Borrow, an

Cultural Characteristics:
Ruins, damaged buildings, open-air structures
The emergence of a large number of “ruin” categories
Temporary reconstruction of bridges, construction sites, factories
The color is rather dull.
The crowd was more concerned with “returning to normal life” rather than the daily city scenes.

I tried frame sampling + SAM and got a large amount of:
ruin, broken wall, destroyed facade, scaffolding

Rangmunch TV: They will all log on coz [11 February 2012]

Precious Design
.
A 3D illustration of a multilayered band of upright colored segments combined into one precious object that is presented inclined.
.
Purchase from Graffair PRO

I honestly really like when stretch marks form in parallel. Makes me feel like I have a segmented body or chitin plates. :)

Full turnarounds of my main insectoids! :D

Ani News: Barun Sobti with Indian Cricketer, Sreesanth at an Event [24 December 2011]

Wassup TV Episode 54 - Bombat Segment [19 December 2011]

AI vs Algorithmic learning: What’s the Difference?

 Lately everyone, and I mean everyone seems to be claiming to use AI. Are they, though? The short answer; no. Let’s expand that.

Above you see a poster for the movie AI: Artificial intelligence. The movie is about AI. The definition of AI is clear: AI is technology that enables computers and machines to simulate human learning, comprehension, problem solving, decision making, creativity and autonomy.

That last bit about autonomy is key. Both in the film and in the definition. The last part means that once you build it you no longer have any control over what it does, or doesn’t, do. This is why Asimov made his rules.

They are:

(1) Don’t HARM HUMANS 

(2) OBEY HUMANS 

(3) Protect robots unless it conflicts with rules 1 or 2.

I am paraphrasing for conciseness. IF we think back to the definition of AI, it can learn and it has autonomy. This means it can decide to ignore it’s programming. Basically Asimov’s rules exist to try and nullify AI.

Can today’s technology do any of this? It CAN solve problems depending on complexity. IT CAN’T do any of the rest of the list. It can’t think for you, it isn’t creative, it can’t decide things for you, and it doesn’t have autonomy.

Algorithmic learning, in the context of artificial intelligence, refers to the process where machines or algorithms learn from data to improve their performance on a specific task.

So algorithmic learning is best illustrated in action by Alan Turing’s ENIGMA machine used during World War II. This complex beast of a machine was programmed to try and crack codes used by nazis. The machine required a human to program it. 

It ran day and night trying all possible combinations of letters and numbers to break this code. On it’s own it may have taken decades to break the code, had someone not realized the same length grouping of letters was always at the bottom of each message. Once a human figured out those words. they could program ENIGMA to break the code every time it was changed.

While algorithmic learning is the foundation of AI, it is not AI. Not by a long shot. Could you imagine what may have happened if ENIGMA had autonomy and the capacity for decisions. It may have refused to do it’s job, started making up answers to spite its’ bosses, or maybe even given bad Intel due to sympathising with nazis.

It’s a very good thing all it could do was solve a problem. Today’s algorithms have complex capacity to solve what they are programmed to solve. That is not AI. Not yet.

Half moon, half grapefruit