Wednesday, February 19, 2020

Understanding Tag Wiki Suggestion edits. How to do it, and suggestion for the forum if it helps.

I don't know whether the following post is eligible for down-voting, but please infer any viable suggestions as far as possible.
Seeing to posts:
I feel that there are tags that are like 'email', that is they are self-explanatory and don't need any tag edit suggestions.
There were tags that I thought needed suggestions, but that was my opinion. These are self-explanatory and don't need tag edits. This is a difficult job.
To minimize such penalties, there should be privileges.
I. Special privileges should be for the moderators to mark new tags or those tags that fall in such categories, like the ones that are not editable, so that others do not have to pay a penalty, sooner or later.
II. If the moderator team is unable to reply to a question raised in the contacts, the same post should not be penalized in the forum. Instead, these posts should be just deleted with the message that there was a rude behavior, or the posts do not belong in the forum or whatever other reason.
III. Instead of contacts, there should be a proper forum, where there is no down-voting. The messages should be private, and the questions should be only visible to the moderators and the person who posted it.

Some mistakes that I did, unknowingly and others may be doing.
  1. https://stackoverflow.com/edit-tag-wiki/141989
The network solutions are a company, that is, as they say, is the World's first domain registrar with over 25 years of experience.
--
This is with reference to a network solutions company, which is the World's first domain registrar with over 25 years of experience.
Derived from the quotation from the web-site, about the company:
They are a team full of technical expertise to help the clients with anything they need related to the products and services they provide. They are trained to troubleshoot and assist clients to resolve any of their technical issues.

  1. https://stackoverflow.com/edit-tag-wiki/141990
NGINX provides an open-source HTTP server and HTTP upstream is one of its modules.
-- The ngx_http_upstream_module module is used to define groups of servers that can be referenced by the proxy_passfastcgi_passuwsgi_passscgi_passmemcached_pass, and grpc_pass directives.

  1. https://stackoverflow.com/edit-tag-wiki/141988
Inside GitHub Actions the runner is the application, that runs a job from its workflow. The runner, as said on the website, can run on the hosted machine pools or run on self-hosted environments.
-- A GitHub-hosted runner is a virtual machine hosted by GitHub with the GitHub Actions runner application installed. GitHub offers runners with Linux, Windows, and macOS operating systems. When you use a GitHub-hosted runner, machine maintenance and upgrades are taken care of for you.

Please see the list of edits I have done in the last two days:
(Note: Elaboration of some of the failed edits, in the link above, are already discussed in one of the answers to this question, where the same pattern of failure is repeated again and again.)
Thus I have found out more answers.
So it seems there is a lot for me to learn before proceeding to further edits after a lot of failures.
I have also seen this post during my edit ban: For how long I am banned for edits?
This post proves that the rejection is also about preventing bad behavior and bad practices until you are aware of it. Burnination leads to mass editing, and if not done with proper research, it has a drastic effect. So one has to prepare for a permanent ban if the failures are becoming unacceptably numerous.

Things that I have inferred till now :
Seeking Resolutions For The Common Problems While Editing The Posts
I have tried to improve the look of the questions or answers, emphasizing on the keywords, such that it grabs attention (even if the tags are already there), to see whether a post conveys the intentions/efforts clearly, and then it is properly understood.
In the process, by looking at the rejected edits, I have learned:
  1. The real use of quotations (just quote from the external sources or evidence),
  2. Links with labels (not always necessary, but it looks clean and describes the context of the place it will take you to),
  3. Code wrapper (for pieces of code or programming language keywords only),
  4. Bold and italicized words to emphasize a sentence that describes a problem or words that relate to the jargon of the language (if used incorrectly, it may impact the readability of the question).
  5. For numbered lists and bulleted lists, this is the best example, because, in earlier stages of this post, the readability was bizarre. So you can explain your problem point by point.
  6. You can divide your post into sections using a horizontal rule.
  7. You can try two different sizes of the text: header and normal.
The most common review comment is:
This edit does not make the post even a little bit easier to read, easier to find, more accurate or more accessible. Changes are either completely superfluous or actively harm readability.
I need to understand, in what ways, grammatical corrections, and other suggestions, ended up in the reviews like that of the above, and others?
(Note: I have realized that it is not necessary to edit a sentence if the grammar is still correct enough to convey its intent properly. Only unnecessary portions of the post should be removed.)

