678 karma · joined January 11, 2014
I've designed a water cooled mITX system with PCIe GPU that should've fitted into a 2DIN car radio slot, which is doable with a deep enough slot, a PCIe riser, and even a DC/DC power supply in the box. I never got around to actually building that due to life getting in the way, but the components ended up in a laser-cut acrylic cube crammed as small as can be. I have to say the laser-cut acrylic case works quite well, and is well within reach of anyone with a maker space close-by and basic CAD skills.
TL;DR: anecdote about SFF PC building.
Especially doing embedded work, and without doing proper mockups and test driven dev, the turnaround time with uploading code, rebooting the device, and waiting for a runtime error is quite long, and more compile-time error checking could help.
However, I also feel like types are more important to JITs and compilers optimizing high-performance numerical code, and dropping to C to do that with Elixir's FFI is thankfully simple enough.
I'm quite ok with Duck-Typing, as it does help me to iterate fast, even if it doesn't help the computer go fast :)
The best end result was largely unreadable code. Why? Because the junior developers tasked with the MISRA compliance efforts were measured by reducing the number of warnings instead of improving code quality.
The bonus was actual breakage in the field, as the test coverage of the legacy code being converted was particularly abysmal. But not to worry, another junior dev was tasked with creating unit tests for every function! With a codebase unsuitable to unit testing through fuzzy interfaces, that effort was about as effective as one would expect, too. </rant>
This is not surprising, as the team structures, at least as of a few years ago, were traditionally set up with tradtional manufactirng in mind, around parts and control modules, while the functionality exploded (within 1 or 2 generation of cars) and crossed those boundaries without adequate processes in place properly architect the interactions from a bird's-eye view, creating major computing power, network bandwidth, and most importantly to OEMs, cost bottlenecks.
And as cost is king, nobody wants to budge on increasing cost on their own module, and critical architectural decisions aren't made as much as put off until there isn't any other choice left except to hacking in the most critical bits with one eye closed and hoping somebody else's jenga tower falls first.
That, I imagine, is how you get that GPS time thing, I can see how it all started: "Oh, I can save $.30 on my module if I don't put in an RTC, that'll get me a nice bonus for cost saving, GPS is going to have one anyway ..."
For all intents and purposes, they worked and felt like the modern scooters, except that they had quick swap, fast charge AGM batteries. If we wanted to run an errand the next town over that would exceed a 30-40min ride (30min was a typical rental period), we'd just pack some extra batteries!
Those scooters were custom inventions, but larger scale commercialization never got anywhere and the business eventually died because of the battery tech being too cumbersome for consumer use, and the same legal questions that still plague us today, though it seems like electric bike usage the past 15 years has allowed at least some legislatures to give alternative powered transport a chance. As they should, as replacing large lumps of metal moving through our cities at unsafe speeds with much smaller lumps of metal moving a lot slower can only be a good thing for residents, pedestrians, and the environment.
The idea that FBA doesn't actually get me parts from the seller I picked has never crossed my mind. I certainly wouldn't have bought quite a few things if I knew that possibility existed.
The released video looks like the latter, though it could also just be standalone dashcam footage. It is also pretty mangled by compression, especially the dark parts are just completely blocky, so it is probably not a good indicator of what the vehicle saw.
OTOH, bikes can be notoriously hard on image recognition, for example it is not unheard of that reflective rims are interpreted as continuation of a curb or lane marking. LIDAR and RADAR should see them, though, and they probably did, so it is indeed unclear where it all went wrong.
The purpose of robots.txt is to guide bots away from circular links and such that would result in bogging down the site and causing undue amounts of nonsense traffic.
The purpose of robots.txt not access control.
EDIT: typo fix
Stuff like this exacerbates disrespect, distrust and suspicion in employer/employee relationships, in a way I believe no one benefits. Employers tend to use these tools to aggressively police minor infractions, though pretending to only want to catch the few bad apples, driving away the good employees in favour of those who think they can game the system anyway with a tit-for-tat mindset.
In the end trust is eroded, everybody is unhappy, and the underlying issues as to why those bad apples aren't doing their jobs in the first place is never resolved or even investigated.
But, human interaction will never be without ambiguity, and we cannot eliminate the risk of being misunderstood or deliberately misconstrued without (especially) marginalizing those who are at a disadvantage in the first place.
I feel like this is the right way to approach things: treat everyone respectfully and responsibly, even if there's a slight risk to it. (As a strawman: "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety")
- if you need more parts, eg. flash, you go from having one thing in your pocket to carrying a bag anyway
- dedicated UI and buttons for adjustments while shooting without having to look away from your subject or having to change your grip
- much larger sensors means more light to work with during shooting and post-processing - dedicated glass that you can't quite yet replicate with light-field tech
The smartphone can do many of the things a dedicated camera can, it's just not as good on almost all fronts, and much worse in some aspects. You can under more and more conditions get images that rival DSLRs, but not ALL condititions: If you can control time, light, and subject all at once, a dedicated camera can be matched. If you can't control of only one, grab a dedicated camera.
The tactile UI is one major gripe against smartphone photography for pros and enthusiasts alike, which is why a phone to some extent needs to be smart/automatic, and while today's image sensors straight beat the pants off any predecessing image sensors, physics still poses hard limits on noise and light capture.
Today's image sensors are very close to be able to count individual photons, and making the sensor larger means being able to capture more of them at a time. Tricks are being worked on to extend dynamic range and lower noise (like double exposure HDR), so image quality still increases, but the larger image sensors profit from those developments just as much as the small phone ones. The days of small image sensors being good enough to beat a human eye are still far off.
TL;DR: dedicated tactile UI, physical interfaces, physics, can't quite be beat by all the high-tech we can pack in a smartphone package.
If you have an arabic sounding or looking name, it's really not a stretch to imagine that you have a name that is similar enough to someone on a watchlist and are interrogated for it, or held, or prevented from boarding a flight. If you are travelling with your family, this is not a minor inconvenience, but a real source of stress and anxiety. You just don't know the repercussions it will have on you AND your family.
The "get pulled aside for some extra questions" happens to a Maroccan colleague of mine every time he visits the US for work, and means sitting around in a crowded room for a couple of hours at best. He expects it, and just tells his colleagues to just meet him at the hotel after getting out of the plane, but this isn't something that I consider acceptable.
What has been slowly creeping in without enough people noticing is that instead of being welcoming, travellers are now foremost suspects instead of guests (not only the US). If you're funny looking, you suddenly have no rights, and there is no due process. That is scary, especially when you're far away from home.
Even for people like me, who aren't funny looking or are in any form or shape a threat, there is a chilling effect. I like to travel, and for example have been to Iran a couple of years ago as part of a longer trip. Today, I could not make that same trip as lightheartedly, and would probably "self-censor" myself out of it in fear of future repercussions when travelling to the US or other western countries with an iranian stamp in my passport. Even if it is simply FUD, and most probably would not cause real problems for me, I do not wish it to happen to anybody just because they were born in the wrong place or have the wrong name.
i would agree only if there is sufficient discipline and experience on the team, management included. Spaghetti C++ can be a lot harder to untangle than spaghetti C, in my experience.
I don't quite think that's the case. More like 35, by the timeline given. This isn't old-timer grumpyness, it's simply seeing something you grew up with change, while you lose your childhood naivity, and it loses its innocence. Welcome to adulthood. It ain't quite as unilaterelly great as we all pictured growing up ;)