mpolichette

8 ms·

1.
by mpolichette 8mo ago
I don't disagree, but I think there is the otherside of that same coin... What if we could do other stuff while remaining productive. Rather than the example of missing first steps, what if we had, "Ok Claude, prepare a few slide
2.
by mpolichette 8mo ago
I thought they were talking about one of their coworkers /s
3.
by mpolichette 10mo ago
I've recently started writing an app intended for a raspberry pi that uses IMAP to automate this exact thing. The goal is for it to apply the rules and followup with actions while still letting me interact with my email from any client
4.
by mpolichette 1y ago
I'd also consider that, for these people, getting away with the cheating _is the game_ for them. What they're cheating at might be less important.
5.
by mpolichette 2y ago
Short of jail, nowhere in adulthood are you required to stay somewhere by law. On top of that, I don’t think the kid quietly using their phone and ignoring class is the main issue here… it’s causing issues with the other kids and making the
6.
by mpolichette 3y ago
I like the cataloging, but I dont see the periodic part of this.
7.
by mpolichette 3y ago
Could dementia in congress create a security threat?
8.
by mpolichette 3y ago
I tend to agree, however, I typically tell people that if you see longer function names, you should watch out for complexity. In fact, if I have to write some overly complex code that I can’t isolate for some reason, I will usually try to
9.
by mpolichette 3y ago
Computers were invented to speed up calculations, and yet the primary thing we use them for today is to read the news and send each other messages and memes… I think it’s totally reasonable, to expect developers to find the real use
10.
by mpolichette 4y ago
I have the same rules
11.
by mpolichette 4y ago
I think this option is still ripe for issues within a domestic abuse situation. The abuser would simply use their phone to “trust it”. Maybe a longer dismissal though?
12.
by mpolichette 4y ago
I always have to remind myself that they’re dependency arrows and not a sequence ordering. They make it look like it flows right to left even though time (or at least sequence) flows left to right.
13.
by mpolichette 4y ago
Oh, come on now, Zabzonk is a great name
14.
by mpolichette 4y ago
I read this as “The book is included”
15.
by mpolichette 4y ago
If you don’t fix it… and the code is working… what is the problem? I leave notes like that sometime as indicators of intention… or invitation to the next reader… but if it never changes and is not causing issues… that’s fine, leave it as is
16.
by mpolichette 4y ago
I can empathize with the author here that types can be very challenging to get right, especially with high amounts of dynamism. However, I think that saying it is "terrible for library developers" is a bit far. I think its terrib
17.
by mpolichette 4y ago
I've been using Workflowy for years now. I really love it. They been working lots of interesting features in but stick to the basics that everything starts as a list. You would be surprised what is possible w/ just a list!
18.
by mpolichette 4y ago
MDN docs are the best... they should monetize via high level articles and example implementations for systems. For example, the webRTC docs are great and explain a lot about how it works... however, there is very little information about go
19.
by mpolichette 4y ago
I think these questions come from the idea baked into charitable giving. When you purchase a good, the thing you're getting is obvious, it is what you're purchasing. However, when you're giving to charity, what are you getti
20.
by mpolichette 5y ago
I've thought about hooking into messages w/ a running mac before... Do you have a high level description of your approach? I looked in the iMessage GraphQL Server server repo for docs but didn't see anything obvious... On a
21.
by mpolichette 5y ago
I'll entertain this... Because, like it or not, you're often still sending/receiving documents? :) Also the semantics of the actions map really well to the use cases still. You're, of course, more than welcome to avoid t
22.
by mpolichette 5y ago
I'm with you on this one. I prefer it to be in your face simple to understand over the terse-ness. In the gist example, I actually prefer the SQL-92 approach where we are joining given an explicit comparison condition. Every other imp
23.
by mpolichette 5y ago
This ^ I feel like JS gets thrown under the bus in discussions, but no body talks about arcane file structures in Java or implicit pathing lookups which have the same kind of "historical path dependence" to why they exist as JS ha
24.
by mpolichette 5y ago
I want to agree with you... the problem arises because you're applying your values to those items... e.g. "yeah they're embarrassing/bad, but not really that bad"... However, it becomes scary when the people with ac
25.
by mpolichette 5y ago
I hope it stays down... oh wait, that was yesterdays thing...
26.
by mpolichette 5y ago
I used a fake name/email... went through the 22 questions and got meaningless results. Questions get grouped into 3 groups and you get a numerical score... literally it only says "Result: 22". No scale, no units, at best th
27.
by mpolichette 5y ago
It's wild that their demo is a real customer >This is a read-only view of real growth data from a Saascast customer — don't worry; they don't mind sharing it with you! I wonder if it'd be easy to tell based on the pay
28.
by mpolichette 6y ago
I don't think React is the problem here. I think communication and leadership is where fault lies. 1. Why hire a team of non-webdevs to do webdev. (on 2nd read, it appears they wanted to use the same team from the WPF app... ¯\_(ツ)_&#x
29.
by mpolichette 6y ago
It makes it seem really bad when you say "Government takes". The truth is, you're contributing back to people and the system which let you make and run a business that makes millions starting in your 20s.
30.
by mpolichette 6y ago
I don't agree... I think browsers are not the weak link here. I'll agree they have a large attack surface, but the communication channel needs to be secure regardless of what client receives it. > the most an attacker can do

More ›