Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shandor
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
181.
▲
by
shandor
10y ago
Definitely. This is exactly the reason I switched from Chrome ro Firefox. I mean, when I'm on mobile it's even more important than on desktop that I have my adblocker in place, as both bandwidth and screen estate are more limited.
182.
▲
by
shandor
10y ago
Could you elaborate a little what has changed there? My understanding is that submodules are still considered a mess, but would be really nice if some actual improvements have happened.
183.
▲
by
shandor
10y ago
This probably depends on your exact role, but usually there's enough technical role left for devs-come-PMs that keeping your technical skills top-notch is really important. In the end, you are the one to make a lot of decisions that ha
184.
▲
by
shandor
10y ago
Sorry but why is that a bad thing? I can understand that it's "bad" that their story was lacking at release, but isn't it awesome that they'd go to such lengths to serve fans and buyers and have a good product in th
185.
▲
by
shandor
10y ago
The same got my attention too. A really great idea, though I'm not aware of it being used currently at all. It might be, but I've never come across/heard anyone mentioning it. Hopefully this takes root! Actually, couldn'
186.
▲
by
shandor
10y ago
That's actually fascinating. Is the formula for the mentioned "developer impact" a hush-hush trade secret, or can you go into more detail on how you calculate it? Would be really interested in hearing more!
187.
▲
by
shandor
10y ago
Yeah, but actually the easier the exploit the more concerning this kind of stuff is. I mean if we can't even trump the easy stuff, how about the more sophisticated attacks?
188.
▲
Stealing sensitive information by using pixels of ad banners
(boingboing.net)
6 points
by
shandor
10y ago
|
5 comments
189.
▲
by
shandor
10y ago
Sorry, but I really have to say that I think adding a waypoint through yet another language can't be a good thing. You're probably much better served by using the time saved from the second rewrite on the actual rewrite (C to Rust
190.
▲
by
shandor
10y ago
I have nothing against Joel. But to be fair, as people in finance use to say, "history is not indicative of the future".
191.
▲
by
shandor
10y ago
While this sounds good in theory (and I've been in teams that were very self-organizing and operated well without a formal tech lead), I feel that it omits some key aspects of real life. Let's look at the list towards the end, for
192.
▲
by
shandor
10y ago
Well, one might notice "everybody" has to be a rhetoric exaggeration, since there's absolutely no way even remotely close to "everybody" would have any codebase at all whatsoever, not to talk about 20 year old legac
193.
▲
by
shandor
10y ago
> IMO it would be great to get folks who write the enormous base of existing realtime apps driving critical devices everywhere to sit up and take notice of Rust. It would, and definitely should, move into the direction of safer languages
194.
▲
by
shandor
10y ago
Officials reported (sorry, no link) that they had "heavy reasons" to think that the attack was 1) done by actual criminals 2) pointed elsewhere, and the heating system was just one of the many systems used to initiate the attack.
195.
▲
by
shandor
10y ago
> we encourage candidates to use all resources on our take home interview test This sounds great. In my response to another comment I was worried if accepting-but-not-encouraging this kind of behavior would put the interviewees on uneven
196.
▲
by
shandor
10y ago
You and GP both bring up a really mind-opening view into this. "Conversation catalyst" indeed, sorry but I'm definitely stealing that one. > Outside of very specific roles, non-trivial software development is a team effort
197.
▲
by
shandor
10y ago
> We have an extension to the take home done paired on site that usually involves significant refactoring That sounds actually brilliant. While some might argue that this comes back to the "whiteboarding under pressure", honest
198.
▲
by
shandor
10y ago
Sure I would, I have the $X/h to divide between them for helping me ;) Seriously though, I guessed that many companies probably must have this kind of laid-back attitude on the matter, since it would be stupid to presume they are ignor
199.
▲
by
shandor
10y ago
This seems like a pretty popular take on the interview process here on HN. However, there's one pretty glaring flaw that I've never seen discussed: if the interviewee can take the problem home, what prevents them setting up a hack
200.
▲
by
shandor
10y ago
I hear this from all over the world, and I honestly don't understand it. Or rather, the only way I can see this happening is that everyone, everywhere on the buying side is either actively doing harm or so incompetent those are indisti
201.
▲
by
shandor
10y ago
I won't pretend to having any kind of statistics on the matter. But the whole point is that usually in embedded systems, there is no separation between "application" and "kernel", at least on the low-end of CPU powe
202.
▲
by
shandor
10y ago
Sure, it's not a panacea. But at least it gives a much better foundation than what we usually are having now.
203.
▲
by
shandor
10y ago
I'm having really big expectations on seL4. The modularity of a microkernel with the security of formal methods is something that would give hope of solving some really fundamental problems with the "IoT scene". I.e. having g
204.
▲
by
shandor
10y ago
I have a feeling that we're talking about a little different things. My meaning was that I rigorously try to put a price tag on my free time, just like my minutes are counted and paid for at work. This really helps me to put many prior
205.
▲
by
shandor
10y ago
Oh my god yes. I generally put a price tag on everything I do. Depending on ones salary it might be anything from 20 to 300 per hour. Then, if I see myself "making a loss" according to that calculation, I start paying for someo
206.
▲
by
shandor
10y ago
Yes, just rebase your whole feature branch on top of origin/master. Long-running branches with huge amounts of commits are bad anyway for multiple reasons, so it's not like you're bringing too many commits at once with any gi
207.
▲
by
shandor
10y ago
This is why rebase is so, so much better than merge. And it's infinitely better for bisecting, too. Simple, completely linear history for origin/master is just so powerful in many that aspects that I'm constantly baffled why
208.
▲
by
shandor
10y ago
> Actually the easiest thing is simply not to care about how your log looks. Yes, that sounds as easy as anything that accepts the idea of "let's do this the shitty-but-quick way now, and pay the technical debt later". So
209.
▲
by
shandor
10y ago
This. I previously worked for a company that does purely outsourcing work; they nowadays have a bossless hierarchy (apart from project leads, who are named anew for every project, and basically anyone willing can volunteer). It seems to wor
210.
▲
by
shandor
10y ago
Another problem is power consumption. Wit the current, appallingly bad battery technology the only way off-the-grid IoT can hope to proliferate is by keeping the power consumption as small as possible. This is of course a problem for a rath
More ›