hamiltont

We're not taking funds from customers yet — we're personally paying for all the provider requests during this phase. Credit purchases are disabled.

This appears on their credit purchase page right now, but you have to email them to get credits (everyone starts with zero)

Not sure I'm fully following your question, but maybe this helps:

IME deep thinking hgas moved from upfront architecture to post-prototype analysis.

Pre-LLM: Think hard → design carefully → write deterministic code → minor debugging

With LLMs: Prototype fast → evaluate failures → think hard about prompts/task decomposition → iterate

When your system logic is probabilistic, you can't fully architect in advance—you need empirical feedback. So I spend most time analyzing failure cases: "this prompt generated X which failed because Y, how do I clarify requirements?" Often I use an LLM to help debug the LLM.

The shift: from "design away problems" to "evaluate into solutions."

Anecdotal tip on LLM-as-judge scoring - Skip the 1-10 scale, use boolean criteria instead, then weight manually e.g.

- Did it cite the 30-day return policy? Y/N - Tone professional and empathetic? Y/N - Offered clear next steps? Y/N

Then: 0.5 * accuracy + 0.3 * tone + 0.2 * next_steps

Why: Reduces volatility of responses while still maintaining creativeness (temperature) needed for good intuition

ok, will do

Hi - I'm working on something like this because I needed it too ;-)

It's not yet ready for release, but I should be ready for beta-test within 2 months. If you're interested I would be happy to add you to my list of "people to notify when I am ready to beta test"

We adopted Amazon's 6-pager strategy for meetings. It has been incredible helpful. TLDR - one person writes a document explaining the proposed feature, max length 6 pages. That one person does 80% of the work (whatever your org wants e.g. timeline, target customers, planned KPIs and/or ROI).

Process: Start the meeting, turn on your camera (surprisingly important for us), and set a timer. Everyone quietly reads for ~20min. AFTER they finish reading, restart and engage via comments - positive/agreement comments are great, questions are useful, answering/responding to other's questions is encouraged. Post 20min, one speaker goes through the comments. Many (70% is common for us) will already have been resolved or will not require discussion. Long comment chains or lack of consensus on a comment chain is where we spend the discussion time. Common pitfall - Speaker DOES NOT present the document, that just wastes 20min and bores everyone to death. Small nuance - speaker (doc preparer) is already familiar with doc, so they watch the timer. They also check in e.g. at 15 give a 5min warning, at 20min check if anyone needs more time, etc.

Huge net positive for us: - No more "pre-read" (no one does it), we just say that a 45min meeting is when you BOTH get the information AND discuss is - Post the "20min" we are already 80% on the same page - Far far fewer "basic" questions that kill time - those were answered by the doc - Quiet reading gives people time to mentally switch/shift from their last 5 meetings and come up to speed. Less "anxious energy" when talking - Increase collaboration - "Type A" talkers cannot (as easily) dominate the comments. Leaves "airshare" for quieter team members to participate via comments. We've begun encouraging all to leave at least 4-5 comments

Negatives: - REQUIRES senior team member support, else 1 senior "ass" will break the rules and start talking - Writing the document is time consuming and not easy. This really becomes one persons "work" to gather the data from all stakeholders in a 1-1 fashion, organize it, summarize it

Yes and No.

No because the official OSM tile layer is heavily subsidized by Fastly (€720k last I checked) and rendering by AWS (€40k)

Yes because technically it would use fewer resources thus easier on AWS+Fastly and also easier to self-host

In last risk assessment I read closely(1) OSM noted "If we lost [Fastly] sponsorship, we would likely cut off all third-party access to the standard tile layer and run a small number of Varnish servers."

As I understand it, primary drivers for vectors was not cost more improving internationalization, generally enabling client-side rendering decisions, and driving a modern toolchain that would net multiple follow-on benefits

I'm a bit behind, there is more recent info available at (2)

1.https://operations.osmfoundation.org/2024/01/25/owg_budget.o... 2. https://osmfoundation.org/wiki/Finances

Anyone else wanting to see the original content of /unicorn? Cats are great and all, but we want unicorns!!

<3 wonderful project. Brings back memories of excitedly writing HTML in my drawing notebook and daydreaming what the pages would look like

...these are small enough to enter the body’s cells and tissues

Same. No training to identify concern vs FUD in health news, but I'm erring on side of caution. We are limiting exposure to plastic drink bottles in general (sport drinks in plastic during/after children sporting events are common where I live)

My ad experience has changed dramatically after I leaned into multiple browser personas. In personal persona, I hate ads with passion and do everything to get rid of them (browser extensions, premium membership, etc). I value my personal time and the ads are totally useless.

