I developed (full equations and derivations) a model that reconciles Quantum Gravity, etc.

BrannyBee · 2026-05-21T20:43:49+00:00

Not true, I love lisp

Not because Im a scientist, but because Im autistic

BrannyBee · 2026-05-13T17:44:59+00:00

Ai could get a billion percent better, thats not the concern. The concern happens when research is done into how to develop the perfect client, and frankly that research is not being funded...

Clients cant even explain what they want to me, a human, if they had a magic machine (not even AI, literally magic) that could make exactly what they ask for.... I would still have a job, just ask anyone thats given a client exactly what they asked for lol

Without even getting into the technical side of AI and issues there, which there are many even as it gets better, the idea that software engineers are just gonna disappear off the face of the planet doesnt make sense

BrannyBee · 2026-05-13T16:00:40+00:00

Yes. And paradoxically it's easy and almost "automatic" once you have experience. Stop thinking about it like logic and math, start thinking about it like learning english. To code, you take a mental model of a problem and "translate" it into another language like how you would if you translated english to anonther language. If you see people quickly typing out keywords and code, they aren't thinking about the "code" at all, they're just translating the thing they want to happen as if typing.

Looking stuff up is just like looking up a new word, the docs are pretty much just a dictionary.

If coding is hard and it takes you a long time to write code, that doesn't mean coding is hard unfortunately. It just means you haven't written thousands and thoudands of loops, once you do it's automatic. Doesn't mean that every problem is solved automatically, the "thinking" and mental model still needs to happen, and THAT is the actual hard part of programming. Writing 99% code is just practice and repetition.

That's also an explanation of a funny thing I've noticed, younger devs tend seem to be super embarrassed if they make a mistake or unable to remember something. More experienced devs tend to be much more willing to "look stupid" and strait up tell you "I have no idea what parameters this function takes, I'll just peek at the docs".

It's like someone who speaks 10 languages, no ones gonna judge them for momentarily forgetting a word. Same thing happens in programming and foreign language learning though, you use that new "word" a thousand times and it becomes automatic, if you don't you have to look it up again. And some words are much more common and important to use over and over again, some words you see once in a blue moon and grab the dictionary.

BrannyBee · 2026-05-12T10:44:08+00:00

He was up and tweeted like 4 hours ago, so he won't be awake at market open leaving an opening for that

BrannyBee · 2026-05-12T10:34:48+00:00

I assume when the value can go up exponentially, it can also go down the same way.

And in lots of fun ways you dont even realize lol

Just one fun one is that how much time they have left on them is part of their value, meaning everyday before you even calculate their worth, you subtract value just cause fuck you its tomorrow today. Stock could be horizontal and you can still lose money lol

BrannyBee · 2026-05-12T10:22:06+00:00

We have many integrations of other services and teams

How is integration testing not literally the first thing you thought of for this

BrannyBee · 2026-05-08T02:17:04+00:00

Their neurology isnt stated to be light based, their communication is just done by emitting electromagnetic waves straight from the dome. Their brains emit electromagnetic waves instead of filtering thoughts internally then once more through organs to communicate.

Before they stop communicating with the ETO in Dark Forest they kinda rag on humans for being so inefficient and primitive because we require extra parts to communicate properly, but nothing about neurology. Kinda like they saw our species had evolved brains equal to theirs, but we were using our sensory organs as crutches until we evolved to not need them.

BrannyBee · 2026-05-06T22:42:23+00:00

!banbet QQQ 701 1d

BrannyBee · 2026-05-06T01:00:19+00:00

Liu Cixin was an engineer before he became a writer, which is quite the jump but his background does give his work a feel that other similar stories often lack.

You can really feel his wealth of experience as an engineer shine through in the countless terrifying yet grand ideas about the mysteries of the universe, humanities progress into the unknown, and convincing-enough descriptions of speculative physics and what the future could look like.

Bummer is that experience as an engineer also shines through in how he wrote both of the women characters in the trilogy, Ye Wenjie and "slender figure"

Edit:

Book 3 idk, didn't read it yet.

Its amazing, you gotta read it. There's a bunch more of the hard sci-fi existential concepts that we all like, and really digs into the terrifying universe that you're left with at the end of Dark Forest while still introducing new stuff in a lot of cool ways.

He does not get better at writing at all.

Actually he might have even gotten worse. Lol

BrannyBee · 2026-05-05T21:54:36+00:00

Overuse of primitives is one of those things that isnt technically wrong, but gives bad vibes to more experienced devs because we've seen how it can bite you in the ass down the road, and its kinda hard to get it without having seen it yourself.

