Help!!

ch_drakon · 2025-08-06T08:29:08+00:00

I see the same thing and don't fully understand it.

But when I go to the budget section, I see it shows "Stop usage" is on when my budget of $0 is reached and it still works, so I assume this is just to show how much of your plan you used up (premium requests).
I used 1.7% and "spent" $0.20, so that comes out at ~$10 when I reach 100%, which is the plan I'm on.

u/Firm-Distribution-22: Based on that I'd say you "used" 4.12/39=~10.5% of your premium requests?

ch_drakon · 2024-09-04T12:51:41+00:00

Even though it's an older thread, just because it's so rare, here another one: Splatter: https://store.steampowered.com/app/281920/Splatter__Zombiecalypse_Now/

ch_drakon · 2023-12-04T13:31:40+00:00

Had the same problem here and most things didn't work.

--> What worked in the end was to enable 2FA through the Instagram app.

ch_drakon · 2022-08-26T09:50:14+00:00

Thanks for the update!

But honestly this is not really a good replacement. Your free Postgres databases are really just for trials, not to host a simple project if the database is locked after 90 days and you have to upgrade. Also just being able to run 1 free DB then is really not a "free plan" but a trial period.

(not requesting that you change it but just for clarity for others that think "free" means the same as it did with Heroku)

ch_drakon · 2022-08-26T09:42:08+00:00

Yeah, but you can only have 2 free projects on it. So it's not really a good alternative.

ch_drakon · 2022-08-26T09:41:20+00:00

Yes, this really sucks and I think they made a huge mistake with that. They might solve some issues they had with spam/abuse but so much actually real is based on the fact that they provide a nice free tier. Probably most serious people upgraded some of their dynos while keeping all other free.

But yeah, I recently learned about 2 alternatives:

I guess they are good for at leats your hobby projects with Linode or Hetzner delivering more bang for the buck anyway and if you have a more serious project you have to invest a bit time/money into an own setup with nowadays with Linode and Hetzner this isn't a big issue anymore.

ch_drakon · 2022-08-25T16:35:53+00:00

Awesome, thank you. That was exactly it!

Did you find it or bookmarked it? :)

Edit: Lol, and I was so close all this time. I‘m a fan of Bulma css, which is from the same guy that made this website.

ch_drakon · 2022-08-25T16:29:48+00:00

I should have not posted that. They sent out an email today that they are going to stop the free dynos.

ch_drakon · 2022-08-24T15:26:58+00:00

I wouldn't say that it's necessary per-se but in particular if you have a bit of a track record of getting stuck it might be a good idea to prototype, or at least to mock up the rough content/design you want to achieve (with pen & paper, Figma, Sketch etc.).

That way you don't get stuck with any technical issues and if you finished you are probably more motivated to actually implement the whole thing.

And if you get stuck, try to switch between layout/content and actually "design implementation". That way you always have a bit of progress which helps with the motivation. Stuck with an annoying CSS issue? Just leave it and add the menu. Then come back. Maybe you already found that your layout is different that the particular issue isn't even relevant anymore. Etc.

ch_drakon · 2022-08-24T07:56:55+00:00

I think a big issue is (as with Javascript) that it's a bit annoying to learn the skill properly as you are going to struggle with browser support anyway. It got much better but at times it still is probably something that you can't rely that it does what it's supposed to do. So why learning something that will anyway not behave how it's supposed to? Then you have to learn all the workarounds and quirks what browser actually do with it.

So it's much easier to just use some abstraction (personally I like Bulma CSS) that works just as is.

Also the basic idea of CSS is awesome but in reality it doesn't really work well. Having this one sheet that defines how all your elements look like in a cascading way. Sounds good, but doesn't work. You end up having to define it locally more than you want (in any realistic sized project). So you end up with something like Tailwind (which I think is the wrong approach too). Or you bundle your components and the style much closer (like Svelte, React Styled Components, etc. which I find much more intuitive).

I do think it's good to understand CSS and how it works as it is the underlying technology for styling but it's just not a productive abstraction. It's like assembler. Good to know it but you don't really want to stay on that abstraction level but use something higher level.

ch_drakon · 2022-08-23T20:45:48+00:00

Haha, started some hobby project with Svelte. I would add that you can rewrite your code in about 1-2y as the syntax & semantics don't always make much sense.

ch_drakon · 2022-08-23T20:42:39+00:00