In work persona, I suddenly have found ads are actually useful. Often find myself choosing to spend 30 seconds watching a YouTube ad because it is relevant to topics I need to be aware of as a CTO. It's clear my daily browsing history influences the ads I am seeing, and I see useful information. Been looking into SIEM tools lately, and via an ad I was just made aware of some data center appliances for security. I clicked to their website and browsed a while to learn what was available. When you have some real challenges to solve and the targeting is on point, ads can be a great news feed.

Clearly segmenting my browser history into one persona where I am actively looking for solutions vs my personal persona where I want to be left alone helped the feeds target me.

Still, surreal feeling to intentionally choose to watch an ad...

Think I read somewhere that of one of their content production differentiators is their direct-to-consumer approach. Classically lots of content was produced for the "average" consumer. Netflix can use their subscriber data to create low-cost content for extremely niche consumers, who might love that extremely relevant production (think super edgy, super graphic, super cartoon, etc - the type of extremes not covered by the average).

Not sure how much this holds true anymore, as now many big players have direct-to-customer streaming, but just sharing since it was a neat thought when I first read it

Not a stretch at all, it is perfectly reasonable to consider an app and an website embedded by the app as two completely different things. First there is no guarantee the WebView will open to a website owned/operated by the same entity that owns/operates the app, so it is definitely "outside the app". From the user's privacy perspective, you also want to communicate that just because the website might be branded "Facebook" and be run by Facebook and maybe you trust FB with your messages, but if it's an embedded browser opened via a WebView then the app can technically snoop on the private message you are typing into the WebView

This is saying "if an app opens a webview, the app can monitor your browsing activity inside that webview."

It is written vaguely and should be re-written to be precise, but as they are going for "end user" language here I can understand that it is hard to communicate to non-technical users that "embedded browser" and "browser" are different things given that they have similar UX and similar functionality.

A common use case of an embedded webview is an app that uses a website for some portion of a user flow, IME this is typically when there is a B2B2C business relationship. I think it can also happen for an OAuth2 integration but I'd expect there are some iOS native SDKs that are preferred. IME, many businesses use "web SDKs" instead of native libraries, and their integration guide will say something like "have your app open a webview to URL X, then user does Y as we have agreed, then we will close the webview" (occasionally, a few will use hooks in the webview to communicate result information to the native app).

There is some strange allure for spending time crafting Dockerfiles. IMO it's over glorified - for most situations the juice is not worth the squeeze.

As a process for getting stuff done, a standard buildpack will get you a better result than a manual Dockerfile for all but the most extreme end of advanced users. Even for those users, they are typically advanced in a single domain (e.g. image layering, but not security). While buildpacks are not available for all use cases, when available I can't see a reason to use a manual Dockerfile for prod packaging

For our team of 20+ people, we actively discourage Dockerfiles for production usage. There are just too many things to be an expert on; packers get us a pretty decent (not perfect) result. Once we add the packer to the build toolchain it becomes a single command to get an image that has most security considerations factored in, layer and cache optimization done far better than a human, etc. No need for 20+ people to be trained to be a packaging expert, no need to hire additional build engineers that become a global bottleneck, etc. I also love that our ops team could, if they needed, write their own buildpack to participate in the packaging process and we could slot it in without a huge amount of pain

Sure. Our solution so far has been both simple and pragmatic - the main DB's do not live inside containers. It's a bit of manual ops, but it works for us. All the 'media' in the stacks I am dealing with is minor enough to serve over a custom API e.g. no massive image/audio/etc datasets where files need to be first class citizens.

We generally avoid mounting volumes at all costs. The challenge of mapping host uid:gid to container uid:gid (and keeping that mapping from breaking) proved painful and not worth the effort

Wanted to second that Docker Swarm has been an excellent "middle step" for two different teams I've worked on. IMO too many people disregard it right away, not realizing that it is a significant effort for the average dev to learn containerization+k8s at the same time, and it's impossible to do that on a large dev team without drastically slowing your dev cycles for a period.

When migrating from a non-containerized deployment process to a containerized one, there are a lot of new skills the employees have to learn. We've had 40+ employees, all who are basically full of work, and the mandate comes down to containerize, and all of these old school RPM/DEB folks suddenly need to start doing docker. No big deal, right? Except...half the stuff does not dockerize easily requires some slightly-more-than-beginner docker skills. People will struggle and be frustrated. Folks start with running one container manually, and quickly outgrow that to use compose. They almost always eventually use compose to run stuff in prod at some point, which works but eventually that one server is full. This the is the value of swarm - letting people expand to multi-server and get a taste of orchestration, without needing them to install new tools or learn new languages. Swarm adds just one or two small new concepts (stack and service) on top of everything they have already learned. It's a god send to tell a team they can just run swarm init, use their existing yaml files, and add a worker to the cluster. Most folks start to learn about placement constraints, deployment strategies, dynamic infrastructure like reverse proxy or service mesh, etc. After a bit of comfort and growth, a switch to k8s is manageable and the team is excited about learning it instead of overwhelmed. A lot (?all?) of the concepts in swarm are readily present in k8s, so the transition is much simpler

