# saving Published articles for saving. 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. ## Childhood Computing DevFeed: [Childhood Computing]() Original publisher: [Read original article]() Published: 2026-05-24T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [Programming](), [Code](), [ibm](), [pc](), [Open Source]() Tags: [blog-post](), [code](), [computer](), [computing](), [dos](), [graph](), [ibm](), [open-source](), [pc](), [programming](), [saving](), [test]() ### AI overview A personal essay recalls learning programming in a school computer lab in 1992 using IBM PC-compatible machines, MS-DOS, floppy disks, and Logo. Limited computer access led the author to write and test programs on paper, while classmates copied and modified one program in an early informal form of software sharing. ### Source excerpt I recently stumbled upon a nice blog post titled Childhood Computing. It made me think about my own childhood computing experience. I am much older than the author of the aforementioned post, but like them, I too love computers. I have for most of my life. In 1992, when I was eight years old, my parents decided to transfer me to a new school because of its curriculum. They did not know it then, and it probably did not even matter to them, but this new school had a computer lab. That was quite remarkable for its time. I grew up in a very tiny industrial town. The computers in the lab were hand-me-downs from the silica factory around which the town was built. We got only about two hours of time per month in the computer lab, but the little time I got there opened up a whole new world for me. Before entering the lab, we had to leave our shoes at the door. 'These are expensive machines. We must keep them free of dust', our teacher would say. It was a ritual. The computers were very old IBM PC compatible machines, mostly with monochrome cathode-ray tube (CRT) monitors. They had no hard disks at all. They had a few hundred kilobytes of RAM. Every time, we performed the same ritual. Insert a 5¼-inch floppy disk to load MS-DOS into memory. Then insert another disk to load LOGO.COM. Then write small Logo programs and watch the turtle move. I have written more about that early Logo programming experience here: FD 100. Further, since there were no hard disks and storage was at a premium, nothing was ever saved. The moment you turned off the computer, all your work vanished. So saving a program meant literally writing the program down in a physical notebook. Video capture of IBM Personal Computer Logo [MP4] Since I had so little time with an actual computer, most of my Logo programming happened with pen and paper at home. I would 'test' my programs by tracing the results on graph paper. Eventually, I would get about thirty minutes of actual computer time in the lab to run them ## 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 ## Mobile NixOS January 2020 Round-Up: New Stage-1 Init and Planned Early-Boot UI DevFeed: [Mobile NixOS January 2020 Round-Up: New Stage-1 Init and Planned Early-Boot UI]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2020-02-04T00:00:00Z Content type: article Language: en Sources: [Mobile NixOS news]() Topics: [Boot Process](), [USB](), [Mobile]() Tags: [boot-process](), [dependencies](), [implementation](), [logs](), [recovery](), [saving](), [ui](), [usb]() ### AI overview The January 2020 Mobile NixOS update describes a redesigned stage-1 init with USB gadget handling, USB networking, firmware loading, log multiplexing and saving, reboot and poweroff support, and handling for configured special file systems. Its dependency-based design reduced reliance on sleep and wait times and made boot steps quicker. Work was also in progress on a graphical early-boot interface for recovery, generation selection, and eventually entering a passphrase for an encrypted system. ### Source excerpt This update is the third in a series of regular updates on the state of the project. Usually, only changes that have been accepted and merged in Mobile NixOS in the given month are chronicled here. There's always more work currently in-progress. Notable changes Only 1 PR was merged during the month. Though, keep on reading, as one of the biggest PR, started in mid-December, was the main focus of the month. New Stage-1 init This is quite the misnomer, while true, that the PR mainly introduced a completely re-done init, it brought much more. "New-style" USB gadget (gadgetfs) handling. USB Networking for newer devices. Vendor partition firmware loading. Logs multiplexing and saving in stage-1. Proper reboot and poweroff in stage-1. Actual handling of NixOS-configured specialFileSystems. This new init is built using a dependencies-based system, reducing the complexities from the inflexible "big script" approach of the previous init. With this new approach, we can simply dump all of the things we need to happen in the init, tell them how they're linked, and boot. The current implementation is naïve, but even with a naïve approach, the benefits are apparent. First, the developer does not need to care about the ordering of things, only describing what has to be, and what to do. Then, the relatively surprising part: this made things a bit quicker to boot. This reduced reliance on sleep and wait times during the boot to provide assurance that things were ready, meaning that steps happen much quicker in succession. To the annoyance of the author, this means that the well-choreographed boot images whizz by too quickly, reducing their meaningfulness. In the end, this is a hidden change, that serves mainly to ensure a rock-solid foundation for what's coming soon. See the PR for more details. Upcoming changes Speaking of coming soon, As previewed in a tweet, work is in progress to provide a graphical interface that can be used in early boot. This can be used to make a "recovery" ## 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. ## Using VueJS + GraphQL to make Practical Magic DevFeed: [Using VueJS + GraphQL to make Practical Magic]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-08-27T22:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [GraphQL](), [vuejs](), [Content Management System](), [Front end](), [JavaScript](), [axios](), [Bootstrap](), [Jamstack]() Tags: [auto-complete](), [axios](), [bootstrap](), [craft](), [everyday](), [form](), [graphql](), [headless](), [insights](), [jamstack](), [javascript](), [like](), [magic](), [practical](), [problems](), [saving](), [searching](), [solve](), [submission](), [using](), [vuejs]() ### AI overview A practical tutorial showing how to use VueJS and GraphQL with a headless Craft CMS backend to implement auto-complete search and save contact-form submissions. It introduces the frontend and backend tooling used in the examples, including Axios, Bootstrap 4, Craft CMS, and CraftQL. ### Source excerpt Make some practical magic with VueJS + GraphQL to solve everyday problems like auto-complete searching and form submission saving with a headless Craft CMS server ## Saving your time: how to work with large reference databases on WP7 DevFeed: [Saving your time: how to work with large reference databases on WP7]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2011-11-16T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [Development](), [Batch file](), [Script](), [debugging](), [configuration](), [Visual Studio]() Tags: [batch](), [configuration](), [databases](), [debugging](), [development](), [how-to](), [saving](), [script](), [sql-server]() ### AI overview This tutorial explains how to speed up development deployments of a large read-only SQL Server CE reference database on Windows Phone 7. It compares isolated storage with packaging the database in the XAP file, then presents a batch-script approach for uploading the database to an emulator and configuring different debug and release behaviors. ### Source excerpt In the previous post I showed how to load the large SQL Server CE database on WP7. However, if you are working with a read-only reference database, deploying it to the phone or emulator may take up to several minutes. In this post I will try to explain how to save your nerves and time, making the regular development and debugging easier. So for now, there are 2 options for deploying the database with your app: Use Isolated Storage. Upload the database to the device with the help of ISETool. For ~50 mb database it takes 4 minutes on my laptop. Pack it as the application content (setting Build Action to Content). In that case, the database is packed into the XAP file on your machine and then unpacked back on the device. While this approach is a bit faster then the first one, it still takes something about 1 minute to deploy your app, which I find unacceptable. Note that the 1st option should be used only for Debug configurations. The only way to include the reference database when delivering the app to the users is by packing it into the XAP (you may, however, copy it to Isolated Storage upon the first launch, but I don't see any sense why should you do so). So I can't fasten the packaging process, but I can upload my database to the Isolated Storage once and it will be preserved between the application deploys when debugging. When I need to release the application build, I will include the database to XAP file content. Sounds easy. Being lazy motivates me to script the uploading routine. Here is a batch file that takes the IS snapshot with ISETool, adds the database file and restores the snapshot on the emulator: set isePath="C:Program Files (x86)Microsoft SDKsWindows Phonev7.1ToolsIsolatedStorageExplorerToolISETool.exe" set tempPath="C:TempDatabaseIS" set dbPath="your_db_path" set appId=your_app_id %isePath% ts de %appId% %tempPath% copy %dbPath% %tempPath% %isePath% rs de %appId% %tempPath% In the snippet above you need to replace your_db_path with the path to your