I have always believed that the MagSafe connector should be on the brick. A short, regular USB type C cable to the power brick and a MagSafe connector between the brick and the wall.
Bonus points if the brick incorporates a small hub with additional ports. This would allow you to choose between using a regular USB type C power cable or the proprietary brick with MagSafe built in.
One of the great features in Chrome is that you can open your recently closed tabs with CTRL+SHIFT+T. This will bring back an entire window full of tabs and even works between reboots. I usually have a dozen tabs open and when I reboot, I simply open up Chrome again, CTRL+SHIFT+T, and I am right back where I was.
To get around this problem I just use a simple command-line utility that I wrote called gitswitch that I call whenever I jump to a new project. My name never changes but my email does, so that's all the utility changes. I suppose it would be neat to build in profiles, but I jump between 2-3 PCs regularly and would probably forget to update my profiles.
Thanks for sharing this. I have been evaluating the red gate suite of tools. Is there a particular module in their deployment suite that helps manage/automate standards as you mentioned?
Our team consists of a single DBA and around a dozen developers. We're a .NET/C# shop but we use Oracle Databases.
On the project we used red gate for we were dealing with a Microsoft shop, so SQL Server. And we used the full suite, including SQL source control which gave hooks for some of our custom scripts to run too, but most of it was doable with the tooling. The software wouldn't catch all policy violations, but what it make it quick for us to fix them when they were found. But in general we were able to automate 98% of the tasks and only deal with true outliers.
I am not sure with Oracle what is available specifically and it has been a number of years since I worked with redgates tooling, but it was quality stuff. And I remember them being super helpful when we were getting started and answering a ton of questions, so maybe reach out to them with your specifics and see what they have to say. Some things they helped us do were not obvious in their documentation or UX, so it is worth a chat with them.
It's more likely that he has a browser extension that is doing this. I have DarkReader installed, and I similarly saw a bunch of style tags at the beginning of the page related to DarkReader (which applies some CSS rules to make everything "dark mode"). To the GP, you probably want to double-check your browser extensions (unless you were actually kidding).
This seems to generate mostly word salad. I haven't been able to find an artist (even one of the recommended artists like Drake) that it generates intelligible lyrics for. It seems to grab existing lyrics from other songs and mash them together, but it's not doing a great job of it.
Interesting. I think this is useful if implemented correctly.
I had an idea similar to this a few years ago. Basically, you would be able to bookmark your place on the page and come back to it later or send the link to someone else. I didn't think that using a word or phrase was useful because it could show up multiple times on the page. Instead, I used the scroll distance. Here's a crude demo:
It's an interesting concept. You need more photos - I need to see how the slats interlock, I need to see photos of how the frame works. My immediate thought was that with a long enough desk (de-sk?) it would bow in the middle. A lot of questions I have don't seem to be answered on the landing page. I think overall, the landing page could be simplified and cleaned up so I don't need to go hunting through the "FAQ" and "Why De-sk?" pages to know if this is the desk for me.
As others have pointed out, I think the biggest weakness is the seams. It looks like it would be impossible to write on. I would suggest that you include some sort of optional desk pad as an add-on.
I'm from the US. Although it doesn't look like you're shipping here yet anyway, you might include inch/pound units too if you plan to ship internationally at some point.
Cool concept, good luck.
EDIT: Here's what I meant by a desk pad, in case it wasn't obvious. This one has a lip so that it stays put, and a metal backing so that you wouldn't feel the slats underneath while you were writing: https://www.ikea.com/us/en/catalog/products/40246156/
>It's an interesting concept. You need more photos - I need to see how the slats interlock, I need to see photos of how the frame works. My immediate thought was that with a long enough desk (de-sk?) it would bow in the middle.
He doesn't explain it but it seems pretty clear to me how it might work. The slats don't interlock. Underneath each slat are wooden tabs (one on each end) that fit snugly inside the frame. Each frame is sized to fit a certain number of slats.
And a long desk won't bow in the middle because the slats run the short end of the frame, not the long end.
The long axis of the desk still has a load bearing member that can flex. Presumably if you get a longer desk frame the member would be adjusted (in size or thickness or whatnot) to not bow.
> As others have pointed out, I think the biggest weakness is the seams. It looks like it would be impossible to write on. I would suggest that you include some sort of optional desk pad as an add-on.
I wonder why didn't did use flush cut tongue and groove? You would loss some of the hot swappablity of it current 10cm plywood strips, but it would be even, & more table overall.
> As others have pointed out, I think the biggest weakness is the seams. It looks like it would be impossible to write on. I would suggest that you include some sort of optional desk pad as an add-on.
Or possibly a large "slat" you can put into the middle.
Seasonic does. They make excellent power supplies. I've used a 400w fanless in a media center PC, but they also make higher wattage units like this for example: https://seasonic.com/prime-titanium-fanless
A higher wattage than 400W is utterly pointless for a fanless PSU; if you need to dissipate constant loads of >400W of heat, you will need a fan somewhere (exotic options like mineral oil cooling aside).
Well you can always add absurd amounts of surface area and mass to the heat sinks to take advantage of thermal inertia, or possibly change components to simply raise your safe operating temperatures to absurd levels. But that's pretty involved. Spacecraft take care of huge temperatures with no fans or even conductive or convective cooling. But that requires enormous, sail-sized surfaces to take advantage of extremely slow radiative cooling.
It would be an exotic option for sure. And not something you'll find pre-built.
Wow. That thing has more surface area than a motorcycle engine. I guess it really needs it with such a relatively low temperature gradient, not to mention the absence of airflow from movement. I'd love to see how that really performs.
I have a Seasonic Platinum X-400 fanless, but I'm quite disappointed because mine suffers from quite loud coil whine noise that is more annoying to me than a fan would have been.
My immediate thought was to store the information in a doubly-linked list type structure in SQL. Obviously the space efficiency is not optimal, but I am surprised that the article didn't even point this out.
The table could be designed with a unique PK, the todo item, and some binary or bool field to determine first (head) and last (tail). You would then add 'previous' and 'next' fields that would be updated for insert/delete/updates.
The problem with that is that it kind of breaks SQL to traverse the list.
Let's say you have a 1M element list, and you want to get the first 100 elements. Normally you would write something like:
> select top(100) * ... order by itemPosition asc
To walk a linked list, you'd either have to:
- walk it on the client, one query per element, resulting in way too many roundtrips to the server.
- get all the data in one go and then walk it on the client. Here we're selecting and returning 1M records and throwing most of those away.
- walk the list in the database with a recursive common table expression. CTE's aren't appropriate for this; it'll be slow, and we'll run up against a recursion limit for large lists.
- walk the list in the database with cursors/loops/etc. Very icky, and breaks composability.
You are right and make many succinct points. I imagined this in the context of the todo list example given in the article, and assumed there would be a sane limit on items in a list, and that each record in the database would be tied to a list ID, or user ID, or some other method to allow only pulling the items that are actually in the list.
That being said, this would not alleviate the problems you mentioned when walking the list. It would need to be arranged once retrieved either by the client, or by the backend before passing to the client. I imagined that I would traverse the list recursively to order it before passing it off to the client. This should take O(n) time, since we only need to traverse the list once, and we haven't retrieved from the database any unrelated rows (list ID, user ID, etc - there has to be some boundary in place).
This is probably decently efficient if you use recursive CTE's to traverse it, and use keyset pagination rather than limit/offset.
with recursive cte (udo_id, prv, nxt, label) as (
select *
from udo
where udo_id = :first_item_id
union all
select u.*
from udo u
join cte
on u.prv = cte.udo_id
) select * from cte limit 100
Your best solution would probably be to use a recursive CTE if your DB supported it, but as a sibling post mentioned, it's probably not a good approach.
Bonus points if the brick incorporates a small hub with additional ports. This would allow you to choose between using a regular USB type C power cable or the proprietary brick with MagSafe built in.