![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
I did this back in probably 2008 with Linux mint.
I did this back in probably 2008 with Linux mint.
The difference is in exact wording Agile: the software shall properly authticate a user within our active directory.
Documention : user authentication will be provided by functions ”valisate username” as described in section 14,7 subsection 4, ”validate password” as described in section 16.2 and validate the correct pasword as described in section 23.4.Proper authication to the correct use group shall comply with the requirements in document 654689 section 64.7 subsection 17
Yes there is a difference and one is better…
Did you look at the source code? If not open the source and zoom out…
Wonder of we feed this into an Ai what would happen… https://github.com/mame/quine-relay
There are two hard challenges in computer science cache invalidation and naming things
Yeah… Which is 100x more complicated cause Microsoft has no idea how to name consoles
I didn’t even consider incorporating toy distribution… At what levels should kids get a small gift(a toy or game) vs a large gift(bike, game system etc).
In a real world scenario I would probably spilt this between 2 databases… One for kids (“with a nice score of 2 you get a toy of value 4 or less”) and one for toys (“the toys available with a value less than 4 are…”)
All I’m going to say is I still remember “correcthorsebatterrystaple”…
I mean in a certain light, christmas presents are a yearly bonus for children and Santa checking his list is a management review of the child’s performance…
Actually I think there should be a intermediary table as a history of activities of each child. Like child table is I’d, name, age, address, and naughty/nice value, activities would be Id, description, and good/bad value. Then a history table of ID, child_id, activity_id. So santa can recalculate a child’s naughty/nice value to “check it twice”
I think you would have a table of “activities” with a value of how good/bad each is. So like cleaning your room would be +5 but crying in a store because mommy wouldn’t buy you a toy would be - 15. Then you have a table for children and each child starts with 0 in January and then for each activity the child does there naughty/nice value gers adjusted. December 24 Santa runs a query on the dB and gets a list of every child with a positive value.
Keep in mind I currently feel sick and put about 5 minutes of thought into thus.
This actually gave me an idea. Over break I wanted to practice dB design and entity framework. Designing a database and interface for santa to track kids naughty or nice could be a fun/interesting way of doing it.
Something like c sharp acedemy would be kinda cool. Basically do some beginner projects with good code reviews you get a “belt”. That belt allows you to review the beginner projects as you work on intermediate projects. Then you complete those and get another belt that let’s you do advanced projects and review the intermediate projects others submitted.
Did you bring background instrumentals to support the singing?
If you want to be a Rockstar programmer start here: codewithrockstar.com
Next week we will off high heels camp!
I think a boot camp would be really useful for cobblers
This reminds me of the Rockstar programming language. It started as a joke about headhunters looking for “Rockstar programmers”. The creator ended up making a complete programming language where the program’s code could be sung as a 80s power ballad.
I had that experience last week. I half blame the language though cause the way it works is you don’t initialize a variable, first time you use it the language automatically makes the variable and default value is 0.
I had a variable countoot that I had a formula calculate. Then a simple if countoot > 0 do this else do that. The program kept doing that. I knew countoot should be 2. I manually did the formula … The answer was two.
I did the same formula in 3 other programs and it worked correctly. I spent between 1.5 to 2 hours a day for like 3 days banging my head on the desk trying to figure out why it would work. Fourth day me and 2 other guys were trying to figure it out when I finally really looked closely. I realized the formula result was stored in ccountoot(notice 2 c) and the if statement was based on countoot(notice 1 c)…yeah I felt so stupid when correcting the typo fixed the problem.