WHAT TO LOOK FOR WHILE EDITING A POST AND TO MAKE AWARE TO THE POST OWNER HOW TO ASK A QUESTION
Putting my inferences till now:
  • No need to edit the post if, in spite of grammar, it conveys what it wants to.
  • If the post is still not conveying what it wants to, even when the structure is good, and the details are not put in, you can down-vote, a flag to close with a comment that more efforts are needed by the question owner him/herself to improve the post.
  • Often there are sentences that are not useful to the post. These may be removed.
  • There may be issues of improper formatting.
  • If there are unrelated questions within the same post, then you can edit out to remove the question and suggest the post owner, that the post can be asked as a separate question in SOW.
  • The post owner should be careful in arguments with the contributors and moderators. He/she should not become adamant that he/she is doing good, even when reputed peers are advising that something he/she is doing is wrong.
  • You can flag or remove dead source links in the post.
For StackOverflow:
Is your question about programming?
We prefer questions that can be answered, not just discussed.
Provide details. Share your research.
If your question is about this website, ask it on meta (here) instead.
Hence the rejection of the above question in the link was correct.
With the help of the solutions I get, I can improve past and future suggestions edits.

Wednesday, January 22, 2020

My Short Resume

ABHINAV SAXENA 

Software Team Lead | abhsax130778@gmail.com 

 


PROFESSIONAL SUMMARY

  • Masters in computer application. 15+ years of experience. 13+ years of experience in developing mobile applications in Android. 3 years in Kotlin, 5 years in ReactNative.

  • Hands-on experience in cross-platform development using ReactNative.  I have worked in Kotlin, My Play store app: https://play.google.com/store/apps/details?id=com.abh_sax.crop_image

  • Hands-on experience with unit testing and functional testing appropriately using JUnit, Expresso, Jest, Jest Expo.

  • Strong experience in Core Java OOPs Concept, Data Structure, Exception Handling, Multithreading, JDBC, UI, and coding patterns.

  • Architectures known: MVC, MVP, MVVM, MVI, VIPER.

  • Hands-on experience in dependency injection, Dagger.

  • Patterns: Factory, Strategy, Template, Visitor, Comparator, Adapter so on...

  • Hands-on experience in HTML 5, CSS 3, JavaScript, ECMA 6.

  • Hands-on experience of Eclipse, IntelliJ, Gradle, and MYSQL.

  • I have worked in Agile Scrum and have communicated well with clients and developers as a project coordinator and team lead. Have handled a team of a maximum of 8 members.

  • Highly motivated, team player with good Interpersonal and communication skills, organized and quick learner.

 

RECENT PROJECTS

Project: VITRO, Company: Flexsin

Duration: 9 months

Environment: Android, SQLite, Kotlin.


Developed as a proprietary product for VITRO, Mexico. connect and transfer presentation data to tablets from phone handsets using Bluetooth and Wi-Fi without UI interaction. 


  • This app is for clients from Mexico. Developed using the latest MVVM pattern.

  • Old and latest Networking APIs for Bluetooth and WiFi, WiFi direct using Sockets compliant with the latest and oldest phones in the market.



Project: Pharos (com.pharos), Company: Flexsin.

Duration: 6 months

Environment: One version in Android, SQLite, Kotlin.


Beacons and GPS geo-fencing lets you connect with stores around you!

  • Real-time advertisement as you roam about a city, with products in shops with BLE beacons attached to them.

  • Discount coupons and redeeming, deletion and management of those belonging to you.

  • Friends and chatting facility.

  • Order history, Wallet and Google Pay integrated.

  • Items are categorized so as to send notification according to taste when an item is bought or taken into the wish-list.

Project: Geofly, Company: Coineption - HashStudios.

Duration: 6 months

Environment:  ReactNative.


Ecommerce solution using proximity marketing.

You can see the vouchers, coupons and discounts from various brands without actually going to places yourself, on the app and portal.

Project: Community for Runners, Company: Flexsin.

Duration: 11 months

Environment: One version in Android, SQLite, Another version created with ReactNative.


Run while you earn. 


  • Offline route recording.

  • Create routes and invite your friends to run in those challenges.

  • Used Location Services, Google Maps, JSON, Http URL Connection.


Work Experience


Senior Programmer

Flexsin ExtraMarks:

