Last year I found myself in an interesting conversation about which copy to use for a website’s sign up journey. And it wasn’t the first time. Often this devolves into an opinion-based discussion among stakeholders of the ‘what-I-like-based-on-no-evidence’ variety.
I ended up writing a small piece of best practice guidance, based on approximately 12 years’ experience of user testing private and public sector products.
(TLDR: yes, it depends)
The key to choosing terminology is intent — what are you communicating about the experience?
When you want to capture user data for the first time, the way you ask communicates what the website or app is for. This is because you are using words that the user will already associate with other experiences throughout their lives, not just digital products —so you need to be aware of the connotations and mental models that already exist.
Yes, you should do research to understand users and yes you should user test however there are also some patterns that I’ve seen over the years that can help you form your initial hypothesis:
Sign up — is pretty generic and appropriate for most products and services. The only time I’ve seen users hesitate on this phrase is when the website is super secure and ‘sign up’ has been perceived as slightly frivolous.
Register — is slightly more formal and potentially appropriate to a government website, for example you ‘register’ to vote. Users tend to associate this with an almost legal meaning. One person, one registration. It is a claiming of one’s own identity in relation to a product.
#design #forms #ux #ux-writing #sign #log
We all have seen the Monitoring Tab Key Metrics on the VM Page. Yes, it is useful to see whether the CPU has been running or not through the **CPU **metrics, to check when the VM is getting the data from the outside world through Network In metrics and if the VM is doing any kind of write operation using **Disk Operations/Sec **metrics but it’s not effective for the custom services that we build on VM. So, in this blog, I will be giving you an example of how to create your own log based on customer service, bring it to Azure Log Analytics Workspace using its default agent, and query it according to our needs, even better create an alert on it.
Let’s start with the VM itself. You already have the service running on the VM but don’t know how to get those logs into the portal or even create a log for your services. So, let’s assume that you have not created the logs for your services. So for this blog, I will be taking a simple flask app as my example for the service. To get it up and running we must download the flask library from pip and then create a flask app similar to this below:
#logs #log-analytics #azure #azure log analytics
In this article, we will learn how to replace elements in Python NumPy Array. To replace elements in Python NumPy Array, We can follow the following examples.
The following code shows how to replace all elements in the NumPy array equal to 8 with a new value of 20:
#replace all elements equal to 8 with 20 my_array[my_array == 8] = 20 #view updated array print(my_array) [ 4 5 5 7 20 20 9 12]
The following code shows how to replace all elements in the NumPy array greater than 8 with a new value of 20:
#replace all elements greater than 8 with 20 my_array[my_array > 8] = 20 #view updated array print(my_array) [ 4 5 5 7 8 8 20 20]
The following code shows how to replace all elements in the NumPy array greater than 8 or less than 6 with a new value of 20:
#replace all elements greater than 8 or less than 6 with a new value of 20 my_array[(my_array > 8) | (my_array < 6)] = 20 #view updated array print(my_array) [20 20 20 7 8 8 20 20]
Monotone is a Modern Mobile Application, integrated with powerful Unsplash API provided by Unsplash. It implemented almost all features including viewing, searching, collecting photos. And other features, such as profile, license, FAQ are supported as well.
This is an un-official application, exploring the feasibility of some conceptions is the goal of this project. Written in Swift, triggered by RxSwift, draw responsive constraints using SnapKit.
If you like this project or inspired by any ideas of this project, please star it without any hesitation. (ヽ(✿ﾟ▽ﾟ)ノ)
Currently supported tasks:
|Position||Module||Page||Style & Layout||Powered by Data||Animation Effects||Localization|
|Main||Login||Sign Up & Sign In||✅||✅||✅||✅|
|Photo||List (Search & Topic)||✅||✅||✅||✅|
|Collect (Add & Remove)||✅||✅||✅||✅|
|Share to SNS||✅||⬜️||✅||✅|
|Save to Album||✅||✅||✅||✅|
|Made with Unsplash||✅||⬜️||✅||✅|
|Wallpaper||List (Adapt Screen Size)||✅||⬜️||✅||✅|
|Explore||List (Photo & Collection)||✅||⬜️||✅||✅|
This application uses
Cocoapods to manage dependencies. Please refer to Cocoapods Offical Website to install & configure(If you already installed
Cocoapods, skip this).
Monotone is trigged by Unsplash API . The very first thing must be done is applying a pair of OAuth key to run it.
Redirect URI & Permissions - Redirect URIsection, input
monotone://unsplash, make sure all authentication options are checked, just like the image shown below.
# Clone to a local folder git clone https://github.com/Neko3000/Monotone.git # Direct to Project folder cd Monotone # Install Pods pod install
config_debug.jsonfile，and rename it to
config.json(This file is ignored by .gitignore)；
config.json，input your ”Access Key“ and ”Secret Key“，they will be copyed to APP folder when running.(For more information, please refer to the content in Project->Build Phases->Run Script and APPCredential.swift )；
|RxSwift||Framework for Reactive Async Programming.|
|Action||Based on RxSwift，encapsulate actions for calling。|
|DataSources||Based on RxSwift，extend logic interaction of tableview and collectionview。|
|Alamofire||HTTP network library.|
|SwiftyJSON||Handle JSON format data effectively.|
|ObjectMapper||Map data between models and JSON.|
|Kingfisher||Network image cache libray with many functions.|
|SnapKit||Make constraints effectively.|
For more information，please check Podfile。
The basic structure of this project.
Monotone ├── Monotone │ ├── /Vars #Global Variables │ ├── /Enums #Enums (Includes some dummy data) │ ├── /Application │ │ ├── AppCredential #Authentication Credential │ │ ... │ │ └── UserManager #User Managment │ ├── /Utils #Utils │ │ ├── /BlurHash #Photo Hash │ │ ├── ColorPalette #Global Colors │ │ ├── AnimatorTrigger #Animation Effects │ │ └── MessageCenter #Message Notification │ │── /Extension #Extensions │ │── /Services #Services │ │ ├── /Authentication #Requests of Authentication │ │ └── /Network #Requesets of Data │ │── /Components #View Classes │ │── /ViewModels #View Models │ │── /ViewControllers #View Controllers │ │── /Models #Data Models │ │── /Coordinators #Segues │ └── /Resource #Resource └── Pods
The interface you are seeing are all designed by Addie Design Co. They shared this document, everyone can free download it and use it. Those design elements and their level of completion are astonishing. This application would not be here without this design document.
Thanks again to Addie Design Co and this beautiful design document.
Unsplash is a website dedicated to sharing high-quality stock photography under the Unsplash license. All photos uploaded by photographers will be organized and archived by editors.
And this website is one of my favorites, admired for its artistic, the spirit of sharing.
You will find my home page here. (
Not updated frequently since 2020)
Limited by data Unsplash API provides, some parts of this application only finished their styles and layouts(Almost in store, explore, etc). If the API provides more detailed data on these parts in the future, we will add new features as soon as possible.
Meanwhile, focusing on the current application, we will improve it continuously.
If you are an experienced mobile application developer and want to improve this application. You are welcomed to participate in this open-source project. Practice your ideas, improve even refactor this application.
Follow standard steps:
git checkout -b feature/AmazingFeature);
git commit -m 'Add some AmazingFeature');
git push origin feature/AmazingFeature);
For anyone, open an issue if you find any problems. PRs are welcome.
Source code: https://github.com/Neko3000/Monotone
License: MIT license
Logging is one of the those things are universally present in software projects with their different unique forms, requirements, and flavors.
Logging is everywhere, from small 1-person-startups to large enterprises. Even a simple algorithmic programming question involves some logging along the way.
We rely so much on logging to develop, maintain, and keep our programs up and running. However, not much attention has been paid to how to design logging within our systems.
Often times, logging is treated as a second thought – it’s only sprinkled into source code upon implementation like some magic powder that helps lighten the day-to-day operational abyss in our systems.
#to log #not to log,