WOuld not be surprised - he's reported piracy issues in past. FYI I've ordered all books by emailing directly to an email on the website. He replies with "send paypal to xx if you want digital only, send xxx if you want me to mail you a hardcopy". clunky relative to an amazon order but it gets the job done

Passion comment: I'll second that most of Jonathan Levin’s books are outstanding, some of my favorite technical guides.

Spent many years as senior dev for a custom Android ROM, yet Levin's book still introduced me to multiple other Android internals I had not yet looked into. Would happily pay 200-300 for his next Android book. Probably not the best books for a total beginner, but if you're already skilled and looking for the next level I would highly recommend.

My only real complaint is that JL seems to do a lot of the marketing/date-setting himself, and it shows. It can be really confusing to keep current on what book he is working on next, what topics will/will not be covered, how to even pay for the book can be a bit complicated (send paypal to this email), etc. It is fantastic that he adjusts and expands book contents as the market/technology changes (e.g. always chasing to get the newest stuff covered in the newest book), but the current end result is a stream of "update" messages on his website that are hard to follow. Would be wonderful if he had someone help him with that "public-facing" side and try to keep things organized/consistent/obvious and hide a bit of "how the sausage is made"

For their objectives, that was undoubtedly a good return on investment. Even ignoring the ROI, the absolute cost seems quite reasonable given the feature set and target market. Someone picked a good CHS or did a good job with avoiding scope creep.

While I applaud them for their understanding and use of technology, it is a strange feeling to see the FBI start to think like the NSA. Given the positive PR of this approach+result other teams will most assuredly try to replicate it

Not who you replied to, but I believe the current popular answer is to refer to Japan. Numerous articles have been written regarding how they managed their housing crisis by deregulating zoning and building permits. You'll have to read up on it yourself, it's beyond me to summarize as it's a complex topic and the model is not perfectly exportable. Partially for "real" reasons, such as Japan has so many earthquakes that many houses are not intended to last for 100+ years which affects the home economy. Partially for social reasons, e.g. wealthier nations view homes as investments (more-so than as a place to live, like we view an apartment), and people push tons of local/state/federal rules to ensure their investment always grows in value. The easiest way to make the value grow is to ensure there are no more homes e.g. NIMBY

One article to get you started (nothing special about this one, it's just the first I saw from google): https://www.wsj.com/articles/what-housing-crisis-in-japan-ho...

Very in favor of modernizing the definition, very not in favor of subsidizing any network buildout -- if a provider is not offering broadband under the new definition that is not (in my eyes) a problem the government needs to step in to fix, it's simply being honest about our nation's network infra capabilities.

Sure, we can incentivize providers for reaching certain percentage rollouts under the new definition, but history shows us we should not consider schemes to help finance those buildouts.

Internet is not currently a utility, so unless we make it a proper utility with proper regulation before handing over money, the federal government is historically not capable of resisting lobbying pressure aimed at remove the teeth from similar subsidized buildout agreements. In almost all cases the money has disappeared without significant real world improvements.

For example, using the money intended for buildout to instead pay lobbyers to re-change the definition of broadband, thereby actualizing some stated goal of "75% of service area covered by broadband", and then pocketing the difference between the actual buildout costs and the lobbying costs.

If we offer a financing without regulation, we may as well move the money straight into the exec bonus category and totally ignore improving infra

Regardless of your opinion on whether it's acceptable, given what is happening in Belarus, that the protestors are working to identify riot police as a way to "fight back"....it's quite interesting (to me at least) that Apple is trying to direct the actions of an app developer after users have already installed that application. Is Apple now the arbitrator of "what computations are allowable on the device you purchased"?

thanks for the pointer

Ha ha I totally feel that. Especially for a high-ticket item, give me a human to talk to!!

I can't stand it when support is crippled by "policy" - half the time I think they can't either.

For what it's worth, I have an almost identical experience. Build quality is not good, and every service-center visit leaves you feeling like they are stuffing the service centers with way more issues than the people there can handle. Even with all this, the drive feel of my MS is insane and the screen/app are lightyears ahead. I honestly enjoy driving again, even pre-pandemic with crazy traffic. Their offering is so good it outweighs the crappy support. If some other car company would step up to the plate and try to complete with similar tech but offering higher reliability, I would go for a test drive immediately.

Side-note: service at Tesla used to be golden. When they first started, they all knew they were pricy cars and everyone expected some growing pains leading to QC issues. It was great - they would loan you a top-model performance tesla while your car was in the shop (great up-sell!!!), they were doing far more of their "mobile service" (super handy, they drive to you and fix the car where you are), and you would get one agent that called you almost daily with an update.

As they have expanded more towards mass market they have gone the way of google - trying to automate humans out of the loop. It's basically a miracle to talk to a human at a service center now, everything is "schedule it in-app where you get 200 characters to explain your issue, we send over an estimate, you can't call to discuss it either approve or don't, drop your car, use our SMS platform for 100% of communications because email might "violate your privacy" (read: leave a data trail), handle the fact that different agents get your SMS at different times and some have no idea what the history is, handle that agents now "have to reply to all messages before they leave" and you're getting hurried "here's my panicked update" messages at 11:30 at night.

I personally feel they missed an opportunity to offer "luxury service lanes" for folks buying the luxury line when they went mass market.

In case it helps, IME many of the smaller shops are looking for folks like yourself offering no nonsense business relationships predicated on skill and professionalism vs "can you sort a list".

I know I am - I've bookmarked your website. I run a small R&D shop specializing in one-of-a-kind projects that typically have very non-standard toolchains. We are good at what we do, but we are not good at frontend work and often need a frontend dev to help us internally market a successful project -- e.g. we can build the best system ever, but if no one can see or feel it, it's always an uphill conversation to explain the value add to someone in the client organization.

It is :-) From the Readme:

