Found 801 repositories(showing 30)
gonglei007
最全面的游戏开发技术图谱(Game Development Map)。帮助游戏开发者们在已知问题上节省时间,省出更多的精力投入到更有创造性的工作中去。
gonglei007
The most comprehensive technical map of game development. Help game developers save time on known problems and save more energy for more creative work.
wpschaub
A DevOps presentation and posters covering the essentials for a DevOps mindset.
PacktPublishing
Mind-Melding Unity and Blender for 3D Game Development, published by Packt
sandervonk
Client-side French verb conjugation practice written with accessibility in mind. An accessible medium for anyone to practice verb conjugations in a multitude of tenses, whether it be as practice for their school-assigned classes, or to teach themselves something new. https://svonk.me/VITE/About for more https://svonk.me/VITE/docs for devs 😉
lich0821
Give your AI coding assistant a working memory — so it remembers decisions, respects boundaries, and knows when to stop.
BiaAhmed
A product marketing portfolio template for dev-savvy marketers who’d rather show than tell. Built with Astro, Tailwind & strategy in mind.
VinodhThiagarajan1309
No description available
weilaiqishi
前端学习
ahmdaeyz
A generic validator with business logic separation in mind. (pub.dev package)
complyue
No description available
michaelgatuma
This is a grid style dark themed portfolio especially designed with devs in mind. It is based on Vue3 and TailwindCSS. Feel free to contribute and fork.
THEFEASTCOIN
Welcome to The F.E.A.S.T Token (Family Equity Assertion Stability Trust). The F.E.A.S.T Token is the newest massive experiment within the DeFi sector of cryptocurrency. We aim to educate, elevate and encourage the Urban Communities across the World to join in with the F.E.A.S.T Token as we push for an economical freedom through the spontaneous community building and sharing of potential financial opportunities! Everyone is welcome to sit at the Table and Feast Heartily. All we ask is if you decide to pull your token money out early and not HODL (Hold On for Dear Life) as we grow, be respectful to the community and add back into the F.E.A.S.T immediately after you have received your gains. These are good steps to take to be fair to the other investors involved, as we encourage everyone to come get a second serving of the F.E.A.S.T. The community will count on these continued contributions in such a manner for long term financial sustainability. Everyone can prosper and fill their bellies up, we're making it simple and plain..... WE ARE HERE FOR THE PEOPLE TO WIN. What is F.E.A.S.T FAMILY EQUITY ASSERTION STABILITY TRUST The desire to harness capital is at an all time high within the DeFi sector of cryptocurrency. So many people have had a lot of bad experiences never receiving any real gains from their token investments, leaving them with a sour taste about cryptocurrency. We plan to help change all that and attempt to give life changing experiences for all who participate. F.E.A.ST Token is a deflationary currency and was designed to assist the new investors with their DeFi Experience. In a world full of greed, gluttony and selfishness, we aim to give people the opportunity to invest and achieve success. Unbeknownst to the new investors are the “Whales”, who find many of the new investors as Krill Food or Financial “Plankton”. We find them as essential creatures needed to help stimulate the DeFi Ecosystem. F.E.A.S.T stands for Family Equity Assertion Stability Trust. We are giving notice to the families, friends and communities across the world to harness your financial potential. Tap into the F.E.A.S.T Token with a small or large investment and see where it may lead you. We incentivize all HODLERS of the F.E.A.S.T Token by redistributing 3% of every buy/sell transaction back to all active holders HODLing the “FEEDN” Token. There is also a 5% tax on every transaction that will automatically be contributed into the Pancakeswap Liquidity Pool. Because of the 40% supply that was burned at launch, a significant amount of the 3% tax distribution will be absorb by the burned address, resulting in exponential hyper-deflation and a forever increasing floor price for our token! The F.E.A.S.T TOKEN was created to be a community driven project, which requires the community to help market and promote the F.E.A.S.T Token over social media and by word of mouth. WE ARE NOT A MEME TOKEN. The liquidity will be locked for 1 year to ensure there will never be any sort of rug pull from our end. The Dev wallets etc. are locked for 3 months at which point there will still be no type of dump off of tokens from our end, we plan to expand the spectrum of our Tokens reach so we are in it for the long haul. WORD'S OF ENCOURAGEMENT FROM THE FOUNDER/LEAD DEV..... We started from the bottom as many did as well, coming from many different walks of life, we took some years to study and learn that which we know could be of some benefit to many of us. We have reaped a lot of rewards from this realm of economics and we also have taken many losses as well. Yet, what we have released, that if we move in a one mind frame type of thinking, just one good strong time, we can establish something spectacular and very vast economically. We wanted a clear picture painted in that vision so we decided to do everything correctly and cut no corners and try to steer people in the right path with confidence, especially for the first time on-comers. We want the good feeling of reciprocity to be observed, meaning, you bring something to the table and you get something in return for what you bring, and the cycle repeats itself as long as you engage in it in such a way to be of a benefit to all….jump in, jump out, jump back in, then jump back out…. Nonetheless stay within the activity of the cycle continuously and that’s our aim for us to win forever and ever, over and over, no whales become a factor when we use the system with respect of having longevity in mind. We have witnessed so many fly by night tokens that come and go so fast because of greed, gluttony and selfishness. We intend to talk to our community and teach them the methodology of investing and holding and taking out and buying back in and watching the token appreciation etc, we are not teaching people to view this as a hustle scheme or a get rich overnight play. It can become a lifestyle and way of living for many of us, and we want to embellish that kind of mindset and thinking upon our community as we grow and prosper. Those were our initial intentions on wanting to create a token for the people to F.E.A.S.T upon. By locking the Liquidity and the Team Tokens etc, it goes to show that we are not here for any Rug Pulls, we really want this to work and develop into something great. Our team will buy into the Token just as everyone else will do during the presale and afterwards at dips etc. The locked tokens are to secure the potential future we have planned for our token to advance forward, yet we want to create a comfort zone of respect, trust and loyalty that no such shim-shams will happen on our watch. We have witnessed setbacks ourselves from past dealing with these startup tokens and presale’s that went astray, token launch dates turning into a highway robbery of millions from the people who invested, we have become a scarred victim as well. Nonetheless, we had to charge it to the game of the risk versus the reward scenario, we know what we were playing in, and it can and will happen to the best of them. Yet we desire to eliminate all that kind of disturbing drama and backbiting tactics that causes a lot of these tokens to lose their value the same day they are launched within just a few hours. A template and AMA session will enlighten our community on how we are going to be different, there will always be a few who, unbeknownst to us all, many will stray away and try to do something out of the way of the design, yet the majority is what matters. The ones who stand down firm on the tactics that we need to use will continuously help us all to win over and over again, playing alone is a snatch and grab game, playing for the Team is what matters, we are going after a bigger Meal to F.E.A.S.T upon, and we encourage everyone to come sit at the Table and Feast with us, time and time again. TOKENOMICS : F.E.A.S.T TOKEN is released on the BInance Smart Chain Network and available to trade on Pancakeswap. NAME: F.E.A.S.T TOKEN TOTAL SUPPLY: 1,000,000,000,000,000 “FEEDN” SYMBOL: “FEEDN“ DECIMALS: 9 TOKEN TYPE: BEP-20 LAUNCH: TOTAL TOKEN SUPPLY: 1,000,000,000,000,000 TOKENS USED FOR THE PRESALE: 240,000,000,000,000 TOKENS USED FOR LIQUIDITY LOCK: 300,000,000,000,000 TOKENS BURNED AT LAUNCH (AFTER PRESALE & LISTING): 400,000,000,000,000 PRESALE LAUNCH: SOFT CAP: 50 BNB HARD CAP: 100 BNB PRESALE RATE: 2,400,000,000,000 FEEDN per BNB MIN CONTRIBUTION: 0.1 BNB MAX CONTRIBUTION: 1 BNB LISTING RATE AFTER PRESALE: 1,000,000,000,000 FEEDN per BNB PANCAKESWAP LIQUIDITY: 94% LOCKED LIQUIDITY: TOTAL TOKENS FOR LIQUIDITY LOCKED (1 YEAR): 540,000,000,000,000 TOKENS FOR TEAM DEVELOPMENT (3 MONTHS): 25,000,000,000,000 TOKENS USED FOR MARKETING ADS (3 MONTHS): 20,000,000,000,000 TOKENS FOR THE DEPARTMENT OF CULTURAL ADVANCEMENTS (3 MONTHS): 15,000,000,000,000 REWARDS: 5% Auto Liquidity Pool (5% tax on every transaction that will automatically be contributed into the Pancakeswap Liquidity Pool. Because of the 40% supply that was burned at launch, a significant amount of the 3% tax distribution will be absorbed by the burned address, resulting in exponential hyper-deflation and a constant increasing floor price for our token! 3% Redistribution to Holders (3% of every buy/sell transaction is taken and redistributed to all Active Holders HODLing the “FEEDN” Token) 2% will be burned on every transaction (2% burned to help increase price stimulation) Advance Offer to Investor: (Once “FEEDN” tokens are purchased, use the tokens to become a Liquidity Provider for the F.E.A.ST Token and receive %’s of the rewards from THE Liquidity Pool of the (FEEDN/BNB) LP Tokens. Help us and come be a part of the biggest Urban Economical Token movement! @instagram : https://www.instagram.com/thefeastcoin/ @twitter : https://twitter.com/TheFEASTcoin @facebook : https://www.facebook.com/groups/thefeastcoin/ @tiktok : https://www.tiktok.com/@thefeastcoin? @telegram : https://t.me/joinchat/zd6cI68C-K84MmUx @Youtube : https://www.youtube.com/channel/UC0NY7AR9FRAHevRtJESZgmw @Medium : https://thefeastcoin.medium.com/ @Github : https://github.com/THEFEASTCOIN?tab=projects @Reddit : https://www.reddit.com/user/TheFEASTcoin @Discord : https://discord.com/.../85806760020659.../858067601794793504 Be sure to check out our rules before posting and commenting. DISCLAIMER: WE ARE NOT AFFILIATED WITH ANY TOKEN NAMES OTHER THAN THE CONTRACT TOKEN NAME CALLED - ''F.E.A.S.T" TOKEN (Family Equity Assertion Stability Trust) with the ticker symbol “FEEDN”.
Application to create interactive mind maps on a tabletop surface (MT4j) providing additional idea/text entry via bluetooth connected smartphones (Android). Requires the mt4j-core and mt4j-desktop projects to run, available at mt4j.org
DevMindAbhay
No description available
MindMap-AI
Streamline your software development process with project management and mind maps AI to plan features, track tasks, and boost team collaboration. Mind maps AI enhances agile workflows by visually organizing sprints, user stories, and development goals for faster, smarter innovation.
uid000222
A public repo revealing what anti-cheats (Fivem, PunkBuster, RAC, BattlEye, EAC, VGK, Faceit, FiveM, and more) detect and flag. From API calls and kernel tricks to memory scans and behavior checks, uncover how games catch cheaters. Ideal for devs, researchers, and curious minds. Contributions welcome!
pointofsale
Mongo db console commands //showing the existing dbs.. show dbs //use test switching to db test, (only creating it when actually adding new data) //prompts the name of the working db now db //the fllw would prompt the count(), in the link2 collection, in the current db... >db.links2.count() //inserting a record in links2 db.links2.insert({title:"unn titulo", url:"", comment:"", tags:["un primer tag", "un segundo tag"], saved_on: new Date}) //working with an object the javascript way... data = {} | data.title = "un titulo" | data.tags = ["un tag", "otro"] | data.meta = {} | data.meta.OS = "win7" | db.links2.insert(data) //printing the result of the find, in the structured json format. db.links2.find().forEach(printjson) //--> in this case we pass to forEach the printjson function... //retriving only the first of the results of the find method. db.links2.find()[0] db.links2.find()[0]._id //getting the timestamp present in the _id variable (is made of (also) the time it was created) db.links2.find()[0]._id.getTimestamp() /*the following function creates, when called, a new collection inside the same working db, that tracks the last id number we are in. This allows having the same behavieur than in relational DBs.*/ //apparently, u have to declare this function... function counter(name) { var ret = db.counter.findAndModify({query:{_id:name}, update:{$inc:{next:1}}, "new":true, upsert:true}); return ret.next; } //so u can do something like db.products.insert({_id:counter("products"), nombre:"primer nombre"}) //the result is something like: { "_id": 1, "name": "un producto" } { "_id": 2, "name": "otro producto" } /*referencing in MongoDB*/ db.users.insert({name:"Richard"}) var a = db.users.findOne({name:"Richard"}) db.links2.insert({title:"primer titulo", author:a._id}) //reference to other collection throught the _id key... //quering db.users.findOne({ _id:link.author }) //a way to make manual inner joins... within the user db, we search for a coincidence of our _ids on the links2 db, author field. ---note--- embedding is much more efficient when we have significantly more read than writes. Otherwise, consider using the normalized way. These depends on every case. /**/ #importing data from a .js in json format. With mongod running or in a services: > ../../../mongodb/bin/mongo 127.0.0.1/bookmarks bookmarks.js //the first part is the location to the mongo exe in the mongo usual location //the second part is the server and db in which we will be importing in //the third part is the file with all the mongo commands... --this bookmarks file is in C:\Tuto\mongo\trying -- https://raw.github.com/tuts-premium/learning-mongodb/master/08%20-%20bookmarks.js /*bookmarks.js extract*/ var u1 = db.users.findOne({ 'name.first': 'John' }), u2 = db.users.findOne({ 'name.first': 'Jane' }), u3 = db.users.findOne({ 'name.first': 'Bob' }); db.links.insert({ title: 'Nettuts+', url: 'http://net.tutsplus.com', comment: 'Great site for web dev tutorials', tags: ['tutorials', 'dev', 'code'], favourites: 100, userId: u1._id }); /**/ //connecting directly to db bookmarks > ../../../mongodb/bin/mongo bookmarks //searching in the collection all docs that have inside the tags array the "code" element. //this can be done because we are dealing with an array --> array advantages... db.users.find({tags:"code"}).forEach(printjson) //with findOne u can do (not with find) findOne().name db.links.find({favourites:100}, title:true, url:1) //selecting only some fields... db.links.find({favourites:100}, tags:0) //selecting all but the tag field... //selecting inside an object... db.users.findOne({"name.first": "John"}) db.users.findOne({"name.first": "John"}, "name.last":1) var john = db.users.findOne({"name.first": "John"}) db.links.find({userId:john._id}, {title:1, _id: 0}) /*queries directives*/ //greater than 150 db.links.find({favourites:{$gt:150}}, {_id:0, favourites:1, title:1}).forEach(printjson) db.links.find({favourites:{$gt:150}}, {_id:0, favourites:1, title:1}).count() //less than db.links.find({favourites:{$lt:150}}, {_id:0, favourites:1, title:1}).forEach(printjson) //$lte, $gte -- and iqual //using in db.users.find({"name.first":{$in:["John", "Jane"]}}) //the opposite is $nin db.users.find({"name.first":{$nin:["John", "Jane"]}}) //$all -- only the records with all the specifications in "tags" field. db.links.find({tags: {$all:["code", "marketplace"]}}, {title:1, tags:1, _id:0}) //$ne -- not equal //the $or flag search for the fullfillment of at least one of the elements in the array passed... db.users.find({$or: [{"name.first": "John"}, {"name.last": "Wilson"}]}) //the opposite: $nor //inclusive: $and //$exists db.users.find({email: {$exists: true}}) //$mod db.links.find({favourites: {$mod: [5, 0]}}, {_id:0, title:1, favourites:1}) db.links.find({favourites: {$not: {$mod: [5, 0]}}}, {_id:0, title:1, favourites:1}) //elemMatch -- inside logins, search for an element match that has minutes = 20, and return the complete record db.users.find({logins: {$elemMatch: {minutes: 20}}}) //searching for an 'at' prior to 2012/03/30.. and returning the whole record... db.users.find({logins: {$elemMatch: {at: { $lt: new Date(2012, 3, 30)}}}}) //using where -- c) is equivalent to a) a) db.users.find({ $where: 'this.name.first === "John"'}) b) db.users.find({ $where: 'this.name.first === "John"', age:30}) c) db.users.find( 'this.name.first === "John"') //injecting functions in mongodb -- as this example returns trueéfalse, its going to return values randomly var frand = function() {return Math.random() > 0.5} db.users.find(frand) // var f = function() { return this.name.first === "John"} db.users.find(f) //or db.users.find( {$where: f} ) //other queries //distinct -- returns a list of diff results db.links.distinct('favourites') --> [100, 32, 21, 78, ...] db.links.distinct("url") db.links.group({ key:{userId : true}, initial:{favCount: 0}, reduce: function (doc, o) {o.favCount += doc.favourites}, finalize: function(o) {o.name = db.users.findOne({ _id: o.userId}).name } }); *** //the final part is not working... db.links.group({ key:{userId : true}, initial:{favCount: 0}, reduce: function (doc, o) {o.favCount += doc.favourites} }); db.links.group({ key:{userId : true}, initial:{favCount: 0}, reduce: function (doc, o) {o.favCount += doc.favourites}, finalize: function(o) {o.name = "richard"}} ); //regex db.links.find({ title: /tuts\+$/}) db.links.find({ title: {regex: /tuts\+$/}}, {title:1}) //counting db.users.count({'name.first': 'John'}) db.users.count(); //all users in the collection //sorting, limit db.links.find({}, {title:1}).sort({title:1}).limit(1) //1: asc -1: desc //sorting, skipping and limiting... normal behavieur in the pagination rutine... db.links.find({}, {title:1, _id:0}).sort({title:1}).skip(3).limit(3) /*updating*/ //by replacement or by modification... ---general form /* db.collection.update( <query>, <update>, { upsert: <Boolean>, //if not found insert multi: <Boolean>, //change in all the condition <query> is fullfilled } ) */ // more info in http://docs.mongodb.org/manual/reference/method/db.collection.update/ db.users.update({-the query object-}, {-the update object-}, -upsert boolean-); var n = {title:"Nettuts+"} db.links.find(n, {title:1}) db.links.update(n, {$inc: {favourites: 5}}) var q = {"name.last": "Doe"} db.users.find(q, {name:1}) //we can use set to update a field or add a completly new one... db.users.update(q, {$set: {"name.last": "Doetix"}}) //modifying an existing field.. db.users.update(q, {$set: {"email": "doetix81@gmail.com"}}) //inserting a new one... //to remove a field w use unset db.users.update(q, {$unset: {job: "Web developper"}}) db.users.update({"name.first":"John"}, {$set: {job:"Web developer"}}, false, true) //modifying and then inserting an object var bob = db.users.findOne({"name.first":"Bob"}) >bob { "_id" : ObjectId("525f06242df9763abe646b62"), "name" : { "first" : "Bob", "last" : "Smith" }, "age" : 31, "email" : "bob.smith@gmail.com", "passwordHash" : "last_password_hash" } > bob.job = "Thick Brush Painter" > db.users.save(bob) //find and modify -- findAndModify {{}} /* The findAndModify command atomically modifies and returns a single document. By default, the returned document does not include the modifications made on the update. To return the document with the modifications made on the update, use the new option. { findAndModify: <string>, query: <document>, sort: <document>, remove: <boolean>, //one of | update: <document>, //this two | new: <boolean>, //if the new object must be shown or the old one.. fields: <document>, //fields to show in the result upsert: <boolean> } */ > db.links.findAndModify({ query:{favourites: {$gt:150}}, sort:{title:1}, update:{favourites: 333}, new: true, fields: {_id:0} }); //pulling into arrays db.links.update(n, { $push: {tags: "jobs"}}) > db.links.findOne(n).tags //several... db.links.update(n, {$pushAll:{tags: ['blogs','press','contests']}}) //on pull into the array if the new element is not present.. db.links.update(n, {$addToSet:{tags: "dev"}}) //doing the same with an array... db.links.update(n, {$addToSet:{ tags:{$each: ["dev", "interviews"]} }}) //pulling out content from the array... db.links.update(n, {$pull: {tags:'interviews'}}) //pulling several... db.links.update(n, {$pullAll: {tags: ['blogs','dev', 'contests']}}) //poping out from the beginning or the end.. db.links.update(n, {$pop: {tags: 1}}) //--from the end (-1 -- from the beginning) //positional operator... only the subobject gets updated... db.users.update({'logins.minutes': 20} , {$inc:{ 'logins.$.minutes': 10}}, false, true) db.users.update({'logins.minutes': 20} , {$set:{ 'logins.$.location': 10}}, false, true) db.users.update({'logins.minutes': 30}, {$set: {random: true}}, false, true) //renaming the fields name... db.links.update({url: {$exists: true}}, {$rename:{"url": "camino"}}, false, true); //more info on the positional operator in: http://docs.mongodb.org/manual/reference/operator/update/positional/ //taken from there: /* The positional $ operator facilitates updates to arrays that contain embedded documents. Use the positional $ operator to access the fields in the embedded documents with the dot notation on the $ operator. db.collection.update( { <query selector> }, { <update operator>: { "array.$.field" : value } } ) */ /***EXAMPLE Consider the following document in the students collection whose grades field value is an array of embedded documents: { "_id" : 4, "grades" : [ { grade: 80, mean: 75, std: 8 }, { grade: 85, mean: 90, std: 5 }, { grade: 90, mean: 85, std: 3 } ] } Use the positional $ operator to update the value of the std field in the embedded document with the grade of 85: db.students.update( { _id: 4, "grades.grade": 85 }, { $set: { "grades.$.std" : 6 } } ) ***/ //removing db.users.remove({'name.first': "John"}) //all the collections in the selected db... show collections //dropping completly a collection... db.acoll.drop() //indexes... db.links.find().explain db.links.ensureIndex({ title: 1}) //in ascending order.. in mainly important in cpompund indexes.. //a reflect of this index can be found in that db indexes collection db.system.indexes.find(); //u cound put an index to a canging value, but every time u change that value the index must be updated. keep in mind. //usually is a good idea to set the indexes at the beginning when no data is present in the collections. However, u could use the following formula to treat duplicates and unique data //keeping only the first one, deleting the others.. db.links.ensureIndex({ title: 1}, { unique: true, dropDups: true}) //when considering the case of some of the documents without the idexed field, to save mongo from storing space for this index if the field itself has not been inserted: db.links.ensureIndex({ title: 1}, {sparse: true}) //its important to think of the compund index as a nested one, an index of an index. Its related to each problem-case. Like in the case of the recepies: indexing first the ingredient and the the recepie, makes more sense than indexing in reverse. Its all related on how u are going to search. db.links.ensureIndex({ title: 1, url: 1}) //this one means that u can search on title; or on title and url... db.links.ensureIndex({ a: 1, b: 1, c: 1}) //searches are possible on a; a, b; a, b, c //deleting indexes db.links.dropIndex("title_1"); //the same way that appears in system.index collection... /*concepts to follow*/ //Sharding and Replica Set... http://www.slideshare.net/Dataversity/common-mongodb-use-cases-13695677 http://docs.mongodb.org/ecosystem/use-cases/product-catalog/ db.collection.update({"grades.grade":80}, { $set: {"grades.$.std": 18}})
khaled-benahmed
PI-DevMinds2024
erfansn
مجموعه دیدگاه هایی که به عنوان یه توسعه دهنده نمی خواهم دوباره فراموششون کنم
xd43vild69
Mind maps for developers - Simplify - Organized - Unify. (Image+Souce)
tesla809
Knowledge vault for web3 Development and zk-based layer-2. Aims to cross-referenced and link all web3 topic content.
abhishekkumar62000
No description available
abhishekkumar62000
No description available
CheeseWithSauce
A complete Quran dataset in JSON format with 114 per surah files and one full quran.json containing every verse. Each verse has a continuous global ID for easy lookup, plus surah/ayah info and Arabic text. Made specially keeping our Muslim devs in mind.
Teppo652
Test Assignment - Project Sports Poll Overview The "Sports Poll" app is a dead simple poll system around some sports events which can be fetched from this JSON file It allows users to vote on each event and then shows another random event to vote on. There should be one poll, that displays one (random) category at a time. E.g. load Football category with poll options to vote on from DB, and only display those at a time, next browser reload would maybe display Tennis. The polling options should be what team will win or if it will be a draw, e.g. ● Home Team win (Team A) ● Draw ● Away Team win (Team B) Delivery When you have completed the task, we’d like you to deliver the following: ● A description of what you have done and how far you got in time allotted for the work on the project. ● Which development tools you used and your general progression on the key issues, what you got stuck on, what you did or didn’t solve etc. ● A step by step instruction to how to run the project. ● Share the source code in a private code hosting on Bitbucket or Github (Bitbucket has free private repositories). ○ For Bitbucket - Share that repository giving admin permissions to bojan.zrnic@itengine.rs and GLOMOadmin and send the URL in an email to dev@glomo.se. ○ For Github - Share that repository giving admin permissions to zrnicbojan and adminglomo and send the URL in an email to dev@glomo.se. Tasks and deliverables per job position Junior Frontend Developer This exercise is expected to take 3 to 6 hours to complete. 1. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 2. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 3. It’s not allowed to use any CSS framework like Bootstrap or similar. 4. The JSON file with the events can be accessed directly from the frontend or hardcoded in the website. 5. The odds can be generated randomly. There is no need to keep track of votes across page reloads. Senior Frontend Developer This exercise is expected to take 4 to 8 hours to complete. 1. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 2. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 3. It’s not allowed to use any CSS framework like Bootstrap or similar. 4. The JSON file with the events can be accessed directly from the frontend or hardcoded in the website. 5. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 6. Keep event votes stored in a browser local storage so they can persist across page reloads. 7. Add different kind of visualisations based on event attributes (country, state, sport and so on). It is up to you to decide how to best represent the data. 8. Add a couple of automated tests. Fullstack Developer This exercise is expected to take 5 to 10 hours to complete. 1. Create a backend for Sports Poll. The backend should be created using Node.js. Whichever Node.js framework you select will not impact the way we assess your test. 2. At start, fetch the events from the JSON file and store them in a local database of your choice. 3. Create a backend API to read events. 4. Create a backend API for voting for events (home win, draw, away win). 5. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 6. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 7. 8. It’s not allowed to use any CSS framework like Bootstrap or similar. 9. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 10. Add a couple of automated tests. Senior Fullstack Developer This exercise is expected to take 7 to 15 hours to complete. 1. Create a backend for Sports Poll. The backend should be created using Node.js. Whichever Node.js framework you select will not impact the way we assess your test. 2. At start, fetch the events from the JSON file and store them in a local database of your choice. 3. Create a backend API to read events. 4. Create registration/login for the Sports Poll. It could be either with regular email address or Facebook login. 5. Create a backend API for voting for events (home win, draw, away win), keep track of the votes. Only allow logged users to vote and don’t allow more than one vote per user for each event. 6. Create a page with the best design practices in mind for this small application. The design will be taken into consideration and should be visually pleasant and user friendly. 7. You are free to use any modern Javascript framework that you’d like. The choice of framework may impact the way we assess your assignment. 8. It’s not allowed to use any CSS framework like Bootstrap or similar. 9. The page should be responsive and work well across different types of devices (desktop, mobile, tablet). 10. Add a couple of automated tests.
This repository is designed to help contributors work on a simplified, parallel version of the backend before merging features into the main system. Showcase their work anytime.
khaled-benahmed
Desktop application called NutriFit using JavaFX.
Kickstart your career as a Front End Developer in ONE month!
This repo is to collect details about all weekly newsletters available which may ignite the devops mind in you.