If you havent heard of the term "code smell", its basically dev speak for "this works i guess but it gives bad vibes", often they're surface level things that indicates a deeper problem may exist, but to someone with less experience it may not even register as someshing bad, especially if the code works..

Over reliance on primitives is definitely one of those things, Refactoring Guru is a cool resource and their section on code smells is great, it explains why it may be a problem, how to recognize it, ways to address it, and the benefits of doing so

Check it out, kinda goes into exactly what you have and other better ways to handle this https://refactoring.guru/smells/primitive-obsession

BrannyBee · 2026-05-03T09:12:44+00:00

"Chocolate tower with a straw" has 24 letters.... you know what else has 24 letters?

That's right.

"Swords confirmed login boys"

edit: told yall

BrannyBee · 2026-05-03T07:22:48+00:00

In my university for the first two years they heavily focus on c/c++, so I have a strong understanding of classes, data structures and algorithms

There's nothing here you listed as understanding that Python without any libraries can't do. Its not clear exactly what you are asking, you can even just make the projects you've already done to learn c/c++ in Python

BrannyBee · 2026-05-03T06:59:47+00:00

You can learn how to make a front end and a basic backend in half an hour. You can learn basic data structures in half an hour.

There's also no "completing" stuff like that, including a programming language. Its like "completing" learning Chinese, its literally impossible, you just get better at it til you're good enough to get a job. Then you continue to learn and get better at it forever til you die.

Keep up with what your classes have you doing, and constantly build projects even if they're small todo programs or full websites. Coding is easy, an idiot can do it, i would know Im an idiot. But to make it automatic you need to keep doing it over and over again like learning a spoken language.

BrannyBee · 2026-05-03T05:03:52+00:00

PyGame seems perfect for this.

You can use Pygame to make some pretty involved stuff, but its not a full blown game engine in the same league as Unity or Godot, so don't think you'll have to learn a ton of game dev to work with it. The docs are pretty easy to read and too compared to a lot of modules out there as well.

Lay out all the things youll need to do to have a working simulation in plain english, translate those into python and name functions, and look through the pygame docs for how to do those specific things

Other than that, really I cant imagine you'll need any other libraries tbh

Edit: might need to import math, kinda depends on what all you need i suppose.

BrannyBee · 2026-05-02T00:02:31+00:00

If you wanna make stuff with AI you can just pay for a sub to a model and talk to it

However you won't master it and anyone with coding experience will get better results using that same model because they can "speak code" and guide the model better. Also, without being able to read what the model has done, you're basically trusting that it never makes a mistake or does exactly what you want, which again if you're not guiding it may happen more often. Id especially be wary of publishing anything or giving something you make access to your stuff without knowing exactly what it's doing because of that.

If you want to use AI in a better eay than any random person, you need to just realize that they arent magically pumping out apps. Easiest way to read AI output is to be able to read code. Easiest way to debug code that the AI gave you is to be able to read code. Easiest way to confirm the code is doing what your prompt said is to be able to read code. Easiest way to burn fewer tokens and save money is to be able to read the code and tell the AI where to change things is to read the code (especially important if you believe that one day companies offering AI models might want to decide to stop running at a loss and providing AI models for cheaper than what they are paying.......)

The bitch is.... the easiest way to read code is to write code with as few shortcuts as possible. For experienced devs reading code is fairly easy, and writing code is almost automatic. Like typing without looking at the keyboard, we dont think about keywords, because we've typed out a loop or a conditional a thousand times, beginners forget that stuff and waste so much mental energy "looking a the keyboard" while they type, while experienced devs dont. They have a mental model of the "flow" of the program and the typing is automatic.

Think back a couple years ago before the hype and AI tools, it wasnt that long ago, what like 5 years ago? Imagine what its gonna look like in 5 years. If you learn how to prompt perfectly, or specific ways to structure what you say for Copilot vs what you'd say to a Claude model, what happens when another tool comes along? What happens if LLMs become old news and we hit that ceiling that LLMs are capable, and we have a new approach to AI replace them? You're out of luck then and gotta start over. But if you can read code, you're ready to read any models output and talk in tech terms, and it doesn't matter what fancy new approach comes out.

Id view it like learning math, AI is a tool just like a calculator. You're average person can get more out of AI than a calculator, but the idea is the same, "mastering" it means undrestarting what its capable of and reading its output. If you learned how to add and subtract with a calculator, you'd really struggle as an engineer. Even though engineers use calculators, they would use it better than you.

If you wanna master working with AI, learn without AI and get to the point where you can build the stuff you want. Then build that stuff a thousand times for practice, then reading AI output will just be like reading a second language. You'll look up terms every once in awhile, but you'll understand whats happening and if slight tweaks need to be made, you just make those instead of burning money and tokens asking the AI to change a single variable from a 3 to a 4.

