#variable — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #variable, aggregated by home.social.
-
Toshiba wins 200-MW Kyogoku pumped-storage order in Hokkaido
KEY POINTSToshiba wins Hokkaido Electric Power order for a 200-MW variable-speed pumped-storage system at Kyogoku Plant Unit 3Variable-speed design enables m…
#Japan #JP #Hokkaido #gridstability #HokkaidoElectricPower #HokkaidoNews #KyogokuPowerPlant #news #pumped-storagehydropower #RenewableEnergy #Toshiba #variable-speedpumped-storage #北海道
https://www.alojapan.com/1514633/toshiba-wins-200-mw-kyogoku-pumped-storage-order-in-hokkaido/ -
The LD_DEBUG environment variable (2012)
https://bnikolic.co.uk/blog/linux-ld-debug.html
#HackerNews #LD_DEBUG #Linux #Environment #Variable #Debugging #2012 #Blog #Post
-
The LD_DEBUG environment variable (2012)
https://bnikolic.co.uk/blog/linux-ld-debug.html
#HackerNews #LD_DEBUG #Linux #Environment #Variable #Debugging #2012 #Blog #Post
-
#NORTH #AFRICAN #OSTRICH advanced-search.allgraph.ro/advanced-sea... #ERNST #BARLACH #HOUSE headlines-world.com?lang=en&q=ER... #COLONY 2026 #FILM semantic-search.aepiot.com/advanced-sea... #STATE #VARIABLE #FILTER multi-search-tag-explorer.allgraph.ro/advanced-sea... headlines-world.com
MultiSearch Tag Explorer -
Easy Nonogram 15x15 - How Fast Can You Solve? #100
🧩 Nonogram Puzzle Medium 15x15 Grid | Easy Difficulty
Watch as we solve this challenging #nonogram puzzle step by step! This 15x15 grid puzzle is perfect for easy Puzzle solvers.
📊 Puzzle Details:
• Grid Size: 15x15
• Difficulty: Easy
• Category: Medium Nonogram#nonogram #picross #griddler #puzzle #brainteaser #logicpuzzle #variable #variables #variablenonogram #nonogramvariable
-
iPhone 18 Camera Rumors: A Major Telephoto Upgrade?
TentorTech reports on a surprising new rumor regarding the upcoming iPhone 18's camera system. A source, not typically linked to Apple leaks, suggests the Pro models may feature a variable aperture telephoto lens. This technology would give photographers significantly more control over depth of field directly from the optical hardware. Additionally,...
#iPhone 18 #Apple rumors #smartphone camera #telephoto lens #variable aperture #TentorTech
-
Un article qui colle bien avec un thème d'une conférence que je vais donner la semaine prochaine à Snowcamp https://jeffbailey.us/blog/2025/12/31/fundamentals-of-naming/ #programming #nommage #variable #méthode
-
Un article qui colle bien avec un thème d'une conférence que je vais donner la semaine prochaine à Snowcamp https://jeffbailey.us/blog/2025/12/31/fundamentals-of-naming/ #programming #nommage #variable #méthode
-
A #Variable #Star is a star whose brightness changes over time, either because its luminosity genuinely fluctuates or because something is periodically blocking its light.
These changes can be caused by internal processes like pulsation or external factors such as being eclipsed by a companion star.
-
A #Variable #Star is a star whose brightness changes over time, either because its luminosity genuinely fluctuates or because something is periodically blocking its light.
These changes can be caused by internal processes like pulsation or external factors such as being eclipsed by a companion star.
-
#Strom wird wieder günstig? – #Naturstrom Chef über #dynamische #Tarife & den neuen #Strommarkt:
Wie funktioniert der neue Strommarkt – und wie können wir alle davon profitieren?
Im Gespräch mit Oliver Hummel, #CEO von #Naturstrom, geht es um #dynamische #Stromtarife, #variable #Netzentgelte und die Frage, wie Bürger*innen aktiv zur #Energiewende beitragen können. -
#Strom wird wieder günstig? – #Naturstrom Chef über #dynamische #Tarife & den neuen #Strommarkt:
Wie funktioniert der neue Strommarkt – und wie können wir alle davon profitieren?
Im Gespräch mit Oliver Hummel, #CEO von #Naturstrom, geht es um #dynamische #Stromtarife, #variable #Netzentgelte und die Frage, wie Bürger*innen aktiv zur #Energiewende beitragen können. -
Basic Coding
#Scratch
#Dragon
#Animation
#Coding
#Programming
#Beginner #VariableSame as before, only this time we are using a variable to store the time we are waiting for.
This saves having to change all the numbers, just change the variable value.
-
[A complex #MagneticField detected on the surface of the star #vega ] Observations made using the SOPHIE spectrograph at the Haute Provence Observatory, and spectropolarimetry with the Narval and Neo-Narval instruments at the Bernard Lyot Telescope at the Pic du Midi Observatory, have enabled IRAP researchers to detect the coexistence, on the surface of the star Vega, of a complex magnetic field : one described as #fossil, the second as #variable : https://www.irap.omp.eu/en/2025/10/detection-of-a-complex-magnetic-field-on-thesurface-of-the-intermediate-mass-star-vega/
-
[A complex #MagneticField detected on the surface of the star #vega ] Observations made using the SOPHIE spectrograph at the Haute Provence Observatory, and spectropolarimetry with the Narval and Neo-Narval instruments at the Bernard Lyot Telescope at the Pic du Midi Observatory, have enabled IRAP researchers to detect the coexistence, on the surface of the star Vega, of a complex magnetic field : one described as #fossil, the second as #variable : https://www.irap.omp.eu/en/2025/10/detection-of-a-complex-magnetic-field-on-thesurface-of-the-intermediate-mass-star-vega/
-
[Un #ChampMagnétique complexe à la surface de l'étoile #Véga] Des observations réalisées au moyen du spectrographe #SOPHIE de l'Observatoire de Haute Provence, et en spectropolarimétrie avec les instruments #Narval puis Neo-Narval au Télescope Bernard Lyot de l’Observatoire du Pic du Midi, ont permis à des chercheurs de l'IRAP de détecter la coexistence, à la surface de l'étoile Véga, de deux champs magnétiques : l'un qualifié de #fossile, le second de #variable : https://www.irap.omp.eu/2025/10/detection-dun-champ-magnetique-complexe-sur-la-surface-de-letoile-de-masse-intermediaire-vega/
-
[Un #ChampMagnétique complexe à la surface de l'étoile #Véga] Des observations réalisées au moyen du spectrographe #SOPHIE de l'Observatoire de Haute Provence, et en spectropolarimétrie avec les instruments #Narval puis Neo-Narval au Télescope Bernard Lyot de l’Observatoire du Pic du Midi, ont permis à des chercheurs de l'IRAP de détecter la coexistence, à la surface de l'étoile Véga, de deux champs magnétiques : l'un qualifié de #fossile, le second de #variable : https://www.irap.omp.eu/2025/10/detection-dun-champ-magnetique-complexe-sur-la-surface-de-letoile-de-masse-intermediaire-vega/
-
🌊 Wave text #animation for #variable #fonts, with #kerning intact! JS by Simon Truffer @simontruffer
-
We present Deforming MeshFonts! Gothic Sans Bevel is the first of our fonts that is implementing deformation, from light to bold and back!
-
-
-
#Wayle is a sans serif #typeface designed by Adrien Midzic and released by Pizza Typefaces. Inspired by classic lineal #fonts, Wayle adds a subtle flair that sets it apart. It is also available as a #variable font. Focused on readability and modernism, it brings just the right amount of whale-sized charm to your #typography.
https://typefaces.pizza/type/wayle
#sansserif #typedesign #fontdesign #variablefont #pizzatypefaces #adrienmidzic #certainmagazine
-
Quelques images de notre workshop de la semaine « Poésie générative, programmation et fontes variables » à l’ésal Metz avec Jérôme Knebush.
#typo #variable #poesie #programmation #web #print #workshop #generativeart #generative
-
帶有 make help 說明的 Makefile
在 Lobsters 上看到「Self-documenting Makefiles」這篇裡面提到怎麼設計 make help 的方法，還蠻不錯的。
他的想法是讓 make help 去讀 Makefile 自己內容，把註解 # 後面的文字拉出來，產生出一包 help document，這邊拿他最後的成品來看：
.PHONY: help
help: # Shows interactive help.
@cat README.md
@echo
#Computer #Murmuring #Programming #Software #doc #document #help #make #makefile #target #variable
-
帶有 make help 說明的 Makefile
在 Lobsters 上看到「Self-documenting Makefiles」這篇裡面提到怎麼設計 make help 的方法，還蠻不錯的。
他的想法是讓 make help 去讀 Makefile 自己內容，把註解 # 後面的文字拉出來，產生出一包 help document，這邊拿他最後的成品來看：
.PHONY: help
help: # Shows interactive help.
@cat README.md
@echo
#Computer #Murmuring #Programming #Software #doc #document #help #make #makefile #target #variable
-
Can You Use DML or SOQL Inside the Loop?
A loop in Salesforce Flow is performed using a loop element that allows you to iterate through a collection of records or items. It is essential for performing actions or calculations on multiple items in a list, such as a group of related records or a set of inputs. This process often involves DML (Data Manipulation Language) and SOQL (Salesforce Object Query Language) to manage data and queries efficiently. Loops are critical in scenarios where you need to update statuses, send notifications, or apply changes across numerous records. To maintain performance and adhere to Salesforce governor limits, best practices recommend placing DML and SOQL operations outside the loop to minimize system load and maximize efficiency.
Key Components of a Loop:
- Collection Variable: The loop requires a collection variable that holds the records or items to iterate over. This could be a list of contacts, opportunities, or custom objects retrieved from a Salesforce query or manually created.
- Loop Variable: During each iteration, the loop assigns the current item in the collection to a single variable (often called a “current item” variable), allowing you to work with that individual record or item.
- Loop Path: The actions or logic to execute for each item in the collection are defined within the loop’s path. For example, you might update a field, perform calculations, or send an email for each record.
- Direction: Loops can iterate through the collection either from the first item to the last or in reverse order.
You retrieve a collection of open cases for a specific account and use a loop to: Update the status of each case to a different value, such as “In Progress” and “Working.”
Send an email notification to the case owner.
While there are situations where you may need to break the rule, DMLs and SOQLs (Create, Update, Delete, and Get) should be placed outside the loop.
What is the reason for this?
What are DMLs and SOQLs?
In Salesforce, DML (Data Manipulation Language) refers to operations that create, update, delete, or retrieve records in the database. These actions include Insert, Update, Delete, Upsert (Apex), Merge (Apex), and Undelete (Apex). DML operations allow you to interact with Salesforce objects (like Accounts, Contacts, Opportunities, or custom objects) to manage data programmatically using Apex code or declaratively through tools like Flows. They are subject to Salesforce governor limits, such as a maximum of 150 DML statements per transaction, which ensures system performance and scalability in multi-tenant environments. Proper handling of DML operations is critical for ensuring performance and avoiding errors like exceeding limits or creating orphaned records.
SOQL (Salesforce Object Query Language) is a query language in Salesforce used to retrieve data from Salesforce objects and related records. It is similar to SQL but specifically designed for Salesforce’s object-oriented database structure. SOQL enables users to select fields, filter records, and sort results, supporting powerful data retrieval through queries like SELECT Name, Id FROM Account WHERE Industry = ‘Technology’. It is used in Apex code, Visualforce, and Lightning components, as well as tools like Developer Console or Workbench. SOQL is subject to governor limits, such as a maximum of 100 queries per transaction, emphasizing the need for efficient query design in Salesforce development. The Salesforce Flow Get element, despite lacking some of the powers of SOQL statements in code, consumes one SOQL execution against the governors limit.
The Issue With Flow Loops
The problem with loops in flow is that you don’t know how many times it will iterate. Today you may have a maximum of 5 cases per account, in the future when the business grows and you start accumulating more history, you may have 200. If you want to ensure your flow design is resilient into the future, you should consider keeping your DMLs and queries (SOQLs) outside the loop.
Execution Governor’s Limits tell us that you can only perform a maximum of 100 SOQLs, and 150 DMLs in a Salesforce transaction. When dealing with a record-triggered flow, these limits apply to the Salesforce transaction as a whole. In other words, your transaction may include items listed on the 20 steps listed on this Order of Execution reference page. If you don’t want to cause errors, you should stay well below these limits in a single record-triggered flow.
That requires that you keep the create, update, delete and get elements outside your loop. Because if you put one get inside your loop and you iterate 101 times, you will receive the famous 101 SOQLs Salesforce error.
Best Practice Design
As stated above, the loop element in Salesforce Flow requires a collection as input. This collection can be a collection of any type, such as text or number, but it is often a record variable.
Remember: A variable is a container that temporarily holds values for us inside our flow. We use these values for further processing.
Let me explain the best recommendation design using the collection record variable as an example. The principle is the same for any type of loop collection. Let’s say we want to update several field values on individual cases in a collection.
How do we defer our DML and SOQL operations until we are done with looping. We need to use a container to hold the modified values, and perform our update outside the loop. To achieve this, do the following:
- Create a record collection variable: For this example, you need to create a new resource; a case collection record variable for your modified case field values (output).
- Loop your input case collection variable (this collection typically comes from a get element)
- Modify the field values for the current case in the collection using an assignment inside the loop.
- Add the current case in the loop record variable to the output case collection variable. This item in the collection holds the modified case record values now.
- Add an update element after your loop (outside). Point your update element to the output case collection variable. This update will perform all changes to the database in one single shot.
How many updates (DMLs) did this design use? Only one. It does not matter whether your loop iterates 10, 200 or 1,000 times. This design will only use one DML against your allotment of 100 per transaction.
The Exceptions
There are certain scenarios where you can break this rule. You become an expert by learning the rules, and then learning when and how to break the rules. You should still follow the best practice when you can.
A few scenarios where this rule can be ignored:
- You have the user modify records that they select from a list in a screen flow. The list is designed to show a max of 10 items.
- Your get element produces your input collection. The get element is set to retrieve a max of 10 items (new functionality).
- You have a scenario where the number of iterations are expected to be low. You introduce a decision and a counter inside your flow, and ensure that the iterations can not go over a certain number, for example 10.
- You are dealing with an action that involves a DML or SOQL, but it does not accept a collection as input. In this scenario, you should still limit the iterations with the use of a counter.
Performance Implications
Remember that regardless of the scenario, a single DML or SOQL are still faster than multiple. If you want to optimize your design for speed and performance, always try to complete your transaction in less number of DMLs and SOQLs.
Please comment and add your questions below.
Read other posts in this series, plus related content:
Salesforce Flow Best Practices
Can You After-Save When You Can Before-Save?
Transform Element and HTTP Callout for Random Test Data
#Collection #DML #Loop #Record #Salesforce #SOQL #useCase #Variable
-
“Web font file size study: a variable font addition” by @stoyan
🔗 https://www.phpied.com/web-font-file-size-study-a-variable-font-addition/
> The sum is smaller than the parts. A variable font that has both normal and heavy (bold) weight (and also everything in between) is slightly smaller than two regular fonts.
⚓️ https://nicolas-hoizey.com/links/2024/10/29/web-font-file-size-study-a-variable-font-addition/
-
“Web font file size study: a variable font addition” by @stoyan
🔗 https://www.phpied.com/web-font-file-size-study-a-variable-font-addition/
> The sum is smaller than the parts. A variable font that has both normal and heavy (bold) weight (and also everything in between) is slightly smaller than two regular fonts.
⚓️ https://nicolas-hoizey.com/links/2024/10/29/web-font-file-size-study-a-variable-font-addition/
-
Flow Naming Convention Tips
Establishing a clear and effective naming convention for your flow resources in Salesforce is a crucial step in optimizing your low-code logic. Thoughtful naming practices not only enhance readability but also simplify resource management within the toolbox and improve the functionality of autogenerated API names. Whether you prefer CamelCase, abbreviations, or full-length descriptors, consistency is key. This article explores practical tips for naming resources, offering insights to help you maintain an organized and user-friendly approach.
Flow Resource Naming Convention Tips
1️⃣ Include Resource Types in Names (for Search)
If you rely on the toolbox’s search functionality, it may be helpful to include the resource type in the name. For example, I avoid abbreviations and use descriptive names like
YesChoiceorReasonPicklistChoice, which clearly indicate the type and purpose.2️⃣ Leverage Resource Manager Grouping
When scrolling through the resource manager, resources are grouped by type in their respective sections. But if you want to leverage search, you may want to include the relevant strings in the name such as
ChoiceorVariable.3️⃣ Sort by Purpose Instead of Type
Personally, I find it more useful to organize resources by their purpose rather than type. For instance, I avoid using prefixes like “Var” at the beginning of a name. Instead, I append the resource type to the name, resulting in labels like
LabelPicklistChoiceandLabelOtherTextVariable.4️⃣ Maximize Autogenerated API Names
Autogenerated API names benefit from clear, consistent labels. Don’t change the autogenerated API names unless you really have to. When dealing with deployments and debugging functionality, API names should lead you directly to the resource names used on Salesforce’s UI.
5️⃣ Abbreviations: Use Sparingly and Consistently
While abbreviations can save space (e.g., using
Varfor “Variable”), long names are often clearer, especially if you struggle with consistent abbreviation usage. Keep in mind that overly long names might get cut off on certain UI displays. If you cannot be consistent with abbreviations, the long version is better than the short version.6️⃣ CamelCase or Underscore?
I prefer CamelCase for naming resources (e.g.,
ReasonPicklistChoice), but this is a matter of personal preference. If the autogenerated API name includes underscores (_), I typically leave them as-is for consistency.SFXD Wiki, an online resource developed by the Salesforce eXchange Discord (SFXD) community, offers a wealth of information and tools for Salesforce professionals. SFDX recommends that each Flow name begins with its originating domain, typically the associated object, followed by an underscore. A code indicating the Flow type—such as SCR for Screen Flows, SFL for SubFlows, SCH for Scheduled Flows, EVT for Event-Triggered Flows, or EML for Email-Sending Flows—should come next.
This article by Rakesh Gupta on Automation champion recommends prefixes like
varB_for Boolean variables,varC_for Currency, andvarT_for Text are recommended to denote data types.Conclusion
Establishing clear and consistent naming conventions for Salesforce Flow resources is an essential practice that enhances both usability and collaboration. Whether you prefer organizing by resource type, purpose, or a mix of both, the key is to ensure names are intuitive, descriptive, and functional across different contexts. Thoughtful strategies like including resource types in names, leveraging sorting features, and using clear API names streamline development and maintenance. By balancing clarity with brevity and adopting best practices—such as those shared by experts— you can create a naming system that not only works for you but also supports your team’s success in navigating and managing complex Flows.
Explore related content:
Keep Salesforce Data Clean With Before Save Flows
Popular Validation Rules for Salesforce Flows including Phone, Email and Address Fields
Create by Checking a Matching Record in Flow
A Comparative Look at Flow Decision Elements in Salesforce
#Apex #ApexHours #API #Automation #CamelCase #Data #LowCode #Picklist #Salesforce #Variable -
“Web font file size study: a variable font addition” by @stoyan
🔗 https://www.phpied.com/web-font-file-size-study-a-variable-font-addition/
> The sum is smaller than the parts. A variable font that has both normal and heavy (bold) weight (and also everything in between) is slightly smaller than two regular fonts.
⚓️ https://nicolas-hoizey.com/links/2024/10/29/web-font-file-size-study-a-variable-font-addition/
-
“Web font file size study: a variable font addition” by @stoyan
🔗 https://www.phpied.com/web-font-file-size-study-a-variable-font-addition/
> The sum is smaller than the parts. A variable font that has both normal and heavy (bold) weight (and also everything in between) is slightly smaller than two regular fonts.
⚓️ https://nicolas-hoizey.com/links/2024/10/29/web-font-file-size-study-a-variable-font-addition/
-
Alphabet Soup: Haskell’s Single-Letter Naming Quirks https://hackaday.com/2024/10/14/alphabet-soup-haskells-single-letter-naming-quirks/ #SoftwareDevelopment #programminglanguage #SoftwareHacks #conventions #dictionary #MiscHacks #variables #variable #haskell #coding #News
-
Alphabet Soup: Haskell’s Single-Letter Naming Quirks https://hackaday.com/2024/10/14/alphabet-soup-haskells-single-letter-naming-quirks/ #SoftwareDevelopment #programminglanguage #SoftwareHacks #conventions #dictionary #MiscHacks #variables #variable #haskell #coding #News
-
Alphabet Soup: Haskell’s Single-Letter Naming Quirks - When you used punch cards or tape to write a computer program, brief variable name... - https://hackaday.com/2024/10/14/alphabet-soup-haskells-single-letter-naming-quirks/ #softwaredevelopment #programminglanguage #softwarehacks #conventions #dictionary #mischacks #variables #variable #haskell #coding #news
-
Alphabet Soup: Haskell’s Single-Letter Naming Quirks - When you used punch cards or tape to write a computer program, brief variable name... - https://hackaday.com/2024/10/14/alphabet-soup-haskells-single-letter-naming-quirks/ #softwaredevelopment #programminglanguage #softwarehacks #conventions #dictionary #mischacks #variables #variable #haskell #coding #news
-
🧐🔥
“Science Gothic is based on Bank Gothic: the typeface of superheroes, action, legal drama, and science fiction.Newly reinvented as a variable font, it is far more versatile than ever before.”
#webfonts #variable #fonts #typefaces #openfonts
http://sciencegothic.com/
