Commander Keen rocked. I am surprised id Software didn't make an official crossover!

Simply not true. Will you get some directors using cookie cutter sound templates? Of course... bad ones. Hell, Bay reuses entire shots in his movies (often in the same damn franchise).

But good filmmakers will hire good sound designers and they will create good sound with what they have available.

Computers are a tool, nothing more. Digital sound is no different to digital imagery... people say they hate it, but they only hate BAD examples of it.

Can foley survive? Short term, maybe; long term, unlikely.

Fundamentally, it'll come down to the same question as any other technique in any commercial artform... cost vs quality. If foley remains the best way to get a sound, you will find people willing to pay for it. As digital sound creation gets better and better, there WILL come a point where no-one can tell the difference.

If you don't believe me look at guitar amplifiers. For decades, guitarists have preferred old vacuum tubes (known as valves) to generate the sound they want in a guitar amp. Digital (commonly referred to as solid state) amps are cheaper and generally pretty crap.

But these days, even people who love valve amps (and I include myself in that) have to admit that it's almost impossible to tell the difference between a genuine valve amp and a good computer model of the same (side note for guitar techy people... I know modelling != solid state).

And that's not just in playback, it's in live performance too. A kemper or an AxeFX FEELS like a valve amp, and you can vary the settings like a valve amp.

I believe that foley will ultimately go the same way. People like Wes Anderson will continue to use it, but for most filmmakers on a budget, they'll go with the sound creation software.

By far the best class I took while getting my Computer Science degree was "Software Engineering Project". We got assigned a project and divided up into teams including CS, CIS, and MIS majors. The MIS people managed and divided up assignments, and the CS people handled different aspects of the programming, like data structures / algorithms / UI / whatever.

This looks like an extremely fun and interesting extension of that. There's CS guys programming, EE guys doing hardware / sensors / haptic panels, full-on Engineering guys doing fluid dynamics, etc.

Destin seems like a great "jack of all trades" type that can get in there and ask really smart questions off the cuff. All the guys geeking out and being impressed with his intuitions and yet hesitant to confirm anything is hilarious to watch.

I got a 4mb Voodoo 1 passthrough card when they first came out and to this day still think it was the most "holy shit!" game changer I have ever seen. 800x600 using Glide was unreal. I also had a GF 256 and while it certainly smoked the Voodoos in performance, the difference between software rendering and the Glide API was mindblowing.

It is good to see that SkyNet's target recognition software is coming along, despite the delays based on the schedule we were taught.

Also, I am 10 angry ferrets in a suit, so I wonder how I would show up on this scan.

Slashdot had a post about an upcoming (about 1 year out) phone that can run pretty standard Linux distros. I took interest because I'm very annoyed about how UNconfigurable android is.

I have a Samsung Galaxy S2, very old by now, but hardware wise it still works fine. Software wise, it is shit. Android apps are massively bloated compared to when the phone was new, so the "system" partition of the phone is too small to install anything other than like 1-2 apps. From what I can tell, rooting might not help because there are still standard partitioning requirements? I dunno. Anyway, it is a big mess compared to a desktop, where I can partition things any way I want (which works great if you know what you are doing).

Anyway, I don't want to shill for Purism, the company that will be making the phone in the Slashdot article (for one thing, the phone is still a year or so away from final production), but they seem to be doing things right. They DO have some laptops on the market now, which apparently include a relevant feature mentioned in the write-up about their upcoming phone: hardware kill switches for the microphone, camera, and WiFi/Bluetooth.

If you read the ToS (hah! as if) for things like Facebook's app or the phones / OS themselves, you might see that you are "agreeing" to this kind of data collectionspying. If that sets the bar for "good" behavior, imagine what the bad guys (NSA, other agencies, state actors, unscrupulous advertisers, malware producers, etc.) can and will do. That's why any software solution is dubious. That's why electrical tape over your webcam is better than assuming that the record light is trustworthy. That's why a hardware kill switch is a good feature if you're concerned about this (like me).

Here's links to:
an article about the hardware kill switches in Purism's laptops, and
an article about their upcoming phone the Librem 5

I don't own any of their hardware. I don't like paid shills. That being said, I'm interested in what they are doing.

I doubt steam will be the first company with verifiably active software out there that it still being used past the reasonable lifetime of the licencee.

My prediction is that someone will see a business opportunity in buying up licence enforcement rights and doing what patent trolls do today... threaten to bring hell down on everyone whose licence is over, say, 30 years old unless they pay a relatively small (possibly recurring) amount to relicence. Even genuine licencees would need to produce proof under pressure.

