• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

• There are 54 files with 9,392 lines of code.
• 1 very long files (1,682 lines of code)
• 3 long files (2,043 lines of code)
• 9 medium size files (2,588 lines of codeclsfd_ftr_w_mp_ins)
• 9 small files (1,329 lines of code)
• 32 very small files (1,750 lines of code)

There are 31 files with lines longer than 120 characters. In total, there are 117 long lines.

File	# lines	# units	# long lines
instance.go in root	729	68	16
compute.go in compute	1682	118	15
step_wait_for_instances_signal.go in root	367	15	9
main.go in daisy_test_runner	590	22	7
resource_registry.go in root	229	12	6
step_create_instances.go in root	193	7	5
disk.go in root	185	12	4
resource.go in root	220	17	4
snapshot.go in root	64	6	4
machineimage.go in root	70	7	4
step_detach_disks.go in root	84	3	3
subnetwork.go in root	124	10	3
target_instance.go in root	70	6	3
firewall_rule.go in root	68	6	3
forwarding_rule.go in root	76	6	3
image.go in root	366	54	3
network.go in root	124	10	3
step_create_images.go in root	128	6	2
machinetype.go in root	26	1	2
step_wait_for_quota.go in root	82	3	2
step_deprecate_images.go in root	76	3	2
license.go in root	12	1	2
step_attach_disks.go in root	92	3	2
main.go in cli	267	7	2
workflow.go in root	724	42	2
step_copy_gcs_objects.go in root	160	4	1
disktype.go in root	6	-	1
storage.go in root	43	2	1
step.go in root	301	14	1
logger.go in root	240	17	1
step_create_disks.go in root	65	4	1