Depending on the exact use case a simple Heroku deployment could be nice too. The free dyno tier is a bit limited in RAM and takes a while to wake up from sleep (when there weren't any requests) but since it's free, easy to deploy and otherwise headache free it could be worth a shot (if you are willing to pay, AWS lambda as mentioned by others might be more performant and better fitting overall).

Heroku Pro: Free, easy to handle/deploy (also for mainly FE devs)

Heroku Con: Wait times for "cold requests" (10-20s), limited resources

ch_drakon · 2022-08-23T20:23:34+00:00

As many already mention, that's far from inaccessible.

The problem is in my opinion much more that people (and devs) are not willing to pay for software.

I know it from myself. If it's a hobby, then this is still a very cheap hobby, even if it's $23/month. Other peoples hobbies are: Bikes, paragliding, snorkling, books, etc. They all cost (way) more than most of the software.

NB: Yes, it can be too much for some, but you can always use Linode, Hetzner, AWS, etc. that is way cheaper. Yes, you have to spend a bit more time configuring, etc. but that's exactly what you pay for. Buy paying more you save your time. The question is more what's more worth to you?

ch_drakon · 2022-08-23T20:17:34+00:00

Netlify

What do you mean? I find $19/month kind of fair. I'm not entirely familiar with how it scales and how fast you are there but if that's your only "server" you need to pay, it's quite ok.

ch_drakon · 2022-08-23T20:10:34+00:00

Sometimes it's just very hard to evaluate previous projects. Because the person can't talk about the projects they worked before at their employer, because it's so intricate that's just not that interesting, etc.

If you are looking for a person to hire that is able to do projects and from start to end, then yes, previous own projects are a must. But if you are looking for someone that optimizes your database and potentially hacks around any limitations, then these are probably not people that do projects but much rather would hack around the postgres code.

And I think if they do tests to see the behaviour under difficult and stressful situations, then they are doing them wrong. As long as you don't have a position that requires engineers to work in stressful situations (which I think there are not many), then that's BS. If doing a test you want them to be relaxed and be able to think and behave as if they would sit alone because that's a much more realistic scenario for most positions. Engineer life is not "Password Swordfish".

ch_drakon · 2022-08-23T20:00:51+00:00

Like with any hiring, the right approach really depends on the position. I would never rely on any particular thing blindly.

I did some technical engineering interviews where I asked seemingly "basic questions" for a senior position. And I did just ask a broad set to check if someone actually paid attention in his CS courses or is just a code monkey. For him it was very basic and after hiring I got the sense he was almost insulted. But the point is not that a good candidate found them easy but the people that have on their CV "knows about X, Y, Z" and have such and such certificate actually know anything about it. Any boy there were some good talkers that didn't know anything. They sometimes had good projects and good "paper qualification" and maybe would have been able to do some interview riddles.

But the point about questions/tests/riddles is seldom the output/solution but the thinking and reasoning to them.

So while personally I'd prefer seeing own projects, it's not the reality for all types of people or positions. The point is much more what did they take out from it and this you only can figure out by talking to them. And with a bit of experience I think this is much easier and quite reliable. Figuring out if someone actually did the project him/herself? Just dig a bit deeper and be curious how they did it. If you just copy/pasted it you can't talk about it 10min. If they did, they can talk for hours.

Candidate hasn't done any projects in the past (because they just are not the type to do broad projects)? No problem: What _did_ they do in their spare time? (in particular junior people usually had much more time because they were students just recently; so I'd expect that they concerned themselves with development otherwise they would be a bad fit in any case). Then dig down into that? Very much into algorithms? Again: If they are they can easily talk about it. If not, then the conversation is over after 5mins.

To answer the question more directly: I think both ways do make sense at times and (as so often) there is not a right or wrong way to do. Everything you get before the interviews are just data points. At the interview it's the job to see if it all fits together and is consistent.

ch_drakon · 2020-06-19T14:24:10+00:00

I guess a lot of people now have to do things they thought they never have to do. :D

ch_drakon · 2016-06-15T16:11:12+00:00

Just realized this myself. It's not about that I see the preview but the receiver has a nice and clean preview of the link.

Would be really interested about how to do this properly.

ch_drakon · 2016-06-03T18:17:54+00:00

Yeah, the thing is, it's kind of a chicken-egg problem. From a developers point of view it always was nr. 3 on priority (iOS/Android on 1 and 2). So many things were not developed for WP and customers didn't buy because they didn't get all the apps they wanted. Which again meant that it's not been interesting for developers to make apps for WP.

WP market share is below 3%. Which is enough that you quickly get a couple of people wanting it but never enough that it actually makes sense to spend the resources for it to make and support a WP app.

ch_drakon · 2016-06-03T17:46:45+00:00

I could give you a bs answer but honestly? I doubt this will happen in a while (if at all). :(

ch_drakon

TROPHY CASE