prions

This was my question as well. I believe the scope of this project is to interpret Python bytecode using Python.

A lot of the arguments complaining about the iphone's notch are missing two points:

1. The notch is necessary to house faceid sensors that no current android phone with a notch has

2. The notch isn't cutting into the screen, the ears of the notch are actually cutting into the bezel.

A lot of hate towards Apple (justified or not) has been towards their preference of form over functionality. It's ironic to see Android handset makers taking a functional compromise from the iphone X and making it a completely cosmetic feature.

iOS Developers have well known that in order to develop apps for Apple, you play by their rules. Why is this a surprise to anyone?

Give your requirements, Newark would be the best candidate

- EWR close by, with public transportation connections

- Strong local universities, both in tech and business (Rutgers, NJIT, Stevens)

- Newark development is rising, downtown is still relatively sparse

- Audible is already in Newark

Skeptical it will actually happen though. Wouldn't even consider myself a fan of Newark (even though I go to school here), but it's interesting that it's the smallest city on the list population wise.

What's different now is that we're seeing huge mergers between telecom companies and media companies.

The internet is more vital to everyone now than compared to 15 years ago. Every year more and more people are choosing to eschew traditional cable for Netflix et al.

With NN being repealed, it opens up ways for ISP's to promote their own content and shut out others like nothing that's happened before. This whole repeal smacks of anti-consumerism and pro corporate nonsense.

Hopefully they improved the wobbly hinge/upper half and the sharp scratchy corners.

I believe we'll see more interesting solutions in industrial IOT when 5G becomes more widespread and industries can start touching problems that lower latency and higher bandwidth wireless can tackle.

Fellow beer brewer here!

I wrote my own small weather service, http://www.brilcast.com/, and re purposed the waterproof sensor to help track and record the process from lautering/sparging all the way to transfer to primary fermentation.

The setup is simple. Sensor code is written in Python, then it's sent to a SQLite database running on a Flask webserver. The frontend uses D3.js to visualize the data. The entire service is hosted on Pythonanywhere. It's quite spartan, but it works well. https://github.com/williamBartos/brilCast

I currently work at Nokia/Alcatel-Lucent/Bell Labs/foo and there's a lot of restructuring going on. Lots of layoffs and org changes which is making everyone's head spin and adding a lot of uncertainty into the workplace.

A big part of the Alcatel acquisition was acquiring their customers - in a recent All Hands meeting, Nokia stated they were planning to move away from "nuts and bolts engineering". In America at least.

I'd say cost. All the author did was remove the cpu lid and replace the cheaper thermal paste with a better after market brand.

Billable hours are the work of the devil. I remember my boss explaining how "I needed to work back all my vacation hours" was a good thing.

A French press works perfect for me. The cold brew has too much silt which instantly fouls the coffee filter.

Yes! They also have a museum and a showcase room. I was able to see the first transistor.

I believe they're reconstructing Dennis Ritchie's original office. They still have his chalkboard too.

I just stared an internship at Bell Labs Murray Hill. Growing up in Holmdel, I've been a fan of Bell Labs since childhood and feel so happy to be working here. The atmosphere and energy from all the amazing achievements is really palpable.

Word is the acquisition of Alcatel Lucent by Nokia has really put Bell Labs back into the public spotlight. Excited to see what the future holds and I hope I can still be a part of it!

"Move fast and break things (and shortchange everyone in the process)"

We're so sorry (again)

Exactly- risk aversion is the driving force. When I was a civil engineer, paper was king. It's wasteful printing 5x copies of one 1000+ page spec, but it's reliable.

I did write a shop drawing automation program when I worked at the office. There was resistance to it at first, but getting the right people on board and demonstrating the improvements helped a lot to get it all the way to the executives of the company. During my push to get my software adopted I learned a lot similar to your perspective; many professionals don't dislike new technology, but they're unwilling to put their name beside it unless it's proven to work.

A lot of young engineers like myself want to walk in on the first day and start shaking things up. But working in a slower, more risk averse field has made me a better software engineer by tempering some of those impulses to adopt the latest and greatest tech. Taking a pragmatic and proven route will nearly always get you reliable and predictable results.

The other comment answers your question. PATH trains going along 6th ave share stations with NYCT, but run in their own tunnels.

The effects political dysfunction are really starting to materialize now. Penn Station, North River Tunnels, PATH tunnels are all in really critical states now.

I live in Bayonne and the truck traffic is horrendous. Not only is the congestion from the port to the toll plaza bad, the traffic on the two lane highway getting onto the turnpike (and especially the turnpike bridge) is awful.

I'm cautiously optimistic that the construction will help, but the big issue is that as long as trucks are sharing the road, traffic will be much worse.

Law enforcement and politicians really need to pay more attention to how dangerous or careless some truck drivers are. It gets old having to literally and figuratively hold your breath every time you get stuck near a truck.

