Disqus - Latest Comments for skoop

Re: Mental Health in the Workplace (Stefan Koopmanschap) > SymfonyCon 2019 Amsterdam Conference Videos | SymfonyCasts

skoop — Fri, 06 Aug 2021 09:11:00 -0000

Glad you liked the talk. And yes, one-on-one's can be really useful, but for it to be useful the environment needs to be safe to talk about such things. Unfortunately in quite a few companies I've noticed that the environment does not feel safe enough to mention such things.

Thanks for your comment!

Re: Check your SQL — Skoop.dev —

skoop — Sat, 02 Jan 2021 04:17:19 -0000

This is a good point, I could've indeed done that. Unfortunately I don't have access to their production servers. Locally it would've indeed been possible. But once I tried the main query on that request and that wasn't the issue, I wasn't sure anymore it was an SQL problem, so I decided that profiling made more sense. The fact that I ended up back at the database... well, yeah, I could've used the slow query log for that.

Re: WordPress and HTTPS-terminating proxies — Skoop.dev —

skoop — Mon, 11 Mar 2019 06:13:52 -0000

Thanks, I had not thought of this.

Re: Surface Book 2 For Development — Left on the Web —

skoop — Fri, 01 Mar 2019 03:20:02 -0000

I've never really got airdrop to work correctly. I've mostly used Dropbox and Google Drive in the past for exchanging files, and that still works fine after switching to Windows.

Re: Some changes for me — Left on the Web —

skoop — Mon, 28 Jan 2019 09:44:36 -0000

If I can do it, you can do it. Just keep making radio, and keep creating demo's to send to radio stations. :)

Re: Surface Book 2 Nvidia card not recognized — Left on the Web —

skoop — Fri, 21 Dec 2018 06:31:49 -0000

Hi Michael,

No, I've never really found a solution. However, the problem seems to have disappeared by itself after some time. I have no idea how, or why. My current theory is that the connection between screen and base station some times does not make the right connection if you've disconnected the screen and reconnected it. This is the best theory so far. No idea though.

Re: Surface Book 2 For Development — Left on the Web —

skoop — Mon, 23 Apr 2018 09:51:46 -0000

Laragon? I had not looked at that, will have a good look once I purchase the Surface Book

Re: Surface Book 2 For Development — Left on the Web —

skoop — Mon, 23 Apr 2018 02:58:12 -0000

Aside from using bash in the WSL, I haven't dug into it much. I like being able to use bash (or zsh) for quick access to files with less and tailing log files. Aside from that I haven't dug into it much more. I had no real need for it, especially given the limited time for testing. If I were to actually get a Surface Book 2, I may dig deeper into it. Perhaps running Docker on the WSL instead of Docker for Windows would be a good idea, for instance.

Re: Surface Book 2 For Development — Left on the Web —

skoop — Mon, 23 Apr 2018 02:55:15 -0000

Sequel Pro does anything I need it to do: I can buiild queries easily, alter data, update schema. And the interface is very intuitive. I'd be interested in hearing what your problems are with Sequel Pro, as I've never really had any issues with it.

I need to check DataGrip again. I tried it when they first introduced it but it really wasn't usable yet at that point

Re: Surface Book 2 For Development — Left on the Web —

skoop — Mon, 23 Apr 2018 02:53:19 -0000

excellent, thanks

Re: 3 weeks without coffee — Left on the Web —

skoop — Tue, 20 Mar 2018 02:16:53 -0000

oh, that last side effect was something I didn't even know could happen. I'll be curious to see how that will work. I'll test that side effect in Verona when I'm at PHPDay :)

Re: 3 weeks without coffee — Left on the Web —

skoop — Tue, 20 Mar 2018 02:15:51 -0000

haha. nothing sad about it. it's not a competition :)

Re: Call to conference organisers: pay your workshop instructors

skoop — Thu, 08 Feb 2018 04:44:49 -0000