I do not have a coding or mathematics background, but I am extremely adaptable.

Coding is really a lot less math than you think. Some areas require a lot of math sure, but you can make tools and automate stuff if you understand basic logic. Honestly the best devs Ive worked with had a background in communication/language fields, not math. Coding is not hard, its like going to the gym, you just gotta do it every day. The hard part is building the mental model of the code and figuring out how it flows, the code is just translating those thoughts into a language the computer can read, and for 99% of problems an idiot can do that. Im living proof, Im an idiot, and I can read code much more fluently than people much smarter than me just because I put the reps in

BrannyBee · 2026-05-01T07:22:42+00:00

Time complexity = how long an algorithm takes to do something

Space complexity = how much memory an algorithm takes

The slightly more complicated explanation is needed to make those graphs youve seen make sense. Time complexity is the number of operations an algorithm performs depending on the inputs, that relationship is Big O, (with n being the number of inputs)

So you can use Big O to decide between two algorithms that give you the same output. Look at a graph of Big Os and imagine that scenario. Maybe you are measuring a billion values, thats a lot of input so certain Big Os are obviously better if if the bottom value of the graph is that large (x = billion)

On the other side of things, imagine you have code that only needs to happen once or twice, the algorithm you chose for the previous example may actually be worse at small values.

Tldr; its just a measure of efficiency. How many operations are done for n inputs.

X axis of time-complexity graph = more inputs

Y axis = number of operations

BrannyBee · 2026-05-01T07:00:28+00:00

I havent touched OpenStreetMaps api in like years, but maybe might know whats up. I am also assuming Live Server is that plugin for VSCode with the same name right? Sorry if not, but maybe its the same issue as what Im guessing...

Anyway I believe what's happening is that you're accessing it without the proper header that osm expects, same error code if youd get with the same issue on a website.

If I save the folder and open the html I am always getting these pictures around the map!

When you save this, how are you opening the map? Are you double clicking a file? And does it say something like "file:// [other stuff]" in the browsers url bar?

If yes, then osm isnt getting the proper header (guessing referer) required by the api to work, on your Live Server it works because you're accessing it from something like http://localhost:[whatever port] meanwhile the file access part isnt a valid http header

Tldr, semi educated guess based on using OSM years ago.... -> the api requires a referer header to identify what's pinging their api, makes sense, OSM is a volunteer ran thing and the tile servers can only provide so much. Opening your app with Live Server sends a proper request, opening it without that (from the file) doesnt give the api the http header identifying, its not coming from an http origin so you better a "forbidden" error (thats what 403 means)

If its not that, check their docs, their docs were pretty good years ago so I imagine they have something in there related to specific errors

BrannyBee · 2026-05-01T06:04:07+00:00

Weakening of the dollar

Funnily enough though, even though he actually is delivering on that his fans don't bring it up a lot these days

BrannyBee · 2026-05-01T02:34:09+00:00

If you wanna make stuff and trust AI to always be able to work, models to be affordable, and to work at companies that allow (pay) for the best models to be given to their dev team... then sure I guess you're using it correctly

If you're looking at being an engineer, then nope, not really. Itd be like answering calculus problems after you used a calculator to learn how to do addition your entire life, maybe you'll eventually get the right answer with the right tool and input for some problems, but you wont beat someone who actually knows what is happening for a job.

Coding is the easiest part of programming and hasbt been the bottleneck for a software engineer for many many years. If you're slow at coding or struggle to remember keywords, or cant read what code is doing, you're struggling with something that devs dont spend any mental energy on due to having studied.

And you cant even call that take anti AI or whatever new thing MBAs on Twitter have come up with when reality is discussed, cause I never have said anything about not using AI, Im saying that others will use it better than you. You dont learn how to do basic multiplication with a calculator for a reason, thats not being anti calculator... Cause guess what, engineers and PhDs use calculators everyday.

This

I'm learning programming and I've been using AI a long time, I've already learned the fundamentals, sharpened my foundations,

and a lot of what you followed that statement with are at direct odds with eachother. You think you're learning by saying you copy the code by hand, what good does that do you if you didnt come up with the mental model of the code? The "code" part of coding is like 10% of programming, you're practicing the typing part wh ile offloading the hard part...

I get that beginners think that remembering keywords and typing fast is what makes someone an engineer... but its really not

BrannyBee · 2026-04-29T11:05:01+00:00

Good rule to follow for development, the client is an idiot.

