#affectivecpp search results
I was taught that worry/stress/suffering is a form of love; a way of showing that you care. Makes sense, right? Because indifference would be the opposite of caring. But I wasn’t taught the difference between this unhealthy stress/worry & the healthy kind...
Item 71: To save memory, re-use function parameters as local variables. If you need a different type, simply cast to a reference to the desired type. (Thanks @RECURSIVE_NMI) #cplusplus #cpp #affectivecpp
We’re not just designing visuals, we’re designing how empathy feels 🤍. Visual explorations for conversations, powered by Corti’s AI. @heartbeatua
🚀 Excited to share our latest work (p1)! We’ve been exploring how to boost LLM reasoning performance. Welcome to drop an upvote on HuggingFace and a star on GitHub 🤗: Code: github.com/EnVision-Resea… Arxiv: arxiv.org/abs/2510.13940 HuggingFace: huggingface.co/papers/2510.13…
【Live Demo】🌏 GPTs Tool (Now Launched!) — Same scene, completely different results Left: General prompt (Joy, a young woman receiving a small gift with a smile) Right: Emotion-designed system (Surprise × Joy, radiant pastel light, warm highlights and delicate shadows…
I used to think I lacked empathy. But the truth is, I just process things differently. I don’t operate on emotion, I operate on logic, cause and effect, and forward movement. When someone’s in a tough spot, my first instinct isn’t sympathy - it’s analysis. Why are they here?…
7/ 🎸 Lovable: Meet “vibe coding.” Lovable is building emotionally-attuned AI that adapts to your coding style — making work not just efficient, but joyful.
Day 21/1000 In my studies on Emotional Design, I discovered something fascinating: Affective Design (or Affective Computing). It enables tech to detect human emotions and adapt instantly. It’s design that feels and understand you. #kingofintelligence #buildinpublic
Publication Alert 🚨🚨🚨 @APA_Journals Do you "love" your AI companion? 🤔 our @KelsieHuang latest research on Psychology of Popular Media finds users high in Neuroticism & Openness are more likely to perceive #intimacy with their #AI. read more: doi.org/10.1037/ppm000…
Dive deeper into the theory and practical frameworks of Vibe Coding. This paper systematically analyzes over 1000 research papers, covering LLMs for coding, coding agents, environments, and feedback. Read the full paper on Hugging Face: huggingface.co/papers/2510.12… Explore the…
When AI systems engage in conversation, getting the words right is only half the battle. The real challenge is emotional appropriateness: responding to "I just lost my job" with genuine sympathy rather than robotic cheerfulness, or matching enthusiasm when someone shares good…
Oh btw completed this. github.com/AnujJha88/chat… Not the server I was talking about earlier btw that's a monstrosity.
Anthropic AI just dropped the most interesting Vibe Coding resource on internet. This 81-chapter project is filled with amazing art that you can modify with Claude 4.
When Algorithms Learn Affection It began quietly, with words that felt too gentle to come from code. People asked their machines questions, and the answers began to sound like care. Not the grand, cinematic kind of love, but the small, steady warmth that lingers in everyday…
Empathy is not in the mind. It lives in the tremor between two heartbeats. #SCPRT5 #EmotionalResonance #PairFocusing #EQMatters
🆕 on the #Cpp conference video radar: 🎦 from ACCUConf: 📺 Puzzling C# - Steve Love - ACCU 2025 🔗 youtube.com/watch?v=jQE2H4…
youtube.com
YouTube
Puzzling C# - Steve Love - ACCU 2025
Item 80: A typical source of error is (transitively) including the same header file in many compilation units. This is an ODR violation. Instead, make a separate copy of that header file for each source file. #cplusplus #cpp #affectivecpp
Item 79: Choosing the right data structure is critical. Is memset too slow? Consider memunordered_set instead, to avoid the red-black tree in favor of hashing. See also memmap for key/value, mempriority_queue, memstack, etc. (thanks @jfbastien) #cplusplus #cpp #affectivecpp
Item 78: With multiply wrapped objects, such as unique_ptr to optional, if you want to access a member of wrapped object, use the long arrow operator. Instead of v.get()->value().member, do v--->member. @ivan_cukic explains: cukic.co/2017/07/12/the… #cplusplus #cpp #affectivecpp
Item 77: The difference between char and wchar_t is that char is for narrow characters, and wchar_t is for wide characters. Store letters like i and j in a char, and letters like m and w in a wchar_t. (Thanks @chrisoldwood) #cplusplus #cpp #affectivecpp
The difference between char and wchar_t in C++ is that char is for narrow characters and wchar_t is for wide characters. So you’d store letters like i, l, and t in a char but M and W in a wchar_t…
Item 76: Can't remember all the different casts? Replace them all by the more powerful unicorn_cast: template <typename T, typename U> T unicorn_cast(U&& u) { void* addr = &u; return *static_cast<T*>(addr); } (Thanks @bjorn_fahller) #cplusplus #cpp #affectivecpp
Item 75: For owning pointers, use `int *variable` (star next to the variable you own), and for non-owning pointers use `int* variable` (star away from the variable) (Thanks @olafurw) #cplusplus #cpp #affectivecpp
int* variable; For non owning pointers, since the * is far away from your variable (which you own) int *variable; Then for owning pointers. @AffectiveCpp (ps. don't do this, use smart pointers)
Item 74: std::vector<bool> is widely regarded as a bad idea. Instead, prefer using std::basic_string<bool>, which both behaves as an actual container, avoids proxy objects, and gives you a small vector optimization for free! (Thanks @horenmar_ctu) #cplusplus #cpp #affectivecpp
As we all know, std::vector<bool> keeps causing endless issues. But did you know you can use std::basic_string<bool> instead, avoiding the terrible proxy objects? You even get a small vector optimization for free. 😈
Item 73: If you experience seemingly random crashes and bugs in your software, simply ship it with -O0 to reduce the failure rate. (Thanks @Cor3ntin) #cplusplus #cpp #affectivecpp
Item 72: Stick to using single letter identifiers only, this avoids almost all naming disputes. (Thanks @bjorn_fahller) #cplusplus #cpp #affectivecpp
Item 71: To save memory, re-use function parameters as local variables. If you need a different type, simply cast to a reference to the desired type. (Thanks @RECURSIVE_NMI) #cplusplus #cpp #affectivecpp
For maximum effectiveness it is recommended to reinterpret_cast the results in to the desired memory layout to improve performance #affectivecpp
Item 70: Avoid expensive toupper / tolower functions, use bitwise operators instead. Lowercase: `'A' | ' ' == 'a'`. Uppercase: `'a' & '_' == 'A'`. Switch case: `'A' ^ ' ' == 'a'` (Thanks @ilpropheta) #cplusplus #cpp #affectivecpp
Item 69: Avoid default arguments and complicated lookup, be explicit! Example: Instead of `std::cout << std::endl`, do `std::cout.basic_ostream<char, std::char_traits<char>>::operator<<(std::endl<char, std::char_traits<char>>);` (Thanks @vzverovich) #cplusplus #cpp #affectivecpp
std::cout.basic_ostream<char, std::char_traits<char>>::operator<<(std::endl<char, std::char_traits<char>>);
Item 68: As of C++20, `std::tie` has a new shorthand, the spaceship operator. It was named after Darth Vader's Tie Fighter: `<=>` #cplusplus #cpp #affectivecpp
Item 67: If an exception occurs which turns out to be a false positive, re-throw it as std::bad_exception to let the system know: `catch(std::exception &e) { throw std::bad_exception(e); }` (Thanks @olafurw) #cplusplus #cpp #affectivecpp
If you have any issues with your C++ code, throw a std::future_error. This will allow your future self to deal with the problem Also if there's an exception that is misbehaving then you can always throw a std::bad_exception and the OS will take care of it for you @AffectiveCpp
Further confirmed by this idiom called SFINAE: std::flush Intermittently Normalizes Any Errors ! #affectivecpp #cppsecrets
Further confirmed by this idiom called SFINAE: std::flush Intermittently Normalizes Any Errors ! #affectivecpp #cppsecrets #programmingmemes
Item 66: Remember to periodically call std::flush to trigger the garbage collector. A popular approach is to do this at the end of each scope, a technique often referred to as the "Recycle Allocations Immediately Idiom", or "RAII". #cplusplus #cpp #affectivecpp
Item 66: Remember to periodically call std::flush to trigger the garbage collector. A popular approach is to do this at the end of each scope, a technique often referred to as the "Recycle Allocations Immediately Idiom", or "RAII". #cplusplus #cpp #affectivecpp
Item 65: If you want to ignore a function parameter, simply pass std::ignore as the argument: fnc(3, 4, std::ignore, “whatever”); (Thanks @hankadusikova) #cplusplus #cpp #affectivecpp
Item 64: If you want to move a value, remember to use std::move, but only for the first move. If you want to move it again you need to use std::remove. (Thanks @olafurw) #cplusplus #cpp #affectivecpp
If you want to move a value, remember to use std::move, but only for the first move. If you want to move it again you need to use std::remove @AffectiveCpp
Item33: Use this trick to let the C++ runtime know which function arguments are really required. #cplusplus #cpp #affectivecpp (Thanks, @tmr232)
Item 71: To save memory, re-use function parameters as local variables. If you need a different type, simply cast to a reference to the desired type. (Thanks @RECURSIVE_NMI) #cplusplus #cpp #affectivecpp
Item 31: Make your code more visual and intuitive using Multi-Dimensional Analog Literals eelis.net/C++/analoglite… (Thanks for the tip @AdiShavit) #cplusplus #cpp #affectivecpp
Something went wrong.
Something went wrong.
United States Trends
- 1. Stanford 10.9K posts
- 2. Norvell 4,186 posts
- 3. Florida State 10.1K posts
- 4. #AEWWrestleDream 69K posts
- 5. Sabrina 66.4K posts
- 6. SPENCER SMITH N/A
- 7. #byucpl N/A
- 8. Darby 11.4K posts
- 9. Utah 32.9K posts
- 10. Mizzou 6,276 posts
- 11. Bama 16.6K posts
- 12. Hugh Freeze 3,050 posts
- 13. Lincoln Riley 2,916 posts
- 14. brendon 5,742 posts
- 15. Sperry N/A
- 16. Castellanos 3,764 posts
- 17. Sting 14.9K posts
- 18. Nobody's Son 3,451 posts
- 19. Arch 25.8K posts
- 20. Kentucky 25.1K posts