# like The SQL LIKE operator determines whether a character string matches a specified pattern, including wildcard characters. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## On my resignation as regulator of the Dutch intelligence and security services DevFeed: [On my resignation as regulator of the Dutch intelligence and security services]() Original publisher: [Read original article]() Published: 2022-09-09T08:55:00Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Security](), [like](), [interception](), [Hacking]() Tags: [authorization](), [hacking](), [intelligence](), [interception](), [national-security](), [security](), [technical]() ### AI overview A former member of the Dutch intelligence and security services oversight board explains his resignation. He says proposed changes would largely eliminate his technical risk-analysis role, reduce regulatory requirements for bulk interception, permit algorithmic analysis of bulk-intercepted data without external approval, and shift parts of oversight from prior authorization to ongoing or retrospective review. ### Source excerpt I've seen some mediocre automated translations of my Dutch language resignation statement go round. To prevent any confusion, please find the story here in English: Until today I was one of the three members of the board that checks warrants for the Dutch intelligence and security services. This board is called "Toetsingscommissie Inzet Bevoegdheden" or TIB. If either of the civil or the military intelligence and security services of The Netherlands want to use their lawful intercept, SIGINT or hacking (& some other) legal powers, they have to first convince their own jurists, then their ministry and finally the TIB. ## Bad Clients, Gordian Knots and Transparency DevFeed: [Bad Clients, Gordian Knots and Transparency]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-03-28T17:01:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Back end](), [Laravel](), [Development](), [like](), [PHP](), [JavaScript]() Tags: [backend](), [consulting](), [developers](), [javascript](), [laravel](), [php](), [shopify]() ### AI overview A consultant recounts a troubled backend project involving Shopify, Laravel, PHP, and JavaScript, using the experience to discuss how developers can recognize and resolve problems with difficult clients. ### Source excerpt I have now been doing consulting professionally since 1988 (first client was the EPA) and despite that, bad clients, are always problematic. That's longer than my adult child has been alive, longer than I've ever been married, etc. I'd like to think I'm excellent at consulting but no one, no matter how experienced, can fail to make mistakes. This is a tale of when a consulting project goes wrong and how to extricate one's self. Today I finished up a project with a bad client and I wanted to write up my solution as a help for other developers in similar situations. I'm not writing this up as a humble brag or an "I'm so smart" but rather as a way to point out that: Anyone, no matter how smart, can get caught up by bad clients Sometimes you have to do the utterly unexpected to resolve things And, sometimes, you have to double down in order to resolve things The TLDR On the Situation Here is the situation: In May of 2021, a friend contacted me for a backend project using Shopify, Laravel, PHP and JavaScript. I'm a rails and Ruby guy by choice but Laravel is so clearly Rails derived that I took it on. And I did know PHP albeit from 2006. There wasn't a ton of money with this job but I like my friend and they viewed this job as a way to secure their existing web site development arrangement with this customer. I didn't know Laravel at all but I figured that even if I didn't make much from the job at least I would learn Laravel. Shopify is the only publicly traded Ruby company I know of and I have intense admiration for them so getting any experience with Shopify I felt was positive (disclaimer - I was so impressed with Shopify that I recently became a stock holder). We were going to be a consulting company to Company B which, in turn, was a vendor of primary company A's product. Our original contact at Company B was a man called D who, during the course of all this, sold the company to a man called M. The code we were contracted to write was an ecommerce "configurator" fo ## GSoC 2019 - File Search (Final Report) DevFeed: [GSoC 2019 - File Search (Final Report)]() Original publisher: [Read original article]() Published: 2019-08-26T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [like](), [ReactOS](), [file](), [Windows](), [GUI](), [Regular expression]() Tags: [file](), [free](), [gsoc](), [keyboard](), [open-source](), [os](), [react](), [reactos](), [regular-expressions](), [report](), [text](), [win32](), [winapi](), [windows]() ### AI overview The article reports completed work on ReactOS's file search project, including a Start menu or keyboard shortcut launch, case-insensitive recursive searching, UTF-16 text-file support, and wildcard file-name filtering. It also notes possible future support for case-sensitive search and regular expressions. ### Source excerpt This is a summary of all the work that has been completed this summer on the file search project. All contributed code can be found in this GitHub pull request. Summary Here is a list of the main features: Quickly open it from the Start menu or with the keyboard shortcut Windows + F Search is case-insensitive and recurses all sub-folders Support for UTF-16 encoded text files File name filtering with support for wildcards " ## Live development with Light Table for JavaScript, Python, and Clojure DevFeed: [Live development with Light Table for JavaScript, Python, and Clojure]() Original publisher: [Read original article]() Published: 2013-07-10T00:00:00Z Content type: article Language: en Sources: [Adam Bard]() Topics: [Development](), [Clojure](), [Programming](), [coding](), [JavaScript](), [like](), [Python](), [Lisp](), [Emacs](), [Erlang](), [API]() Tags: [clojure](), [coding](), [development](), [javascript](), [languages](), [python]() ### AI overview The article explains live development as sending code from an editor or tool to a REPL for evaluation. It discusses exploratory programming and reviews Light Table's support for JavaScript, Python, and Clojure, including its inline evaluation workflow. ### Source excerpt Live development is nothing new; it's been well-explored in Lisps and in other languages like Smalltalk and Erlang since more or less the dawn of man. Emacs was for a long time - and by many still is - considered the only way to develop for Lisp, thanks to SLIME. But I with projects such as Light Table, and a growing popularity of functional and dynamic languages in general, I think we'll see live coding become seriously popular as capable mainstream tools collide with capable mainstream languages. ## Introducing Extensions DevFeed: [Introducing Extensions]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-10-21T11:45:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [Extension](), [like](), [backups](), [Code]() Tags: [backups](), [code](), [extensions](), [postgresql]() ### AI overview An introduction to PostgreSQL extensions, describing how they can add custom code, behavior, data types, operators, functions, and index support. The article explains extensions as separately managed scripts, with metadata and dependencies that allow extension-related objects to be excluded from database dumps and reinstalled from the filesystem. ### Source excerpt After reading Simon's blog post, I can't help but try to give some details about what it is exactly that I'm working on. As he said, there are several aspects to extensions in PostgreSQL, it all begins here: Chapter 35. Extending SQL. It's possible, and mostly simple enough, to add your own code or behavior to PostgreSQL, so that it will use your code and your semantics while solving user queries. That's highly useful and it's easy to understand how so when you look at some projects like PostGIS, ip4r (index searches of ip in a range, not limited to CIDR notation), or our own Key Value Store, hstore.