My suggestion to someone enterprising who has too much moral fibre for the above is to somehow patent this as a business method, wait for the practice to become slightly established, then bring righteous justice down in a fiery rain of lawyers.

1. Mass shootings are <1% of the murder rate, and murder is <1% of the death rate. Getting wound up about mass shootings is as dumb as getting wound up about terrorism. They're both very small in relation to how much people freak out.
2. We already have lots of gun control. Especially in places like California, where the killer bought most of his guns legally and passed a background check.

3. Bump stocks were the real problem. Even the NRA is open to restricting bump stocks. Let's do that.

4. Let's not go overboard with the Australian solution. Australia's murder rate almost halved from 1990 to 2015, and people erroneously give the buyback credit for that, but in that same 25 year time span the US murder rate went down even more (from 9.4 to 4.5 per 100,000) The murder rate went down everywhere in that time frame due to banning leaded gasoline that causes brain damage. Also due to some smaller factors (more abortion, better software for predictive policing).

Freedom of religion is independent of civilian armament.
History shows that religious persecution is normal for humanity, and in most cases it's perpetrated by the government. Sometimes to consolidate power (with government tie-ins to the main religion), and sometimes to pander to the grimace of a majority.

Ironically, in this country, freedom of religion only exists due to armed conflict, albeit merely as a side effect of independence from a religiously homogeneous ruling power.



It's true that Catalonians would likely have been shot at if they were armed.
However, likewise, the Spanish government will never grant the Catalans democracy so long as the Catalans are not armed - simply because it doesn't have to.
(*Barring self suicidal/sacrificial behavior on part of the Catalans that eventually [after much suffering] embarrasses the government into compliance - often under risk that 3rd parties will intervene if things continue)

When the government manufactures consent, it will be first in line to claim that people have democratic freedom. When the government fails to manufacture consent, it will crack down with force.

At the end of the day, in government, might makes right. Laws are only words on paper, the government's arms are what make the laws matter.

Likewise, democracy is no more than an idea. The people's force of arms (or threat thereof) is what assert's the people's dominance over the government.



You can say the police/military are stronger and it would never matter, however, the size of an [armed] population is orders of magnitude larger than the size of an army. Factor in the fact that the people need to cooperate with the government in order to support and supply the government's military. No government can withstand armed resistance of the population at large. This is one of the main lessons from The Prince.

Civilian armament is a bulwark against potentially colossal ills (albeit ills that come once every few generations).

Look at NK. The people get TV, radio, cell, from SK. They can look across the river and see massive cities on the Chinese side. They know they have to play along with the charade that their government demands. At the end of the day, without guns, things won't change.

Look at what happened during the Arab Spring. All these unarmed nations turned to external armed groups to fight for them to change their governments. All it accomplished was them becoming serfs to the invited 3rd parties. This is another lesson from The Prince : always take power by your own means, never rely on auxiliaries, because your auxiliaries will become your new rulers.






Below is general pontification. No longer a reply.
------------------------------------------------------------------



Civilian armament does come with periodic tragedies. Those tragedies suck. But they're also much less significant than the risks of disarmament.
(Eg. School shootings, 7-11 robberies, etc -versus- Tamils vs Sri Lankan government, Rohingya vs Burmese government. etc.)

Regarding rifles specifically (all varieties combined), there is no point in arguing magnitudes (Around 400 lives per year - albeit taken in newsworthy large chunks). 'Falling out of bed' kills more people, same is true for 'Slip and fall'. No one fears their bed or a wet floor.

Pistols could go away and not matter much.
They have minimal militia utility, and they represent almost the entirety of firearms used in violent crime. (Albeit used to take lives in a non newsworthy 1 at a time manner)

