This is AI generated image is it good ?
Yup !! I can say it is perfect
Yup !! I can say it is perfect
❤1
Forwarded from KhilX 6month challenge
Your time is limited, so don’t waste it living someone else’s life.
Don’t be trapped by dogma — which is living with the results of other people’s thinking.Don’t let the noise of others opinions drown out your own inner voice and most important ,have the courage to follow your heart and intution,they somehow already know what you truly want to become.
Every thing else is secondary.
Steve Jobs
Don’t be trapped by dogma — which is living with the results of other people’s thinking.Don’t let the noise of others opinions drown out your own inner voice and most important ,have the courage to follow your heart and intution,they somehow already know what you truly want to become.
Every thing else is secondary.
Steve Jobs
❤1
Forwarded from Edemy
Things Feel Hard Until You Actually Start
In tech, many things sound difficult long before we ever try them.
Before learning Docker, I already believed it would be complicated
not because I had worked with it, but because of how people talked about it.
Just hearing terms like image, container, and DevOps workflows made it feel heavy.
But once I started learning Docker and using it in a project, it was far more understandable than I expected.
Most of the confusion faded once I stopped listening and started doing.
This isn’t only about Docker.
The same thing happens for other terms.
From the outside, things look overwhelming.
Once you’re inside them, they turn into clear steps you can work through.
The real issue is that many juniors never reach that point.
They stop at the idea of difficulty.
We often hear experienced engineers talk in advanced terms,
and we forget that they also started by not understanding much.
Fear usually comes from: not starting, overthinking, and comparing yourself to people who are further along
So the solution is to start even if things are not clear yet.
If you’re a junior:
don’t let technical language scare you
don’t wait until everything feels clear
start small and learn as you go
You don’t need full clarity to begin.
You gain clarity by starting.
Most projects look difficult
until you sit down and actually work on them.
That’s where learning really happens.
@edemy251
In tech, many things sound difficult long before we ever try them.
Before learning Docker, I already believed it would be complicated
not because I had worked with it, but because of how people talked about it.
Just hearing terms like image, container, and DevOps workflows made it feel heavy.
But once I started learning Docker and using it in a project, it was far more understandable than I expected.
Most of the confusion faded once I stopped listening and started doing.
This isn’t only about Docker.
The same thing happens for other terms.
From the outside, things look overwhelming.
Once you’re inside them, they turn into clear steps you can work through.
The real issue is that many juniors never reach that point.
They stop at the idea of difficulty.
We often hear experienced engineers talk in advanced terms,
and we forget that they also started by not understanding much.
Fear usually comes from: not starting, overthinking, and comparing yourself to people who are further along
So the solution is to start even if things are not clear yet.
If you’re a junior:
don’t let technical language scare you
don’t wait until everything feels clear
start small and learn as you go
You don’t need full clarity to begin.
You gain clarity by starting.
Most projects look difficult
until you sit down and actually work on them.
That’s where learning really happens.
@edemy251
Forwarded from Web Development
1 2 3 4 5, and you've got a dynamic gallery implemented in CSS 🤩
The important property in this is auto flow, which is a very cool property!
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
# Definition for a binary tree node.
# class TreeNode:
# def __init__(self, val=0, left=None, right=None):
# self.val = val
# self.left = left
# self.right = right
class Solution:
def isSameTree(self, p: Optional[TreeNode], q: Optional[TreeNode]) -> bool:
if not p and not q:
return True
if not p or not q:
return False
if q.val != p.val:
return False
return self.isSameTree(p.left, q.left) and self.isSameTree(p.right, q.right)
#recursion
I finally finished an exhausting final exam 😮💨 I hope the results will be good.
I will now continue the learning journey and start building staffs.
I will now continue the learning journey and start building staffs.
⚡3