I see where you come from, but to put your call into a bit more context:
A lot of conferences don't make a profit. The conference-part actually loses money. workshops/tutorials are usually the way for a conference organizer to break even.

I understand where you come from, and I surely agree both tutorial speakers and conference speakers could be valued a bit more by conference organizers (most organizers know the value, but there are a few that certainly don't). Having said that, I'll gladly submit a tutorial to a conference that won't pay me for doing the tutorial. I like delivering a tutorial and the conference will give me a platform. More often than not I give a smaller version of a full training, and mention so at the conference so people know there's more where that came from. But I've set a personal rule on conferences, to make sure they value me as a speaker (see: https://leftontheweb.com/bl... ) I only submit to conferences that make an effort to reimburse me for the costs of speaking.

Re: Pragmatic coding — Left on the Web —

skoop — Wed, 11 Oct 2017 14:06:44 -0000

When you get the result that they are looking for your solution is right. It may not be the only solution to the problem, however. There is no single right solution to these problems, and that is the beauty of it.

Re: Company and team culture — Left on the Web —

skoop — Tue, 04 Jul 2017 02:17:01 -0000

Yes, you are right. Perhaps the focus should be more on simply not excluding people. That should just be the default, but unfortunately, it is not that way on a regular basis.

Re: The idempotent command — Left on the Web —

skoop — Wed, 14 Jun 2017 11:01:54 -0000

OK, that sounds good actually, and for this use case would actually work well. But the caveat you find is something to keep in mind.

I guess both solutions would work well and have their own ups and downs. For the specific situation that we were handling above I guess your solution would work fine. Good to keep in mind. Thanks.

Re: The idempotent command — Left on the Web —

skoop — Wed, 14 Jun 2017 10:45:14 -0000

That is good to know. But what if the machine that was marked the leader would somehow go down or otherwise end up in a hanging state. Would another machine get the tag 'leader'? And does it get a notification of that?

Re: The idempotent command — Left on the Web —

skoop — Wed, 31 May 2017 08:08:27 -0000

Yeah, I like that approach, I think it works really well, but for our current use case, that's still overkill. At a later date, we may still want to migrate to a system like that though.

Re: The idempotent command — Left on the Web —

skoop — Wed, 31 May 2017 07:08:18 -0000

For us, this is not (yet?) a problem. Of course, we could extend the timeout if this becomes an issue.

Re: The idempotent command — Left on the Web —

skoop — Wed, 31 May 2017 05:12:39 -0000

If it is an uncaught exception or somesuch the console.terminate will handle the cleanup. If PHP actually crashes and dies then the timeout that is passed to the acquireLock will make sure that once the timeout is gone, the script can be run again. For our usecase, that is good enough.

Re: To Exception or not to Exception — Left on the Web —

skoop — Mon, 24 Apr 2017 03:00:36 -0000

that's what we got the @throws docblock for

Re: To Exception or not to Exception — Left on the Web —

skoop — Mon, 24 Apr 2017 03:00:18 -0000

yeah, I agree with this naming scheme. Sounds good.

Re: To Exception or not to Exception — Left on the Web —

skoop — Mon, 24 Apr 2017 02:59:29 -0000

hmm... I personally don't like this naming scheme. Although it is very clear, I'm not sure we should be *this* explicit about the behaviour of code. I feel it should read like language. Like english. This reads like technical documentation. And of course, returning null is a whole different subject that is open for discussion.

Re: To Exception or not to Exception — Left on the Web —

skoop — Mon, 24 Apr 2017 02:58:05 -0000

agreed.

Re: To Exception or not to Exception — Left on the Web —

skoop — Mon, 24 Apr 2017 02:57:44 -0000

I don't fully agree with your statement about find having the expectation to find something anymore than any other search. You always expect to find something. But yeah, the struggle of naming, for sure. perhaps the getById() example is not right, but let's call it fetchById() then. Still the same implication: Something with that ID should exist. With findById(), this is not that clear.