Dragos Ionel

Mobile dev

[Dragos Ionel @dragosionel]

@ms_mcclure @TCSBears You should try dessert for lunch! :-)

[Dragos Ionel @dragosionel]

Just bought "iOS Unit Testing: The Definitive Guide" by @qcoding. Looking forward to reading it.

https://t.co/eUGWpYSEes

[Dragos Ionel @dragosionel]

@twannl My pleasure. The value I am getting from your posts is a hundred times more valuable so I am getting a super deal :-)

[Dragos Ionel @dragosionel]

In school, we are taught that there is always a number between two real numbers. So there is not such a thing as the smallest positive number. Except in Swift, that is. It is called "CGFloat.leastNormalMagnitude" and it is defined as the smallest of them all.

[Dragos Ionel @dragosionel]

Great video. Halfway I was ready to add a comment saying that Enum is better than Struct for constants because you cannot initialize it, but then @v_pradeilles presented that option as well. Nice!

[Vincent Pradeilles @v_pradeilles]

When you need to group constants together, should you use an enum or a static let?

The choice might be confusing, and rightfully so because it actually depends a lot on the context 🤨

So let me give you a few tips to pick the right answer!

https://t.co/M1Xt43MtlD

[Dragos Ionel @dragosionel]

@johnsundell Great article!

[Dragos Ionel @dragosionel]

Great article about the future of Combine (at least how it looks in the present) by @johnsundell
https://t.co/VfGBUYohea

[Dragos Ionel @dragosionel]

If you thought you knew everything about retaining cycles using self, you might learn a couple of new things from this video, just like I did :-)

[Vincent Pradeilles @v_pradeilles]

Retain cycles are always a big source of trouble for iOS developers…

Today I want to show you how a syntax that looks safe on the surface, will actually lead to big old retain cycle 😱

https://t.co/zRGUWCZQAO

[Dragos Ionel @dragosionel]

@qcoding Always default, unless there is a strong reason against it.

[Dragos Ionel @dragosionel]

Great code - Tip 20 - Write your code in 5 "C" steps

1. Write Code that works

2. Write Comments that explain the code

3. Combine the Code and the Comments

#codinginstyle

[Dragos Ionel @dragosionel]

@thedevme Looks like one of those useless books that are super interesting and satisfying to read and understand!

[Dragos Ionel @dragosionel]

Great code - Tip 19 - Do not create entities with names that are very similar and can be confused especially when using autocomplete.
#codinginstyle

//bad choice of names
func loadUserDetailsScreenFromMapUserScreen() {}
func loadUserDetailsScreenFromMapUsedScreen() {}

[Dragos Ionel @dragosionel]

"Voice Driven Development: Who needs a keyboard anyway?" by Emily Shea (2019) - talk to show how stubborn are the devs when they want to code :-)
https://t.co/B55B03ljus

[Dragos Ionel @dragosionel]

Great code - Tip 18 - Simplify the if-s by adding each condition on a new line
#codinginstyle

[Dragos Ionel @dragosionel]

"The default place for all of our code — UI code and otherwise — is the main thread". Great article by Brent Simmons: https://t.co/XWUEw4RXhG

[Dragos Ionel @dragosionel]

Great code - Tip 16

Simplify your code by adding the constants in the smallest context possible and in the appropriate places

#codinginstyle

[Dragos Ionel @dragosionel]

Great podcast from @OfferZen https://t.co/iJVTp5bZp3

[Dragos Ionel @dragosionel]

Great Code - Tip 14

Simplify the switches by combining the conditions that are leading to the same result - suggested by Sean Batson
#codinginstyle

[Dragos Ionel @dragosionel]

@twostraws Guilty. Jerk until yesterday. Not a jerk starting today. Thanks, @twostraws

[Dragos Ionel @dragosionel]

Great Code - Tip 12 - Simplify the if-s by being positive first. It makes the code easier to understand

#codinginstyle