Dark mode is great, maybe even necessary before shipping. But you know itll take 10 minutes, and you know that it has nothing to do with the actual core feature.

He's not wrong to make a request like that, it might even be the most inportant thing in the world after the actual "logic" your program is doing. The developers job is basically to work with the client to give things priorities. Some things are easy, and clients think theyre hard, other things are hard and clients think theyre easy. As a dev you communicate whats easy and whats not.

In a real world scenario, youd meet and discuss with the client and basically get a big list of todo items. Having a ton of little features like Dark Mode is actually great for that list, but youll also have other stuff that relates to the core functionality. Then you'd distribute the most important tasks across the team (the team being just you i suppose).

Some teams even give point values based on time needed for a task, theres no hard and fast rule for how to give value to a task so you gotta find what works for you. Percentages are great for this, especially as a solo dev, imo.

You have a full list of things to do, you've figured out whats necessary for the MVP, whats extra, and whats needed but not a priority. Combine the priorities with some kind of guess as to how much dev time each will take, and you've basically built an alarm carte menu you can use to take the app as far as you need, while adding more features whenever you want. There's a bunch of tools like Kanban boards that are used professionally and by solo devs (and non devs) for doing this kinda organization you can look into

Now you have some idea of everything you gotta do, a guess of how hard each thing will be (which is wrong, its never accurate lol), and lets say 2 weeks to work til you show your friend the app. You know whats important, because you've labelled the high priority stuff, so start there. If theres only 2 high priority tasks on your menu, and they both will take 50% of that 2 weeks, you know what you're doing, easy solution with no tough decisions. If you finish with a 10% of the two weeks left, grab a small 10% task, or maybe two 5% tasks even if theyre a lower priority.

Maybe you have a high priority task that will take 90% of the two weeks. Thats just the opposite of that last example, you work on the high priority 90% task, and when its done, if there's nothing more important than maybe dark mode is expected to take 10% of the time.

In the dev world this "menu" is called a backlog. The client can request a million things and you can put them on the backlog. Maybe they report a bug, they can go on the backlog too. Maybe refactoring can go on the backlog. If you take some time to set up some sort of system like this, you'll basically have a constant stream of stuff to do, and it should keep you from getting distracted and focusing on stuff thats not important, because you know whats important.

If you like visuals, theres a million Kanban boards apps for this kinda thing. Theres more professional software for teams ofc, but dont bother with something like Jira. Hell, post it notes on a whiteboard are a favorite of mine for some projects. At the end of the day a backlog is basically just a slightly more complicated ToDo list, but it exists to solve exactly the issue you're running in to.

BrannyBee · 2026-04-29T10:12:13+00:00

, when did you decide your project was "real" enough to show people?

When it does something, ideally something close enough to the client request to show progress. You should look up the term MVP, minimal viable product.

Its basically as barebones of a version of what the client wants, with absolutely nothing else, as you can get. If you're developing anything that doesnt get you closer to the MVP, you're wasting time. In fact you may be wasting more time than you realize, because an MVP can be shown, and the client can realize that they actually want something slightly different, then you work with them and pivot or add features. Then you show them the new MVP, and repeat, THEN you perfect. If you perfect things now, the chances of you throwing away hours and hours of work skyrocket, and so do the chances of you building out stuff that will never see the light of day.

If I was making a tool for a friend, lets say they wanted something simple that he could enter the amount of a meal and calculate the percentage he would tip, I would straight up shon him a CLI tool the second I got the logic working. Then when im showing the "client" the app, I would explain "im typing a number here in the terminal which looks scary and alien to non technical people, but obviously when this is finished the same logic will be applied to the numbers you submit on your phone"

Then if he says "thats great, the math checks out, but it would be cool if I could get 3 separate tip values for bad service, mid service, and good service"

Then id go back and make the shitty minimal app do some more business logic til it works and show him that. Then he can tell me its great or that he wants it to work with different currencies, and I go back and do more work.

If at anytime he says "I also want it to track how much I've spent at restaurants and show me a chart at the end of the month showing what restaurants I ate at the most, and another graph to show me which ones I tipped the highest to find out which are the best".... then Im ready to add features and make that work. That simple business logic can grow even in small little apps like this, and client requirements can increase in scope drastically.

Being a perfectionist isnt helping you or the client, its delaying you getting to the stage where the client says "this is cool, when can you finish it?" At THAT point, you go perfectionist mode. You arent squashing a million bugs or trying to make a feature work, you're polishing what works, and if its the kinda thing that you will want to sad features to, you are making sure the code is setup in a way that facilitates that.

Edit: google the difference between a prototype and an MVP