(In the U.S.) If tragedy was the only way to die (otherwise infinite lifespan), you would live on average 9000 years. Guns, car crashes, drownings, etc. ~All tragedies included. (http://service.prerender.io/http://polstats.com/?_escaped_fragment_=/life#!/life)






A computer learning example I was taught:

Boy walking with his mom&dad down a path.
Lion #1 jumps out, eats his dad.
(Data : Specifically lion #1 eats his father.)
The boy and mom keep walking
Lion #2 jumps out, eats his mother.
(Data : Specifically lion #2 eats his mother)
The boy keeps walking
He comes across Lion #3.

Question : Should he be worried?

If you are going to generalize [the first two] lions and people, then yes, he should be worried.

In reality, lions may be very unlikely to eat people (versus say, a gazelle). But if you generalized from the prior two events, you will think they are dangerous.

(The relevance to computer learning is that : Computers learn racism, too. If you include racial data along with other data in a learning algorithm, that algorithm can and will be able to make decisions based on race. Not because the software cares - but because it can analyze and correlate.)

(Note : This is also why arguing religion is likely futile. If a child is raised being told that everything is as it is because God did it, then that becomes their basis for reality. Telling them that their belief in god is wrong, is like telling the boy in the example that lions are statistically quite safe to people. It challenges what they've learned.)



I mentioned this example, because it illustrates learning and perception. And it segways into my following analogy.



Here's a weird analogy, but it goes like this :

(I'm sure SJW minded people will shit themselves over it, but whatever)

"Gun ownership in today's urban society" is like "Black people in 80's white bred society".

2/3 of the population today has no contact with firearms (mostly urban folk)
They only see them on movies used to shoot people, and on the news used to shoot people.
If you are part of that 2/3, you see guns as murder tools.
If you are part of the remaining 1/3, you see guns like shoes or telephones - absolutely mundane daily items that harm nobody.

In the 80's, if you were in a white bred community, your only understanding of black people would be from movies where they are gangsters and shoot people, and from the nightly news where you heard about some black person who shot people.
If you were part of an 80's white bred community, you saw black people as dangerous likely killers.
If you were part of an 80's black/mixed community, you saw black people as regular people living the same mundane lives as anyone else.

In either case, you can analytically know better. But your gut feelings come from your experience.



Basically, I know guns look bad to 2/3 of the population. That won't change. People's beliefs are what they are.
I also know that the likelihood of being in a shooting is essentially zero.
I also know that history repeats itself, and -just in case- I'd rather live in an armed society than an unarmed society. Even if I don't carry a gun.

-scheherazade

Gutenberg called, he wants his kerning back.

To me red colored font is the go-to for people that just discovered the free video editing software on their computer.

There's YouTube and Facebook making it easy to add captions, there's the Apple Clips app and there are "social media video text packs" to use in editing software..
nooooooo..

Subtle subtitling is fine though.

Half of these apply to software development.

Lower case "i"s were popular back in the mid 90's with many software pirating groups. It doesn't have anything to do with the video but I thought I'd share. FYI.

I still have software boxes. The oldest one is Firehawk, Thexder 2, which my parents kept in my old toy box that I discovered several years ago!

First piece of advice. "Clever" code is usually bad code. If I saw that line of code in a code review, I would have to have words with the programmer.

More seriously, it depends where you are. There area lot of jobs right now. If by no professional experience you mean no internship experience, that can make things harder but isn't a huge obstacle at all (the experience itself doesn't often count for much, it's really more of a "why didn't you get an internship?" sort of thing). A good way to start in that case is to look for contract-to-hire positions, possibly through a recruiting/placement agency (look for ones that specialize in engineers). They generally know what they are doing, and will work hard to find a good place for you and they are genuinely on your side. We like to use these where I work because you can hire someone on a three month or whatever contract, and if it doesn't work out, it's a relatively painless separation for everyone (ie, you weren't "fired" you just finished the term of your contract). It's easier to get your foot in the door through a CTH, and then you just have to diligently and prove yourself.

As for preparing for real work (the actual coding part), that's harder. Since you really don't know what you'll be doing, it's not easy to prepare for it. You really have to learn software engineering on the job, and companies hiring entry level talent know that. That said, if you have a particular field in mind, looking for *good* open source projects along the lines of what you want to do and studying the source is good idea. Exposure to real-world, non-academic code is very useful. Getting involved and maybe becoming a contributor is a great idea (and looks good on a resume and gives you something to talk about in an interview). Working on personal hobby projects is a good thing too (though not as good as working on larger projects with other people), which again, gives you something to talk about in an interview. Keep your hand in. Have something to talk about at your interviews.

There are some good books. "The Pragmatic Programmer" by Hunt/Thomas is an excellent general-purpose programming practices book (more about mindset and approach and good patterns than technical details), and I can't recommend it enough. There are some others, but they escape me at the moment. Google is probably your friend here. If you can find a second hand set of Knuth for a reasonable price, buy it up. It's not even remotely worth actually reading, but it looks good on a shelf.

Good luck and don't sweat it. You have a degree that makes you very employable. You'll find something that you like without a doubt. If you're lucky it will be your first job, if not, no big deal--move on to the next thing.