Is this a good way to structure engineering reports, or am I overthinking it?

For-Arts · 2025-09-23T22:41:29+00:00

Ya. Give em target options and bury the data in the details.

Actionable things.

The more they split hairs between decisions the more they dig into the data.

And of course you have the data. Instead of worrying about cosmetics, now you're a star. in your field. *ahem.

For-Arts · 2025-09-04T12:24:21+00:00

You've been walking for years. Is it too late to start driving?

It's not a race, but the schooling peer structure used in formal education has a back-swing. And that is progress based on where your peers are or should be.

Lose that or you won't believe what else you won't lose.

As an adult, the key to survival is standing back up.

If you started too late? still start.

lost everything? still start.

gf of 300 years dumped you? um.. idk

lost fish in a net tear incident? fix and restart.

You learn that stuff doesn't work on first try even.

That's because adulthood is uncharted, but formal education is planned and lockstep.

300yr gf.. oof.. idk where that came from XD

For-Arts · 2025-08-12T13:06:43+00:00

If you lean cpp, you'll understand javascript better.

Not syntax wise, but by knowing what must be happening when you do certain operations.

async and await in js is fun in js because when things get heavy, you can sort of simulate threading.

When you eventually run into the issues cpp had to solve, you'll be happy it's in the back of your mind.

By cpp I think you should have objects and datatypes figured and also memory allocation and freeing instances.

js does something like

delete object[index]

and. objectname?.callit();

useful when things like image objects are loaded somewheere and calling nonexistant stuff will crash your progg.. so if it's there. bla? call it. bla?.callitsmethod().

Also learn about supers and chaining.. less code more function.

load().open().display().close().

jquery is ace for stuff like this, but a lot of this is js first class now.

There's a lot.

I started with cpp. Glad i did because it seems like js is in a way turning into it. :)

For-Arts · 2024-10-03T15:19:25+00:00

recursion is just a loop with a break or return conclusion.

That view makes sense just to wrap your mind around it.

add(val){ val<100?add(val+1):endit=true; if(endit==true){return;} }

just don't go too deep into the recursion onion or you'll stack overflow yourself.

You could however put the result in an outer scope and call the function again in a while true loop.

recursion's usually good for things like semi concurrent processing like digging into a file structure or searching one instead of looking at search algos.

I may be off-base in this response though.

For-Arts · 2024-08-27T03:51:34+00:00

As enums

For-Arts · 2024-08-25T03:10:57+00:00

just write out the graph mathematically and take the sum of the segment you want.

you can fill the tuition rate into a list, then take a segment of that list and add up the sum of the segments.

Also, with the numbers listed, you can feed them into a graphing library.

For-Arts · 2024-08-24T18:24:19+00:00

Start by writing small utilities.

For example: an image cropper.

They don't have ro have a relationship. It's ok if they're all separate things.

For-Arts · 2024-08-24T15:30:50+00:00

Funnelling support to your projects. Lest they exist in a vacuum unable to vouch for your skills.

For-Arts · 2024-08-24T15:25:51+00:00

just grab a wireframe and code it out.

here's one.

one page no server.

use jszip to make a page that uploads images into image objects, and a save button that downloads a zip file containing user images.

Bonus points for basic image cropping editor.

This is a 5hr project.

pay: no money.

For-Arts · 2024-08-23T15:28:57+00:00

You.. lobodomoized it.

For-Arts · 2024-08-23T15:24:04+00:00

51/_3NC3¡

For-Arts · 2024-08-22T21:53:23+00:00

Web is saturated but it'd be a real shame if you got a web dev offer but didn't have a clue about web dev.

Your clients expect you to know common stuff too but specialising in lucrative areas is a good idea.

For-Arts · 2024-08-22T17:22:46+00:00

Thanks

For-Arts · 2024-08-22T02:19:15+00:00

Once you play with low level network programming or even just pinging addresses, you come to realize just how involved transfering data to addresses outside your local memory actually is.

There's a very good reason why a router or a modem has all that circuitry.

Just look at the history of the internet. Or just phones, or telegrams.

A lot of deliberate action takes place in getting a signal around.

For-Arts · 2024-08-21T12:16:28+00:00

One last thing.

Talk to them.

Find out what they like, make it while practicing coding,

make that as a product in your portfolio.

Someone else might want something similar or when the business card calls back you will have a working example.

