Who is liking the new colors in the logo?
I don’t mind it.
It’s a nice change, fits with the color scheme and not completely obnoxious, so I’m all for it.
Just ran across this on Superuser. Thought it was relevant.
I don’t think I could ever do this challenge… when I sit to program, before I know it 6+ hours are gone… working in 1 hr increments would be torture.
I didn’t see any time limit
the rules say
Whole December. Every day. At least 1 hour a day.
Looks like it needs a regex:
I am in. Going to write the Longest Hello World program in the world
Lazy programming, not counting for edge cases.
Fix this, commit it and I’ll consider merging it at that point.
Alright, I’m awake from my nap! Time to get to work!
Did you just assume my variable type?
I believe its to keep one dedicated, and focused on the problem.
Oh, so this is why static typing has fallen out of favour. Now I see how it is.
[email protected] ~/code/src/gitlab.com/devember2017 $ git push heroku master Counting objects: 26, done. Delta compression using up to 4 threads. Compressing objects: 100% (22/22), done. Writing objects: 100% (26/26), 26.60 KiB | 5.32 MiB/s, done. Total 26 (delta 2), reused 2 (delta 0) remote: Compressing source files... done. remote: Building source: remote: remote: -----> Node.js app detected remote: remote: -----> Creating runtime environment remote: remote: NPM_CONFIG_LOGLEVEL=error remote: NPM_CONFIG_PRODUCTION=true remote: NODE_VERBOSE=false remote: NODE_ENV=production remote: NODE_MODULES_CACHE=true remote: remote: -----> Installing binaries remote: engines.node (package.json): 8.9.1 remote: engines.npm (package.json): unspecified (use default) remote: remote: Resolving node version 8.9.1... remote: Downloading and installing node 8.9.1... remote: Using default npm version: 5.5.1 remote: remote: -----> Restoring cache remote: Skipping cache restore (not-found) remote: remote: -----> Building dependencies remote: Installing node modules (package.json + package-lock) remote: added 49 packages in 2.735s remote: remote: -----> Caching build remote: Clearing previous node cache remote: Saving 2 cacheDirectories (default): remote: - node_modules remote: - bower_components (nothing to cache) remote: remote: -----> Build succeeded! remote: -----> Discovering process types remote: Procfile declares types -> web remote: remote: -----> Compressing... remote: Done: 17.8M remote: -----> Launching... remote: Released v3 remote: https://fast-gorge-78145.herokuapp.com/ deployed to Heroku remote: remote: Verifying deploy... done. To https://git.heroku.com/fast-gorge-78145.git * [new branch] master -> master
Dang it! Why did you have to post this!!!
I’m so burnt out from work, but really want to do some “me” programming rather than “can you program this for me” programming.
I’ve done my hour for the day, so I’m in the clear, but I’ll have to consider it…
I’ll probably do some super boring “back to the basics” programming and not anything sexy.
Like writing a LRU cache in C, or emplementing an AVL tree in Ruby. We’re talking an algos and data structure refresher here
Sheeze, I really miss “fun/meaningful” programming.
Try x86 Assembly
@cotton Here is a hello world example I did to help get you started.
~> nasm -f elf source.asm ~> ld -m elf_i386 -s -o executable source.o ~> ./executable
That’s for sure a goal. Hopefully, that will lead to reverse engineering, but I don’t have the willpower to push through that. Lol!
I’m just going back to boring basics.
I really need to brush up on my pointers and data structures. You never know when you may need a solid fifo queue in C++
Come on, do it! There’s still time left in the day.