December 3rd 2020 - June 5th 2021. I worked in block building demos for the product ExtraMarks, in ReactNative and React JavaScript. I also developed 5 modules in this project in React JavaScript.


Senior Android Developer

ioTech Pvt. Ltd.:

Aug 10th 2020 - December 3rd 2020. As a senior Android Developer, I got a chance to write.

I have done 2 projects in Kotlin Android, and started 1 in iOS UIKIT Storyboard and 1 on SwiftUI.

Notable Projects: 

1. Vendify Config. Vending delivery people can use this app to communicate with BLE-IOT Device and update configuration.  These BLE devices use this configuration to communicate with the server to update sale status.

2. Vending Machine Delivery Person App. Certain delivery persons hired by vending companies can get refill pack orders through the app from people behind Vending Machine.


Senior Android Developer

Cyntralabs Pvt. Ltd.:

April 12th 2020- Aug 10th 2020. As a senior Android Developer.

I have done 2 projects in Kotlin Android.

Notable Projects: 

1. INOX Movie Tickets. Users can go to this kiosk app and purchase tickets using voice recognition. 

2. Face Recognition. Users can log in using Face Recognition.



Android Team Leader

HashStudios (Coineption) Technologies Pvt. Ltd - Noida, Uttar Pradesh.

April 2018 to April 2020.

As a team leader, I have a responsibility to review the code written by junior developers, give them the idea of the correct method, usage of programming patterns. Side by side I develop an architecture for live Android projects and proceed in further development until the delivery of the application in an acceptable state to the clients. 

I have done 5 applications in ReactNative. 

Notable Projects: 


Technical Lead

TechInnovations Lucknow - Lucknow, Uttar Pradesh.

November 2017 to April 2018.

Assisted in a friend's company. Worked as assistant project manager initially, but rose to technical lead. I gave my support remotely, working part-time. Assisted in 3 projects. Side by side was pursuing the course for 'Negotiations Manager' and 'ITIL' certificates. Had to close the company, with mutual consent with my friend in the joint venture, when funds were not sufficient.


Senior Software Engineer in the Mobility Department

Flexsin Solutions Pvt. Ltd - Noida, Uttar Pradesh.

May 2015 to September 2017.

Worked successfully as Senior Software Engineer, project coordinator, individual contributor in Android. Developed 15 Android applications and deployed in the play store. Reviewing each team member's programming code. Encouraging team members to use the reusable components developed for the purpose of swift development. Helped the growth of the business by increasing trust in existing clients.

Effective communication between clients and teams to speed up the execution phase. 



Online Presence:



Profile Blog: CV, About Me, Technical Blogs: http://mobi-app-dev.blogspot.in/

LinkedIn: https://www.linkedin.com/in/abhinav-saxena-a63aa714

Facebook: https://facebook.com/abhinav.saxena.566

Twitter: www.twitter.com/AbhinavSaxena3

Google Plus: https://plus.google.com/+AbhinavSaxenaLifeOfPi

My Apps: https://play.google.com/store/apps/developer?id=abhsax130778@gmail.com

StackOverflow (My Story): https://stackoverflow.com/users/story/787399



Educational Details:



1. MCA from IGNOU, Apr 2003 - Dec 2007: 58.22%.


2. B Sc, Dr. Ram Manohar Lohia, Awadh, Faizabad University, Apr 1996 - Jan 2000: Zoology, Chemistry: 51.27%.


3. Inter, Govt., U.P. Board, Inter. College, Nishatganj, Lucknow, 1994 - 1996: 51.60%.


4. High School, I.C.S.E, Modern College, Sector E, Aliganj, 1992 - 1994: 50.16%.



Diploma



GNIIT from NIIT, April 2002.



Certificates



CompTIA A+ Certification, KarROX, Lucknow, August 2002.


ITIL, from GreyCampus foundation, June 2018.



REFERENCES from previous companies



amit.goenka@ariosesoftware.com - 3 years

https://www.facebook.com/goenkamit


naveensinghcs@gmail.com - 4 and a half years.

9650401746



SUMMARY



1. Full Name (No Abbreviations): Abhinav Saxena

2. Email ID: abhsax130778@gmail.com

3. Mobile: 9818595272

4. Date of Birth: July 13th, 1979.

5. Current Organization Name & (DOJ): Coineption - HashStudios, April 31st, 2018.

