I agree with all of this if the programmer understands when to break off these functions into a object or abstraction. Other wise you are trying to figure out how to create a car object and turn it on while passing by all the engine functions that are parts of the implementation you simply don't care about. I'm starting to think compiled languages have something else going for them above interpreted languages as I start to miss reading and writing headers for how to use my class.
This is the best part of this site, I completely forgot what this article was about and I'm 60 comments deep about the history and trends of the word "cyber". There needs to be a site dedicated to these entertaining comment threads / bravo
Some of the related videos for their intro video on their site are great and make me want to try it. There was one of a guy who created a old school 3D maze with random generated levels and one wich played the whole "rick roll" song . It amazes me we can simulated computers and hardware in a computer with this depth ...inception level 1
I'm typically thinking about what I have to do at work, or complaining about what processes is horrible and how I can propose to make it better. If I charged for those brainstorming hours during driving I would have a very nice car every year but I feel it makes me better at work and I've come up with some of my best ideas while stuck in traffic.
They still haven't figured out our pattern of "if you keep me out of a meeting about my project that's the day I'm taking a hour lunch during your hour meeting". So either invite me to the meeting about my project or I'm taking lunch because if you think I'm going to pound away on a keyboard while you learn what to come back and tell me out of context then your wrong.
We are moving to aws before the end of the year and it will be a 50% price cut from the dedicated providers we have been using. Our dedicated servers are just about out of space and their bs cloud environment is about 350$ for what you get for 70-80$ on linode. When we need 10-50 processing servers quickly cloned up we go to linode do our work and try to sling the data back ...it's all too annoying now. We're moving to aws, reserving some instances for our client front ends and and booting up what we have to when we need it for mapreduce jobs. For us reserve pricing isn't so bs.
Can geekedin help us hire developers that have some security awareness? Maybe make a site that list those that work for departments that get breached in the future and there will be some accountability for the first time.
I think I have the opposite issue at my current job as the person in charge wants to put every site, every db, every cron job ,every filesystem on one server and then wonder why we have a io problem...
1 instance on aws...sure hope our availability zone stays up next year.
I learned a lot about what I was lacking or what was expected of me in early interviews, it's as if we need a few more blogs like this and some transcribed interviews to prepare people for those "oh shoot I forgot to learn something simple" moments. It's going to happen for college kids and self thought no matter what. If this were a intern job he would have still gotten it and been trained on git. The OS X time machine reply is priceless though...I can remember the copy a folder for backup every hour programming days...horrible times:)
My assumption for this has always been I've had time to check off why my first group of ideas won't play out well "like chess moves" which leads me to a better more thought out move. This new idea is created with the reasons why you dot want to do your other idea "cost to much, burns to much CPU , over engineered whatever..". Takes time to narrow down what you really want to do and yelling out 3-4 ideas the first minute is a good start but giving it time is important.
We use to do this until someone added a simple bug fix to master and someone added a new feature that wasn't ready to go out yet to master and then master got pulled to update the website and the users were wondering what the hell these new features were that were untested and broken.
Quarterly website release cycle with 3-5 developers. usually one liner bug fixes are the only thing pushed to master without a branch as in master -> master. Everything else is a branch / independent feature each developer is working on and we pull them all into a staging copy of master to pretest Which makes it easy to just delete the staging if we want to repull a feature or two and scrap what other features we pulled, once staging is well tested we merge with master on bitbucket as the new release.
The biggest change for us when we starte was do not push features for the 3 month release into master so at any moment or bug fix master is always ready to go live anywhere without some dumb new feature we don't want. Keep master clean dammit :)
I've tried for the past couple of years to get into vim but I can't force myself to remember the odd short cuts I can't seem to ever match up with the action it's doing. I could if I rewrote them butttttt then that blows when I want to jump into a new server without my config. So it's always been nano for one liners and sublime through sftp mounted filesystem.
I hated trying to read about pointers in c when I was about 15, a few years later a different book put it more clear and it all snapped into place for me.
Currently at work someone wants to learn to create web pages and prototype his ideas. He asked me if he's ready because he's learning JavaScript and I had to reply you still need to learn html, Css, sql and a server language to do what we do how we do it. It's a shame so he moved on to some new site / page from mit that's allows drag and drop boots troop elements and drag and drop database logic like "users must be logged in". It's unfortunate there's not much of a middle grown between learning 5 things and drag and drop.
Looks decent compared to some of the minimized ram versions I saw a few years ago but I used them to look into really old windows 9* pcs. Worth a test run.
I'm a system admin with about 40 passwords for work I need to remember so this year I've been using keeweb to keep a encrypted password file/searchable file. This year I started throwing the dreaded htaccess passwords around company only sites we control incase a old employee wants to jump back in until we can decide on a better system/ clean up how we do things.
I know a lot of math majors thrown into c++ jobs that write unreadable code almost forgetting they are allowed to use words and not just single letters (though they would probably be fine in the functional programming scene). There's a learning curve either way, write like your co-workers unless you have the experience to know your co-workers suck.
I wish it was the neighbor using their wifi because it was a wep based setup and that's the ip AT&T gave so they raid and screw up the wrong guys house. But one side it happens all the time.
Seems like more questions should be asked during this whole thing. I want a warrant for a ip of a Facebook user / why ? / because he said mean things about me./ oh he's not a real threat and didn't really break the law...no.
I used "callbacks" when needed in objective-C in my app days and got sh#t done just fine. I think the best thing to come from node is the ability for a younger crowd to jump into proton/electron desktop apps without needing to get into sdl, qt, or some platform specific language like objective c or the .net C# whatever family. Nose might not be the finally language to take us to that area but it's a start and a ton of awesome open source apps came out of the scene quickly.
It said no communication during but you could devise a strategy before play. What I would do on the first challenge is say I would write down the opposite color of what I see and tell the other person the write down the same color they see so you will definitely at least win $50 "or 100$ if you have the same color". For the suite challenge do the same strategy but split 2 people write down the same suite and have a plan for the other 2 to pick what they don't see.