Life is simple at time!

Dear All,
Let me introduce myself by saying that I have gone thru each and every pain in business and made every single mistakes that one can possible make. The most important part that I learnt in all these chaos is thinking simple!
I have spent almost 20 years online. Dating, looking for jobs, Banking, Business and all those things that makes me anyone in a million.
One of the most important thing that started disturbing me, during late 2013 that only companies who can fund for their…

Life is simple at time!

Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

  • Get
  • Set
  • Contains
  • Add
  • Remove
  • Push
  • Pop
  • Clear
  • Close
  • Lock
  • Open
  • Unlock
  • Enqueue
  • Dequeue
  • Activate
  • Deactivate
  • Translate
  • Move
  • Jump
  • Fill
  • Empty
  • Draw
  • Take
  • Give
  • Stash
  • Group
  • Shuffle
  • Mix
  • Sort
  • Merge
  • Inline
  • Validate
  • Check
  • Execute
  • Apply
  • Compose
  • Decompose
  • Decay
  • Break
  • Gather
  • Fuse
  • Grow
  • Rise
  • Drop
  • Fall
  • Pick
  • Select
  • Accept
  • Decline
  • Retire
  • Upgrade
  • Degrade
  • Increase
  • Decrease
  • Stop
  • Continue
  • Pause
  • Resume
  • Process
  • Advance
  • Create
  • Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

  • Get
  • Set
  • Contains
  • Add
  • Remove
  • Push
  • Pop
  • Clear
  • Close
  • Lock
  • Open
  • Unlock
  • Enqueue
  • Dequeue
  • Activate
  • Deactivate
  • Translate
  • Move
  • Jump
  • Fill
  • Empty
  • Draw
  • Take
  • Give
  • Stash
  • Group
  • Shuffle
  • Mix
  • Sort
  • Merge
  • Inline
  • Validate
  • Check
  • Execute
  • Apply
  • Compose
  • Decompose
  • Decay
  • Break
  • Gather
  • Fuse
  • Grow
  • Rise
  • Drop
  • Fall
  • Pick
  • Select
  • Accept
  • Decline
  • Retire
  • Upgrade
  • Degrade
  • Increase
  • Decrease
  • Stop
  • Continue
  • Pause
  • Resume
  • Process
  • Advance
  • Create
  • Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

  • Get
  • Set
  • Contains
  • Add
  • Remove
  • Push
  • Pop
  • Clear
  • Close
  • Lock
  • Open
  • Unlock
  • Enqueue
  • Dequeue
  • Activate
  • Deactivate
  • Translate
  • Move
  • Jump
  • Fill
  • Empty
  • Draw
  • Take
  • Give
  • Stash
  • Group
  • Shuffle
  • Mix
  • Sort
  • Merge
  • Inline
  • Validate
  • Check
  • Execute
  • Apply
  • Compose
  • Decompose
  • Decay
  • Break
  • Gather
  • Fuse
  • Grow
  • Rise
  • Drop
  • Fall
  • Pick
  • Select
  • Accept
  • Decline
  • Retire
  • Upgrade
  • Degrade
  • Increase
  • Decrease
  • Stop
  • Continue
  • Pause
  • Resume
  • Process
  • Advance
  • Create
  • Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

  • Get
  • Set
  • Contains
  • Add
  • Remove
  • Push
  • Pop
  • Clear
  • Close
  • Lock
  • Open
  • Unlock
  • Enqueue
  • Dequeue
  • Activate
  • Deactivate
  • Translate
  • Move
  • Jump
  • Fill
  • Empty
  • Draw
  • Take
  • Give
  • Stash
  • Group
  • Shuffle
  • Mix
  • Sort
  • Merge
  • Inline
  • Validate
  • Check
  • Execute
  • Apply
  • Compose
  • Decompose
  • Decay
  • Break
  • Gather
  • Fuse
  • Grow
  • Rise
  • Drop
  • Fall
  • Pick
  • Select
  • Accept
  • Decline
  • Retire
  • Upgrade
  • Degrade
  • Increase
  • Decrease
  • Stop
  • Continue
  • Pause
  • Resume
  • Process
  • Advance
  • Create
  • Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

How to mount my own xmpp server in my pc?

I just want to mount my own xmpp server and need some way to get this purpose. I just thought using openfire but i have some questions before to setup it.

The first thing which are the steps? The second i must to open ports to setup my own xmpp server or just using internet is enough?

Could someone guide me a little to setup my own server in a easy way.

What ideas should be mastered to go from a junior to a middle skilled iOS developer? [on hold]

I taught myself how to develop iPhone apps and have been doing so for 5 years. My skill level (junior) is described here: https://github.com/BohdanOrlov/ios-skills-matrix

What ideas must I master to become a middle level developer? What resources would you recommend? Particular books to dive into would be very appreciated!

I’ve learned to code following this line of thinking: “if it works, it works.”

With this, I’ve built several apps from idea to production (some gaining 100k+ users) but as you can imagine, my code is messy.. or at least I think it is. I’ve worked on web apps (php, javascript) and iOS apps (objective-c and swift). Moreover, when I interview for iOS dev jobs, I feel a bad case of imposter syndrome. While juniors who’ve never shipped code that is used by people land jobs, I don’t pass any interviews.

I want to cross the junior to middle skill matrix. What must I learn to do so? Ideas I know I am no expert is so far are: architecture, testing and documentation. What else?

Industry Best Practices for Managing Application Versions

I’m trying to see if there is an accepted industry best practice for managing the current version of a project in a single place for many things to utilize.

So I have a shared object that I developed. This shared object is packaged in two forms, a Conan package, and an RPM. It is a Qt project, so it has a .pro file associated with it. Up until now, we have managed our dependency versions through the .pro file by defining:

MAJOR = 1 MINOR = 2 PATCH = 3 

but now, with Conan and RPM, it is becoming a bit of a nightmare to maintain. Should we still be managing the version from the .pro file and scraping the version out for the Conan package version and the RPM version or should we have a separate version file that anything that needs it can scrape from?

How do agile teams deal with non-agile organizational structures?

I’ve worked at the same employer my entire career (going on 13 years now). We’re big and deal with sensitive data. Technology is not our product, but it helps support our main product.

I want to know how other large organizations are structured. Here we have silos of functional areas within IT. We have separate units responsible for Cloud Engineering, Identity Management, Application Lifecycle Management (maintain build servers and build definitions), Database Administrators, and Information Security. These separate areas all have their own separate priorities and marching orders.

I sit on a development scrum team. We represent the horizontal bar at the bottom. We execute project work that spans all the above functional areas. What this means for us is that when we want to execute a project we put in service request tickets to all these areas. Typically a new project will start with us requesting services through ~50 tickets. This is driving us developers nuts.

Is this how big companies do things? Is this probably more probable in companies where tech isn’t their main business line? What alternative structures have you seen in your roles?

enter image description here