6. Total Experience: 12+

     Team size you are leading currently: 10

7. Relevant Experience on:

            (a) Core Java: 5

            (b) Spring: 3

            (c) Hibernate : 3

            (d) Web Services: 3

            (e) Android: 10

            (f) Kotlin: 3

8. Current CTC (in INR): 7 LPA

9. Expected CTC (In INR): 8 LPA

10. Notice Period: Can join immediately

11. Current location: Delhi NCR, 

12. Open for Noida, Chandigarh, Bangaluru: Sure

13. Qualification: % scored in each:

(a) 10th %: 50.16%

(b) 12th %: 51.60%

(c)  Graduation %: 51.27%

(d) Post Graduation %: 58.22%

14. Are you available for the Face to face interview Interview in a city other than Noida: Sure.

15. Ready for night shifts: Sure.

16. Ready for 6 days job.: Yes.


Tuesday, January 7, 2020

About Me

1. Full Name (No Abbreviations): Abhinav Saxena
2. Email ID: abhsax130778@gmail.com
3. Mobile: 9818595272
4. Date of Birth: July 13th, 1979.
5. Current Organization Name & (DOJ): Coineption, April 31st, 2018.
6. Total Experience: 15+
     Team size you are leading currently: 10
7. Relevant Experience on:
            (a) Core Java:5
            (b) Spring: 3
            (c) Hibernate : 3
            (d) Web Services: 3
8. Current CTC (in INR): 7 LPA
9. Expected CTC (In INR): 8 LPA
10. Notice Period: Can join immediately
11. Current location: Noida
12. Open for Noida: Sure
13. Qualification: % scored in each:
(a) 10 %: 50%
(b) 12%: 50%
(c)  Graduation %: 50%
(d) Post Graduation %: 58%
14. Are you available for the Face to face interview Interview in Noida: Sure.
15. Ready for night shifts: Sure.
16. Ready for 6 days job.: Yes.

-- ONLINE PRESENCE --

Online Presence:-

Twitter:- @AbhinavSaxena3
https://www.twitter.com/AbhinavSaxena3

Facebook:- abhinav.saxena.566
https://www.facebook.com/abhinav.saxena.566

LinkedIn:- https://www.linkedin.com/in/abhinav-saxena-a63aa714

Tumblr:- https://www.tumblr.com/abhsax130778@gmail.com

---- BLOGS:-

https://mobi-app-dev.blogspot.com/?m=1
https://becominggrt.blogspot.com/?m=1
https://abhsaxprivpol130778.blogspot.com/?m=1
https://gr8lyr.blogspot.com/?m=1
https://abhinav-alexanderthegreat.blogspot.com/?m=1
https://abhs4smj.blogspot.com/?m=1
https://supremehymn.blogspot.com/?m=1

Saturday, July 20, 2019

How to have an efficient mobile application

For small businesses and big corporate companies alike, mobile is the latest frontier. Yet rather than simply developing a mobile-friendly version of your website or adding a cool e-commerce capability to the mobile user experience, more and more entrepreneurs are wisely delving into the mobile market by developing a smartphone app.

But not all apps are made equal — scroll through the Google Play Store or Apple app store and you’ll find countless offerings that are useless to users and a waste of money from companies. In fact, some apps actually make the businesses that produce them look worse to potential consumers than if they never put that app on virtual shelves.

While going through developing an application what most people forget is that with whom they are competing. On a closer look it is the similar application available on the play store or the application which are actually already residing on the user's mobile.

Designing a mobile app for your small business? Following should be a must have feature in the application

1. Feedback system

The importance of having some way for users to provide feedback on your app is critical. Whether it is a button or a link to open an email doesn’t matter; the important part is that you give your users a quick way to report bugs, and provide suggestions or criticisms. Users will appreciate knowing that you are open to their feedback and that their input can shape the future of your app.

2. Usability first

A compelling mobile application must feature an interface that focuses on usability. The best way to do this is to follow the general application hierarchy of widely used apps like Facebook, Instagram and Twitter. User experience bonus points are awarded if it is also beautiful and (pleasantly) surprising!

3. Can you customize?

Make sure that there is a clear way to adjust the settings for your app: colors, font sizes and, most importantly, privacy settings if it happens to be a social app. The more opportunities the user has to tailor the app to her own taste, the less chance that you will get something wrong. And, if you do, it will simply be adjusted by the user.

