#CodingEssentials - Twitter Hashtag

nivek | Google Dev Expert • Angular

@nivekcode

over 1 year ago

A must-read for those interested in beginning their journey with #Vim #CodingEssentials

1

6

0

3

677

Victor Okeke @TechProVee

almost 2 years ago

Today in class! We explored loops in control structures & I used the mortar&pestle vs electric grinder analogy to drive the point home! Students saw the power of loops in action! Sometimes, a funny gesture goes a long way #TechProvee #FrontendTutor #CodingEssentials

TechProVee's tweet photo. Today in class! We explored loops in control structures & I used the mortar&pestle vs electric grinder analogy to drive the point home! Students saw the power of loops in action!

Sometimes, a funny gesture goes a long way #TechProvee #FrontendTutor #CodingEssentials https://t.co/u3Mc29FgIq

0

11

3

0

190

Manas @manas_raj_

over 2 years ago

Day 8 of #30DaysOfCoding complete! Reviewed the basics with functions for even/odd check, rectangle calculations (area & perimeter!), and grade conversion. Building a strong foundation is key! #CodingEssentials #BuildingBlocks #CodingChallenge #LearningByDoing

manas_raj_'s tweet photo. Day 8 of #30DaysOfCoding complete!

Reviewed the basics with functions for even/odd check, rectangle calculations (area & perimeter!), and grade conversion.
Building a strong foundation is key!
#CodingEssentials #BuildingBlocks #CodingChallenge #LearningByDoing https://t.co/gAayWGLuYc

0

34

React Native Heroes

@ReactNatHeroes

over 2 years ago

🚀 New on YouTube: "Dive Deep into Blockchain Development: React Native Edition" 🎥 Led by @synesthesiait's tech lead and dev Umberto Lanno & Mirko Quaglia. 🔗https://t.co/VqsXviqAXX #BlockchainDev #TechInnovation #Developers #CodingEssentials #WatchNow

ReactNatHeroes's tweet photo. 🚀 New on YouTube: "Dive Deep into Blockchain Development: React Native Edition" 🎥 Led by @synesthesiait's tech lead and dev Umberto Lanno & Mirko Quaglia.
🔗https://t.co/VqsXviqAXX

#BlockchainDev #TechInnovation #Developers #CodingEssentials #WatchNow https://t.co/tYpc10QJwk

0

5

0

91

Mudit (devloprr.com)

@devloprr

about 3 years ago

The three essential elements for coding success: patience, pizza, and perseverance. Without them, you're bound to encounter endless syntax errors! 🍕🧠🔍 #CodingEssentials #CodeSuccessFormula #100DaysOfCode #buildinpublic

1

13

0

493

Tirumal Rao @code_n_deploy

about 3 years ago

🔧 Demystifying Makefile's .PHONY: Why and When to Use It 📚 #DevTips #CodingEssentials #MakefileMagic In make, the .PHONY target is used to specify that a certain target is not associated with a file. This is useful because make is designed to build files from other files. By default, make uses the timestamps of files to determine whether they need to be rebuilt. If there's a file with the same name as a target, make can become confused and may not execute the target when expected. The .PHONY declaration helps you avoid this issue. Here are a few reasons to use .PHONY: ============================ => Non-File Targets: In many makefiles, there are targets that do not produce a file. Common targets like clean, all, and install might not correspond to actual files, but are instead just commands you want to run. => Force Execution: Even if there is no dependency change, marking a target as .PHONY will ensure its commands get executed every time it's called. => Avoid File/Target Name Confusion: If by any chance a file with the same name as the target gets created, it would prevent make from running that target. Declaring the target as .PHONY avoids this problem. Here's an example: (see attachment) ============== In this example, all and clean are declared as .PHONY targets. This means: => When you run make or make all, it will always try to build myprogram, even if there's a file named all in the directory. => When you run make clean, it will always run the rm command, even if there's a file named clean in the directory. => It's a good practice to use .PHONY for any target that does not produce a file to avoid unexpected behaviors.

code_n_deploy's tweet photo. 🔧 Demystifying Makefile's .PHONY: Why and When to Use It 📚 #DevTips #CodingEssentials #MakefileMagic

In make, the .PHONY target is used to specify that a certain target is not associated with a file. This is useful because make is designed to build files from other files. By default, make uses the timestamps of files to determine whether they need to be rebuilt. If there's a file with the same name as a target, make can become confused and may not execute the target when expected.

The .PHONY declaration helps you avoid this issue.

Here are a few reasons to use .PHONY:
============================
=> Non-File Targets: In many makefiles, there are targets that do not produce a file. Common targets like clean, all, and install might not correspond to actual files, but are instead just commands you want to run.

=> Force Execution: Even if there is no dependency change, marking a target as .PHONY will ensure its commands get executed every time it's called.

=> Avoid File/Target Name Confusion: If by any chance a file with the same name as the target gets created, it would prevent make from running that target. Declaring the target as .PHONY avoids this problem.

Here's an example: (see attachment)
==============
In this example, all and clean are declared as .PHONY targets. This means:
=> When you run make or make all, it will always try to build myprogram, even if there's a file named all in the directory.

=> When you run make clean, it will always run the rm command, even if there's a file named clean in the directory.

=> It's a good practice to use .PHONY for any target that does not produce a file to avoid unexpected behaviors.

0

1

0

354

Remoti Recruitment @remoti_TI

over 3 years ago

Hey, fellow devs! What are the essential components for a cool setup for coding? Share your recommendations! #developerlife #codingessentials #techgear"

0

2

0

45