This is a fork of the excellent gideonred/dockerdoomd using a slightly modified Doom, forked from https://github.com/gideonred/dockerdoom, which was forked from psdoom.

Here you go: http://psdoom.sourceforge.net/screenshots.html

Thanks for your work!

Thanks. Mind sharing where you are browsing from and what you get when you try to hit the link (DNS failure, site not responding, etc)? I can forward an issue report on to the maintainers

I'm currently helping with translations for https://www.voiceofbelarus.com/

The things being done to these people in detention are horrible. We just translated an article about a 16-year-old boy beaten into a coma. When he awoke he said he was one of the lucky ones. ( https://www.voiceofbelarus.com/how-to-save-timur/ )

From consistently talking to multiple opposition members, here is my take on the current mindset:

Every single protester on the street is aware that the police are waiting for them to do anything that gives an excuse. Foreigners don't always understand the dictatorships use a two-pronged approach, one part being heavy-handed violence and the other being heavy-handed propaganda. Like it or not, there's always a percentage of the population that buys into the propaganda, either by being stupid or by being centrist.

The protesters are very intentionally being careful to not give any excuse. That's why you see 70-year-old grandmothers walking in the streets wearing pure white, they want the evidence to be obvious when the police shove down and beat grandmother's bloody. They also want it to be impossible for the state to spin them as violent criminals

In short, these people are brave as f*

Many do suspect this will end in all out violence, but everyone knows that would give Russia an internationally acceptable excuse to join the party. The current thinking is Lukashenko may make a mistake (it is widely reported internally that he is on heavy medication and typically takes an entire month away from office following the election period, which has been impossible with the constant mass protests). His family has begun to leave the country, excluding his young son who he takes with him everywhere.

The people are being careful to say, at least for the time being, they do not want him dead, they only do not want him in the country. They're trying to give him every opportunity to flee and leave them to repair their own country

If you want to help, the biggest thing you can do is continue to give them international recognition. Share it on social platforms. After the first wave of violence, the international outcry caused Lukashenko to order the police to temporarily stop the beatings. The protests have continues to grow, and the violence has started again (as we all know, dictators have a really small playbook of possible control tactics). International outrage is more effective than you might realize.

EDIT: For those unaware, IT has grown significantly in Belarus. It's debated why this is the case (e.g. perhaps the dictatorship just does not know how to extract value from a company where seizing assets just leaves you with an empty shell of a previously valuable company), but regardless multiple Belarusians are entering the world stage with a reputation for being competent/capable/innovative with technology. It's been a interesting emergence of a new skilled class. Right now, Lukashenko is squishing that with his actions. Shutting of the internet is one example. Another example is retaliation, such as what is being done to PandaDoc (a Silicon Valley-based company). Their founders are Belarusian. After a statement by the founders, the state retaliated by raiding their Minsk offices and arresting employees. For more info, see https://savepandadoc.org/en/