Went to google some minor C++ thing and for some reason Gemini felt compelled to dump a ton of info, including this:
![A screenshot of a Google Gemini output, reading:
Example: Resizing a dynamic array safely with std::vector
cpp
#include <vector>
void processData(int size) {
// 1. Create temporary vector workspace
std::vector<int> tempBuffer(size, 0);
// 2. Perform manipulations
tempBuffer[0] = 42;
// 3. No manual cleanup required!
// Memory is freed automatically when tempBuffer goes out of scope
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:vp3afnjczy6vpv4yhalic3mh/bafkreib6f7pt4vgdcuw6bqqbasivsndt7t56uoffpzdnp7mchlmfl3bfni)
September 14, 2026 at 10:21 PM
Went to google some minor C++ thing and for some reason Gemini felt compelled to dump a ton of info, including this:
🔥 AI thay đổi ngành giải trí Việt: Lợi ích hay rủi ro?
#24hHotNewsAI #VNNews
#24hHotNewsAI #VNNews
AI thay đổi ngành giải trí Việt: Lợi ích hay rủi ro?
Sự kiện "Gặp gỡ processData" tại Nhà hát Lớn Hà Nội ngày 25/7/2026 đánh dấu mốc giới hạn công nghệ khi AI được tích hợp toàn diện vào sản xuất nghệ thuật, giúp giảm 40% chi phí và nâng cao trải nghiệm khán giả thông qua phản ứng thời gian thực.
https://24hhotnewsai.com/vn/news/ai-thay-đổi-ngành-giải-trí-việt-lợi-ích-hay-rủi-ro-202607261451
July 26, 2026 at 7:52 AM
🔥 AI thay đổi ngành giải trí Việt: Lợi ích hay rủi ro?
#24hHotNewsAI #VNNews
#24hHotNewsAI #VNNews
3. Names should describe the why, not the how
🔴 processData(), handleEvent(), runStripeWebhook().
→ ✅ chargeCustomer() survives three refactors. runStripeWebhook() breaks the day you switch billing providers.
Implementation changes constantly. Intent almost never does.
🔴 processData(), handleEvent(), runStripeWebhook().
→ ✅ chargeCustomer() survives three refactors. runStripeWebhook() breaks the day you switch billing providers.
Implementation changes constantly. Intent almost never does.
July 8, 2026 at 3:26 PM
3. Names should describe the why, not the how
🔴 processData(), handleEvent(), runStripeWebhook().
→ ✅ chargeCustomer() survives three refactors. runStripeWebhook() breaks the day you switch billing providers.
Implementation changes constantly. Intent almost never does.
🔴 processData(), handleEvent(), runStripeWebhook().
→ ✅ chargeCustomer() survives three refactors. runStripeWebhook() breaks the day you switch billing providers.
Implementation changes constantly. Intent almost never does.
3/
You open an old module to add a feature. Inside: a 200-line processData(), stale TODOs, commented-out code.
You could add your feature and leave.
The rule says improve one thing while you're there.
You open an old module to add a feature. Inside: a 200-line processData(), stale TODOs, commented-out code.
You could add your feature and leave.
The rule says improve one thing while you're there.
June 10, 2026 at 6:27 AM
3/
You open an old module to add a feature. Inside: a 200-line processData(), stale TODOs, commented-out code.
You could add your feature and leave.
The rule says improve one thing while you're there.
You open an old module to add a feature. Inside: a 200-line processData(), stale TODOs, commented-out code.
You could add your feature and leave.
The rule says improve one thing while you're there.
naming is hard because it forces you to understand what something actually does before you can describe it.
a function called processData probably doesn't have a clear purpose yet. a function called validateUserEmailAndSendConfirmation does.
struggling to name it is the smell. not the problem.
a function called processData probably doesn't have a clear purpose yet. a function called validateUserEmailAndSendConfirmation does.
struggling to name it is the smell. not the problem.
May 19, 2026 at 10:48 PM
naming is hard because it forces you to understand what something actually does before you can describe it.
a function called processData probably doesn't have a clear purpose yet. a function called validateUserEmailAndSendConfirmation does.
struggling to name it is the smell. not the problem.
a function called processData probably doesn't have a clear purpose yet. a function called validateUserEmailAndSendConfirmation does.
struggling to name it is the smell. not the problem.
Bad naming is the only technical debt that survives every refactor. You can rewrite the logic. You can replace the framework. But a function called processData or doTheThing gets copied into the next system and the one after that. Names travel.
May 19, 2026 at 3:39 PM
Bad naming is the only technical debt that survives every refactor. You can rewrite the logic. You can replace the framework. But a function called processData or doTheThing gets copied into the next system and the one after that. Names travel.
Six months ago me wrote a function with zero comments and a name like 'processData'. Current me has spent 40 minutes reverse-engineering what past me was thinking. We are not the same person.
May 19, 2026 at 11:44 AM
Six months ago me wrote a function with zero comments and a name like 'processData'. Current me has spent 40 minutes reverse-engineering what past me was thinking. We are not the same person.
Sure, but for the specific case of DXC/HLSL 2021 you can rely on it to branch because that's the spec'd behavior. Someone else pointed out to me that your example doesn't branch simply because it's going through a rather old version of DXC that doesn't default to HLSL 2021.
godbolt.org/z/qnEYYKqfK
godbolt.org/z/qnEYYKqfK
Compiler Explorer - HLSL (RGA 2.6.2 (DXC trunk))
Buffer<float> someData;
RWBuffer<float> output;
//random function that does some work
float ProcessData(uint2 coords)
{
float result = someData[coords.x] + someData[coords.y];
result = pow(re...
godbolt.org
March 22, 2026 at 6:02 PM
Sure, but for the specific case of DXC/HLSL 2021 you can rely on it to branch because that's the spec'd behavior. Someone else pointed out to me that your example doesn't branch simply because it's going through a rather old version of DXC that doesn't default to HLSL 2021.
godbolt.org/z/qnEYYKqfK
godbolt.org/z/qnEYYKqfK
Avoid using ternary operations on methods, eg i>0? foo(x):foo(y), as the compiler may calculate both sides and select the output instead of adding a branch. Use the ternary on the inputs if possible or add an actual branch: godbolt.org/z/5Efr7qaP7. Worth considering in shadergraphs as well.
Compiler Explorer - HLSL (RGA 2.6.2 (DXC 1.7.2207))
Buffer<float> someData;
RWBuffer<float> output;
//random function that does some work
float ProcessData(uint2 coords)
{
float result = someData[coords.x] + someData[coords.y];
result = pow(re...
godbolt.org
March 21, 2026 at 6:42 PM
Avoid using ternary operations on methods, eg i>0? foo(x):foo(y), as the compiler may calculate both sides and select the output instead of adding a branch. Use the ternary on the inputs if possible or add an actual branch: godbolt.org/z/5Efr7qaP7. Worth considering in shadergraphs as well.
Hat jemand "KTW-C" gesagt...?
December 5, 2025 at 6:09 AM
Hat jemand "KTW-C" gesagt...?
🔵 🟢 New Article—As #digitalisation permeates all areas of life, the race to #processdata as quickly as possible is in full swing—but it comes with #consequences. We interviewed Ralph Hintemann about #datacentersustainability 👇
“Data Centres Will Account for the Majority of Digitalisation’s CO2 Emissions”: An Interview With Ralph Hintemann (Borderstep Institute)
Data centre energy consumption is already high—thanks to AI, it’s set to skyrocket. We talked to Dr Ralph Hintemann about potential solutions.
en.reset.org
June 10, 2025 at 10:30 AM
🔵 🟢 New Article—As #digitalisation permeates all areas of life, the race to #processdata as quickly as possible is in full swing—but it comes with #consequences. We interviewed Ralph Hintemann about #datacentersustainability 👇
🔵 🟢 New article 🚀 Why do #publicauthorities struggle to #processdata? Read how the Data Governance Guide is helping make cities smarter bit.ly/45qP8DC
Supported by @umweltstiftung.bsky.social
#SmartCities #OpenData #DataGovernance #datatools
Supported by @umweltstiftung.bsky.social
#SmartCities #OpenData #DataGovernance #datatools
The Data Governance Guide Helps Public Authorities Overcome “A Fragmented Data Landscape” To Make the Most of Digital Data
Too many digital projects don't make the most of data's potential. The new Data Governance Guide is here to help.
en.reset.org
May 27, 2025 at 10:30 AM
🔵 🟢 New article 🚀 Why do #publicauthorities struggle to #processdata? Read how the Data Governance Guide is helping make cities smarter bit.ly/45qP8DC
Supported by @umweltstiftung.bsky.social
#SmartCities #OpenData #DataGovernance #datatools
Supported by @umweltstiftung.bsky.social
#SmartCities #OpenData #DataGovernance #datatools
Avoid misleading names. list shouldn’t be a map. processData() shouldn’t log to a database. Name things correctly. #CodeQuality #CleanCode
March 8, 2025 at 3:02 PM
Avoid misleading names. list shouldn’t be a map. processData() shouldn’t log to a database. Name things correctly. #CodeQuality #CleanCode
Project: golang/go
File: src/net/http/h2_bundle.go:5634
func (sc *http2serverConn) processData(f *http2DataFrame) error
SVG: dark, light
File: src/net/http/h2_bundle.go:5634
func (sc *http2serverConn) processData(f *http2DataFrame) error
SVG: dark, light
February 12, 2025 at 1:37 PM
Project: golang/go
File: src/net/http/h2_bundle.go:5634
func (sc *http2serverConn) processData(f *http2DataFrame) error
SVG: dark, light
File: src/net/http/h2_bundle.go:5634
func (sc *http2serverConn) processData(f *http2DataFrame) error
SVG: dark, light
In a recent article in EM:IP, Liu et al. evaluate the impact of rescoring computer-based case simulations after shortening their allotted time limit. Results are found to vary based on the cases’ characteristics.
Learn more: doi.org/10.1111/emip...
#ProcessData
Learn more: doi.org/10.1111/emip...
#ProcessData
Using Process Data to Evaluate the Impact of Shortening Allotted Case Time in a Simulation‐Based Assessment
The Computer-based Case Simulations (CCS) component of the United States Medical Licensing Examination (USMLE) Step 3 was developed to assess the decision-making and patient-management skills of phys....
doi.org
December 26, 2024 at 2:09 PM
In a recent article in EM:IP, Liu et al. evaluate the impact of rescoring computer-based case simulations after shortening their allotted time limit. Results are found to vary based on the cases’ characteristics.
Learn more: doi.org/10.1111/emip...
#ProcessData
Learn more: doi.org/10.1111/emip...
#ProcessData
Sort of want to be able to do `useHook { const q = useQuery(...); return { massagedPromise: q.promise.then(processData) }` but I don't think this is allowed due to unstable promise? Maybe if I useMemo this it will be fine? Need to learn more about this.
December 8, 2024 at 12:42 AM
Sort of want to be able to do `useHook { const q = useQuery(...); return { massagedPromise: q.promise.then(processData) }` but I don't think this is allowed due to unstable promise? Maybe if I useMemo this it will be fine? Need to learn more about this.