The Frog’s Games
问题描述 :
The annual Games in frogs’ kingdom started again. The most famous game is the Ironfrog Triathlon. One test in the Ironfrog Triathlon is jumping. This project requires the frog athletes to jump over the river. The width of the river is L (1<= L <=<PHONE_NUMBER>). There are n (0<= n <= 500000) stones lined up in a straight line from one side to the other side of the river. The frogs can only jump through the river, but they can land on the stones. If they fall into the river, they
are out. The frogs was asked to jump at most m (1<= m <= n+1) times. Now the frogs want to know if they want to jump across the river, at least what ability should they have. (That is the frog’s longest jump distance).
are out. The frogs was asked to jump at most m (1<= m <= n+1) times. Now the frogs want to know if they want to jump across the river, at least what ability should they have. (That is the frog’s longest jump distance).
输入:
The input contains several cases. The first line of each case contains three positive integer L, n, and m.
Then n lines follow. Each stands for the distance from the starting banks to the nth stone, two stone appear in one place is impossible.
Then n lines follow. Each stands for the distance from the starting banks to the nth stone, two stone appear in one place is impossible.
输出:
The input contains several cases. The first line of each case contains three positive integer L, n, and m.
Then n lines follow. Each stands for the distance from the starting banks to the nth stone, two stone appear in one place is impossible.
Then n lines follow. Each stands for the distance from the starting banks to the nth stone, two stone appear in one place is impossible.
样例输入:
6 1 2 2 25 3 3 11 2 18
样例输出:
4 11
/*
分析：
二分，水。。题。竟然ac了、着实捏了一把冷汗、1Y。。。
读完题后直接就想到二分了、不过看了数据范围后、感脚数据如果够强大
的话、是过不了滴。。当然、关键的系事实证明它咩有那么强大囧～～（不过
看到那个L的范围后着实被雷的里焦外嫩的、虽然acm里面不是第一次了、不过
你家养的蛤蟆经得起这样的折腾啊。。）
2013-07-03
*/
#include"iostream" #include"cstdio" #include"cstring" #include"algorithm" using namespace std; const int N=500005; int dir[N],dis[N]; int main() { int n,m,L; int i; int low,mid,up; int temp,max,cnt; while(scanf("%d%d%d",&L,&n,&m)!=-1) { dis[0]=0; for(i=1;i<=n;i++) scanf("%d",&dis[i]); dis[n+1]=L; sort(dis,dis+n+2); max=0; for(i=0;i<=n;i++) { dir[i]=dis[i+1]-dis[i]; if(max<dir[i]) max=dir[i]; } if(m>n) {printf("%d\n",max);continue;} low=max;up=L; while(low<=up) { mid=(low+up)>>1; i=cnt=0; while(i<=n && cnt<m) { cnt++; temp=mid; while(i<=n && dir[i]<=temp) { temp-=dir[i]; i++; } } if(cnt<=m && i>n) up=mid-1; else low=mid+1; } cout<<low<<endl; } return 0; }
版权声明：本文为博主原创文章，未经博主允许不得转载。
参考：http://blog.csdn.net/ice_crazy/article/details/9237207
(adsbygoogle = window.adsbygoogle || []).push({});
另求背景音乐.
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
唔，我想说这案例题很与时俱进，更新的快的一笔
大致看了下，算法的时间复杂度没有很本性的提升，算不上高效。
学习了。找到这题
int L[m+1][n+1];这样定义出错，这个在gcc上可以编译通过 在VS上不行 应该改为new 或者vector
神奇的网站
27行 minStack.push(minValue); 去掉就对了
嗯，尽量吧。题目太多了，很多解题报告是用程序自动发布的，所以就只有代码了
能告诉我为什么对于每一个m，cnt的值不用更新吗?这儿我想不通啊，谢谢
分析的很专业！
排版
分析的很专业！
#include <stdio.h>
int main()
{
int n,p,t[100]={1};
for(int i=1;i<100;i++)
t =i;
while(scanf("%d",&n)&&n!=0){
if(n==1)
printf("Printing order for 1 pages:nSheet 1, front: Blank, 1n");
else {
if(n%4) p=n/4+1;
else p=n/4;
int q=4*p;
printf("Printing order for %d pages:n",n);
for(int i=0;i<p;i++){
printf("Sheet %d, front: ",i+1);
if(q>n) {printf("Blank, %dn",t[2*i+1]);}
else {printf("%d, %dn",q,t[2*i+1]);}
q–;//打印表前
printf("Sheet %d, back : ",i+1);
if(q>n) {printf("%d, Blankn",t[2*i+2]);}
else {printf("%d, %dn",t[2*i+2],q);}
q–;//打印表后
}
}
}
return 0;
}
对，算是枚举吧，已修正
很有意思，可惜我很菜啊
这是研发的在线笔试题吗?发现很多C啊，阿里不是JAVA多么？


I was born and raised in Pretoria South Africa, the first programming Language I learnt is visual Basic, and then C++ and 3rd it was C# and I automatically fell inlove with C# programming Language and appearantly that's my best Programming language so far.