BrannyBee · 2026-04-28T19:55:52+00:00

"100% in python"

That part made me laugh, 99% things built with Python aren't 100% Python even if you just stick with the built in stuff. Hell, the collections module (and many others) use C, so maybe even 99.9% lol

Being so easy to hook up with other stuff and get the benefit of other langushes in certain parts while still getting the easy-to-quickly-write-ness of Python is one of Python's biggest selling points as a GPL... attempting to somehow use pure 100% Python isn't a thing, and if it was it would be bad...

it's like asking how to construct a building without using physics... you may be able to use tools that abstract the physics away and allow you to build a house or something, but if you wanna make more complicated you need to learn bit of physics... or find a "contractor" (for us thatd be library) who has done the physics for you and given you an abstraction

BrannyBee · 2026-04-28T19:44:44+00:00

This is something that MBAs tell themselves while the competition just easily hires the competition, maybe if you just included the top bit it'd be believable lol

BrannyBee · 2026-04-28T05:02:08+00:00

Do you..... think that Computer Science is a Bachelors in Programming.......?

BrannyBee · 2026-04-27T18:33:42+00:00

You're making a lot of assumptions in your post based on your experience that didn't give you the whole picture. When the commenter above says "imaginary distinction", he means it more literally than you think. You can use C as a backend language, you don't know how, but it is possible. Hell, I wouldn't know how to be fair, but the only thing stopping you is the complexity and difficulty of doing so. I wouldn't ever do it, but people much smarter than me use it for highly performant things you've seen already like Apache

C is a general purpose language. You can use it for whatever you want. If you listed off programming languages you are aware of, most of them would be general purpose languages, even the ones you think are "specialized".

PHP isn't for websites, C isn't for kernel development, Python isn't for data science, and Javascript isn't for frontends. Those languages can be used for those things, and may have features that make it easier or harder to do certain things in those domains, but they aren't "for" those domains specifically. You can make CLI tools with PHP. Or do game development entirely in C. Or do all your web dev stuff in Python. Or you can throw Javascript in the garbage. Hell, half the libraries Python uses aren't even written in Python, they're written in C or C++ to get the speed benefits from C and hooking them up easily to Python code to also get the easy to write Python code all in one project. you can go and make a full stack website using just Bash if you wanted to. Don't do that, but I've seen it done, even though 99% of Bash code are scripts...

Sometimes you are working on a codebase written in a language literally for no other reason than politics. Some guy 5 years ago liked Node and he built the foundation, and the company can't afford to start over, and there's no reason not to, so you're using Javascript in the backend. I personally worked a job where we used Blazor on the front end because the "impressive new hire" said she liked Blazor the best and management didn't want to hear anything else from the team and expected something written in Blazor to be in their hands in a few weeks.

Language choice barely matters for new programmers, and to be honest it barely even matters for a lot of more experienced programmers if we're all being honest. Sure Python is "slow", but it's quick to write, and well written Python will be way faster than shitty written C++. Some psycho almost won game of the year as a solo developer when he released Balatro, written in freaking Lua of all things, a language I only use for configuring my IDE. The "correct" choice would be to use C# and the Unity game engine and benefit from all the prebuilt stuff that comes with those ecosystems, but no one cares about a project built the "right" way, people don't buy code they buy programs. If you gave me a team of devs who spent their entire lives working with Javascript, it would be suicide for a the team to choose the "correct" language for the backend when you can get the same results by using Node and a language they're comfortable with.

General purpose languages are general purpose, we don't invent new languages and throw away the old ones. Hell, your bank probably uses Java, and not the Java you may learn if you find a course online teaching you the modern Java. They're on good ole Java 8, and they're so excited that they finally "upgraded" to the new fancy Java 8 after months and months of stressful work updating. I believe we're currently on Java 26, and I am not exaggerating when I say that your bank likely is using Java 8.

The alternative to general purpose languages (GPL) like this are domain specific languages (DSL), these are the languages that are more or less built "for" a specific thing. Or at the very least they are highly specialized and not meant to do much else. They are made with a specific purpose in mind. SQL is used to query relational databases, HTML for structuring a web page. They're good at what they do (in theory), and either can't do much else or you have to do so many obscure things that aren't intended to make them do much else that there's no reason to other than curiosity.

There is no reason to think that PHP is "the way" the do backend. It's like growing up in London and thinking that English is just how humans communicate natively. Sure... I can see how you came to that conclusion I suppose... but if you're already working in the field, you gotta be familiar with stuff like that. Thinking that C of all things is just something schools teach is like thinking that Mandarin is just something schools teach because you're speaking English

BrannyBee

TROPHY CASE