The issue with PATH is that the tunnels are extremely old - older than the Manhattan subway tunnels.

Whereas Manhattan subways have two tracks per tube, the PATH has only one. Service is not only slower, but you usually wait significantly longer just sitting on the PATH before it even leaves the station.

Hurricane Sandy also did irreparable damage to the tunnels crossing the Hudson.

As a (now former) wastewater engineer, I'd take sanitary sewers over septic tanks anyday.

With septic tanks you run into many more maintenance issues with things like clogging, overflowing, cleaning, etc. Not to mention this cost is borne onto the homeowner and not the municipality.

There's also persistent groundwater issues. Even if you have good soil permeability and aren't impacting an aquifer, multiple septic systems can really start causing environmental harm on surrounding waterbodies.

For many people, having sewerage isn't an option, but there's a good reason many municipalities are investing millions into moving their residents off of septic systems.

If you're serious about writing a parser, why not go for a bottom up parser?

It eliminates a lot of the headaches with top down/recursive descent parsers like left recursion and backtracking.

It really should be considered. I'm a registered (civil) EIT. IT would help towards the ambiguity in hiring and the ever increasing absurdity in interviewing.

Especially since the conflicting statements of "software jobs need protection to ensure good salaries" and "everybody needs to code" are all to prevalent here.

Being a PE means you have a certain level of experience and skill. It's a distinguishing feature and sets you apart as a "real" engineer. Additionally, it holds you to an ethical code.

What continues to astound me is the lack of rigor and ethical backbone coming from engineers in important places. Yeah you're not building a bridge, but incidents like Volkswagen and Yahoo could have been prevented if people's jobs were bound by not being unethical.

I'm still breaking into a software job and had a homework problem for a company, with a week deadline. Since I worked full time, I spent the majority of my free time working on this problem.

I was happy with my solution, and disappointed when I was rejected.

Rejection is fine, but what upset me more was radio silence when asking for any feedback on my solution. As a young engineer it would have been amazing to get feedback from professionals.

The two other books in the series (Count Zero and Mona Lisa Overdrive) are both great as well, but I found that the first had the most magic.

In the same vein, Snow Crash by Neal Stephenson is great as well. Its essentially a parody of cyberpunk but hilariously well written.

Seeing this list inspired me to write about the list I keep for the books I read, many of them cyberpunk/scifi. After reading so many of these types of books, you can't help notice their elements in other media.

It's interesting in seeing the print inspirations for many of these movies. The term "The Matrix" was first coined in William Gibson's Neuromancer and considered to be the seminal Cyberpunk novel, even predating Ghost in the Shell.

Definitely a must read for any Cyberpunk fan!

I'm someone who graduated with a non-cs engineering degree (and worked professionally as an engineer) whose now in a MSCS program after trying my hand in the job market. Not for a lack of trying, but my experiences definitely relate to an uphill struggle just to get even noticed. And before anyone says "you should do x|y|z", I've done my part pretty well. A few decent sized personal projects, constant studying, meetups, networking, github, etc.

I hear a lot of anecdotal evidence (mostly from professional devs who have degrees) that they know a friend or coworker who doesn't have a degree.

The truth is that the system for recruiting and hiring is really based around colleges, students, and degree holders. Starting from the application requirements, you see that most applications require a CS degree (or equivalent). Then the technical interview is aimed at fundamental CS questions, most of which students are accustomed to.

So for someone self taught, face to face interactions are a lot better. But even going to events/meetups, you notice a distinct change in demeanor of the recruiter when you mention you don't have a CS degree. It really is a tiring battle just to prove that you're competent.

Do I believe that you 100% need a degree to get a CS job? Definitely not. But without one, your options are very limited and on top of that you'll need a lot of luck and effort just to get past the first hurdle.

Definitely The Book of the New Sun by Gene Wolfe.

Definitely justified. Most civil engineers are state licensed which is a years long process in itself. Just to become a certified Engineer In Training I needed a 4 year engineering degree and a 6 hour exam. To become licensed you need 5+ years of experience and an 8 hour exam.

I'm not arguing against those safeties, but I believe there can be improvement in the regulation process. The NJDEP has only recently moved to a digital permitting system.

Most are moving to digital formats, it's just very time consuming when you have stacks of 24x36 plans. Our firm has an entire portion of a building dedicated to just paper storage and we have interns scanning old material every day.

One of the most satisfying parts of my job is getting first hand access to seeing so much interesting infrastructure.

I specialize in water, so getting access to the treatment plans is my favorite. Drinking water plants are mostly off limits for the public but I've gotten tours of a few.

If you're around the NYC area try visiting the Brooklyn Wastewater Treatment Plant. Those egg shaped digesters are really well designed. I even heard of a couple getting married there.