Famous last words of many a unemployed junior developer...just sayin'.
4,146 karma · joined September 7, 2015
Famous last words of many a unemployed junior developer...just sayin'.
> ...evidence that substances claiming to treat or prevent alcohol-induced hangover work.
> Will BlackBerry Android devices still work after EOL date?
> BlackBerry Android devices will not be impacted by the EOL of infrastructure services unless they are receiving redirected email sent to a BlackBerry hosted email address, or assigned an Enhanced Sim Based License (ESBL) or Identity Based License (IBL). ...
[1] https://www.blackberry.com/us/en/support/devices/end-of-life
I'm led to believe[1][2] outrageous profiteering starts well before such donated assets---which are sold in bales---ever reach the shores of Africa.
What privileged 1st world citizens naively perceive as altruism turns out to be nothing more than a facade for egregious textile dumping with middlemen in transit to squeeze out any remaining residual profit...and it's turtles all the way to the ad hoc environmental disasters this racket has created in already immensely impoverished countries.
[1] https://www.abc.net.au/news/2021-08-12/fast-fashion-turning-...
In the US market[1], it appears to be a discontinued model.
[1] https://www.lenovo.com/us/en/p/accessories-and-software/moni...
In practice, I'd hazard a yes.
Keyword: regularly...unless you're driving something that's pissing oil all over the place and/or has a cooling system that's out of service, at which point you clearly have much bigger maintenance problems and probably shouldn't be on the road with that vehicle anyways (perhaps even in a lawful sense).
> I would've said that the speedometer really isn't needed - if you go with traffic and don't hang out in the passing lane, you're never going to get in trouble.
The obvious naivety here is a dependency on another driver ahead of you both maintaining situational awareness and doing the right thing...never mind sparse traffic scenarios, e.g. super late/early hours, neighborhoods, small towns, rural areas, etc. In the case of incident, the police won't care; your insurance provider won't care.
> It's a lot more important to me to know if I've lost oil pressure or am overheating.
Contrived. There's a reason why high-contrast event indicators (termed "telltale" as defined by US FMVSS statutory regulation[1]) baked directly into every passenger vehicle which control for permissible location, identification, color, and illumination targeting driver visibility. These discrete telltales are explicitly designed to ping a driver's peripheral vision with the intent of eliminating a need for active monitoring in practice.
[1] https://www.ecfr.gov/current/title-49/subtitle-B/chapter-V/p...
I suppose that's an indirect admission that you weren't an EE major.
Furthermore, it's not a UltraSharp series display, which suggests (at a minimum) no proper color calibration out of the box...perhaps not just a personal nit given desktop productivity users tend to use them in multi-display setups almost exclusively. A decade-ish ago when the U2412M was in production, shit color calibration was a particularly egregious trend that Dell eventually corrected with their U2415 offering. Now the best they have to offer is U2421E, which eliminates the bottom bezel (nice for portrait mode users) and throws a USB-C hub on, but still no progress on the native resolution front and panel quality is reported to be inferior to its U2415 predecessor.
So I'm also stuck with U2415 for now, but I'd really like to see if coding on higher resolution displays truly squares with all the hype. Might have switched to 16:9 a while ago, but the substantial loss of vertical coupled with excessive horizontal when working in CAD has been a showstopper for me.
I just browsed through Lenovo's display offerings and didn't see a single 16:10 aspect ratio display listed anywhere.
Given the scale of the breadboarded rat's nest prototype, was this actually achieved?
[1] https://github.com/jdah/jdh-8/blob/c621a9980a7d4eb7aa4debc62...
Since when?
Design criteria baked into international building code is quite robust; not just naive static load, but wind, snow, seismic activity, fire/flood/termite resistance, etc. are all considered. That's a far stretch from something that can "barely stand".
I tried poking around here[1], but CPUC public discoverability is up there with the worst of enterprise...never mind that a decision/resolution/ruling/general order all sound roughly asymptotic to a non-lawyer.
Some common commands can also be annoying when the required minimum characters don't cleanly map to a single hand, e.g. [E][X][P][L][Enter] to explode; or when they map to the other hand, e.g. [P][L][Enter] for polyline.
Altium's approach is literally single hotkey sequencing (i.e. no [Enter] after every command) which map directly to menus that underline each hotkey as a reminder, e.g. to [P]lace a [W]ire or [P]art in schematic capture, it's [P][W] or [P][P], respectively, while the menus change with ever key press. Yeah, your left hand is all over the keyboard, but every key press is a meaningful context switch.
AutoCAD strikes me as a fundamentally different paradigm in that its command interface is "always active" so to speak, whereas menus/toolbars feel mostly like an optional overlay, at least to an experienced user.
Although AutoCAD is my preferred tool when drafting electrical architectures and wiring diagrams, the mouse as primary human interface is simply unavoidable in any sensible CAD, which makes constantly having to release the mouse to type the next command, or F3/F9 to toggle object/grid snaps (especially with shit modern keyboards without standard F-key separation e.g. MX Keys) admittedly annoying. I contrast this UX to SolidWorks which is overwhelmingly mouse+toolbar in a way that's comparatively trivial to navigate, or Altium which is driven by single hotkey sequencing that allows the other hand to stay fixed on mouse.
To be sure, military aviation doesn't give a flying fuck about virtue signaling. The name of the game is checklist and enumerated procedure compliance or GTFO the flightline/deck; it doesn't matter if you're a fighter pilot or maintenance ground crew.
> #1: MethaneSAT is the world's first satellite launched by an independent NGO.
So have they or have they not deployed?
I really want to believe KiCAD is there...but when billable labor rates are $150+/hr, and a single iteration of that complexity can easily burn US$10k+/ea in one-off prototype quantities + 4-6 month slip for manufacturing, assembly, reintegration, and verification testing, all of a sudden (free == cost-effective ?) becomes a very real risk consideration...never mind that I've yet to engage a customer that was willing to subsidize my development budget based on technical decision to assume a tool risk because it makes the cost of doing business marginally cheaper for me.
[1] https://web.eecs.umich.edu/~fessler/course/100/misc/chowning...
> As convoluted as this sounds, it makes more sense when visualised: [1]
...but does it??
[1] https://ajxs.me/static/img/articles/dx7_technical_analysis/f...
[1] https://www.bloomberg.com/news/features/2018-06-14/trump-s-p...