# saving In computing, saving is the action of storing data or files on a storage device for future access or use. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Tips for Saving Game Data in Godot DevFeed: [Tips for Saving Game Data in Godot]() Original publisher: [Read original article]() Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Godot](), [saving](), [Concurrent Programming](), [data](), [JSON](), [Hardware](), [Testing]() Tags: [bug](), [code](), [disk-space](), [game](), [games](), [json](), [mutex](), [os](), [saving](), [testing](), [thread](), [tips]() ### AI overview This tutorial describes a save-data approach for Godot games, based on experience shipping two games. It compares custom binary and JSON formats, recommends frequent debounced saves on a separate thread, checks available disk space, and discusses temporary-file replacement to reduce corrupted save-game reports. ### Source excerpt Saving game data is easy. Making your save code survive every kind of hardware failure is not. A lot of these issues will never show up during testing, but if your game reaches a wide audience with many different kinds of hard drives in different states of degradation, you will start to get bug reports about save games not working. I decided to write up my approach, learned over the course of shipping two Godot games, that has reduced our corrupted save game bug reports to virtually nothing. ## Big Tech's Money Paradox DevFeed: [Big Tech's Money Paradox]() Original publisher: [Read original article]() Author: Evan King Published: 2024-12-09T22:10:13Z Content type: opinion Language: en Sources: [Evan King]() Topics: [saving](), [Software]() Tags: [money](), [saving](), [tech]() ### AI overview An opinion essay argues that highly paid Big Tech engineers can become excessively focused on saving and optimizing investments, at the expense of happiness and relationships. Drawing on personal observations and a cited view from Arthur Brooks, it recommends balancing financial security with spending on shared experiences. ### Source excerpt Big Tech engineers making hundreds of thousands of dollars a year are the world's most anxious penny pinchers. I saw it every weekend while living in Seattle: software engineers making half a million dollars arguing over dinner bills down to the cent, cramming into someone's car to save $5 on an Uber, and pre-gaming at home to avoid $15 cocktails. All while making more money than we knew what to do with. It took moving to LA to realize just how weird this behavior is. Here, I've made friends outside the tech bubble -- people making significantly less than my Seattle circle, yet somehow living much richer lives. They grab the check without hesitation. Spring for concert tickets on a whim. Generally seem to enjoy their money rather than hoarding it like dragons guarding their gold. The contrast was jarring. In Seattle, we'd spend hours fine-tuning our investment strategies and debating the optimal savings rate. Every dollar spent was a dollar that could be invested, and we could calculate exactly how much we expected that dollar would be worth in 30 years. The engineer's mindset applied to lifestyle choices -- and it was making us miserable. I get it. We're analytical by nature. Tech attracts people who love watching numbers go up and to the right. But we're optimizing for the wrong variable. The proof is right there on Blind. Some of the unhappiest posts come from people making $1M/y who are stressed about not saving enough. They've solved the money problem but lost sight of the happiness equation. Arthur Brooks, a Harvard professor who studies the science of happiness, was asked a simple question: does money buy happiness? His answer was surprising. "Yes," he said. But it came with a crucial caveat: "yes, if that money is spent on experiences with the people you love." On the other hand, he found those hoarding money, regardless of how wealthy they were, were almost always the least happy. Here's what I've learned since leaving the tech bubble: investing in experience ## Crash Course on the Android UI Layer | Part 2 DevFeed: [Crash Course on the Android UI Layer | Part 2]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2023-12-19T00:00:00Z Content type: article Language: en Sources: [Manuel Vivo .dev]() Topics: [Android](), [ui](), [saving](), [business logic](), [screen]() Tags: [android](), [architecture](), [best-practices](), [blog-post](), [business-logic](), [saving](), [screen](), [state](), [ui]() ### AI overview Part 2 of a series on the Android UI layer explains state holders, state hoisting, saving UI state, and the distinction between business logic and UI logic. It also discusses how UI logic responds to different device configurations, such as phones and tablets. ### Source excerpt Part 2 - State Holders and Saving State ## Managing State and Persistence with remember() in Jetpack Compose DevFeed: [Managing State and Persistence with remember() in Jetpack Compose]() Original publisher: [Read original article]() Published: 2022-01-12T19:41:23Z Content type: article Language: en Sources: [Colin The Shots]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Persistence](), [ui](), [saving](), [Kotlin]() Tags: [android](), [compose](), [jetpack-compose](), [kotlin](), [persistence](), [remembersaveable](), [rotation](), [saving](), [stateless]() ### AI overview This article explains how to use remember() in Jetpack Compose and when to choose rememberSaveable() or persistent storage. It recommends remembering only essential data, using rememberSaveable() for state that must survive rotation, and persisting larger or longer-lived data through a ViewModel. ### Source excerpt During the first Kotlinconf in 2017, I asked Google for some kind of declarative user interface (UI) framework for Android. Specifically, I approached Stephanie Cuthbertson and Yigit Boyar at that ## A Deep Dive into Extensible State Saving DevFeed: [A Deep Dive into Extensible State Saving]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-03-19T20:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [saving](), [Code]() Tags: [android](), [code](), [kotlin](), [marton-braun](), [saving](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This article explains how extensible state saving is implemented in AndroidX libraries and how ViewModel state saving connects to the system. It examines SavedStateRegistry, registered state providers, unique provider keys, saving state into a Bundle, and restoring provider data on request. ### Source excerpt A perhaps overly thorough look at how extensible state saving is implemented in the AndroidX libraries, and how ViewModel state saving specifically is hooked into this system. ## Hostage Negotiation 101 DevFeed: [Hostage Negotiation 101]() Original publisher: [Read original article]() Author: Graham King Published: 2011-09-18T20:24:18Z Content type: opinion Language: en Sources: [Graham King]() Topics: [trust](), [saving]() Tags: [behaviour](), [book](), [friendly](), [negotiation](), [society](), [strategy](), [things](), [time](), [trust]() ### AI overview A summary of Gary Noesner's memoir about hostage negotiation, covering peaceful surrender, exclusive communication, environmental control, calm listening, organizing demands, and building trust. ### Source excerpt Negotiating lives: Insights from an FBI hostage negotiator's memoir.