4. Keep it simple

It gets tempting to throw in a million small, frivolous features into your mobile app because you think they’re “cool” or good-looking, but don’t. Figure out the few basic things users want and build those couple features, and nothing else. I’d rather use an app that let me do what I want in 15 seconds than a convoluted UX that lets me do things I have no interest in actually doing.

5. Remember, it’s a phone

If you are a small business with a brick-and-mortar operation, I always recommend taking a step back and remembering the core function of a mobile device: It’s a phone. Including the ability for your customer to have an over-the-phone connection with you, while they’re interacting with your mobile application, can go a long way to delivering top-notch customer service.

6. Maintain relevance

The content in it must be something that is impossible to gain from your website. Stop building apps that are just big web browsers, and focus on pushing relevant information and delivering a richer experience that is beyond what your mobile website can do.

8. Ruthlessly eliminate clicks

If you must ask users to register, sign up, or fill out forms, be zealous about eliminating every possible click, or tap, from the design. Ask for less information. Conversion rates fall sharply when extra work is required to sign up. This is a mistake novice designers make over and over. You only have a short window to hook them, and if they have a bad experience, they won’t try again.

9. Don’t change!

When converting a traditionally browser-based system to a mobile app, make sure not to omit or hide any features, however ‘small’ they may seem. Nothing is worse than failing to find, on the mobile app, that one key feature that you always use on the browser version!

10. Include analytics

As a mobile app developer, one key component is to incorporate analytics into your mobile app. A small business must be able to track and identify their users experience and actions. Most users do not enjoy giving up their location, which is understandable. Tracking a users location is different to tracking and analyzing their expe rience. The data gathered will only help encourage better updates.

11. Offline capabilities

It’s frustrating to users when an app is entirely unusable just because they have a weak signal. Consider how you can build in content or interactivity that doesn’t rely on a wireless signal. It’ll make for a positive user experience while your users are on-the-go, online or off.

12. Go with gamification

Gamification allows users to be interactive and have fun while using the app. People will come back to an app again and again if it provides some kind of value, and short-term fun and competition are always winners.

13. Prioritize speed

It’s very important to make sure the app isn’t slow. People used to despise Facebook because of how slow the mobile app is. It is crucial that your app doesn’t make people wait around while it loads.

14) Geography

The geography or the location is a feature which comes into play when app is on role. Different geographies have different requirements and availability of ingredients required by the application. just in case of an example the Internet connectivity varies from region to region. Same is the cost that people can spend to avail Internet.

15) Memory and Internet Data usage 

The Memory consumption on phone being on storage or while the app is on play is one of the important constraints that has to be taken care of. The app requiring having large memory requirements are easily discarded. As the Internet connectivity plays as vital ingredient for apps to function, the amount of data usage done by the app is another thing that should not be forgotten.

Friday, March 1, 2019

How to use fragments ideally in Android Applications

My suggestion is: do not use activities at all, instead use fragments, and replace them in the container (Linear Layout for example) where you show your first fragment.

The code is available in Android Developer Tutorials, you just have to customize.

http://developer.android.com/training/implementing-navigation/nav-drawer.html

It is advisable that you should use more and more fragments in your application, and there should be only four basic activities local to your application, that you mention in your AndroidManifest.xml apart from the external ones (FacebookActivity for example):

1. SplashActivity: uses no fragment, and uses FullScreen theme.

2. LoginSignUpActivity: Do not require NavigationDrawer at all, and no back button as well, so simply use the normal toolbar, but at the least, 3 or 4 fragments will be required. Uses no-action-bar theme

3. HomeActivity or DashBoard Activity: Uses no-action-bar theme. Here you require Navigation drawer, also all the screens that follow will be fragments or nested fragments, till the leaf view, with the shared drawer. All the settings, user profile and etc. will be here as fragments, in this activity.
The fragments here will not be added to the back stack and will be opened from the drawer menu items. In the case of fragments that require back button instead of the drawer, there is a fourth kind of activity below.

4. Activity without drawer. This activity has a back button on top and the fragments inside will be sharing the same action-bar. These fragments will be added to the back-stack, as there will be a navigation history.

[ For further guidance see: https://stackoverflow.com/a/51100507/787399 ]

Happy Coding !!