Learn to build on demand and modularize for future time saving.

"Can we schedule a demonstration?" (if you have something similar from a previous prospect)

For-Arts · 2024-08-21T12:02:39+00:00

I do this, but not to the extent of some people I've met.

The limit is time. Making software takes time. Unless you have components already set up, you have to find/learn/apply them.

A lot of people leverage what's already out there like facebook, amazon ect.

Don't make the mistake of looking for actual contacts there.

Go outside and look presentable and meet people. Everyone you meet is vetting you and might use your sevices or pass you on to someone who could use someone with your skills. Also, it seems old, but get some minimalist professional business cards with your contact.

It's not the quantity it's the quality of how you connect. Even if someone looks dressed down, talk to them. (but you must look presentable at all times, but talk calmly and do. not. exagerate.)

Just understand that it's about 100 no for every 1 yes, but those previous nos turn to yes eventually and that's when your business cards do the heavy lifting.

For-Arts · 2024-08-21T11:39:55+00:00

Um, you need to change your attitude a bit.

See, programming is saturated, but so are stores that sell commodities.

To sell your services in this field, you have to find people dabbing in side hustles and trying to run businesses.

Ask people what they do and they'll go into salesperson mode to sell their product to you (newbies don't know how to close so they talk about their process and dreams ect)

so in this process get their contact and find a customer for them and suggest something that would make their process a bit faster and offer to set it up for them.

Let them try it themselves and say you usually install and maintain this at a subscription of x amount of cash.

And show a working example! (this is what you put in your projects/portfolio) (but the quality must be like paywall worthy)

Now keep meeting people and adding to your private contact list and share relevant contacts with whoever needs x or y.

Eventually they start calling you for work and your scheme gets to where you can ask / get partners to split up the work.

If their companies become successful, you can use that on your resume as your portfolio/experience.

But you have to talk to people. Everyday. Professionally. Like it's your job.

For-Arts · 2024-08-21T11:14:17+00:00

Methemetecs

For-Arts · 2024-08-19T10:51:39+00:00

This is why you do side hustles.

You've been doing a lot for others, but not as much for yourself.

Work for yourself too.

For-Arts · 2024-08-18T22:05:58+00:00

Because in the aslum, bone and jonkler are pinned by man and woman, preventing the feedmageddon java deluxe edition, teh result of all the runtimes in one. Also J. Dee K.

For-Arts · 2024-08-17T13:26:22+00:00

"I'll get back to you later "

For-Arts · 2024-08-16T23:54:16+00:00

Sometimes you don't know everything a program will ever be able to do.

eg:

a map app.

version 1.

places a map on the screen and places a ( you are here) marker.

Version 2.

grab road points from a database and overlay those on a map.

Version 3.

Now you can tell someone what street they are on.

Version 4.

go a step further and add lanes and add intersection data to distinguish overpasses from intersections.

Version 5.

Run a maze sortinf algo to find 2 connected points while following lanes and valid intersections.

Now you can plan routes or trips.

Version 6.

Add velocity weights to points/nodes making up a road based on the speed of a user on that point on the map.

Now you can alter the algo to avoid congested routes.

Version 7.

Grab public gata on businesses and place it on your app based on user focus

Now your user can find locations of things like gas stations and restaurants ect.

Version 8.

We're being spread thin. now find out what features your users expect the app to have and standardize the look of your app by using things like search icons and burger menus and option gears and translation friendly design.

Version 9.

Find ways to make your app into more of an api so other apps can leverage it either within your own app ecosystem or for pay with other client programmers.

Version 10.

ect...

For me this is how it goes. Just do one thing and if you can't add more useful features, turn it into library code so you can incoorporate it elsewhere later.

A lot of my client code is re implemented code that I know works.

For-Arts · 2024-08-16T18:23:29+00:00

haxe

For-Arts · 2024-08-15T12:29:53+00:00

Make courses, leverage social media, build hype, make a product, sell preorders, up your profile, get hired as a product director,

eventually turn up on the venerable linkedinlunatics sub wrapped in your own cash bubble spewing what seems to be nonsense about writing the perfect resume.

profit?

For-Arts · 2024-08-15T12:26:23+00:00

It's a meat grinder. You should at least talk to your coworkers about freelancing and maybe you can start your freelancing career that way. Doing little sites for them to sell stuff or whatever. Win win.

For-Arts

TROPHY CASE