Except that compilers are (at least to a large degree) deterministic. It's complexity that you don't need to worry about. You don't need to review the generated assembly. You absolutely need to review AI generated code.
Not sure? It seems to me that the pen that launched with the Surface Pro 3 (V2), still works to an extent with the Surface Pro 11? That seems rather good, no?
Funnily enough the first smartwatch that was interesting to me was a round watch, so I got the Pixel watch. I don't mind having the UI not being as usable (debatable), but I much rather have a nice looking watch, more like a classic watch. That's like, your and my opinion, everyone has their preferences.
For what it's worth, I do regularly set timers with Alexa when cooking, and I still hate using voice controls in the car... With timers the alternative is also a multi step process with probably smudgy hands, whereas just one button press to turn down AC will evolve into "turn down more, turn down more" with voice
Ever had a (lightly) sleeping baby in the car? Glad it finally got to sleep after hours worth of crying? Maybe, just maybe, I don't want to risk asking a voice assistant to turn up or down the AC. Scenario also works for sleeping co-driver.
Buttons are fine. Even though I prefer driving EVs, the reliance on touchscreen/ voice for everything is just annoying. At least for the most common functions like volume control, AC and stuff.
My absolute go to issue these days with Node is the persistence on doing the same type/interfaces as the browser. The absolute sh* show trying to make a FormData request in Node to work with native Node streams is mind boggling, just because fetch/FormData needs to be EXACTLY like in the browser. Sure, but how about I do not want to put a 100mb file into memory just because I want to use native fetch ....
To be honest, I just went for a small business subscription of Office 365 for personal use, which also gives you mail with a custom domain. SharePoint is decent enough when accessed from the mobile OneDrive App and offers out of the box indexing + OCR of images and pdfs. Also their document scanner is good enough to quickly get rid of all paper coming in...
> No links
> You can’t link to conversations. This means if you want to add context to a Jira ticket or in a code comment, you can’t easily do so.
You can, at least technically, if you know the message IDs (search for Teams deep links).. Not sure why they don't expose this on the UI though.. Shameless plug: If you are looking for linking conversation to Jira, try our app: https://marketplace.atlassian.com/apps/1220851/microsoft-tea...
Yeah, besides finally having some progress regarding signing, I think it's great they went with an option that is open and already is gaining traction.
I am:
a) a dev myself
b) head of a small dev/SAAS company/team
c) Atlassian Marketplace vendor
Jira is fine. Atlassian will be around for quite a bit, imho. They have a somewhat decent ecosystem, which helps a lot with the stickiness.
Jira could see a lot of improvement product wise, but at least it has been getting faster in the last year (still slow, though, but not as bad). Their new stuff seems to be a hit or miss, but I especially like their new Jira thing (Jira Product Management), mostly because it comes very opinionated.
I think Jira/Atlassian would benefit a lot from actually providing more guidance on how to properly use their product(s) depending on team size (e.g. moving from 5 to 50 to 500 person teams). Most other tools don't do this as well, but I think that would improve the experience for everyone, dev & mgmt alike..
You have an 8core laptop with 32gig RAM for $700? That's not super common though, I think usually you'd spend more like $2500-$3000k for it. Count in the reduced maintenance and hardware support + having your whole stuff in one place.. Might make sense if you are not super low on money
You can also make this the default when you press "Print" on your keyboard. Go to Windows settings and search for "screenshot". It's so hard to discover -.-
You'd think that choosing a stack based on your target audiences computing needs would be more common.
Choosing React over vanilla JS is not only required for simple state things imho - for complex state I'd even say some may use something like Redux/MobX. The development experience and speed vs vanilla JS is just unmatched. The amount you need to worry about adding / removing classes, with implicit state all over the place will soon slow you down soon much because of all the edge cases you haven't thought of.
I hope nobody starts off development for new apps in 2020 based on pure JS - even if you explicit target ultra-low-end devices, maybe try a lighter framework like preact (et al).
You know why it won for me? It had a Windows version from the start, so our team (Mac/Win) could actually get work done, since most other tools are Mac only.
email: tobi at yasoon.com