Kafka Streams
Stream Processing Library for Apache Kafka
@jaceklaskowski
/
StackOverflow
/
GitHub
/
LinkedIn
The "Internals" Books:
books.japila.pl
## Agenda 1. [Kafka Streams](#/intro) 1. [High-Level Streams DSL](#/high-level-streams-dsl) 1. [Low-Level Processor API](#/low-level-processor-api)
## Kafka Streams 1. **Kafka Streams** is a client library for **stream processing applications** that process data stored in Kafka 1. Uses Kafka Producer and Consumer APIs 1. Stream processing primitives * High-level **Streams DSL** * Low-level **Processor API** 1. Supports **Exactly-Once Processing** * Records are processed once and only once 1. Supports **Fault-Tolerant Local State** for stateful operations * e.g. windowed joins and aggregations 1. [Home Page](https://kafka.apache.org/documentation/streams/)
## High-Level Streams DSL
(1 of 2)
1. **Streams DSL** is a high-level API built on top of the Processor API 1. Built-in abstractions for streams and tables * **KStream** * **KTable** * **GlobalKTable** 1. Declarative, functional programming style * Stateless transformations (e.g. **map** and **filter**) * Stateful transformations (e.g. **count**, **reduce**, **join**, and windowing) 1. Recommended for most developers, esp. beginners
## High-Level Streams DSL
(2 of 2)
1. Typical development flow 1. Read input streams (from Kafka topics) 1. Apply transformations 1. Write output streams (to Kafka topics) 1. Interactive queries (e.g. via a REST API) 1. Learn more in [The Internals of Kafka Streams](https://books.japila.pl/kafka-streams-internals/kstream/)
## Low-Level Processor API 1. Stream **Processor API** is a low-level API to compose topologies made up of custom processors * Node in a processor topology for a single processing step 1. [Processor
](https://kafka.apache.org/33/javadoc/org/apache/kafka/streams/processor/api/Processor.html) * (KIn,VIn) ==> Processor ==> (KOut,VOut) 1. Allows for stateless and stateful operations * Arbitrary stream processors * Connect processors with state stores 1. Combining the convenience of Streams DSL with the power and flexibility of Processor API
## Recap 1. [Kafka Streams](#/intro) 1. [High-Level Streams DSL](#/high-level-streams-dsl) 1. [Low-Level Processor API](#/low-level-processor-api)
# Questions? * Read [The Internals of Apache Kafka](https://books.japila.pl/kafka-internals/) * Read [The Internals of Kafka Streams](https://books.japila.pl/kafka-streams-internals) * Read [The Internals of ksqlDB](https://books.japila.pl/ksqldb-internals/) * Follow [@jaceklaskowski](https://twitter.com/jaceklaskowski) on twitter (DMs open) * Upvote [my questions and answers on StackOverflow](http://stackoverflow.com/users/1305344/jacek-laskowski) * Contact me at **jacek@japila.pl**


My name is Omer Yahalom, 22 years old from Israel. I currently study at RMIT University through OUA and my student number is s3858332. Currently, I live in Israel as it is my hometown but I used to live in several places like Germany and Poland. I speak English and Hebrew and I am an aspiring Polish learner. Today I am working as a freelancer for a cybersecurity company called Tufin as a front-end developer. I used to work in several companies until I decided I want to become a freelancer because of the freedom and interesting people you meet along the way. I usually like to build websites, web applications, and mobile applications. I am in love with cooking, watching documentary movies, and taking photos in my free time when I am not coding. The name we choose for the team is The Notorious Geeks.
My name is Ali Hammoud, 28 years old from Sydney, Australia. My student number is s3798721. I am currently working as a sales professional in the IT industry, but my road to get there was not quite direct. I had an interest in computers from a young age, and I was always the go-to IT person in our circle of family and friends. I studied a few semesters of Architecture and Computer Science, before leaving uni to work as a Jr .NET Developer. I worked in development for a few years before transitioning into an IT focussed sales position. I now have returned to my studies several years later with a renewed motivation to complete my degree here at RMIT. I am hoping to develop both personally and professionally, and it all starts here in the Introduction to IT subject, as part of The Notorious Geeks.
My name is Troy Glossop, I am 45 years old and live in Perth, Western Australia. I currently study full time at RMIT via OUA and my student number is s3572875. I have a background in I.T. and have worked in the industry since 1998, where my first role was as a technician building PCs for a large Computer store. In 1999, the store I worked at launched its own ISP, and as I had extensive experience with Unix and Linux, I became a System Administrator. This is the role I usually worked in until 2014 where I had to leave the industry due to health reasons. I am very interested in many facets of I.T, many of my hobbies are impossible without knowledge of Computers. My hobbies include playing music with my friends, building FPV Drones, playing Fighting Games competitively, Sim Racing and adoring my 20-year-old cat “Little Cat”. Our team name is “the Notorious Geeks”.
My name is Mohamed Abdirashid, I am of Somali descent and was born in Nairobi, Kenya. In 1998 my family and I migrated to Adelaide, South Australia where I lived for several years, before relocating to Melbourne where my mom opened up a successful furniture store. I come from a big family of seven siblings; four brothers and three sisters, and I’m a proud uncle to three girls and one boy. In the family household I speak either English or Somali. I am an enthusiastic foodie and enjoy traveling, exercise and experiencing different cuisines as hobbies. In 2020 I began my studies as an OUA student through RMIT studying both Introduction to Information Technology and Introduction to Programming, my student number being s3450966. I am new to the IT industry, however from a young age, I have always had a keen interest in Technology and Computers. In particular through my career as a Security Supervisor I have developed the keen interest of protecting, preventing and monitoring systems in the physical world. I plan on integrating these skills into the cyber world as a Cyber Security Analyst in the near future. Since starting my studies in March, I have learnt many aspects of IT such as Cloud computing, self-driving cars, ethics and laws within the industry, E-wallets and much more. Now as a member of the Notorious Geeks, I am very excited to interact with like-minded individuals and look forward to learning and exploring more topics and techniques in the IT industry through our group assignment.
Mohamed Abdirashid Ali: Myers-Briggs test result is ENFJ. Online Learning Style test result is Tactical Learner. ‘Arguing Style Test’ Result Is Positive Fighting Tactics 76/100.
Omer Yahalom: Myers-Briggs test result is INFJ. Online Learning Style test result is Auditory/Visual learner.‘Big Five Personality’ result is Extraversion.
Ali Hammoud: Myers-Briggs: INFP-T Mediator Learning Style: Verbal Gallup CliftonStrengths: 1. Restorative 2. Connectedness 3. Ideation 4. Adaptability 5. Input
Troy Glossop: Myers-Briggs: INTJ Learning Style: Auditory Psychometric Test: 7/10
In assignment 3 there was a change in the tool utilised for collaboration as zoom had limited meeting time, there was a shift to teams in assignment 3. In assignment 2 and in accordance to the Myers-Briggs test, our group displayed a balanced dynamic that brought different qualities to the team that benefited everyone. Ali’s personality type (Mediator) allowed him to be inspired by ideas rather than logic and analytics, and it often allowed him to be a bridge between different ideas and perspectives. Omer (Advocate) complements Ali’s personality type quite well in that he has large ambitions and ideas and is also led by morality. He can also see the practical steps to get there. He is inspired by morality and idealism and can easily get to the heart of an issue. Troy (Architect) has a profession for analytics that can be used to gather data and ensure the rest of the group has all the information needed to make decisions. Architects are great at design and implementing effective plans. Mohamed (Protagonist) brings everything together by being a natural-born leader and can bring out the best in everyone and make sure they have what they need. Each of us has different learning styles, which means we can bounce ideas off of each other and make sure none of us gets left behind. Information can be displayed in different ways and from different perspectives, and this is an extremely healthy way to learn. These qualities manifested within the team during assignment 2. In contrast every individual within the group has weaknesses according to Myers Brigg personality test and although such weaknesses were not manifested throughout assignment 2 these weaknesses can develop into conflict situations. As underlined in the table below here are the groups weaknesses based on the Myers Brigg personality test.
| Ali (Mediator) (Strengths & Weaknesses | Mediator (INFP) Personality | 16Personalities, 2020) |
Weaknesses
|
| Omer(Advocate) (Strengths & Weaknesses | Advocate (INFJ) Personality | 16Personalities, 2020) |
Weaknesses
|
| Troy (Architect) (Strengths & Weaknesses | Architect (INTJ) Personality | 16Personalities, 2020) |
Weaknesses
|
| Mohamed (Protagonist) (Strengths & Weaknesses | Protagonist (ENFJ) Personality | 16Personalities, 2020) |
Weaknesses
|
Conflict generally arises due to disagreements such as values, inspirations, ideas, or even desires. A conflict situation may arise within the group due to some of these differences. One way to overcome conflict is through communication and looking towards similarities rather than focusing on differences. Another way conflict may arise is by speaking over, ridiculing those with opposing views rather than being empathetic and having a discussion. Overall, our group is incredibly balanced, and our skills complement each other in many ways. We are aware and thoughtful of each other's differences and each individual brings something different to the table our styles get along which allows us to collaborate effectively despite our weaknesses.
Our group all have very different ideal jobs and goals. They vary both in their scope and in their technical focus. Ali’s role, product manager, focuses more on the management of teams and the direction of products. Technical understanding is important, but communication skills are more important for this particular role. Omer’s role as a senior front-end engineer is in very high demand and is a classic skillset in the development world. It is an essential role in bringing many only platforms to life. Troy’s ideal role as a firmware/hardware engineer ventures into the role of actual hardware, which introduces a new dynamic and requires a completely different skillset. Finally, Mohamed’s role as a security analyst requires a keen and devious mind, as well as the technical skills to back it up to defend systems against potential adversaries.
The Notorious Geeks website Website
The Notorious Geeks Github Repository:
The tools we have been utilising are as follows:
| Tool | Function |
|---|---|
| Microsoft Teams | Video and Voice chat meetings |
| Google Docs | Shared Document Collaboration |
| Instant Messaging/Quick Status updates |
We have been using Microsoft Teams for meetings as we decided during Assignment 2 that Zoom was very limiting and possibly hindering our workflow. While there are many functionalities we are not utilising, we are finding it assists us greatly in our meets and collaboration. We also store some shared documents on our Teams channel, which is a great “one-stop-shop” if you need to quickly check the Rubric of assignment 3 and don’t have a browser open (For example).
Initially we wanted to move away from Google Docs and use Word integration for Microsoft Teams, however we discovered we were really trying to replace Google Docs with something else that had the exact same functionality. Therefore, we decided to stick with Google Docs as it works perfectly for our needs. While Microsoft Teams is extremely useful to have, the ease of access Google Docs Web interface presents is irreplaceable for our needs.
We used WhatsApp much less than in previous Assignments. Although we have used it for meetings when one of our members is unable to get to a PC, we mainly use it for quick status updates and “heads up” messages so we are all aware of everyone’s status and current tasks.
Our Audit trail does not reflect the contribution of our team members, we have been using Google Docs as a platform to collaborate on shared Documents, and then uploading the completed Documents to our Github.
We aim to provide accessibility and growth development in order to help people to find nearest toilets and companies to sell their products in a refreshing way. On the other hand, our goal is to reach millions of people and companies by bringing easy to use applications that are understandable and user-friendly. Eventually we want to revolutionize the usage of toilets and the way companies sell their products.
Flusha is one of a kind application in terms of accessibility and affiliate-marketing. Our application is a mobile app that gives information of nearby free to use toilets based on smart algorithms and community support.
Planning - Since our application is based on accessibility and affiliate-marketing we ought to look at two parameters, how to make our app more informative and easy-use and how to connect smart sales with toilets. We brainstormed about what we should offer to the users and we decided to go to an existing market that has a lot of competition but still wanted to innovate and enhance the way we see and use toilets.
Wireframing - The next thing we have done is to plan the back bones of our application.Wireframing was crucial yet tough to perform and to understand because we needed something that eventually will be usable, simple, beautiful and understandable.First we draw on a piece of paper what is going to be the structure of the application, the main pages included pages like login page, home page, search and recommendations. We planned the positions of each button and image till the small detail as much as we could.We used several types of wireframing softwares like Figma, Wireframe.co and Photoshop but at the end we decided to go with PhotoshopCS6 and IllustratorCS6. The process of converting a drawing to Photoshop was quite hard, nor difficult because everything had to be precise with our idea. We were trying to be collaborative and efficient as much as we can and after several attempts of designing the mockup the outcome was productive, we came with a first translation of our idea and then we all really understood how we were going to develop our application.
Development - The development stage has not been made yet due to limited time scopes but we are planning to execute a solid development approach within the 2nd year of this program. To simplify the application, we would use a major and enhanced development framework, React Native which enables us to create cross-platform development without handling difficult technical issues like platform development, user experience and relevance. React Native gives us the possibility to create a functional product using built-in tools, community support, enriching courses and easy path to learn and it focuses on the frontend side of the application. For the backend we would use NodeJS which also gives us full support from the learning path, understandable documentation and community support. NodeJS and React Native make it possible, by creating user-friendly interfaces, connectivity to the backend side and building unique APIs for further app growth.
Development Cycle - We envision a 3 tier Development cycle, namely “Dev”, “Staging” and “Live”. The “Dev” or “Development” cycle and platform is the first stage. It is in heavy construction and not ready for any external functionality. You can think of it as a “pre-Alpha” state. The “Staging” cycle can be considered analogous to late Alpha, transitioning to Beta. Late in this cycle the product should be considered ready for testing but not ready for any external customers. This is where you have the important functionality completed but expect issues to arise. After refining and testing the product it should be ready to go live. “Live” is the product as it is intended to be released to the public. After passing through Dev and Staging cycles, it is expected to be a complete and customer ready product. Utilising the existing IP address filtering functionality in CentOS we can control connections to the live Node.JS instance via an IP pool. This allows us to control exactly who can connect to the instance while it is in Development and Staging, therefore utilizing AWS as a development environment. The benefits of utilising AWS as a development platform are Twofold. AWS is accessible globally, so if we have robust security measures in place, the development environment can be accessed by our team anywhere. This is especially desirable in 2020 as many people are working from home. We do not have to maintain multiple servers for Development, Staging and Live. The product can be developed on the same server and iterated through Development, Staging and Live cycles without the need to migrate to any other servers. This saves unforeseen configuration issues which can arise from mismatched versions, network configuration and hardware mismatches, and this saves time (which is an expense). Once this instance is available, and basic backend functionality is completed, the Front-end Developer, iOS Developer and Android Developer can start on their respective customer interfaces. The Web front end development will take place on the CentOS instance, while the iOS and Android development cycles will take place on the respective workstations of these Developers. Utilising the built-in emulation facilities in Eclipse and XCode, the iOS and Android Developers will be able to iterate from Development to Staging cycles before trialling on the end point hardware (Android and iOS based handsets respectively).
Enhancing User Experience and Accessibility - As we defined in our aims and goals of this project, user experience and accessibility is one of our foundations for this product. In order to understand consumers and companies we would need to understand better how they use it in real time and get insight on what can we do better within the usage of the app. We will present the idea and vision of our company and how we can solve a better toilet finding yet enhance sales conversions within the same use. We would present the designed app and ask if they can understand how it might work and eventually do our homework based on relevant feedback. In addition, after we got the information we need to approach a better user experience and we will use softwares like Axure and Adobe XD in order to insure we will have not only a design to show our clients but a proof of concept (POC) and how everything should work after the development stage. We will implement animations, enhanced typography and colors for accessibility and easy to use user experience paths so that people can understand how to use the app within the first time they download it.
Behind the idea of Flusha - As young entrepreneurs, we want to change the world, innovate and solve problems that we think can enhance humanity. Everything began right after Ali, Omer, Troy and Mohammed discussed a project for the second assignment we were assigned. It took us weeks to come up with a revolutionizing idea that can potentially help hundreds of millions of consumers. At first, we thought the idea was silly and unhelpful. Although it was silly, we continued with that train of thought and came to realise we may be onto something that is genuinely helpful. We feel we differentiate ourselves from similar applications due to the decisions we have made in the aspects of engineering, design and business development. We progressed with our idea and currently we are working on the UI/UX which might take us a couple of months to finalize before we get feedback from other designers and UX consultants. Afterwards we plan to develop an MVP in order to reach out investors and expand our idea further.
Our aim as a team is to create a community and user experience that provides as much value as possible. The goal is often an “MVP” - minimum viable product. This will certainly be our goal when it comes to approaching investors. But when it comes to market, we want to create a minimum valuable product. This means releasing something not when it’s ready to be used, but when it’s ready to create a memorable and valuable experience for our customers. The application has a few moving pieces, so it is important to be precise but not overly rigid in our approach, as things can change. The application has 3 main parts, each of which has minimum required features, listed below.
| User Application | Host Application | Host Web Portal |
|---|---|---|
| Create an account with email, Gmail, Facebook, or mobile number. | Register as an owner of an establishment/lavatory. | Register as an owner. |
| View local lavatories as tags/pins on a map display allowing pinch zoom and radius search. | Update lavatory as “recently cleaned/last cleaned at” | More complete and robust lavatory/establishment management features |
| Information display when tapping on a tag: Name, rating, rate, favourite, contact host, offers, mother friendly, accessibility features, opening hours, etc. | Offer and manage promotions which can be redeemed through the user application. | Create and manage promotional offers. |
| Keyword search for particular establishments and ability to view as a list or map display. | Manage lavatory details to ensure information is accurate. | - |
| Tags glow when there are marketing offers available. | - | - |
| Click on offers in order to view and redeem. | - | - |
| Navigation to lavatory through Google Maps | - | - |
The above are the core features that are critical to providing the best customer experience as possible. Users have certain expectations when they use applications and it is important to not undermine those expectations, as this can influence micro-decisions and split second thoughts that can ultimately mean the difference between continuing to use the app or not. Maps have a slippery slope of getting cluttered with different overlays, landmarks, features, etc. In our case we are focusing entirely on displaying commercial/public lavatories that are open to the general public or customers. We will not develop inhouse navigation as will leverage what is available through Google Maps integration. Our initial release will be in Melbourne, with a gradual rollout to other major cities. Once we have traction, we can then quickly scale to other major cities around the world. We don’t need to “complete” a country before going overseas. For example, London would be a higher priority than regional Victoria. As development progresses, new ideas and features will naturally arise, and it will be important to scrutinize these ideas and determine if they hold up to the standard of our minimum valuable product.
| Product Name | Version req. | License Type | Notes |
|---|---|---|---|
| Ubuntu workstation | 18.04 LTS | GPL / Open Source | Package managed Distribution |
| Vim (IDE) | 7.4 | GPL / Open Source | Included in modern distributions. |
| SSH Client | 7.6 | GPL / Open Source | Available via Apt |
| Chrome | 78 Stable | Freeware | Available via Apt |
| RDP (Remmina) | 1.2 | Copylefted Libre | Available via Apt |
| Thunderbird (Email) | 60 stable | MPL 2.0 | Available via Apt |
The hardware requirements for the Backend Developer are very minimal, as with many Developers all that is required is a modern workstation with a suitable set of applications. A Linux based Operating System is not essential, but a very suitable choice for the initial configuration and administration of a Linux based Application Server. Many of the required tools such as an IDE (Vim with syntax highlighting), SSH Client, Remote Desktop Client (Remmina) are bundled with Ubuntu and are ready to work straight “out of the box”. Many applications are available via APT, the Ubuntu packaging system and are covered by GPL/GNU or Open Source Software Agreements, and free to use for commercial purposes.
| Product Name | Version req. | License Type | Notes |
|---|---|---|---|
| Windows 10 | Build 1909+ | Retail | $225.00 AUD from Microsoft. |
| VS Code | 1.45 | MIT License Agreement | Free Download |
| Adobe Illustrator | CC 2020 | Monthly Subscription | $29.99 AUD Monthly |
| Adobe Photoshop | Cc 2019 (20.0) | Monthly Subscription | $29.99 AUD Monthly |
| FileZilla (FTP/SFTP etc) | 3.48.0 | Retail | $25.45 AUD |
| Microsoft Outlook | Build 2004+ | Retail | Component of 365 |
| Microsoft Outlook | Build 2004+ | Retail | Component of 365 |
| Microsoft Office | Build 2004+ | Retail | 365 Suite $27.50 AUD a month |
| DBeaver (SQL Client) | 7.0.5 | Apache Software License | Free Download |
| Chrome | 78 Stable | Freeware | Free Download |
| Firefox Developer Edition | 75.0 | Mozilla Foundation EULA | Free Download |
The hardware requirements for the Web Developer/ Front End Developer are rather moderate, however, a modern workstation is recommended to run resource intensive applications such as Adobe Photoshop and Illustrator. Web Developers will often need to install multiple versions of browsers to see how the “pages are rendered” on different platforms.
| Product Name | Version req. | License Type | Notes |
|---|---|---|---|
| Apple iMac | macOS Catalina | APSL / Apple EULA | macOS is required for iOS development |
| XCode | 11 | Freeware / Open Source | Required to publish iOS applications |
| Microsoft Outlook | 16.37 | Retail | Component of 365 |
| Microsoft Office | 16.37 | Retail | 365 Suite $27.50 AUD a month |
| Adobe Illustrator | CC 2020 | Monthly Subscription | $29.99 AUD Monthly |
| Adobe Photoshop | Cc 2019 (20.0) | Monthly Subscription | $29.99 AUD Monthly |
To develop applications for the iOS platform, using an macOS based system is recommended. Xcode is only available on the macOS platform and is required to certify and provision the iOS application with the Apple Store before being approved for distribution. While there are other solutions available to run macOS on non-Apple hardware, this is unsuitable for a commercial product.
| Product Name | Version req. | License Type | Notes |
|---|---|---|---|
| Windows 10 | Build 1909+ | Retail | $225.00 AUD from Microsoft. |
| Eclipse IDE | 64bit 2020-03 | EPL | Free Download |
| Microsoft Outlook | 16.37 | Retail | Component of 365 |
| Microsoft Office | 16.37 | Retail | 365 Suite $27.50 AUD a month |
| Adobe Illustrator | CC 2020 | Monthly Subscription | $29.99 AUD Monthly |
| Adobe Photoshop | Cc 2019 (20.0) | Monthly Subscription | $29.99 AUD Monthly | FileZilla (FTP/SFTP etc) | 3.48.0 | Retail | $25.45 AUD |
The hardware requirements to develop an Android application are very minimal, and can be accomplished on almost any hardware platform. Any modern Workstation that is capable of running the selected IDE (Eclipse) and Adobe Illustrator and Photoshop is suitable for this task.
Platform Requirements (External facing)| Product Name | Version requirements | License Type | Notes |
|---|---|---|---|
| Amazon AWS | EC2 | AWS Customer Agreement | Server Platform for Delivery to Customers. |
| CentOS | 8.0 | Open Source / GPL | 8.0 is latest LTS |
| mySQL | 8.0 | Open Source / GPL | Current Stable release |
| Node.js | 10 | BSD License | Current Stable release |
(Amazon Web Services) is a popular hardware platform for virtual servers, as you are able to start small with a low overhead cost and scale up if needed. CentOS is a Linux distribution focused on a Server role, and contains SELinux, which is a Linux kernel module that allows you to implement custom security policies. Node.js is utilised as an application server (Javascript) with MySQL (SQL based Database).
| Product Name | Version requirements | License Type | Notes |
|---|---|---|---|
| Amazon AWS | EC2 | AWS Customer Agreement | Server Platform for Internal BAU (Business as usual) |
| CentOS | 8.0 | Open Source / GPL | 8.0 is latest LTS |
| Atlassian Jira | 7.4 | Atlassian Software Agreement | Project and Support tracking |
| Atlassian Confluence | 7.4 | Atlassian Software Agreement | Internal Knowledge Base/ Document collaboration |
Jira and Confluence are invaluable tools to track problems, tasks to be completed and document internal support methods of practice and procedures.
| Technology | Team member Experience |
|---|---|
| Ubuntu Workstation: | Troy has used Ubuntu as a workstation in a professional capacity when he worked as a Sys Admin. Troy started using Linux in 1997, professionally in 1999, and is very familiar with many Distributions. Ali has 5 years experience using Ubuntu as a personal computer and creating scripts in Perl and bash. Omer has 1 year experience using Ubuntu for script creation in Bash. Mohamed has no experience with Ubuntu Workstation |
| Vim: | Troy has used Vim and Vi since first using Linux in the late 90’s Ali has some exposure to Vim but has not used it in a professional capacity. Omer has no experience with Vim Mohamed has no experience with Vim |
| Ssh Client: | Troy has used many different types of Ssh client to remotely connect to servers as part of his role as a Sys Admin. Ali has exposure to ssh by having to connect to university servers remotely during his studies. Omer used SSH to connect to servers as part of his development job. Mohamed has no experience with Ssh Client |
| Chrome: | Troy has used Chrome since it was released to the public in a professional and personal capacity Ali uses Chrome as his main internet browser. Though he has some experience in development, he has not done any kind of web or extension development. Omer is currently using Chrome as his main preferences for browsing. Mohamed is currently using chrome and has been using chrome for several years . |
| Remmina (RDP Client): | Troy has used Remmina to connect to Windows Servers and Workstations remotely as part of his role as Sys Admin. Ali has no experience using Remmina. Omer no experience using Remmina. Mohamed has no experience with Remmina. |
| Thunderbird: | Troy uses Thunderbird as his Email client when using Linux as a workstation, and has done since 2004. Ali has no experience using Thunderbird. Omer has no experience with Thunderbird. Mohamed has no experience with Thunderbird |
| Windows 10: | Troy has used Windows 10 on his 3 personal computers since release. Ali used Windows 10 and personally and professionally, but has transitioned to a Mac environment. He maintains a Windows 10 machine for miscellaneous use. Omer currently using Windows 10 on most of his machines (laptop and PC) Mohamed is currently using windows 10 on his laptop and has been doing so for several years. |
| VSCode: | Troy has no experience with VSCode Ali has no experience with VSCode. Omer has experience with VSCode as he uses it for his development job Mohamed has no experience with VSCode |
| Adobe Illustrator: | Troy has minimal experience with Illustrator. Ali has no experience with Illustrator. Omer has experience with Adobe Illustrator as he uses it for his development job Mohamed has no experience with Adobe Illustrator |
| Adobe Photoshop: | Troy used Adobe Photoshop in 2001 for a University assignment and has not used it since. Ali has no experience with Photoshop. Omer has experience with Adobe Photoshop as he uses it for his development job Mohamed has used Adobe photoshop in 2002 for recreational purposes and has not utilised the application since that time. |
| FileZilla: | Troy has used FIleZilla for file transfer (SFTP/FTP) in his role as a System Administrator. Ali has no experience with FileZilla. Omer has experience with FileZilla as he uses it for his development job. Mohamed has no experience with FileZilla |
| Microsoft Outlook: | Troy has used Outlook for Email and Appointments when in a Windows Environment in multiple roles. When Troy would use Linux as a workstation OS, he would often use a Windows Virtual machine with the express purpose of only running Outlook on it. Ali has used Outlook in a professional and educational setting over the last 10 years. Omer has experience with Adobe Illustrator as he use it for his development job and personal use. Mohamed uses Microsoft outlook regularly keeping track of messages sent and has been doing so for the past 10 years. |
| Microsoft Office: | Troy has used Word frequently in the last 30 years and is less familiar with other components of the Office suite. Ali uses the MSO suite for general personal and professional use. Omer has used Microsoft office products but switched to Google products. Mohamed uses Microsoft office regularly to create policy and procedures, write up assignments and even send in timesheets to employers. |
| DBeaver: | Troy has not used this graphical DB tool, however he has used many others in Windows and Unix environments. Troy is very familiar with administration of SQL DB instances using multiple tools, text based or graphical. Ali has no experience with DBeaver. Omer has no experience with DBeaver Mohamed has no experience with DBeaver |
| Firefox Developer Edition: | Troy has used Firefox Developer Edition previously when assisting a colleague in his role as level 2 Support. Ali has familiarity with Firefox Developer Edition and it’s uses but has not had to make use of it. Omer has used Firefox for personal uses but now only uses it for his development job. Mohamed has no experience with Firefox Developer Edition |
| Apple iMac: | Troy has owned 2 Apple laptops and is familiar with macOS, however, Troy has used Unix based operating systems in a professional and personal environment since 1994. Ali currently uses a MacBook Pro as his daily driver for personal, educational, and professional use. Omer owns a Macbook Pro but uses it only from time to time for work purposes. Mohamed does not use apple iMac and knows limited amounts about apple iMac |
| XCode: | Troy has not used XCode. Ali does not use XCode for development. Omer used XCode for experimental purposes. Mohamed not used XCode |
| Eclipse IDE: | Troy uses Eclipse IDE for his Java assignments at RMIT, and has assisted colleagues to set it up in the past, in his role as Support person. Ali has used the Eclipse IDE during his time at university (UNSW) for various Java projects. Omer has not used Eclipse IDE yet. Mohamed has used Eclipse IDE for his java assignments at RMIT and has built various monolithic , modular and object oriented programs through the platform. |
| Amazon AWS: | Troy has not used AWS, however he has multiple years experience using and administering Virtual servers, hosts and guests. Ali has not used AWS. Omer used AWS Cloud for development and integration purposes. Mohamed has not used Amazon AWS |
| CentOS: | Troy in his role as Sys Admin for a payment company, has administered multiple instances of CentOS application, web and database servers in a live and mission critical environment. Ali has not used CentOS. Omer has no experience with CentOS. Mohamed has no experience with CentOS |
| mySQL: | Troy has administered multiple instances of mySQL servers containing sensitive information such as Credit card and Personal Customer information in a live environment for Optus, iiNet and other large Australian IT Companies. Ali has studied databases at university and has had to make use of this skill in various subjects during his studies. Omer had to use mySQL only for work purposes, now he uses MongoDB. Mohamed has no experience with mySQL |
| Node.js | Troy has not used Node.js and has no experience with this application. Ali has no experience with Node.js Omer has experience with NodeJS while building web applications and connecting APIs. Mohamed has not used Node.js and has no experience with this application |
| Atlassian Jira: | Troy has administered multiple Jira instances in his role as Sys Admin, and has used it to track Support issues in his role as a System Administrator Ali has used Jira professionally for development and customer support purposes. Omer has used Jira for work purposes and personal uses. Mohamed has not used Atlassian Jira and has no experience with this application |
| Atlassian Confluence: | Troy has administered multiple Confluence instances in his role as a System Administrator, and has used it to write Technical Documentation and author Methods of practice for various platforms. Ali has used Confluence in a professional setting to refer to internal documentation. Omer has not used Confluence because of better alternatives. Mohamed has not used Atlassian and has no experience with this application |
There will be various types of testing we will incorporate into our development. We plan on incorporating standard software testing methodologies into our development cycles. This includes unit testing, integration testing, system testing, and acceptance testing. Success is measured based on passing each of the test cases. It will be the responsibility of the team to build and expand on each stage of testing as we develop the product, listing test cases and corner cases as we go. Testing will be both programmatic and manual. We will conduct manual user testing in-house, inviting friends, family, and people we know to be part of our testing, and compensate them with a free lunch. We can leverage services like UpWork to find manual testers overseas for $10-$15/hour. We would be able to build a cost effective team of around 5 testers based in Asia for timezone purposes. We will not need the testers full-time, but when we do require them it will be in short bursts of high volume testing. These testers would ideally have experience manual testing and using tools such as Jira. As we begin to rollout the product, we will begin with an open beta in a localized area, such as the Melbourne CBD. To ensure we can deal with a large volume of users, we will be conducting load testing on our application and servers. Although there is a risk in deploying an app such as Flusha in a high volume area, a large community is essential to the operation of the app.
| Week: | Goals |
|---|---|
| Week 1 |
- Get to know the team. Introduce ourselves, share our experience and why we are doing the course. - Brainstorm ideas |
| Week 2 |
- Determine very high level overview of the app and the features - Figure out what the value proposition is and what problem we are trying to solve in order to give the product direction |
| Week 3 |
- High level overview of what technologies are needed to build an application like this
- Start researching what kind of resources we need, i.e. developers, tools - Hand in Assignmet 2 |
| Week 4 |
- Begin consolidating research and information into a finalised format and plan
- Have a concrete idea of a project plan, required resources including staff and infrastructure - Product concept is finalized with granular features. |
| Week 5 |
- Create user stories and high fidelity mockups in photoshop - Create a timeline of the project and plan out minute details such as testing, scope & limits, risks, exactly who we need to hire and start putting this all together in a report. |
| Week 6 | - Finalise report and hand in for review |
| Week 7 |
- Interview Team members - Confirm Hires - Provision the infrastructure (AWS) |
| Week 8 | - Conduct research and usability testing on our current mockups with friends, family, and any business owners we know. |
| Week 9 |
- Iterate on the findings of our research from the previous week. - Finalise high fidelity mockups and get them ready for mobile and front end developers |
| Week 10 |
- Backend Developer starts configuration of AWS instances - Front end, iOS and Android Developers join the team later in week and get settled at their workstations, come to terms the project |
| Week 11 |
- AWS Basic Configuration complete - Backend Developer starts developing the AWS instance for the App - Frontend, Android and iOS Developers start on assets and basic App infrastructure |
| Week 12 |
- Meeting to ensure everyone is on task - Backend Dev working on Node.JS instance, ensuring MySQL structure is efficient and secure. - Frontend Dev working on Web assets and internal framework - Android Dev working on internal assets iOS Dev working on internal Assets |
| Week 13 |
- Backend Dev has MySQL instance and Node.JS instance ready for staging. - Backend Dev and External team is completing a basic security audit of AWS instance and report is expected next week. - Front end Dev has completed basic testing and is |
| Week 14 |
- Backend Dev has completed early phase of development, enough for basic connections and testing. - Front end Dev has completed very rough framework that will be developed into Flusha Web - Android Dev has completed very rough framework that will be developed into Flusha Android. - iOS Dev has completed very rough framework that will be developed into Flusha iOS |
| Week 15 |
- Development meetings to ensure all targets are met. - At this point MySQL Database structure is confirmed and is ready for testing and populating with test data. - Front end Dev should be able to demonstrate connections to the Application server are working - Android Dev should be able to demonstrate connections to the Applications server are working. - iOS Dev should be able to demonstrate connections to the Application server are working - Results of Second Security Audit to be actioned in week 16. |
The software tools we are using for the project are relatively easy to use and straightforward as far as the engineering is concerned. Our main risks come in 2 forms. One is the effect of a large number of users and ensuring our servers and architecture can handle the scale and growth. This is somewhat a generic risk to any marketplace or gig application, and is not something specific to Flusha. Another risk comes in the form of the potential negative impact our application can have on businesses. We have a rating system, so there is the risk that users will naturally go to bathrooms with the highest cleanliness ratings. This can affect businesses in multiple ways. Firstly, there is the impact of increased foot traffic and wait times outside bathrooms, with establishments having people use bathrooms who may not necessarily be customers. This creates unnecessary congestion in businesses. The other risk is bathrooms with “lower” ratings creating a negative perception of those businesses and potentially deterring business.
All team members will use Teams and Email to communicate non-urgent information, as it is an easy way to share documents and discuss issues that are not urgent enough to demand a face to face meeting or interrupting your work. During a normal work week, we will have weekly meetings, for an hour after lunch on Tuesdays. This will be face to face if possible, however Video or Voice chat is acceptable, due to the possibility of team members working remotely. All team members will in turn discuss their current action items and any outstanding issues that may warrant a discussion. These meetings may go longer if needed, during the early stages it might be useful to have longer meetings to make sure everyone knows what all team members are doing and so everyone is “on the same page”. During periods of heavy activity, it may be warranted to have longer or additional meetings, however these should be focused on action items and as brief as possible. With such a small team, we will focus on being adaptable and make sure we are always available to other team members on voice (Teams) or text (email and Teams) if possible.
| Back-end developer | |
|---|---|
| Key Technical Skills: | 5+ years Linux Experience (CentOS highly regarded). Cloud experience with Amazon Web Services. SQL experience is desirable. Node.JS experience. Full stack development experience is highly regarded. SysAdmin experience is highly regarded. 8-10 years industry experience in a similar role. Skills: HTML5, Node.JS, MySQL, AWS, Linux, SELinux, Jira, Confluence Other relevant skills:Self-Motivated with time management skills to work to deadlines Ability to work with a small tight knit team Strong leadership skills Excellent communication skills. |
| Front-end developer | |
|---|---|
| Key Technical Skills: | 5+ years’ experience in building responsive web applications. Have an understanding regarding implementation of good UI/UX in web development. Work directly with Back-end developers to conceptualise, build, test and release engaging Web apps. Strong HTML5, CSS, Node.JS and Javascript Experience. 3+ years experience in a similar role. Skills: HTML5, CSS, Javascript, Node.JS, MySQL, Adobe CS, Linux Other relevant skills: Self-motivated with time management skills to work to deadlines. Ability to work with a small tight knit team. Excellent communication skills. |
| Mobile developer (Android) | |
|---|---|
| Key Technical Skills: | 5+ years’ experience as an Android Developer. Experience from concept, design, build, deployment, testing, release to Google Play store and support essential. Work directly with Back-end developers to conceptualise, build, test and release native Android apps. Create compelling device specific user interfaces and functions. Understanding of Android best practices, including design patterns, frameworks, coding standards & practices, quality assurance and deployment. Skills: Android SDK, Native React, Java Other relevant skills: Self-motivated with time management skills to work to deadlines. Ability to work with a small tight knit team. Excellent communication skills. |
| Mobile developer (iOS) | |
|---|---|
| Key Technical Skills: | 5+ years’ experience as an iOS Developer. Experience from concept, design, build, deployment, testing, release to Apple store and support essential. Work directly with Back-end developers to conceptualise, build, test and release native iOS apps. Create compelling device specific user interfaces and functions. Understanding of Apple & iOS best practices, including design patterns, frameworks, coding standards & practices, quality assurance and deployment Skills: iOS SDK, Native React, Swift Other relevant skills: Self-motivated with time management skills to work to deadlines. Ability to work with a small tight knit team. Excellent communication skills. |
What worked well in the group is how well the team was able to collaborate effectively and the time and effort put into the presentation of the application. The group learned from previous assignments and adapted to a more suitable platform for collaborating information. We went from utilising zoom to Microsoft teams. This allowed the team to increase in efficiency and collaborate for longer periods without the subtle interruption. In this assignment I have noticed everyone had a common trait, everyone was not only willing but sacrificed their personal time working late to get things done. This trait was a surprise because it was not only found in a single individual but throughout the team. What had caught me aback in this assignment is the details required to complete sections of the assignment that were perhaps overlooked in the first two or three meetings we had. I would say after trial and error from assignment 1 to assignment 2 there were not many aspects to improve except perhaps to utilise more tools and find more innovative ways to reach out to consumers as innovation is something that has no bounds. I have learnt throughout assignment 2 and 3 how important it is to work as a team in group settings and communication being a key component for groups to work.
The north star of our team was our open and free-flowing communication. Different tools enable different types of communication. We opted to using WhatsApp as our “main” communication and Microsoft teams as our more formal platform for posting documents and critical information. WhatsApp enabled us to easily coordinate and exchange ideas. It was unexpected to see the team’s balance of egos. That is, we quickly recognised great ideas for what they were, and the team as a whole was happy to adopt them. It was very much a meritocracy. Our ease of communication made up for the fact that our project management management skills were lacking. This is definitely an area of improvement. We were good at delegating tasks and knowing who was doing what - and this could work well in a small team working on a small project. However, if we are trying to build a product and a business, this process is not scalable. We need to incorporate project management tools into our workflows. Our work is mostly recorded in our conversations over teams and WhatsApp. Although we didn’t have a formal log, our conversations reflect our activity well in that there is a clear delegation of tasks as well as consistent and practical conversations throughout the project process. After going through this process with the group, I have a newfound appreciation for when people say “communication and planning” are key. When you are working solo, you have all the information in your head and can make decisions based on that information. When you work in a group, your team does not know what you are thinking unless you tell them. Therefore, it is essential to communicate your thoughts and ideas so everyone can act on that information accordingly.
In my opinion, this assignment went smoothly only because of the perfect collaboration and outstanding teamwork. Everything was efficient, even the hard parts we struggled to handle. In this assignment I have a true sense that we became stronger in aspects of leadership, getting inside time and role scopes, and definitely the communication strategies. Furthermore, this assignment was quite similar and different in a lot of ways from previous assignments, putting more of our opinion, vision, and motivation for our mobile app was quite refreshing. The surprising thing was how collaborative we were even after the second assignment. Personally I learned and gained knowledge from this assignment. We used various types of communication tools such as Microsoft Teams, WhatsApp different from Assignment 2 that we also used Zoom but we realized it was not sufficient for our team and for this assignment. In addition to that, I might suggest different management approaches like Agile using tools like Trello that we can 100% track and solve our assignment faster and make it much more efficient. The overall work was amazing and as I mentioned in all of my feedback I would definitely like to work with this team in the near future.
I feel everything went well during this assignment, we all pulled together as a team and worked towards common goals, just like we did in the previous assignment. I feel that we could have improved our workflow, however, it is surprisingly difficult to coordinate a group assignment with members from both sides of Australia and the World, especially when we all have responsibilities outside of study. We did improve upon our methodology from Assignment 2, however there is always room for improvement and gains to be made. I found it surprising how well we work together, even after the small break in between finishing Assignment 2 and starting on Assignment 3. We adapted to the new workflow, and while we had some minor teething problems, we soon hit the ground running. I learned that everyone in the group is very capable and often has hidden skills that we did not know about. Being much older and having lots of industry experience, I expected to be the team member with most knowledge in most areas, but this was not always the case. I really respect my fellow team members and enjoy working with them greatly.
All the active members of the Notorious Geeks feel that everything went very well. Our communications have improved since we moved away from Zoom to Teams for meetings, and the ability to store documents and notes on Teams and have them accessible for all, has helped our productivity greatly. We still use WhatsApp for quick updates, and that works well for us, for example, if someone is going to be late to a meeting because of an unforeseen responsibility they can quickly update the group from their Mobile. All four members of the Notorious Geeks have confirmed they feel we have become a “well oiled machine” and are very capable of any task that is asked of us.
What could be improved?We discovered during the first group assignment (Assignment #2) that our communication methods (Zoom in this case) were not suitable for our needs and made changes to move over to Microsoft Teams. While we utilise some of Teams functionality for Voice meetings and sharing documents, we all agree we could have spent more time learning its advanced features, such as the GitHub bot and Word integration. We decided we were happy to use some of its basic features, but agree we could have improved our workflow if we were able to utilise some of its more advanced features.
What was surprising?We found that it was very surprising how much time can be spent on the small details. For this assignment we found we had to be more agile and able to react quickly when a team members workload is discovered to be greater than anticipated prior to starting it. For example, the team member responsible for the Tools and Technology section had determined it would not take a great about of time, as they have lots of personal experience in this field, however it still was very time consuming and another team member graciously picked up some task from their “To-do list” so they were able to complete it to the high standard that we expect from each other.
What have you learned about Groups?We have all relied on each other much more during this assignment, as we now have worked together for a substantial amount of time. When there were personal issues that arose, we were more able to articulate our needs and work together to make sure our group work was not impacted, without feeling anxious or bad about the situation. We feel we really have become a team and enjoy working together greatly.


Frameworks built on Express
{% include community-caveat.html %}
Several popular Node.js frameworks are built on Express:
-
Feathers: Build prototypes in minutes and production ready real-time apps in
days.
-
ItemsAPI: Search backend for web and mobile applications built on Express and
Elasticsearch.
-
KeystoneJS: Website and API Application Framework / CMS with an auto-generated
React.js Admin UI.
-
Poet: Lightweight Markdown Blog Engine with instant pagination, tag and
category views.
-
Kraken: Secure and scalable layer that extends Express by providing structure
and convention.
-
LoopBack: Highly-extensible, open-source Node.js framework for quickly creating
dynamic end-to-end REST APIs.
-
Sails: MVC framework for Node.js for building practical, production-ready
apps.
-
Hydra-Express: Hydra-Express is a light-weight library which facilitates building
Node.js Microservices using ExpressJS.
-
Blueprint: a SOLID framework for building APIs and backend services
-
Locomotive: Powerful MVC web framework for Node.js from the maker of Passport.js
-
graphql-yoga: Fully-featured, yet simple and lightweight GraphQL server
-
Express Gateway: Fully-featured and extensible API Gateway using Express as foundation
-
Dinoloop: Rest API Application Framework powered by typescript with dependency
injection
-
Kites: Template-based Web Application Framework
-
FoalTS: Elegant and all-inclusive Node.Js web framework based on TypeScript.
-
NestJs: A progressive Node.js framework for building efficient, scalable, and
enterprise-grade server-side applications on top of TypeScript &
JavaScript (ES6, ES7, ES8)
-
Expressive Tea: A Small framework for building modulable, clean, fast and descriptive
server-side applications with Typescript and Express out of the box.


Organisation {{ organisation.name }}
{% if organisation.feature %}
{% if points %}
Boundary
{% include 'partials/_publication-list.html' %}
{% elif organisation.publications %}
{% include 'partials/_publication-list.html' %}
{% endif %}
Lambeth contaminated sites
{% for key in features_by_type.keys() %}


Definition at line 901 of file MKL25Z4.h.
Definition at line 902 of file MKL25Z4.h.
Definition at line 903 of file MKL25Z4.h.
Definition at line 904 of file MKL25Z4.h.
Definition at line 913 of file MKL25Z4.h.
Definition at line 914 of file MKL25Z4.h.
Definition at line 911 of file MKL25Z4.h.
Definition at line 912 of file MKL25Z4.h.
Definition at line 907 of file MKL25Z4.h.
Definition at line 908 of file MKL25Z4.h.
Definition at line 909 of file MKL25Z4.h.
Definition at line 910 of file MKL25Z4.h.
Definition at line 905 of file MKL25Z4.h.
Definition at line 906 of file MKL25Z4.h.
Definition at line 916 of file MKL25Z4.h.
Definition at line 917 of file MKL25Z4.h.
Definition at line 918 of file MKL25Z4.h.
Definition at line 919 of file MKL25Z4.h.
Definition at line 920 of file MKL25Z4.h.
Definition at line 921 of file MKL25Z4.h.
Definition at line 925 of file MKL25Z4.h.
Definition at line 926 of file MKL25Z4.h.
Definition at line 923 of file MKL25Z4.h.
Definition at line 924 of file MKL25Z4.h.
Definition at line 894 of file MKL25Z4.h.
Definition at line 892 of file MKL25Z4.h.
Definition at line 893 of file MKL25Z4.h.
Definition at line 890 of file MKL25Z4.h.
Definition at line 888 of file MKL25Z4.h.
Definition at line 889 of file MKL25Z4.h.
Definition at line 896 of file MKL25Z4.h.
Definition at line 897 of file MKL25Z4.h.
Definition at line 898 of file MKL25Z4.h.
Definition at line 899 of file MKL25Z4.h.


A Date Uploader DRE Extension...
Please upload your medical record here. Acceptable formats are:
Great! We've got your record, now we need to login to DRE
Upload Complete


Welcome to breakout!
This game of immense skill and talent requires YOU to break through the alein fortress and save the world!
David Browning
2017


Project Manager, Backpacker, Photographer
Jean Huang is an experienced project manager with a demonstrated history of working in the information technology and services industry. Skilled in Communication, International Business, Management, Business Process Improvement, and Time Management. Strong program and project management professional with a Bachelor's degree focused in Information Management from National Taiwan University.
Taipei, Taiwan
Email: jinghuangtw@gmail.com


class ImageView2 extends QiniuFop
Methods
|
__construct()
|
||
|
reset()
|
||
|
quality($quality)
|
||
|
crop($crop = true)
|
||
|
longAndShortEdge($long, $short)
|
||
|
widthAndHeight($width, $height)
|
||
|
cover()
|
||
|
contain()
|
||
|
format($format)
|
||
|
interlace($bool)
|
||
|
__toString()
|
Details
at line 37
public
__construct()
at line 41
public
reset()
at line 55
public
quality($quality)
at line 60
public
crop($crop = true)
at line 65
public
longAndShortEdge($long, $short)
at line 72
public
widthAndHeight($width, $height)
at line 79
public
cover()
at line 84
public
contain()
at line 89
public
format($format)
at line 94
public
interlace($bool)
at line 120
public
__toString()


Dennis Kamau K.is an apt and avid web developer specilised
in front-end web development.
I am currently at moringa school furthering my studies in the same. I studied web-development at Moringa-school where i completed
Moringa prep on the 25th of july 2018 and began core classes on 6th august of 2018.
I play basketball for fun.
I also like swimming and skateboarding
This project was done precisely using html, css and bootstrap. It is a mimick of what a restaurant website would look like
ViewThis project was done in purely javaScript, Html and css.It lets users to play and roll dice in turns an gather points
ViewWas done in entirely AngularJS.Users get to post quotes ang get upvotes and downvotes from other users
View


Back
My 5 Songs I enjoy
Rank
Artist
Song
1
Yung Gravy
Flex on christmas
2
Travis Scott
Goosebumps
3
J.cole
No role models
4
Post malone
Jackie Chan
5
Yung Gravy
Flex season
Previous
Next


Please log in
Access Code:
Verify Code:
Analysis of Results
Axis
Amplitude (mm)
Frequency (Hz)
X
Y
Z
Roll
VistA RCP
VistA RCP demonstrator
Logged in as
Select Patient
Select Patient
Patient Name
Get Details
X
Add Allergy
Reactant
Observed
Historical
Symptoms
Comments
submit here
Patients By Dept.
Patients by Age
___________________________________
Patient Demographics
Reasons for Contact
Presenting Complaints/ Issues
Family History
Problems,Issues & Diagnoses
Procedures
Investigations & Results
Lab Tests
Vital Signs
Tremor Readings
Medications
Allergies & Adverse Reactions
Safety Alerts
Plans & Requested Actions
Close
Patient Demographics
Name
Date of Birth
Age
Sex
Ethnicity
NHS Number
Other Identifier
Location
Participation in Research
Contacts
Presenting Complaints
Diagnoses
Procedures
Lab Tests
Vital Signs
Problems and Issues
Medications
Tremors
Recording will begin 3 seconds after clicking the Start button
Allergies
Safety Alerts
System Alerts


--- title: "About R Actuary" author: "Andy Merlino" ---
RActuary develops open source packages and educational material to facilitate actuarial analysis in R. RActuary is a project by Tychobra, LLC.
R is a powerful platform for data analysis, and it continues to improve. We believe R’s current capabilities, its rate of improvement, and its ability to adapt to the changing data science landscape make it ideal for the future of actuarial analysis. You can get a sense of the acceleration of innovation in R when you look at growth in packages on CRAN.
CRAN was created in 1997, so it took 10 years to get to 1,000 packages in 2007 and 10 more year to get to 10,000 packages in 2017. The number of packages on CRAN is doubling every 3 years. Will CRAN have 100,000 packages in 2027?
Most actuaries think R is interesting, some actuaries even use R regularly, but as of 2017 it is rare to find an actuary who uses R (or any programmed data analysis) more than he or she uses Excel.
By transitioning more of our analyses to R we can unlock the ever expanding power of the R ecosystem. We just need to build out the tools and spread the knowledge. Major improvments are within our grasps.
The largest and most immediate improvements to actuarial analysis can be made by using R to generate reports, communicate via the web, and work in reproducible workflows. To help actuaries use R efficiently, we create open source R packages and projects that focus first on practical actuarial analysis (such as report creation) and second on advances in actuarial modeling.
We use Rstudio’s products and packages and we try to emulate the Rstudio approach to data science. If you are not familiar with Rstudio, we highly recommend the resources on their website.
We are just getting started, but would love your feedback. Please check us out on GitHub and let us know what you are up to: andy.merlino@tychobra.com


{% extends 'base.html' %} {% block content %}
Don't have an account? Register here.
Forgot your password? Head over here to reset it.


Videos that introduce you to your future customers
At Studiotale, we create unique, handcrafted videos that link ideas to emotions, connect brands to audiences and help you get where you need to go.
At Studiotale, we create unique, handcrafted videos that link ideas to emotions, connect brands to audiences and help you get where you need to go.


Hi, my name is Ian! I am a Senior Software Engineer at Seequent where I am a core developer on a web visualization library using three.js. I currently have an interest in Computer Graphics, Web Assembly, and Machine Learning.


This is an interactive visualization tool for the
yellow taxi flows in New York City in May 2016 — by location and by time. The map is divided into "Neighborhood Tabulation Areas" (NTAs) and the colors show density of pickups, dropoffs, their difference, etc. The data is from the
NYC Taxi & Limousine Commission (TLC). © 2017 Victoria Lin, Zhe Liu, Costis Maglaras, Aruna Prasad, Georgina Davis, Cyndia Yu


Financial insecurity is the number one reason survivors of domestic violence remain in or return to abuse. In order to break the cycle of violence, we must remove obstacles to financial security for survivors. Our team has developed an empathy and awareness-building calculator. This interactive application will help raise awareness and understanding of what it really takes to leave behind that life.
 Even after leaving, many return to the violence due to financial destituion.
According to a recent CDC study, an estimated 99% of domestic violence cases involve financial abuse.
In the same study, it costs female abuse survivors an average of $104,000. CDC


It is not recommended to use procedure-like syntax for methods. It is
inconsistent,
may lead to errors and will be deprecated in future versions of Scala.
* Reference: The talk "Scala with
Style" by Martin Odersky at
ScalaDays 2013
Hint: You can use Analyze / Run Inspection by Name (Ctrl+Alt+Shift+I) to apply this inspection to the whole
project
Before:
class Impl {
def method() {
// ...
}
}
After:
class Impl {
def method(): Unit = {
// ...
}
}


The world of artificial intelligence today is still centered around the aspiration for machines to understand: from virtual assistants capable of anticipating our needs and helping us drafting emails or handling our complex schedule, to self-driving cars, and personalized medicine. The Poster Session aims to investigate the boundary of artificial intelligence that understands and predict what's next.
The Poster Session intends to connect people, very much like in a poster session of an academic conference. We are bringing together individuals to show case the latest research in the fields of artificial intelligence and cognitive computing. Come learn about new technologies and discoveries made in companies or research centers - or come show your latest achievements!
A “poster” can be as simple as a 3’x 4’ board, on which you have information about your work. The poster should focus on communicating your work and how it relates to the industry.
Demos are encouraged but not required. If you plan to give a demo, please let us know in your submission so we can plan for it. Although space for your poster and WiFi will be provided, you should bring your own laptop or tablet for your demonstration.
We are looking for posters that address the general theme of: "technical solutions to problems in artificial intelligence." Some examples could be a novel software architecture, an analysis of a dataset, or a new process or algorithm. We are looking for submissions that dive deep into the technical problem and how you are attempting to solve it.
To register as a Presenter, send an email to<EMAIL_ADDRESS>with a description of your poster and any affilliations you have done the work for.
Februrary 7th - Poster Submission Deadline
February 15th - The Poster Session.
3 Winners will be declared live!
Google High Line NYC
85 10th Avenue New York, NY 10012
Email<EMAIL_ADDRESS>Join the CAIM Meetup and RSVP!
The event is free of charge*, with food and drinks provided!
[6:00 pm] Welcome Announcement & Networking with Poster Presenters
[6:30 pm] Lightning Talks
[7:00 pm] Panel with Nick Beim (Venrock), Todd Carter (Tagasauris), Joel Tetreault (Grammarly), Micheal Witbrock (IBM)
[8:00 pm] Networking
[9:00 pm] End of event!


{%extends "registration/base.html"%}{% load bootstrap3 %}{% block content %}
Password or Username is incorrect
Instagram
Sin in to see photos and videos from your freinds.
Don't have an account?
Get the app.


--- layout: post title: inode count date: 2011-01-11 11:00:45.000000000 +01:00 categories: - linux tags: - inode status: publish type: post published: true meta: _edit_last: '1' _wp_old_slug: '' author: ---
This is something that I never had to deal with before! But one of the customised systems when was being used for some other purpose ran into inode count being full issue! That is, you have disk space left but no inode. Happens when you ve a lot of small files. In this case, the system was customised to reduce the number of inodes for the original purpose, (had quite some space with lesser number of bigger files).
Anyways,
the way to see the inode count is a simple:
df -i
:)
cheers!
Anshu


Pierre Bondoerffer
developer / musician / lemon
(enable JS for e-mail)
Paris, France
GitHub
SoundCloud
Twitter


While creating new products and services, organizations also produce the knowledge of how these products, services could be created. All sorts of intellectual property, like discoveries, inventions, formulas; music, literature, and other artistic works; software source codes, and designs could be counted as such knowledge.
Although this is a very unique and important asset to the society, majority of the organizations tend to keep this knowledge to themselves by using restricted licenses, patents. In the long term, this 'overprotection' turns out to be a very counter-productive approach, reduces the collaboration chance between the organizations. When the knowledge has not shared, every other organization has to spend a similar time and energy to get to the same level. In other words, we keep reinventing the same knowledge over and over again.
Rewarding the organizations that use licenses with more flexible rights could encourage sharing the knowledge and let us build a common knowledge.
Knowledge Index allows us to compare the patents, licenses side by side and rate them directly. The resources then could be distributed to the organizations based on their license choice.
In the next part, you will see two sample software licenses that represent the existing situation in general. Open source licenses usually give much more right to the users of its product and restricted licenses, mostly used for proprietary products, would only allow the product to be used by its owner.
In reality, from income perspective, restricted licenses dominate their market, meaning that we reward the organizations that keep their knowledge to themselves.
If we could encourage the organizations to share their knowledge and let them cooperate, we would save massive time & energy and start building a common knowledge.
License
link below and rate each item based on their benefits.
In example below, we list some popular software licenses. As an optional step, we would like to encourage you to rate these licenses. This would allow us to see which licenses we think are more beneficial and let us simulate the impact of 'Knowledge Index' in real life. You can read the details of each license by using the following links:


What would the world be like without a "Hello". For BINDster's Hello World add this to your header to include bindster:
Create your model. The model can either be a prototyped object or a plain old object. Here we show a simple object created from JSON. It has a single property called world:
Create your view. This view has two elements, each of which is bound to the world property in the model. The immediate parameter forces the model to be updated immediatly as you type rather than when the input loses focus:
Bind the model to the view by creating a new instance of Bindster and passing it a new instance of your model. This goes just before </BODY>
And here it is. Enter text in the control to see how it works
For those that prefer not to introduce name spaces all bindster attributes are also available using data-xxx where xxx is the specific bindster attribute.