kyled

Mass surveillance does not stop terrorism effectively.

Bruce Schneier wrote a book called Data and Goliath and touches on the subject a bit. Simply to many false positives are detected.

But how will governments decrypt communications you say?

Simple, they hack the devices performing the communication, if they are important enough. They can then get the key if needed. Encryption forces governments to do targeted surveillance.

This isn't just about whats app, it's about all crypto systems. Without privacy, you have no liberty.

Ah, so yes I appreciate demos which pushes hardware to the limit or create some new effect which hasn't been seen before. I feel most demos on older hardware falls within this category then newer demos.

Additionally, please correct me if I'm wrong, older demos didn't have nice graphics apis to call. They had to create and store what's given for free by Apis these days into their binary. I think the Amiga did have some 3d stuff?

With opengl with a handful of lines you could get a spinning cube with lighting. So much more work had to be put into older demos to get to the same point. On top of that, the demo writers really had to know the hardware well, and diving into undocumented behavior. A lot more was being calculated on the cpu back then too.

I haven't been on pouet.net in a while but I will look at newer demos.

I hope so. I'm not involved with the scene at all, but I did read a bunch of history about the scene and watched tons of demos.

I think farbrausch was one of the major groups who did this sort of thing https://github.com/farbrausch/fr_public

Back in the day demos were more impressive imo. A lot of them now use direct x or opengl. For the most part the stuff you see isn't written by hand anymore AFAIK, they just have programs to generate the actual demo. Basically they use modeling programs.

Yui was amazing. Really paved the way for "proper" front end dev.

Would you really answer this way? Maybe they are trying to test communication skills, ie tell me what's only relevant. Can you imagine if you gave this answer to a product manager for a browser? Context people....

It's easy, continually study what interests you. Start this while you are young.

Work for smaller businesses that pay less, get the experience, and move on up.

You could always try to start your own business too.

Learn assembly then c will be easy

Floating points.... Floating points everywhere!

What about secure? So much software, so little is being reviewed...

Watch out for repetitive strain injuries and high stress levels. Don't burn yourself out. Keep work at work, even though it may be tough because you love what you do. Make sure your current job and product are aligned with your goals in life. Be passionate about what you are working on. Keep yourself challenged and you will love it all. Don't undervalue yourself. Make an impact and change the world.

It's simple. If you're not passionate for a topic you're not going to care for it.

I hated math when I wasn't passionate about it. In school a lot of math classes were about route memorization, not going through or writing beautiful proofs.

Why don't they teach more abstract math in school? I love studying number theory and category theory.

Please correct me if I'm wrong, but this won't protect dram from row hammer attacks. You still can access memory cells and cause other bits to flip. Doesn't matter if the content is encrypted or not.

Php-cs-fixer is another example. It does some ridiculous changes though, such as change $i++ to ++$i.

Core.Logic or prolog ftw

No delayed rendering? Isn't the programmer responsible for telling react when to render?

Maybe not the best tactic, but they can selectively issue a 301, and point to a page that contains a new link to the project? The new page can be cached. In the future they can issue another 301 to point back to the original page. Hopefully web browsers will cache the new url.

You can't. When someone else hosts the program the remote system effectively becomes a black box. The only way would be to give the code to the user so they can inspect, compile, and run for themselves. Even allowing the user to inspect the code on remote machine isn't good enough. The methods in which the user inspects the data can be hijacked and make it look like the user is looking at legitimate data.

If you can display an error message, you should be able to record it too. If a network error occurs and prevents the client from phoning home, log the error and send it later.

Great code is mostly pure, dense, defines clean interfaces, and favors composition and reuse. Maintenance, testability , readability etc. are just side effects of well written code.

Have them create a todo list. Make them write it down.

I was like them. I've been programming for over 15 years. I started when I was a kid. When I started programming as a profession, I kept the same habits I had when I was doing it for fun. Ie, find hard new stuff I've never done and learn how to do it! I was inventing new problems to solve because I enjoyed learning new things. Unfortunately this isn't a good model for generating money for a smaller company, you don't yet a lot done if you keep task jumping around. When I started to make a list of things to do I could refer to it and ask myself If the task I Wanted to work on was actually necessary.

Also, don't overload them with stuff to do. Before I if someone had a request for a change I would switch in the middle of a task and try and complete it. This goes back to the todo list, you learn to focus on one thing at a time.

Some things I noticed about myself.

- Less is more. Getting burnt out leads to bad code and less productivity. Avoid the situation by giving realistic expectations. Ask for additional help if needed. It's important to know when to say no and provide alternative solutions. Saying yes all the time is actually unprofessional.

- You need sleep. That's when your brain is actually making connections to different ideas you thought about during the day.

- Over working can and most likely will lead to rsi (repetitive strain injury). Don't be stupid. Make sure you stretch and take brakes. I've been coding for 16 years and last two have been he'll because of it. Actually I'm considering changing careers or taking a while off. I love computing so this is a very hard choice.

- Are you guys doing incremental changes and deploying them ? Lean development? Quick iteration cycles lead to spending time developing the right thing and less wasted time on the wrong thing. Plus, people are much happier when they get what they want in pieces.

Mr. Lizard, a monster! Would you care for a hamburger?!

Maybe it's a test to see how well you can communicate? I would of given a very brief high level overview, such as...

A request is sent to Google's severs for their "new search" page. Google then responds with the necessary data in order for your Web browser to display the Web page . There's a lot more to the full story, but I can go into detail if you would like.

I would offer diving into the important parts related to the position.

You're missing the point. He's talking about the passion for learning about computers. When was the last time you reversed engineered a binary that had self modifying code, just for the fun of it and to learn how it works? Play same code golf games or war games, purely for the challenge? There's nothing wrong with people making money. It's the fact that people are doing it just for the money. I think there is a video called the bbs documentary. Check it out. The culture surrounding computers has changed, a lot.